Hide Forgot
Description of problem: VHD and VHDX are 2 entirely different formats, but the qemu-img man help document appears to conflate the two. The format 'vpc' is used for VHD, and the format 'vhdx' is used for VHDX. Could you help me update it to make clear of them. Version-Release number of selected component (if applicable): host info: kernel-2.6.32-422.el6.x86_64 qemu-kvm-0.12.1.2-2.412.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.check the qemu-img man help docs that only has VHD info, no VHDX info. # man qemu-img ... vpc VirtualPC compatible image format (VHD). ... 2.the QEMU has support the VHDX format disk indeed. # /usr/libexec/qemu-kvm -drive format=? Supported formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 qed vhdx parallels nbd blkdebug host_cdrom host_floppy host_device file gluster gluster gluster gluster rbd 3. Actual results: Expected results: Additional info:
FYI: from Jeff Cody's comment, https://bugzilla.redhat.com/show_bug.cgi?id=999779#c5 Just to make sure it is clear: vpc = vhd = Virtual PC image format vhdx = Hyper-V image format vhd != vhdx vpc != vhdx "vpc" is really misnamed - the format is really "VHD". The "VHDX" format, however, is a completely new format not at all similar to "VHD", except that it is also from Microsoft. So VPC and VHD can be used interchangeably, and is referred to throughout qemu as "vpc". VHDX is completely separate. Best Regards, sluo
Fix included in qemu-kvm-0.12.1.2-2.431.el6
Verify this issue on qemu-kvm-rhev-0.12.1.2-2.431.el6.x86_64 version. host info: # uname -r && rpm -q qemu-kvm-rhev 2.6.32-493.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.431.el6.x86_64 check the qemu-img man help doc: ... vpc VirtualPC compatible image format (VHD). vhdx Hyper-V compatible image format (VHDX). ... # /usr/libexec/qemu-kvm -drive format=? Supported formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 qed vhdx parallels nbd blkdebug host_cdrom host_floppy host_device file gluster rbd ^^^^ Best Regards, sluo
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1490.html