Closed EverybodyKurts closed 8 years ago
Another relevant part of the log:
ERROR warden: Error occurred: Guest-specific operations were attempted on a machine that is not
ready for guest communication. This should not happen and a bug
should be reported.
Any idea what is the solution for this bug? I am also able to reproduce it but without guest additions. Note: My ssh is working in cygwin.
@KurtRMueller can you see if you experience the same behavior with latest vagrant release and one of the bento centos 7 boxes? That error is generally the ssh connection being unexpectedly terminated. Thanks!
Hey there,
I am going to close this due to lack of response. If this is still occurring, please open a new issue and follow the provided issue template that appears when you click the "New Issue" button. This will help us in getting a reproduction and fix. Thanks! 😄
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Vagrant version
Host operating system
Windows 10 cygwin64 terminal
Guest operating system
Vagrantfile
Debug output
https://gist.github.com/KurtRMueller/462fa795520b25e92449
Here's a brief excerpt:
Expected behavior
I should be able to boot up vm and provision it with chef solo.
Actual behavior
I used to be able to spin up a vm and provision it with chef solo. Now however, no dice :(. Running
vagrant up
will cuz the vm boot to time out.vagrant provision
will spit out the errors linked in the gist.Steps to reproduce
Doing any # of things will cause either booting the vm to hang or provisioning to fail.
Thank you for any and all help.
Kurt