VM doesn't boot after taking a snapshot

[acarrie]

Hello,
Sorry if the topic already exists, I don't find it.
I have a problem with my VM after taking a snapshot yesterday.
I work with Oracle VM VirtualBox 5.0.10.
Yesterday I took a snapshot of a clean version of my VM (Server 2003), I didn't change any thing since the snapshot, but today it's impossible to boot my VM.

When I launch VirtualBox, I have a message which tell me that I can't access to my virtual disk. When I look the details, I see that I have an alert symbol on the left of my snapshot's name. I tried to release the snapshot, but it doesn't work.

And when I try to launch the VM, I have this message :

"Parent UUID {00000000-0000-0000-0000-000000000000} of the medium 'C:\Users\acarrie\VirtualBox VMs\Gamma Web\Snapshots/{997d4980-836c-49cd-b5fb-1a19b8f7e5aa}.vhd' does not match UUID {ba7773eb-22ab-11de-9f36-005056c00008} of its parent medium stored in the media registry ('C:\Users\acarrie/.VirtualBox\VirtualBox.xml')."

With the details :

"Code d'erreur :
E_FAIL (0x80004005)
Composant :
MediumWrap
Interface :
IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}"

I don't understand what's the matter...

Can you help me please?

P.S. : Sorry I can't post screenshot, it's my first post...

[mpack]

We would really want to know if it happens with the current release version, so try it with 5.0.12 and let us know.

[acarrie]

Hello,
I have the same problem with the 5.0.12 version.

[mpack]

Did you do anything other than make a snapshot? For example, did you replace or mess with the base VHD in any way?

Post a zip containing the .vbox file of the VM.

[acarrie]

Nothing.

[mpack]

I see from the vbox file that the VHD is not in the VM folder. That is a very bad idea. If you can't afford the space used by a disk then locate the entire VM elsewhere, do not mess with single files.

More to come.

[acarrie]

I understand, but I don't have enough storage in this partition of my physical disk. It's my professional computer and the physical disk is partitioned like this by our support.
Can I put the VM folder in my data partition (D:) instead of the user's folder (C:) or is it a bad idea?

[mpack]

Ok, do the following :-

1. Back up the VM folder if you have not already done so.
2. Unregister the VM (right click, remove - don't delete the physical files).
3. Shut down VirtualBox entirely.
4. Replace the old .vbox file with the attached one. Don't attempt to launch the VM yet, it won't work.
5. Delete the contents of the VMs "Snapshots" subfolder.
6. Move the VM folder to the secondary drive as you prefer, then copy the VHD into the same folder.
7. Run the VirtualBox manager, and re-register the VM using Machine|Add..., navigating to the new fixed .vbox file location.

You should now be able to launch the VM. I suggest that you Google "snapshot problem site:forums.virtualbox.org" before deciding to try that feature again.

[acarrie]

I have this now :

Premature end of data in tag VirtualBox line 8.
Location: 'D:\Users\acarrie\VirtualBox VMs\Gamma Web\Gamma Web.vbox', line 198 (8), column 1.
F:\tinderbox\win-5.0\src\VBox\Main\src-server\MachineImpl.cpp[480] (long __cdecl Machine::initFromSettings(class VirtualBox *,const class com::Utf8Str &,const class com::Guid *)).


Code d'erreur : E_FAIL (0x80004005)
Composant : MachineWrap
Interface : IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
Fonction appelée : IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}

[mpack]

My mistake, I forgot to check it before posting.

[acarrie]

Thank you so much!
So the problem was just the location of the VHD?

[mpack]

I would never use snapshots, so I can't know what makes problems more likely. I know that having the VHD in the root folder is a risky think in itself.