Red Hat Bugzilla – Bug 1097020
[RFE] qemu-img: Add/improve Disk2VHD tools creating VHDX images
Last modified: 2016-04-26 10:00:14 EDT
According the discuses in bug from 879234#c24 to bug 879234#c28, we separate a new bug for rhel7.1 and rhel6.6 which our qemu-img will support the vhdx image created by the Microsoft Disk2VHD tool. Host info: # uname -r && rpm -q qemu-kvm 3.10.0-121.el7.x86_64 qemu-kvm-1.5.3-60.el7_0.1.x86_64 # qemu-img info SERVERIS.VHDX qemu-img: No valid VHDX header found qemu-img: Could not open 'SERVERIS.VHDX': Could not open 'SERVERIS.VHDX': Invalid argument # qemu-img convert -p -f vhdx SERVERIS.VHDX -O qcow2 serveris.qcow2 qemu-img: No valid VHDX header found qemu-img: Could not open 'SERVERIS.VHDX': Could not open 'SERVERIS.VHDX': Invalid argument qemu-img: Could not open 'SERVERIS.VHDX' Best Regards, sluo
Fix included in qemu-kvm-1.5.3-66.el7
Verify this issue on qemu-kvm-rhev-2.1.0-1.el7.x86_64 and qemu-kvm-1.5.3-67.el7.x86_64 which works well. host info: # uname -r && rpm -q qemu-kvm-rhev 3.10.0-128.el7.x86_64 qemu-kvm-rhev-2.1.0-1.el7.x86_64 # uname -r && rpm -q qemu-kvm 3.10.0-128.el7.x86_64 qemu-kvm-1.5.3-67.el7.x86_64 Steps and results: Create a vhdx image by the Microsoft Disk2VHD tool and copy it out. # qemu-img info SERVERIS.VHDX image: SERVERIS.VHDX file format: vhdx virtual size: 1.0G (1073741824 bytes) disk size: 22M cluster_size: 2097152 # qemu-img convert -p -f vhdx SERVERIS.VHDX -O qcow2 serveris.qcow2 (100.00/100%) # qemu-img info serveris.qcow2 image: serveris.qcow2 file format: qcow2 virtual size: 1.0G (1073741824 bytes) disk size: 8.1M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false # qemu-img convert -p -f vhdx SERVERIS.VHDX -O raw serveris.raw (100.00/100%) # qemu-img info serveris.raw image: serveris.raw file format: raw virtual size: 1.0G (1073741824 bytes) disk size: 7.3M Base on above, move this issue to VERIFIED status after it was ON_QA, please correct me if any mistake. 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. https://rhn.redhat.com/errata/RHSA-2015-0349.html