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.
1.Prepare a glusterfs disk.
# qemu-img info gluster://10.66.9.107/volume_name/test.qcow2
image: gluster://10.66.9.107/volume_name/test.qcow2
file format: qcow2
virtual size: 10G (10737418240 bytes)
disk size: 193K
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false
2.Hot-plug it with "blockdev-add".
{"execute":"qmp_capabilities"}
{"return": {}}
{ "execute": "blockdev-add", "arguments": {'options' : {'driver': 'qcow2', 'id':'drive-disk1', "aio":"native", 'rerror':'stop', 'werror':'stop', 'file': {'driver': 'file', 'filename': 'gluster://10.66.9.107/volume_name/test.qcow2'}, 'cache': { 'writeback': false, 'direct': true, 'no-flush': false }}} }
{"error": {"class": "GenericError", "desc": "could not open disk image drive-disk1: Could not open file: No such file or directory"}}
Best Regards,
sluo
Comment 2Markus Armbruster
2014-11-03 17:27:20 UTC
blockdev-add is a work in progress upstream. At this time, we intend to bring the results to RHEL-7 qemu-kvm-rhev, but not to qemu-kvm.
blockdev-add support for gluster is being worked on upstream. It should find its way into qemu-kvm-rhev via rebase or backport (bug 1159726). We don't intend to backport it to qemu-kvm.
1.Prepare a glusterfs disk. # qemu-img info gluster://10.66.9.107/volume_name/test.qcow2 image: gluster://10.66.9.107/volume_name/test.qcow2 file format: qcow2 virtual size: 10G (10737418240 bytes) disk size: 193K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false 2.Hot-plug it with "blockdev-add". {"execute":"qmp_capabilities"} {"return": {}} { "execute": "blockdev-add", "arguments": {'options' : {'driver': 'qcow2', 'id':'drive-disk1', "aio":"native", 'rerror':'stop', 'werror':'stop', 'file': {'driver': 'file', 'filename': 'gluster://10.66.9.107/volume_name/test.qcow2'}, 'cache': { 'writeback': false, 'direct': true, 'no-flush': false }}} } {"error": {"class": "GenericError", "desc": "could not open disk image drive-disk1: Could not open file: No such file or directory"}} Best Regards, sluo