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:
Just as discuss with kwolf in IRC, the problem is that the bdrv_create() implementation for these block drivers directly use POSIX file functions instead of using the qemu block layer, so they work only on local files and fail with glusterfs storage.
BTW, raw/qcow2/qed/vhdx format has no such issue.
Version-Release number of selected component (if applicable):
host info:
# uname -r && rpm -q qemu-kvm-rhev
2.6.32-448.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.424.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
# qemu-img create -f vmdk gluster://10.66.9.107/volume_name/test 10G
Formatting 'gluster://10.66.9.107/volume_name/test', fmt=vmdk size=10737418240 compat6=off zeroed_grain=off
gluster://10.66.9.107/volume_name/test: error while creating vmdk: Invalid argument
# qemu-img create -f vpc gluster://10.66.9.107/volume_name/test 10G
Formatting 'gluster://10.66.9.107/volume_name/test', fmt=vpc size=10737418240
gluster://10.66.9.107/volume_name/test: error while creating vpc: Input/output error
# qemu-img create -f vdi gluster://10.66.9.107/volume_name/test 10G
Formatting 'gluster://10.66.9.107/volume_name/test', fmt=vdi size=10737418240 static=off
gluster://10.66.9.107/volume_name/test: error while creating vdi: No such file or directory
Actual results:
Expected results:
creating vmdk/vpc/vdi image in glusterfs should work.
Additional info:
Worth investigating the effort needed to implement it upstream and in RHEL7 (bug 1098086), but closing as WONTFIX in RHEL6, as the usage scenario is very unlikely to happen in the field.