Upgrading doesn't solve the problem. It does not restore the desired VM so it can be started by Vagrant.
--Alex On Thursday, October 23, 2014 1:07:42 PM UTC-7, Alvaro Miranda Aguilera wrote: > > upgrade virtualbox. > > > On Fri, Oct 24, 2014 at 7:12 AM, Alex Scoble <[email protected] > <javascript:>> wrote: > >> 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 >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/d/optout.
