Re: disappearing VMs

[Alex Scoble]

This is happening to me on a Windows 7 box running Vagrant 1.6.5 and VirtualBox 4.3.16. Very annoying.

Doing the ID thing has not helped. However, the correct box starts just fine from within VBox.

--Alex

[Alvaro Miranda Aguilera]

upgrade virtualbox.

 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Alex Scoble]

Upgrading doesn't solve the problem. It does not restore the desired VM so it can be started by Vagrant.

--Alex

[Alvaro Miranda Aguilera]

there was an issue on virtualbox, can you check if you lose machines on this current version?

 

.18

[Alex Scoble]

I just upgraded and am rebuilding my vm. If it happens again, I'll let you know.

Still would be nice to get a recovery solution...too late for me though. I deleted the VM completely and started over.

Thanks,

Alex

[Henry Hsue]

This is happening for me too. VM I created just disappeared. What was left looks like a base image with my data deleted. Vagrant can't connect to this box, using vagrant up.

Using VirtualBox 4.3.18 on Windows 7, and Vagrant 1.6.5. 

[Bogdan B]

Hi all,

First of all I guess this is a good situation when you learn that using provisioning is a must :)

I've encountered this issue of disappearing machines when using Cygwin and the reason was VirtualBox creating 2 'config' folders, one under Cygwin's /home/{user}/.virtualbox and one in C:/Users/{user}/.VirtualBox

If I was starting first the GUI then the later one was used and the machines created from terminal were not listed.

[Alvaro Miranda Aguilera]

hello, can you update vbox?

New Nov 21st, 2014
VirtualBox 4.3.20 released!