I've seen this on Windows also and I'm sure nothing modified the contents
of the .vagrant folder. My way of solving it (once, when I really needed
the old machine) was to search for the id in the folder where the actual
VMs are stored and update the id in .vagrant folder
On 11 February 2014
Hi,
This happens when VBoxManage fails to occasionally give information about
the old machine. So once again a VirtualBox bug, but I believe the next
Vagrant version will retry getting the info if the first call fails, which
should decrease the possibility hitting it.
--
Cheers,
- Teemu
On
Hi,
Thanks for clarifying that !
I guess it would be good to add a message when doing vagrant up and even
stopping the creation of a new VM in this case.
It's very strange to see everything working 'ok' but once you try to use
the VM nothing works because it's a base box with nothing installed..
On Windows I use cygwin to run vagrant commands and I have seen this happen if
I have the virtualbox gui running before up'ing any vms. I think vboxsvc gets a
different home vm folder when started from cygwin vs gui.
--
You received this message because you are subscribed to the Google Groups
There is a .vagrant folder in the directory that you are using, and it
contains an ID to a virtual machine. if something / something else is
modifying that file outside of vagrant the behavior you are seeing can
happen.
On Tue, Feb 11, 2014 at 4:32 PM, Dave Lowndes d...@room9.co.nz wrote:
