Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
VMDK images with streamOptimized sub-format are accepted
Previously, a Virtual Machine Disk (VMDK) image with a streamOptimized sub-format created by the qemu-img tool was rejected by Elastic Sky X (ESX) services, because the version number of the VMDK image was too low. In this update, the sub-format number of streamOptimized VMDK images are automatically increased. This results in the VMDK image being accepted by ESX services.
Created attachment 1115355[details]
qemu-img-bug.ovf
Description of problem:
qemu-img only creates broken VMDK image files that can't be used for within
an OVA file for importing a virtual machine into VMware vSphere/ESXi. Every
VMDK file created by qemu-img leads during import to the error message:
Not a supported disk format (sparse VMDK version too old)
Version-Release number of selected component (if applicable):
qemu-img-1.5.3-105.el7_2.1.x86_64
qemu-img-2.5.0-3.fc24.x86_64 (rebuilt from Fedora Rawhide for RHEL 7)
VMware vSphere Client, Version 5.1.0, Build 1064113
VMware ESXi, Version 5.1.0, Build 1065491, German-000
How reproducible:
Everytime, see above and below.
Steps to Reproduce:
1. cd /tmp/
2. dd if=/dev/zero of=qemu-img-bug.img bs=1M count=1
3. qemu-img convert qemu-img-bug.img -O vmdk \
-o adapter_type=lsilogic,subformat=streamOptimized,compat6 \
qemu-img-bug.vmdk
4. tar cf qemu-img-bug.ova qemu-img-bug.ovf qemu-img-bug.vmdk
5. Try to import qemu-img-bug.ova into VMware -> fails with error above
6. printf '\x03' | dd conv=notrunc of=qemu-img-bug.vmdk bs=1 seek=$((0x4))
7. tar cf qemu-img-bug.ova qemu-img-bug.ovf qemu-img-bug.vmdk
8. Try to import qemu-img-bug.ova into VMware -> works as expected now
Actual results:
qemu-img created VMDK images lead to "Not a supported disk format (sparse
VMDK version too old)".
Expected results:
qemu-img created VMDK images should not lead to any error message during
import into VMware.
Additional info:
Credit for printf/dd combination at point 6 goes to Radoslav Gerganov.
Robert, thanks for taking the time to enter a bug report with us. We use reports like yours to keep improving the quality of our products and releases. That said, we're not able to guarantee the timeliness or suitability of a resolution for issues entered here because this is not a mechanism for requesting support.
If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain it receives the proper attention and prioritization that will result in a timely resolution.
For information on how to contact the Red Hat production support team, please visit: https://www.redhat.com/support/process/production/#howto
Created attachment 1184059[details]
create ovf file
Reproduced the issue with qemu-kvm-1.5.3-110.el7.x86_64.
After step5, get an error "Not a supported disk format(sparse VMDK version too old)". After step 8, qemu-img-bug.ova can be imported successfully.
Verified the issue with qemu-kvm-1.5.3-111.el7.x86_64.
After step5, qemu-img-bug.ova can be imported successfully.
Steps to reproduce:
1. #dd if=/dev/zero of=qemu-img-bug.img bs=1M count=1
2. #qemu-img convert qemu-img-bug.img -O vmdk -o adapter_type=lsilogic,subformat=streamOptimized,compat6 qemu-img-bug.vmdk
3. #sh create_ovf.sh
4. #tar cf qemu-img-bug.ova qemu-img-bug.ovf qemu-img-bug.vmdk
5. Import qemu-img-bug.ova into ESXi 5.1
6. printf '\x03' | dd conv=notrunc of=qemu-img-bug.vmdk bs=1 seek=$((0x4))
7. #tar cf qemu-img-bug.ova qemu-img-bug.ovf qemu-img-bug.vmdk
8. Import qemu-img-bug.ova into ESXi 5.1
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-2016-2585.html
Created attachment 1115355 [details] qemu-img-bug.ovf Description of problem: qemu-img only creates broken VMDK image files that can't be used for within an OVA file for importing a virtual machine into VMware vSphere/ESXi. Every VMDK file created by qemu-img leads during import to the error message: Not a supported disk format (sparse VMDK version too old) Version-Release number of selected component (if applicable): qemu-img-1.5.3-105.el7_2.1.x86_64 qemu-img-2.5.0-3.fc24.x86_64 (rebuilt from Fedora Rawhide for RHEL 7) VMware vSphere Client, Version 5.1.0, Build 1064113 VMware ESXi, Version 5.1.0, Build 1065491, German-000 How reproducible: Everytime, see above and below. Steps to Reproduce: 1. cd /tmp/ 2. dd if=/dev/zero of=qemu-img-bug.img bs=1M count=1 3. qemu-img convert qemu-img-bug.img -O vmdk \ -o adapter_type=lsilogic,subformat=streamOptimized,compat6 \ qemu-img-bug.vmdk 4. tar cf qemu-img-bug.ova qemu-img-bug.ovf qemu-img-bug.vmdk 5. Try to import qemu-img-bug.ova into VMware -> fails with error above 6. printf '\x03' | dd conv=notrunc of=qemu-img-bug.vmdk bs=1 seek=$((0x4)) 7. tar cf qemu-img-bug.ova qemu-img-bug.ovf qemu-img-bug.vmdk 8. Try to import qemu-img-bug.ova into VMware -> works as expected now Actual results: qemu-img created VMDK images lead to "Not a supported disk format (sparse VMDK version too old)". Expected results: qemu-img created VMDK images should not lead to any error message during import into VMware. Additional info: Credit for printf/dd combination at point 6 goes to Radoslav Gerganov.