vbox-file defect and vm not accessible

Discussions related to using VirtualBox on Windows hosts.
Post Reply
DeHe

vbox-file defect and vm not accessible

Post by DeHe »

Hi out there,

one of my customers uses VirtualBox to virtualize his old Server (Windows Server 2003) on a new physical machine (Windows Server 2008 R2 x64). I updated VirtualBox to version 4.3.20 r96997 but the problem still appears.
I have no idea what happened but it seems that the "ServerMZ.vbox" has crashed or something like that. The file could not be read and even an older backup isn't valid xml.
I've got the original HDD-file serverMZ-disk1.vmdk (from august 2014) and all the snapshots made over the last months. My problem ist that I have no clue how to merge without having the VM in Virtualbox accessible.
Are there any commandline tools to merge the snapshots with the original hard drive file or any other things I can do?

I hope anybody can help me.
Thanks in advance.
Dennis
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: vbox-file defect and vm not accessible

Post by mpack »

An exact error message would be useful. Also a listing of the VM folder.

Look for a file in the VM folder called something.vbox-tmp. If this file exists then change the extension to ".vbox".

Otherwise, look for a file in the VM folder called something.vbox-prev. If this file exists then change the extension to ".vbox".

Otherwise, restore the VM (meaning all the files, not just the disk) from a backup.

If your values data then I suggest that you stop using snapshots asap. The worst possible practice is creating lots of snapshots but taking no backups.
Post Reply