This should not happen and a bug should be reported.

[lautreamont3]

I am using, renamed to precise32cloud.box, ubuntu cloud images from
http://cloud-images.ubuntu.com/vagrant/precise/current/precise-server-cloudimg-i386-vagrant-disk1.box
on Ubuntu 13.04.

➜  vm-test  vagrant up                                                                   
Bringing machine 'default' up with 'virtualbox' provider...
[default] Importing base box 'precise32cloud'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
[default] Machine booted and ready!
[default] The guest additions on this VM do not match the installed version of
VirtualBox! In most cases this is fine, but in rare cases it can
cause things such as shared folders to not work properly. If you see
shared folder errors, please update the guest additions within the
virtual machine and reload your VM.

Guest Additions Version: 4.1.12
VirtualBox Version: 4.2
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.

When I put config.vbguest.auto_update = false in Vagrant file vagrant up goes OK but on:

➜  vm-test  vagrant vbguest --auto-reboot                                                
GuestAdditions versions on your host (4.2.18) and guest (4.1.12) do not match.
Reading package lists...
Building dependency tree...
Reading state information...
dkms is already the newest version.
dkms set to manually installed.
linux-headers-3.2.0-54-generic is already the newest version.
linux-headers-3.2.0-54-generic set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Copy iso file /usr/share/virtualbox/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
mount: warning: /mnt seems to be mounted read-only.
Installing Virtualbox Guest Additions 4.2.18 - guest version is 4.1.12
Verifying archive integrity... All good.
Uncompressing VirtualBox 4.2.18 Guest Additions for Linux............
VirtualBox Guest Additions installer
You appear to have a version of the VBoxGuestAdditions software
on your system which was installed from a different source or using a
different type of installer.  If you installed it from a package from your
Linux distribution or if it is a default part of the system then we strongly
recommend that you cancel this installation and remove it properly before
installing this version.  If this is simply an older or a damaged
installation you may safely proceed.

Do you wish to continue anyway? [yes or no]

Cancelling installation.
An error occurred during installation of VirtualBox Guest Additions 4.2.18. Some functionality may not work as intended.

[tmatilai]

The first error sounds like a timing problem that should be fixed by #80.

[lautreamont3]

I try manual installation, which is same as second text, and everything goes without errors. On reload warning message sometime pop out and sometime not. But vagrant vbguest --status always gives 4.2.18.

[cdmoye]

This, at least the second part, appears similar to the issue I just reported.

[fnordfish]

Looks very much like a duplicate of [GH-85], [GH-80], [GH-64], [GH-43]

Please check #85 (comment) and try if things work "out of the box"

[cdmoye]

Indeed it does work with 0.10. Thanks.

[lautreamont3]

My try (shorten):

$ vagrant box add p32up ~/Downloads/precise-server-cloudimg-i386-vagrant-17102013.box
$ vagrant plugin install pkg/vagrant-vbguest-0.10.0.pre0.gem
$ vagrant up

Everything is ok till the end:

[default] Attempting graceful shutdown of VM...
[default] Booting VM...
[default] The guest additions on this VM do not match the installed version of
VirtualBox! In most cases this is fine, but in rare cases it can
cause things such as shared folders to not work properly. If you see
shared folder errors, please update the guest additions within the
virtual machine and reload your VM.

Guest Additions Version: 4.1.12
VirtualBox Version: 4.2
[default] Mounting shared folders...
[default] -- /vagrant
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.

But after:

$ vagrant halt
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Clearing any previously set forwarded ports...
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
[default] Machine booted and ready!
GuestAdditions 4.2.18 running --- OK.
[default] Mounting shared folders...
[default] -- /vagrant

everything is OK.

With config.vbguest.auto_update = false and after:

vagrant vbguest --auto-reboot

there is no errors.

[tmatilai]

@lautreamont3 Which Vagrant version? If you can repro the error you could gist the output of:

VAGRANT_LOG=debug vagrant up

[cdmoye]

vagrant 1.3.5

I will try the gist.

On Thu, Oct 24, 2013 at 8:52 AM, Teemu Matilainen
notifications@github.comwrote:

@lautreamont3 https://github.com/lautreamont3 Which Vagrant version? If
you can repro the error you could gist http://gist.github.com/ the
output of:

VAGRANT_LOG=debug vagrant up

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/81#issuecomment-26989243
.

[lautreamont3]

vagrant-1.3.5
gist

[tmatilai]

@lautreamont3, a lot of the output from the beginning is unfortunately missing. You can capture it all to a file (while still seeing what's happening) with for example:

VAGRANT_LOG=debug vagrant up 2>&1 | tee vagrant.log

Anyway, the stack trace shows that the SSH commands fails while mounting shared folders. Is that after the guest additions are installed/updated and the machine booted?

I can try to reproduce it myself too, but as downloading the box takes some time, maybe not today. Full debug log would help a lot.

[lautreamont3]

Yes, after remove/install, on reboot.
Try now. Same gist.
gist

[tmatilai]

I think I found it. When the machine is rebooted after upgrading or installing the guest additions, Vagrant didn't wait for the machine to be ready before trying to mount the shared folder. #90 should fix this.

Unfortunately I can't reproduce the error myself. I guess it depends on disk and CPU speeds etc.

[lautreamont3]

You are right, now it works. This issue is now really closed.

[dawngerpony]

Hmmm, I'm still getting this issue (see hashicorp/vagrant#2251 (comment)).

ETA: my question has been answered in the aforementioned issue. Thanks!