Virtualbox VMs won’t boot after taking a snapshot

Virtualbox VMs won’t boot after taking a snapshot

I’ve been needing to do a lot of work with quick VM testing recently, firing up VMs, running scenarios for clients and my first point of call is always Oracles VirtualBox opensource visualization tool. It’s reliable, free, and ideal for mucking about with virtual machines and giving things a once over.

Until today.

Today I had to create a load of VMs, import some backups, run through some scenarios and see what was likely to happen. I have no idea why, but each time I rebooted after taking a snapshot of a VM the guest failed to boot and VirtualBox gave me the following delightful error;

2016-06-03 13_57_16-2016-06-03 12_29_10-

Now this was an issue. Each time I booted the VM after a snapshot was taken, the VM wouldn’t fire up and VirtualBox Media Manager showed exclamation marks for that drive and it’s snapshots.

After a bit of digging and testing with the command line I found that for some reason the snapshots weren’t associated with the original disk. They were there, Media Manager could see them and showed them in the right place, but the snapshots uuidParent tag was blank instead of pointing at the main disk image.

So, if you get an error in VirtualBox stating “Parent UUID {00000000-0000-0000-0000-000000000000} of the medium “blah” does not match UUID” then this might be a help

 

  1. Add the VirtualBox directory to the system PATH variable as there’s a wealth of great command line tools in there and it’s good to access them easily.
  2. Get the uuidCreation parameter of your parent virtual hard disk. I’ve highlighted it in bold.
  3. Get the uuidParent of the snapshot that is mentioned in your error. In my screenshot above the snapshot is catchily called {7cc77399-c4e0-4595-882d-73f81b9c1331}.vhd.
  4. You can see that the output shows that the uuidParent setting for the {7cc77399-c4e0-4595-882d-73f81b9c1331}.vhd snapshot is blank; it’s been orphaned for some reason. Lets fix that.
  5. Now you can either restart VirtualBox and start your VM again or you can click on File > Virtual Media Manager and then click on your disk and click Refresh.

Author

Oliver Marshall
Oliver works as a Director at Oakson who provide absolutely awesome IT support in Brighton, UK. Out of hours he's a runner with a limp, has a board game addiction and a owns a dog that looks like a badger.
Show Buttons
Hide Buttons

Stay in touch

or
Subscribe to my weekly newsletter

If you are enjoying this article then why not like my page.

Stay in touch

or
Subscribe to my weekly newsletter

If you enjoyed this article then why not like my page.