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 12 February 2014 11:59, Teemu Matilainen <[email protected]> wrote: > 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 Wed, Feb 12, 2014 at 5:57 AM, Bogdan B <[email protected]> wrote: > >> 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 23:37, Terrance Shepherd <[email protected]> wrote: >> >>> 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 <[email protected]> wrote: >>> >>>> Every now and again I see a problem where the Vagrant box is built but >>>> if I try Vagrant up or Vagrant ssh I get "VM not created" or it starts >>>> building the box (and failing as "A VirtualBox machine with the name >>>> '[whatever]' already exists."). The underlying Vagrant files are not >>>> changing, although they are on a shared Google Drive. >>>> >>>> This is on MacOS 10.9.1 Mavericks with VirtualBox 4.3.6. >>>> >>>> What triggers Vagrant to re-provision and/or how to I get it to detect >>>> an existing Vagrant box? >>>> >>>> Cheers >>>> >>>> -- >>>> 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 [email protected]. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>> >>> -- >>> 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 [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- >> 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 [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
