Deleting .vagrant will lose all the progress he has made. You should be able to open the VM from within Virtualbox, and if it doesn't work then you might be able to mount the .vdi or .vmdk file using a new VM and recover your data.
On Saturday, September 5, 2015 at 1:17:01 PM UTC-5, zohaib tariq wrote: > > just delete .vagrant directory and then run this command > vagrant up > > On Thursday, 17 October 2013 10:53:20 UTC+5, Etika Ahuja wrote: >> >> Hello >> >> >> Iam facing problem using vagrant >> >> on doing vagrant up iam getting an error >> >> >> Bringing machine 'default' up with 'virtualbox' provider... >> Your VM has become "inaccessible." Unfortunately, this is a critical error >> with VirtualBox that Vagrant can not cleanly recover from. Please open >> VirtualBo >> x >> and clear out your inaccessible virtual machines or find a way to fix >> them. >> >> what is the way to resolve this error so that i don't loose my >> configuration of my virtual box(all the setup i did i don't won't do it >> again on vm) >> >> PLEASE HELP >> >> Etika Ahuja >> > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/c6878794-261b-4486-a629-11b389d3e2be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
