Vagrant reset my virtual machine, and now I'm afraid that I lost my job

Question

I have a terrible situation and I hope you can help.

This morning, the terminal opened in my virtual gallows, I tried to access Virtualbox, and it did not respond. I killed Virtualbox manually and typed vagrant up . Vagrant ( vagrant ssh ) boots into a virtual machine, which pretty much seems to be standard by default, and I'm afraid all my work is lost.

Typing vmboxmanage list vms shows:

wasp_1375609265" {29663113-786b-4b8a-adc8-2edecf06bcff}

which is the same UUID that I found in the .vagrant file.

I am on Mac OSX Montain Lion, the version of the stroller I use is 1.0.6 , and Virtualbox is 4.2.16 .

Is there any way to access the image in the previous state that it had before I manually killed it? I can't believe that the tramp or Virtualbox intentionally overwrite the default image

Answer 1

It turned out that I was an idiot, and the image did not disappear. For some reason, Virtualbox saved it with a mysterious name and a tramp, returning to the default firewall wasp_32... when I started it again. I found the image I was looking for by simply doing all the *.vmdk found in ~/VirtualBox VMs .

After that, I followed the instructions I found here to make a tramp loading the correct image