Opened 12 years ago
Closed 12 years ago
#11502 closed defect (fixed)
VHDX: Required flag of metadata item does not meet expectations (VERR_VD_GEN_INVALID_HEADER). => fixed in SVN
Reported by: | Dark Daskin | Owned by: | |
---|---|---|---|
Component: | virtual disk | Version: | VirtualBox 4.2.6 |
Keywords: | vhdx | Cc: | |
Guest type: | all | Host type: | Windows |
Description
I have a VHDX file from Windows 8 Image Backup. When I try to add it to a virtual machine, I get the following error:
Не удалось открыть жёсткий диск H:\WindowsImageBackup\Main\Backup 2013-02-16 141330\697a862a-18d5-4746-99a4-0725bbd93c2d.vhdx. Could not open the medium 'H:\WindowsImageBackup\Main\Backup 2013-02-16 141330\697a862a-18d5-4746-99a4-0725bbd93c2d.vhdx'. VHDX: Required flag of metadata item does not meet expectations 'H:\WindowsImageBackup\Main\Backup 2013-02-16 141330\697a862a-18d5-4746-99a4-0725bbd93c2d.vhdx' (VERR_VD_GEN_INVALID_HEADER). VHDX: Sector bitmap block at entry 4096 of image 'H:\WindowsImageBackup\Main\Backup 2013-02-16 141330\697a862a-18d5-4746-99a4-0725bbd93c2d.vhdx' marked as present, violation of the specification (VERR_VD_GEN_INVALID_HEADER). VD: error VERR_VD_GEN_INVALID_HEADER opening image file 'H:\WindowsImageBackup\Main\Backup 2013-02-16 141330\697a862a-18d5-4746-99a4-0725bbd93c2d.vhdx' (VERR_VD_GEN_INVALID_HEADER). Код ошибки: E_FAIL (0x80004005) Компонент: Medium Интерфейс: IMedium {29989373-b111-4654-8493-2e1176cba890} Вызванный интерфейс: IVirtualBox {3b2f08eb-b810-4715-bee0-bb06b9880ad2} Код ошибки метода: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
A VHD image of same partition form Windows 7 Image Backup is added without problems and can be accessed by a host OS.
Change History (17)
comment:1 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 12 years ago
Still error with version 4.2.12
Failed to open the hard disk D:\VM\Work_VM\Virtual Hard Disks\Work_VM.vhdx.
Could not open the medium 'D:\VM\Work_VM\Virtual Hard Disks\Work_VM.vhdx'.
VHDX: Required flag of metadata item does not meet expectations 'D:\VM\Work_VM\Virtual Hard Disks\Work_VM.vhdx' (VERR_VD_GEN_INVALID_HEADER).
VHDX: Mismatch between calculated number of BAT entries and region size (expected 268435448 got 1048576) for image 'D:\VM\Work_VM\Virtual Hard Disks\Work_VM.vhdx' (VERR_VD_GEN_INVALID_HEADER).
VD: error VERR_VD_GEN_INVALID_HEADER opening image file 'D:\VM\Work_VM\Virtual Hard Disks\Work_VM.vhdx' (VERR_VD_GEN_INVALID_HEADER).
Result Code: E_FAIL (0x80004005) Component: Medium Interface: IMedium {29989373-b111-4654-8493-2e1176cba890} Callee: IVirtualBox {3b2f08eb-b810-4715-bee0-bb06b9880ad2} Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
comment:4 by , 12 years ago
Is it possible to get the images somehow? I need to have a look at them to figure out whats wrong.
comment:13 by , 12 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Had a look at the image. The VHDX image does not comply to the specification publihed by Microsoft. I disabled the check which causes the error for now. The workaround will be part of next maintenance release. Btw. I missed that you try to attach the image directly to a VM. This will not work at the moment because the format is supported readonly only. You have to convert the image to another format with "VBoxManage clonehd ..." which supports writes.
comment:14 by , 12 years ago
It's what made me windows 8, believe me i didn't make it on my own :) Ok, i will convert it to vhd for virtualbox, thank you!
comment:15 by , 12 years ago
I never intended to say that you made it on your own, but either the spec is wrong or Microsoft dooesn't adhere to their own VHDX specification. ;) With the next maintenance version of VBox you should be able to convert the image to VHD too.
comment:16 by , 12 years ago
Summary: | VHDX: Required flag of metadata item does not meet expectations (VERR_VD_GEN_INVALID_HEADER). → VHDX: Required flag of metadata item does not meet expectations (VERR_VD_GEN_INVALID_HEADER). => fixed in SVN |
---|
comment:17 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Fix is part of VBox 4.2.14.
Please reopen if still relevant with VBox 4.2.10.