virtualbox.org

I have a VM that is inaccessible for the following reason: Machine UUID 'C:\path\to\vm\Machine.vbox' doesn't match its UUID in the registry file 'C:\path/.VirtualBox/Virtualbox.xml'

There appears to be a machine snapshot inside the Snapshots folder. I was able to get the server up and running by just creating a new VM, and using an existing hard disk. The problem is, there are files missing that are probably inside the snapshot.

I tried using various utilities such as WinMount, and the VMware Disk Mount will not mount the .vmdk either. Is there a way to apply this snapshot to the newly created VM? I've tried placing the Snapshots folder inside where I created the new VM, however in VirtualBox when I click on Snapshots, they do not appear.

Does anyone know if there's any way possible to re-apply the snapshot, or extract from the .vmdk snapshot file?

I appreciate anyone's input.

The simplest thing would be to remove the conflicting VM from the GUI, and/or use Machine|Add... to add the .vbox file you have (ignore the vmdk files - disk images do not constitute the VM).

Inexpert tinkering with the individual elements of a snapshot chain will result in lost data - unless of course you kept a backup. If you did keep a backup then I recommend that you restore the base VMDK, as it was supposed to be frozen, not mounted for use in another VM!

I already tried creating a new VM, however it boots in the previous state pre-snapshot.

My question related to getting my snapshot applied to the VM. I'm making some backups and I will see what I can do with these UUIDs.

jpipdw wrote:I already tried creating a new VM

Not using the method I described, which registers an existing VM. If your description in the first post is accurate then it should work. Registering a snapshot by itself is not possible.

I've tried that as well - it adds the machine, however there are no shapshots that display at the top right, even though there is a snapshot inside the Snapshots folder.

I appreciate your input so far.

So I've been able to match up the UUID's and the machine can be booted again - but it's not seeing the snapshot inside the Snapshots folder.

I created a new snapshot to see what VirtualBox writes to the .xml file, and it added a bunch of data as well as the snapshot UUID - however the snapshot UUID of the newly created snapshot does not match the actual filename of the snapshot vmdk.

i'm wondering if I could activate the previous snapshot, if only I could get the correct UUID of the previous snapshot.

Better switch to recovery mode. Put the original (from backup) copies of the base VDI and the snapshot(s) into a single folder, then clone the newest snapshot file with CloneVDI. Don't make the noobie mistake of cloning just the base VDI. If you clone a snapshot file then the result should be a merged VDI which you can build a new VM around - do not add the the clone to the original VM (all that snapshot control info will confuse things).

I suggest you avoid snapshots in future, as they are prone to this kind of problem.

Got it...I will try that as soon as I can and report back! Thank you very much for your help.

I wouldn't get my hopes up too high yet - you seem to have been copying VM files around, so the file in the snapshots folder may not even be related. You'll know that if CloneVDI gives you an error about the file being a difference image.

I don't have a .vdi file - whoever created this VM created a .vmdk. Will CloneVDI still convert this disk?

Nevermind - I just read up on CloneVDI and it supports vmdk.

I'll report back.