Vagrant error: Your VM has become inaccessible.

If you’ve deleted a virtual machine file still referenced by one of your projects, you’ll run into the following error when you try and instantiate the VM via vagrant up.

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.

Vagrant creates a hidden folder within your project directory named .vagrant with files that refer to specific VM IDs.

Simply delete the .vagrant folder within your project and rerun vagrant up. Vagrant will rebuild the .vagrant directory with the correct files and ID.

Thank you for this. I had this exact problem after I had upgraded both my VirtualBox and my Vagrant installation. Appreciate you posting the right solution up. I cleared out my .vagrant directory and redid the “homestead up” and it worked.

Apologies, I only just now noticed this comment. Sorry but I never used vagrant under Windows. All my experience is on linux/mac and I’m *assuming* that issue is going to be Windows environment specific.