Hi, all I created DC, use GlusterFS as the domain type. And created Storage, with storage type "Data/GlusterFS" But VM used FUSE mount point, are not used qemu-glusterfs native integration When i looked at the running KVM processes, i saw -drive file=/rhev/data-center/mnt/ glusterSD/vdsm01.cn.local: local/35c541ad-bd48-4000-ad8f-8539629b7d75/images/9f3ecc5d-5d82-4e83-a89e-b298725e1d63/6a621ecc-715d-4a15-982c-05c618eefd36 But I expect to see -drive file=gluster+tcp:// Fodora 19 oVirt 3.3.4 libvirt 1.0.5 qemu-kvm 1.4.2 _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On Mon, 2014-03-24 at 18:21 -0400, Itamar Heim wrote: > On 03/17/2014 03:18 AM, Андрей Брагин wrote: > > Hi, all > > > > I created DC, use GlusterFS as the domain type. > > And created Storage, with storage type "Data/GlusterFS" > > But VM used FUSE mount point, are not used qemu-glusterfs native integration > > > > When i looked at the running KVM processes, i saw > > -drive file=/rhev/data-center/mnt/ > > glusterSD/vdsm01.cn.local: > > local/35c541ad-bd48-4000-ad8f-8539629b7d75/images/9f3ecc5d-5d82-4e83-a89e-b298725e1d63/6a621ecc-715d-4a15-982c-05c618eefd36 > > > > But I expect to see > > -drive file=gluster+tcp:// > > > > > > Fodora 19 > > oVirt 3.3.4 > > libvirt 1.0.5 > > qemu-kvm 1.4.2 > yes, this is the current behavior, we are waiting on a few libvirt found > gaps in the libgfapi support to re-enable it. > _______________________________________________ Has this been re-enabled in 3.4? Can't find the specific patch but this bug ( <https://bugzilla.redhat.com/show_bug.cgi?id=1017289>https://bugzilla.r...) appears to be fixed.