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