VM has become 'inaccessible' - Vagrant no longer working

windows-7 vagrant virtual-machine virtualbox
Zabs picture Zabs · Jun 5, 2015 · Viewed 25.6k times · Source

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

Ultimate Fighter picture Ultimate Fighter · Aug 13, 2015

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"

Related questions

Getting a LAMP stack running on a Vagrant VM (under Windows 7 host), full instructions?

I have a Vagrant VM standard issue lucid32.box running. What would the complete instructions be to set up LAMP on this? I have looked at knife (part of chef) and attempted: vagrant@lucid32:~$ knife cookbook site install apache2 but …

Read More
How to set java_home on Windows 7?

I went to the Environment Variables in 'System' in the control panel and made two new variables, one for user variables and one for system variables. Both were named JAVA_HOME and both pointing to C:\Sun\SDK\jdk\bin …

Read More
How do I register a DLL file on Windows 7 64-bit?

I have tried to use the following code: cd c:\windows\system32 regsvr32.exe dllname.ax But this is not working for me. How can I register a DLL file on Windows 7 with a 64-bit processor?

Read More