Page 1 of 1

Unable to start VM

Posted: 4. Jun 2012, 21:30
by EPicure
Hello !

I have Oracle Virtualbox (v4.1.8 r75467) on a windows 2008 R2. The guest system is a Debian Linux Squeeze (vhd file).

Friday, I had a crash. No more space on harddrive. The image file (vhd) is stocked on this harddrive.
I stopped Virtualbox, released some space and tried to restart my virtual machine. Unsuccessful.

Here is the error message on "virtual media manager":

Code: Select all

Could'nt open the medium 'C:\Users\Administrateur\VirtualBox VMS\DebianProd\Snapshots\{dd6ee9e0-d4db-4861-9f35-533bbd8e2b6e}.vhd'
VD: error opening image file 'C:\Users\Administrateur\VirtualBox VMS\DebianProd\Snapshots\{dd6ee9e0-d4db-4861-9f35-533bbd8e2b6e}.vhd'
(VERR_VD_VHD_INVALID_HEADER).
Here is the error when I try to start my VM:

Code: Select all

Code d'erreur :
E_FAIL (0x80004005)
Composant :
ProgressProxy
Interface :
IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
This week-end, I found a solution to convert vhd to vdi. Sorry I can't post urls (security policy of this forum).

I followed all instructions, but when I try to start the new VM (vdi file), I've got this error message:

Code: Select all

Chargement de Linux 2.6.39-bpo.2-amd64
error : invalid magic number
Chargement du disque mémoire initial
error : you need to load the kernel first
Tape any key to continue...
Any help will be appreciated. Thx

Re: Unable to start VM

Posted: 5. Jun 2012, 10:47
by mpack
VHDs should not be used if you can avoid them. Use VirtualBox's own VDI format instead.

The "invalid magic number" is probably a grub problem, caused by changing the UUID when you cloned the drive. You need to edit the grub script so that it uses the correct UUID. You can find the correct UUID in the media registry of the VM (view the .vbox file with a text editor).