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.
Description of problem:
as subject. Maybe vmdk only supports regular file(nfs or local file), but block device is very regular block device for users, I think we'd better we can fix it to support or disable it with a friendly message prompt.
Version-Release number of selected component (if applicable):
host info:
2.6.32-412.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.397.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.create a lvm and create it to VMDK format.
# lvcreate -L 10G -n vmdk-data-disk /dev/vg
Logical volume "vmdk-data-disk" created
# qemu-img create -f vmdk /dev/vg/vmdk-data-disk 10G
Formatting '/dev/vg/vmdk-data-disk', fmt=vmdk size=10737418240 compat6=off zeroed_grain=off
/dev/vg/vmdk-data-disk: error while creating vmdk: Invalid argument
2.try to create VMDK format for block device(e.g: iscsi lun or lvm)
# qemu-img create -f vmdk /dev/disk/by-path/ip-10.66.90.100:3260-iscsi-iqn.2001-05.com.equallogic:0-8a0906-0971f7d03-1dff49b26885073d-s2-sluo-172259-lun-0 100G
Formatting '/dev/disk/by-path/ip-10.66.90.100:3260-iscsi-iqn.2001-05.com.equallogic:0-8a0906-0971f7d03-1dff49b26885073d-s2-sluo-172259-lun-0', fmt=vmdk size=107374182400 compat6=off zeroed_grain=off
/dev/disk/by-path/ip-10.66.90.100:3260-iscsi-iqn.2001-05.com.equallogic:0-8a0906-0971f7d03-1dff49b26885073d-s2-sluo-172259-lun-0: error while creating vmdk: Invalid argument
Actual results:
fail to create VMDK format for block device(e.g: iscsi lun or lvm)
Expected results:
I think we'd better we can fix it to support or disable it with a friendly message prompt.
Additional info:
testing for local file:
# qemu-img create -f vmdk /home/vmdk-data-disk 10GFormatting '/home/vmdk-data-disk', fmt=vmdk size=10737418240 compat6=off zeroed_grain=off
# qemu-img info /home/vmdk-data-disk
image: /home/vmdk-data-disk
file format: vmdk
virtual size: 10G (10737418240 bytes)
disk size: 12K
Since this is a corner case and the reason we want to support vmdk is mostly for read-only use-cases, I'm closing it as wontfix.
BTW, Fam believes that not even VMWare supports the creation of vmdk files on block devices.