Create Snapshot, immediately VM is NOT accessible

[JRC@…]

Windows 7, 64-bit host. Windows XP sp3 client/vm.

IF I have a clean, working VHD, on a newly created VM, IF I create a snapshot, without doing anything else, that VM is immediately NOT accessible. It gives an error of:

Failed to open a session for the virtual machine winXPtest.

No error info.

Result Code: E_FAIL (0x80004005) Component: ProgressProxy Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}

---

I've have backup VHD files, and can manually restore this, and make the problem happen MANY times. NOT random. Happens every time.

I've tried assigning new UUID to the original/base VHD. I've tried re-assigning parent UUID to the snapshot. Doesn't matter. It doesn't work. The snapshot that VBox Manager just made by itself, it corrupt.

[JRC@…]

LOG of startup, BEFORE snapshot created

[JRC@…]

LOG of startup, Immediately AFTER snapshot created.

[JRC@…]

Box Configuration

[JRC@…]

Service Startup log when corrupt

[aeichner]

I can't reproduce this problem so far. What kind of VHD image do you use for the base image, fixed or dynamic?

[Frank Mehnert]

No response, closing.

[Möhre]

I ran into the same Problem with Win7 Guest (official Image of Microsoft for IE9 testing).

Manager for virtual media tells me the parent UUID differs after creating a snapshot.

[cameron314]

I just ran into this problem too. Fedora 21 guest, Windows 7 host. After creating the snapshot and shutting down (resetting to the current snapshot), the virtual machine no longer starts.

The VirtualBox GUI informs me that the harddisk image is "not currently accessible". Clicking "Check" on that dialog (as opposed to "Ignore") brings me to the Virtual Media Manager, which shows a new sub-disk for the VM's usual virtual disk (presumably, this sub-disk is used for managing snapshots). Hovering over this sub-disk informs me that the sub-disk's parent UUID is set to null ("{000...}") instead of the actual UUID of the parent virtual disk. The parent virtual disk is a dynamically expanding VHD that was created using the Windows Disk Manager utility.

​This guy seems to have come across the same problem, and built a simple GUI tool for setting the parent UUID of a VHD disk. Using his tool, I changed the parent UUID of the sub-disk to match the actual parent. The warning upon starting the VirtualBox manager went away, and the machine was able to boot again.

Note that even after manually fixing up the parent UUID, if I later restored to a snapshot, the sub-disk VHD would be recreated with a null parent UUID again and I'd have to change it manually again in order to be able to boot.

VirtualBox version: 4.3.20