Vagrant destroyed on host shut down, Windows
vagrant, virtualbox, windows
Solution
This happens to me every now and then, I reboot and there's no trace of my vagrant machine anymore. Even running `vboxmanage list vms` doesn't show my VM, but if I reboot my computer again and this time I open Virtualbox GUI before trying to do `vboxmanage list vms` (or don't open it first depending on which way failed on previous attempt) and it'll list my Vagrant machine and its ID.
Armed with this ID I can go into .vagrant/machines/default/virtualbox/ and create a file named "id" and add a single line containing the id of the vagrant machine. And after that you can start it with `vagrant up` it's probably safest to add --no-provision though as it has happened that it's started provisioning even though a machine already existed..
Problem
After working in a Vagrant VM and making some changes I will suspend the VM using vagrant suspend. If I then restart the host computer and then attempt to run vagrant resume, the terminal sits for a bit and then brings me back to a command prompt without any feedback. So, naturally I then try vagrant ssh, and I receive the following: VM must be running to open SSH connection. Run `vagrant up` to start the virtual machine. If I run vagrant up, I find that all the changes I made prior to the suspend have been overwriten by the base box import. Is this intended behavior? I am runny Windows 8 pro x64.