[ovirt-devel] blockcommit and gluster network disk path

[Sahina Bose]

Hi,

I'm running into problems with blockcommit and gluster network disks -
wanted to check how to pass path for network disks. How's the protocol and
host parameters specified?

For a backing volume chain as below, executing
virsh blockcommit fioo5
vmstore/912d9062-3881-479b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6d8a4/027a3b37-77d4-4fa9-8173-b1fedba1176c
--base
vmstore/912d9062-3881-479b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6d8a4/d4c23ec6-20ce-4a2f-9b32-ca91e65a114a
--top
vmstore/912d9062-3881-479b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6d8a4/027a3b37-77d4-4fa9-8173-b1fedba1176c
--verbose --wait

gives "error: invalid argument: No device found for specified path".


<disk type='network' device='disk' snapshot='no'>
<driver name='qemu' type='qcow2' cache='none' error_policy='stop'
io='threads'/>
<source protocol='gluster' name='vmstore/912d9062-3881-47
9b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6
d8a4/027a3b37-77d4-4fa9-8173-b1fedba1176c'>
<host name='10.70.37.28' port='0'/>
</source>
<backingStore type='network' index='1'>
<format type='qcow2'/>
<source protocol='gluster' name='vmstore/912d9062-3881-47
9b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6
d8a4/d4c23ec6-20ce-4a2f-9b32-ca91e65a114a'>
<host name='10.70.37.28' port='0'/>
</source>
<backingStore type='network' index='2'>
<format type='raw'/>
<source protocol='gluster' name='vmstore/912d9062-3881-47
9b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6
d8a4/f5098809-e719-404b-8d80-3f824f4333a2'>
<host name='10.70.37.28' port='0'/>
</source>
<backingStore/>
</backingStore>
</backingStore>
<target dev='vda' bus='virtio'/>
<serial>27b0cbcb-4dfd-4eeb-8ab0-8fda54a6d8a4</serial>
<boot order='2'/>
<alias name='virtio-disk0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</disk>



thanks
sahina
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20161121/8a11a0a2/attachment.html>