VM lost current-state.vdi and reuse last snapshot as last .vdi file(wrote in it).

[igor]

I have some problem with VirtualBox. I had f Virtual Machine with snapshot like this:

What I've done

1. Create VM with HD. (lambordhini.vdi)

Now HD hierarchi looks like this

Lambordhini.vdi (F) -> {3c78b30d-3c34-4d17-a67e-e05b1a02d7db}.vdi (*)

(*) - Changes write here (F) frozen

.2. Create snapshot (take snapshot)

Now HD hierarchi looks like this

Lambordhini.vdi (F) -> {3c78b30d-3c34-4d17-a67e-e05b1a02d7db}.vdi (*)

.3. Create second snapshot

Now HD hierarchi looks like this

Lambordhini.vdi (F) -> {7d615830-6378-4c25-ba5e-c5700a465716}.vdi (F) -> -> {3c78b30d-3c34-4d17-a67e-e05b1a02d7db}.vdi (*)

.4. One month later. Switch off VM. (from guest OS)

.5. Switch off Host OS.

.6. Run Host OS

.7. Run Guest OS

$ VBoxManage startvm lamborghini --type headless

.8. Found, that active HD is: 7d615830-6378-4c25-ba5e-c5700a465716, and it's not frozen! (no additional snapshot vdi)

Now HD hierarchi looks like this

Lambordhini.vdi (F) -> {7d615830-6378-4c25-ba5e-c5700a465716}.vdi (*)

not even

Lambordhini.vdi (F) -> {7d615830-6378-4c25-ba5e-c5700a465716}.vdi (F) ->-> {3c78b30d-3c34-4d17-a67e-e05b1a02d7db}.vdi ->-> {some_new_number}.vdi (*)

There is no {3c78b30d-3c34-4d17-a67e-e05b1a02d7db} at all.

I'm totaly sure, that do nothing else. (no snapshot restore and anything else). Also I didn't found any errors in log file. vdi file just disappear from config.

$uname -a FreeBSD ny.local 8.2-STABLE FreeBSD 8.2-STABLE #0: Sat Oct 8 10:36:54 UTC 2011 root@…:/usr/obj/usr/src/sys/GENERIC amd64

$ ll ~/backup/Snapshot -rw------- 1 igor igor - 16196390912 Nov 3 23:55 {3c78b30d-3c34-4d17-67e-e05b1a02d7db}.vdi -rw------- 1 igor igor - 8944439296 Nov 7 12:07 {7d615830-6378-4c25-a5e-c5700a465716}.vdi

$ VBoxManage -v 4.0.12_OSEr72916

I attached Log before last start(with actual data)(VBox.log.1) and last run (VBox.log)

Could anybody tell me, how can I restore data from {3c78b30d-3c34-4d17-67e-e05b1a02d7db}.vdi and what had actually happen?

[Frank Mehnert]

Please reopen if still relevant with VBox 4.1.18.