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

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.