VM has become 'inaccessible' - Vagrant no

Question

For some reason this morning when I run 'vagrant up' I get the following error (this has worked absolutely fine for over a year)

Your VM has become "inaccessible". Unfortunately, this is a critical error with VirtualBox that Vagrant can not cleanly recover from. Please open VirtualBox and clear out your inaccessible virtual machines or find a way to fix them.

I could try removing my existing .vagrant folder and doing a vagrant up but that will take forever on our very slow internet speeds - can anyone suggest how to fix this quickly?

Answer 1

VirtualBox Manager will likely give you a bit more useful information, for example in my case it reported that the .vbox file did not exist.

After taking a look the problem was indeed that the file didn't exist - something had renamed it to x.vbox-tmp (shutting the PC down with the VM still running maybe?)

I copied the x.vbox-prev file to x.vbox and tried booting the VM again and everything worked fine.

Answer 2

this works for me:

In my "C:\Users{user}\VirtualBox VMs{vm-id}" folder are two files

• {vm-id}.vbox-prev
• {vm-id}.vbox-tmp

Renaming from "{vm-id}.vbox-tmp" to "{vm-id}.vbox" solved my problem and i can call "vagrant up"

Answer 3

Nothing here worked for me.

1. I deleted (or renamed see first comment) all files from

C:\Users[YourNameHere].VirtualBox

2. Run vagrant again:

   vagrant up

Now it's up.

Answer 4

I had to rename [vm-id].vbox-tmp (on VirtualBox VMs) to [vm-id].vbox. After that, without delete the .vagrant folder, I could run vagrant up and it worked very well.

Answer 5

You can simply delete the .vagrant folder from your project folder and run vagrant up again.

Answer 6

My problem was the same, but the fix was quite different... my VMs are stored on a network drive, accessible by NFS share. The remote drive had failed to come up after a reboot, so the VMs weren't accessible. Took me a while to realise the reason, and meantime hunted all over SO without a solution.

Then I realised, facepalmed, mounted the paths, and it all worked.

So in a nutshell, it was a path issue.

I felt I should include it here in case it helps someone in the same boat.