-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guest-specific operations were attempted on a machine that is not ready for guest communication #2251
Comments
It looks like this was happening with vagrant-vbguest installed. Please try without and see if it happens. |
Hi All. I'm also facing similar issue after upgrading to Vagrant 1.3.1. @mitchellh you suggest removing line "config.vbguest.auto_update = true" from Vagrantfile or uninstalling vagrant-vbguest plugin at all. |
I did both and it worked. But I didnt tried yours. Just test it and post the result :) |
Removing the line seems to work for me as well. Thanks everyone. :) |
The error is back. Since my machine didnt started properly the last times because of erros while mounting the shared folders, I installed the vgguest-plugin again. Now the machine didnt start either and I have no idea to fix that error... EDIT: My Machine was complaining about the wrong guest-extension. VBguest wasnt able to install the newest version (different sources-error). Thats why I installed the extenstion manually via ssh. Afterwards one of my machines behaved like no guest-extension installed. Thats why I reinstalled the extension with vbguest again, which worked this time. Now the old error (of this issue) showed up. Thats why I just uninstalled vbguest again and NOW my machines are working as expected. Long way... |
This problem blow my mind on every mistake. Because here a lot of other very serious steps:) |
Oh, I hadn't notice this issue here. This should be fixed in the next vagrant-vbguest release by dotless-de/vagrant-vbguest#80, dotless-de/vagrant-vbguest@c0272f9, and dotless-de/vagrant-vbguest#90. |
@tmatilai, Thanks!) |
FWIW, I just got this error running on host Mavericks, VBox 4.3.2, Vagrant 1.3.5 and the latest vagrant-vbguest. I destroyed the box and then re'uped and it worked fine. |
Running OSX Mountain Lion host:
The problem still occurs:
Should I still be having this problem? I wasn't sure whether @tmatilai was saying that a fix had been deployed yet. |
@duffj The fix is included in a pre-release version:
v0.10.0 should be released soonish, but unfortunately there are still some other unresolved issues. |
Thanks @tmatilai - much appreciated. It's a headless VM so I will disable vagrant-vbguest in it for now and wait for v0.10.0 to be released. |
Hi, I have the same issue, I just tried everything with some vagrant and VBox versions, using and not the 'vagrant-vbguest' plugin without luck, can anybody help me? |
Solved, I just deleted the folder: ~/.vagrant.d after 6 hours of try everything. After that, do 'vagrant up' will be enough. |
The @kgatjens solution also works for me! |
I still have the problem, and deleting ~/.vagrant.d did not fix it for me. Here is how to reproduce the problem on Ubuntu 16.04 LTS, assuming the relevant stuff (docker, vagrant, npm, etc.) is already installed on your computer:
The above will try to create a skeleton web site for you. It will ask you a couple of questions, then, among other things, will try to use Vagrant. At that point, you will get the "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." error message. You can try to delete ~/.vagrant.d and restart from scratch (including removing the contents of the directory to which you imported stuff with the yo command), and you will still get the same error message. It would be great if you could get this fixed by the end of 2016. |
Hello guys, to solve the problem just do search in the files for .vagrant, .vagrant.d and make sure that you have one of them just ! |
@kgatjens your solution also worked for me on ubuntu 16.04. thanks buddy |
the same issue appears on vagrant 2.2.2 |
Just faced the same issue on my windows 10 machine.
|
@Laraveldeep did you try to delete |
I experienced this problem today and simply doing a |
If you delete
So you have to go back and start over with vagrant install with the VMware plugin. |
I was giving myself the same problem, I solved it. Verify graphically in your virtualization provider that the first adapter is NAT and enabled. This serves so that the communication by SSH is always functional. |
The @kgatjens solution also works for me |
Deleting just ~/.vagrant.d/tmp solved the error for me. |
|
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. |
After vagrant alerts "Machine booted and ready!" I get the error
"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."
I posted my debug-log here: http://pastebin.com/wxFxC4m6
The text was updated successfully, but these errors were encountered: