virtualbox.org

Greetings all!

Here is my error: Failed to open a session for the virtual machine CRI-IRONKEY-VM.

Parent UUID {00000000-0000-0000-0000-000000000000} of the medium 'C:\Users\Administrator\VirtualBox VMs\CRI-IRONKEY-VM\Snapshots\{f843b7fa-d226-42c1-8565-f9f1a967889f}.vhd' does not match UUID {3d9f9278-a634-4f60-9b53-a99859090971} of its parent medium stored in the media registry ('C:\Users\Administrator/.VirtualBox\VirtualBox.xml').

Result Code: E_FAIL (0x80004005)
Component: MediumWrap
Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}

I, honestly, don't know where to start.

I am using Server 2012R2 and the latest version of VirtualBox (ver. 5.something). I created a Win10-64bit image and had it all completed and ready for deployment. At the recommendation of another admin who is familiar with VirtualBox told me to shutdown the VM and to take a simple snapshot, which I did. Upon saving the snapshot, I was presented with this error and have no idea how to proceed. If I inadvertently did something wrong and killed the image, no big deal, I can always rebuild the image.

If it matters, this VM is being used to create a .wim for future use with Windows10togo applications on IronKeys (or whatever they will be called since Kingston just bought Imation's Ironkey stake).

It seems to be saying that your snapshot isn't a snapshot. Were you attempting to clone a VM by cloning the individual VHD files?

Never use snapshots. What was the object anyway? I can't think of a rational one. If you need a backup, make a backup. A snapshot is not a backup. In fact I would avoid VHDs too.

Since it sounds like your snapshot contained nothing anyway, what I would recommend now is that you clone the base VHD to VDI format, then create a new VM around the VDI. That should give you a working VM again, better suited for VirtualBox. If in future you actually need media in a foreign format you can always clone it again.

Thanks for your reply.

He recommended the snapshot just for future rollbacks if we happen to run into any issues down the line.

When attempting to clone the VM that I built, I receive the same (exact) error. So, the same error occurs when I attempt to clone the VM or start it. Disregard the snapshot at this point, I just thought that may have been additional details in helping figure out what this error may mean.

In VB, how would I go about cloning the VHD into a VDI format? All i see stored, that I can locate, is the original VHD of the image I built.

Your help is much appreciated.

I didn't say clone the VM (obviously that can't work), I said clone the base VHD. You can do that with the copy function in File|Virtual Media Manager or on the command line using VBoxManage clonehd.

If you go for the former then use expert mode so you'll be given the opportunity to change the target format to VDI.