[libvirt-users] Libvirt and Glusterfs

[Vijay Bellur]

On 07/09/2013 08:18 PM, Olivier Mauras wrote:
> On 2013-07-09 09:40, Vijay Bellur wrote:
>
>>> Hi, I'm trying to use qemu native glusterfs integration with libvirt.
>>> It's all working well from the qemu side, but libvirt fails to start
>>> a domain with a gluster drive or attach a drive. I have exactly the
>>> same error as this person:
>>> https://www.redhat.com/archives/libvirt-users/2013-April/msg00204.html I
>>> use qemu 1.5.1 with glusterfs 3.4 beta 4 and libvirt 1.0.6. [root
>>> bbox ~]# virsh start test error: Failed to start domain test error:
>>> internal error process exited while connecting to monitor: char
>>> device redirected to /dev/pts/3 (label charserial0)
>>> qemu-system-x86_64: -drive
>>> file=gluster://127.0.0.1/vol0/test0.img,if=none,id=drive-virtio-disk1,format=raw:
>>> Gluster connection failed for server=127.0.0.1 port=0 volume=vol0
>>> image=test0.img transport=tcp qemu-system-x86_64: -drive
>>> file=gluster://127.0.0.1/vol0/test0.img,if=none,id=drive-virtio-disk1,format=raw:
>>> could not open disk image gluster://127.0.0.1/vol0/test0.img: No data
>>> available
>> Do you observe errors in the logs from gluster bricks that make up vol0?
>> Brick logs are available at /var/log/glusterfs/bricks.
>>
>> Thanks,
>> Vijay
>
> Hi Vijay,
>
> Thanks for your answer.
> I did reset the files and tried to attach the device using: virsh
> attach-device test /tmp/gluster_disk.xml
> <disk type='network' device='disk'>
>        <driver name='qemu' type='raw' cache='none'/>
>        <source protocol='gluster' name='vol0/test0.img'>
>          <host name='127.0.0.1' transport='tcp' />
>        </source>
>        <target dev='vdb' bus='virtio'/>
>              <address type='pci' domain='0x0000' bus='0x00' slot='0x07'
> function='0x0'/>
>      </disk>
>
> # virsh attach-device test /tmp/gluster_disk.xml
> error: Failed to attach device from /tmp/gluster_disk.xml
> error: operation failed: open disk image file failed
>
>
> Sadly, nothing reported in ...bricks/*.log
>

Do you notice anything in glusterd.log? Can you try by performing the 
following configuration changes:

1) gluster volume set vol0 server.allow-insecure on

2) Edit /etc/glusterfs/glusterd.vol to contain this line:
option rpc-auth-allow-insecure on

Post 2), restarting glusterd would be necessary.

Thanks,
Vijay