VM has become 'inaccessible' - Vagrant no longer working

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 b         


        

Answer 1

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.