I have been trying to use libgfapi glusterfs support in oVirt but can't get it to work. After talks on IRC it seems I should apply a patch (http://gerrit.ovirt.org/33768) to enable libgf BUT I can't get it to work. Systems used: - hosts Centos7 or Fedora20 (so upto date qemu/libvirt/oVirt(3.5)) - glusterfs-3.6.1 - vdsm-4.16.0-524.gitbc618a4.el7.x86_64 (snapshot master 14-nov) - vdsm-4.16.7-1.gitdb83943.el7.x86_64 (official ovirt-3.5 vdsm, seems newer than master snapshot?? ) Just adding the patch to vdsm-4.16.7-1.gitdb83943.el7.x86_64 doesn't work, vdsm doesn't start anymore due to an error in virt/vm.py. Q1: what is de exact status of libgf and oVirt. Q2: how do I test that patch? Joop
Hello Joop, thanks for raising the issue as it is one of the things I assumed are already implemented and working. Sadly I cannot provide any answer ... On 17.11.2014 09:39, Joop wrote:
I have been trying to use libgfapi glusterfs support in oVirt but can't get it to work. After talks on IRC it seems I should apply a patch (http://gerrit.ovirt.org/33768) to enable libgf BUT I can't get it to work. Systems used: - hosts Centos7 or Fedora20 (so upto date qemu/libvirt/oVirt(3.5)) - glusterfs-3.6.1 - vdsm-4.16.0-524.gitbc618a4.el7.x86_64 (snapshot master 14-nov) - vdsm-4.16.7-1.gitdb83943.el7.x86_64 (official ovirt-3.5 vdsm, seems newer than master snapshot?? )
Just adding the patch to vdsm-4.16.7-1.gitdb83943.el7.x86_64 doesn't work, vdsm doesn't start anymore due to an error in virt/vm.py.
Q1: what is de exact status of libgf and oVirt. Q2: how do I test that patch?
Joop
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Daniel Helgenberger m box bewegtbild GmbH P: +49/30/2408781-22 F: +49/30/2408781-10 ACKERSTR. 19 D-10115 BERLIN www.m-box.de www.monkeymen.tv Geschäftsführer: Martin Retschitzegger / Michaela Göllner Handeslregister: Amtsgericht Charlottenburg / HRB 112767
I'm replying to 'up' this as well as I'm most interested in this. I actually thought this was implemented and working too. On Mon, Nov 17, 2014 at 10:01 AM, Daniel Helgenberger < daniel.helgenberger@m-box.de> wrote:
Hello Joop,
thanks for raising the issue as it is one of the things I assumed are already implemented and working.
Sadly I cannot provide any answer ...
On 17.11.2014 09:39, Joop wrote:
I have been trying to use libgfapi glusterfs support in oVirt but can't get it to work. After talks on IRC it seems I should apply a patch (http://gerrit.ovirt.org/33768) to enable libgf BUT I can't get it to work. Systems used: - hosts Centos7 or Fedora20 (so upto date qemu/libvirt/oVirt(3.5)) - glusterfs-3.6.1 - vdsm-4.16.0-524.gitbc618a4.el7.x86_64 (snapshot master 14-nov) - vdsm-4.16.7-1.gitdb83943.el7.x86_64 (official ovirt-3.5 vdsm, seems newer than master snapshot?? )
Just adding the patch to vdsm-4.16.7-1.gitdb83943.el7.x86_64 doesn't work, vdsm doesn't start anymore due to an error in virt/vm.py.
Q1: what is de exact status of libgf and oVirt. Q2: how do I test that patch?
Joop
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Daniel Helgenberger m box bewegtbild GmbH
P: +49/30/2408781-22 F: +49/30/2408781-10
ACKERSTR. 19 D-10115 BERLIN
www.m-box.de www.monkeymen.tv
Geschäftsführer: Martin Retschitzegger / Michaela Göllner Handeslregister: Amtsgericht Charlottenburg / HRB 112767 _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
This is a multi-part message in MIME format. --------------070607040303030304040205 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit On 18-11-2014 20:57, Christopher Young wrote:
I'm replying to 'up' this as well as I'm most interested in this. I actually thought this was implemented and working too.
On Mon, Nov 17, 2014 at 10:01 AM, Daniel Helgenberger <daniel.helgenberger@m-box.de <mailto:daniel.helgenberger@m-box.de>> wrote:
Hello Joop,
thanks for raising the issue as it is one of the things I assumed are already implemented and working.
Sadly I cannot provide any answer ...
On 17.11.2014 09:39, Joop wrote: > I have been trying to use libgfapi glusterfs support in oVirt but can't > get it to work. After talks on IRC it seems I should apply a patch > (http://gerrit.ovirt.org/33768) to enable libgf BUT I can't get it to > work. Systems used: > - hosts Centos7 or Fedora20 (so upto date qemu/libvirt/oVirt(3.5)) > - glusterfs-3.6.1 > - vdsm-4.16.0-524.gitbc618a4.el7.x86_64 (snapshot master 14-nov) > - vdsm-4.16.7-1.gitdb83943.el7.x86_64 (official ovirt-3.5 vdsm, seems > newer than master snapshot?? ) > > Just adding the patch to vdsm-4.16.7-1.gitdb83943.el7.x86_64 doesn't > work, vdsm doesn't start anymore due to an error in virt/vm.py. > > Q1: what is de exact status of libgf and oVirt. > Q2: how do I test that patch?
I experimented a little more and found that if I create a VM in oVirt on a glusterfs storage domain and start it, it won't use libgfapi, BUT if I use virsh on the host where the VM runs and then add a disk the libgfapi way the VM will see the disk and can use it. So the underlying infra is capable of using libgf but oVirt isn't using it. Thats where the patch comes in I think but I can't get it to work. Q: how do I test that patch I'm able to get around gcc/patch/git etc so don't need a n00b step by step but a little how to get started is very welcome. Thanks in advance, Joop --------------070607040303030304040205 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit <html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 18-11-2014 20:57, Christopher Young wrote:<br> </div> <blockquote cite="mid:CAC1p533uzPA6m96oMFumCZobUeULVnuD5GT82wepCv1rwkfYnw@mail.gmail.com" type="cite"> <div dir="ltr">I'm replying to 'up' this as well as I'm most interested in this. I actually thought this was implemented and working too.</div> <div class="gmail_extra"><br> <div class="gmail_quote">On Mon, Nov 17, 2014 at 10:01 AM, Daniel Helgenberger <span dir="ltr"><<a moz-do-not-send="true" href="mailto:daniel.helgenberger@m-box.de" target="_blank">daniel.helgenberger@m-box.de</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Joop,<br> <br> thanks for raising the issue as it is one of the things I assumed are<br> already implemented and working.<br> <br> Sadly I cannot provide any answer ...<br> <div> <div class="h5"><br> On 17.11.2014 09:39, Joop wrote:<br> > I have been trying to use libgfapi glusterfs support in oVirt but can't<br> > get it to work. After talks on IRC it seems I should apply a patch<br> > (<a moz-do-not-send="true" href="http://gerrit.ovirt.org/33768" target="_blank">http://gerrit.ovirt.org/33768</a>) to enable libgf BUT I can't get it to<br> > work. Systems used:<br> > - hosts Centos7 or Fedora20 (so upto date qemu/libvirt/oVirt(3.5))<br> > - glusterfs-3.6.1<br> > - vdsm-4.16.0-524.gitbc618a4.el7.x86_64 (snapshot master 14-nov)<br> > - vdsm-4.16.7-1.gitdb83943.el7.x86_64 (official ovirt-3.5 vdsm, seems<br> > newer than master snapshot?? )<br> ><br> > Just adding the patch to vdsm-4.16.7-1.gitdb83943.el7.x86_64 doesn't<br> > work, vdsm doesn't start anymore due to an error in virt/vm.py.<br> ><br> > Q1: what is de exact status of libgf and oVirt.<br> > Q2: how do I test that patch?<br> </div> </div> </blockquote> </div> </div> </blockquote> I experimented a little more and found that if I create a VM in oVirt on a glusterfs storage domain and start it, it won't use libgfapi, BUT if I use virsh on the host where the VM runs and then add a disk the libgfapi way the VM will see the disk and can use it. So the underlying infra is capable of using libgf but oVirt isn't using it. Thats where the patch comes in I think but I can't get it to work.<br> <br> Q: how do I test that patch<br> <br> I'm able to get around gcc/patch/git etc so don't need a n00b step by step but a little how to get started is very welcome.<br> <br> Thanks in advance,<br> <br> Joop<br> <br> </body> </html> --------------070607040303030304040205--
----- Original Message -----
From: "noc" <noc@nieuwland.nl> To: users@ovirt.org Sent: Wednesday, November 19, 2014 9:36:28 AM Subject: Re: [ovirt-users] Status libgfapi support in oVirt
On 18-11-2014 20:57, Christopher Young wrote:
I'm replying to 'up' this as well as I'm most interested in this. I actually thought this was implemented and working too.
On Mon, Nov 17, 2014 at 10:01 AM, Daniel Helgenberger < daniel.helgenberger@m-box.de > wrote:
Hello Joop,
thanks for raising the issue as it is one of the things I assumed are already implemented and working.
Sadly I cannot provide any answer ...
On 17.11.2014 09:39, Joop wrote:
I have been trying to use libgfapi glusterfs support in oVirt but can't get it to work. After talks on IRC it seems I should apply a patch ( http://gerrit.ovirt.org/33768 ) to enable libgf BUT I can't get it to work. Systems used: - hosts Centos7 or Fedora20 (so upto date qemu/libvirt/oVirt(3.5)) - glusterfs-3.6.1 - vdsm-4.16.0-524.gitbc618a4.el7.x86_64 (snapshot master 14-nov) - vdsm-4.16.7-1.gitdb83943.el7.x86_64 (official ovirt-3.5 vdsm, seems newer than master snapshot?? )
Just adding the patch to vdsm-4.16.7-1.gitdb83943.el7.x86_64 doesn't work, vdsm doesn't start anymore due to an error in virt/vm.py.
Q1: what is de exact status of libgf and oVirt. Q2: how do I test that patch?
I experimented a little more and found that if I create a VM in oVirt on a glusterfs storage domain and start it, it won't use libgfapi, BUT if I use virsh on the host where the VM runs and then add a disk the libgfapi way the VM will see the disk and can use it. So the underlying infra is capable of using libgf but oVirt isn't using it. Thats where the patch comes in I think but I can't get it to work.
Correct. oVirt up until now didn't use libgfapi because of missing features (e.g. live snapshot). It seems that now all those gaps have been fixed and we're trying to re-enable libgfapi. I just mentioned that I uploaded an el6 build here: https://fsimonce.fedorapeople.org/vdsm-libgfapi/ and sources here (to rebuild on fedora): https://fsimonce.fedorapeople.org/vdsm-libgfapi/source/ Let me know if the most of you are using fedora and I'll make a build on fedora as well. Please let me know how it goes. Thanks, -- Federico
Is there an el7 build of this available too?
On Nov 19, 2014, at 9:50 AM, Federico Simoncelli <fsimonce@redhat.com> wrote:
----- Original Message -----
From: "noc" <noc@nieuwland.nl> To: users@ovirt.org Sent: Wednesday, November 19, 2014 9:36:28 AM Subject: Re: [ovirt-users] Status libgfapi support in oVirt
On 18-11-2014 20:57, Christopher Young wrote:
I'm replying to 'up' this as well as I'm most interested in this. I actually thought this was implemented and working too.
On Mon, Nov 17, 2014 at 10:01 AM, Daniel Helgenberger < daniel.helgenberger@m-box.de > wrote:
Hello Joop,
thanks for raising the issue as it is one of the things I assumed are already implemented and working.
Sadly I cannot provide any answer ...
On 17.11.2014 09:39, Joop wrote:
I have been trying to use libgfapi glusterfs support in oVirt but can't get it to work. After talks on IRC it seems I should apply a patch ( http://gerrit.ovirt.org/33768 ) to enable libgf BUT I can't get it to work. Systems used: - hosts Centos7 or Fedora20 (so upto date qemu/libvirt/oVirt(3.5)) - glusterfs-3.6.1 - vdsm-4.16.0-524.gitbc618a4.el7.x86_64 (snapshot master 14-nov) - vdsm-4.16.7-1.gitdb83943.el7.x86_64 (official ovirt-3.5 vdsm, seems newer than master snapshot?? )
Just adding the patch to vdsm-4.16.7-1.gitdb83943.el7.x86_64 doesn't work, vdsm doesn't start anymore due to an error in virt/vm.py.
Q1: what is de exact status of libgf and oVirt. Q2: how do I test that patch?
I experimented a little more and found that if I create a VM in oVirt on a glusterfs storage domain and start it, it won't use libgfapi, BUT if I use virsh on the host where the VM runs and then add a disk the libgfapi way the VM will see the disk and can use it. So the underlying infra is capable of using libgf but oVirt isn't using it. Thats where the patch comes in I think but I can't get it to work.
Correct. oVirt up until now didn't use libgfapi because of missing features (e.g. live snapshot). It seems that now all those gaps have been fixed and we're trying to re-enable libgfapi.
I just mentioned that I uploaded an el6 build here:
https://fsimonce.fedorapeople.org/vdsm-libgfapi/
and sources here (to rebuild on fedora):
https://fsimonce.fedorapeople.org/vdsm-libgfapi/source/
Let me know if the most of you are using fedora and I'll make a build on fedora as well.
Please let me know how it goes. Thanks, -- Federico _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 19-11-2014 23:44, Darrell Budic wrote:
Is there an el7 build of this available too?
That would be nice too. Forgot that I updated my test env to el7 to see if that helped. Can test on F20 @home tonight if needed. Gonna try something else first and will let you all know how that went. Joop
----- Original Message -----
From: "noc" <noc@nieuwland.nl> To: users@ovirt.org Sent: Thursday, November 20, 2014 8:46:01 AM Subject: Re: [ovirt-users] Status libgfapi support in oVirt
On 19-11-2014 23:44, Darrell Budic wrote:
Is there an el7 build of this available too?
That would be nice too. Forgot that I updated my test env to el7 to see if that helped. Can test on F20 @home tonight if needed. Gonna try something else first and will let you all know how that went.
I've prepared a fedora 20 build as well: https://fsimonce.fedorapeople.org/vdsm-libgfapi/fc20/ -- Federico
On 19-11-2014 16:50, Federico Simoncelli wrote:
----- Original Message -----
From: "noc" <noc@nieuwland.nl> To: users@ovirt.org Sent: Wednesday, November 19, 2014 9:36:28 AM Subject: Re: [ovirt-users] Status libgfapi support in oVirt
On 18-11-2014 20:57, Christopher Young wrote:
I'm replying to 'up' this as well as I'm most interested in this. I actually thought this was implemented and working too.
On Mon, Nov 17, 2014 at 10:01 AM, Daniel Helgenberger < daniel.helgenberger@m-box.de > wrote:
Hello Joop,
thanks for raising the issue as it is one of the things I assumed are already implemented and working.
Sadly I cannot provide any answer ...
On 17.11.2014 09:39, Joop wrote:
I have been trying to use libgfapi glusterfs support in oVirt but can't get it to work. After talks on IRC it seems I should apply a patch ( http://gerrit.ovirt.org/33768 ) to enable libgf BUT I can't get it to work. Systems used: - hosts Centos7 or Fedora20 (so upto date qemu/libvirt/oVirt(3.5)) - glusterfs-3.6.1 - vdsm-4.16.0-524.gitbc618a4.el7.x86_64 (snapshot master 14-nov) - vdsm-4.16.7-1.gitdb83943.el7.x86_64 (official ovirt-3.5 vdsm, seems newer than master snapshot?? )
Just adding the patch to vdsm-4.16.7-1.gitdb83943.el7.x86_64 doesn't work, vdsm doesn't start anymore due to an error in virt/vm.py.
Q1: what is de exact status of libgf and oVirt. Q2: how do I test that patch? I experimented a little more and found that if I create a VM in oVirt on a glusterfs storage domain and start it, it won't use libgfapi, BUT if I use virsh on the host where the VM runs and then add a disk the libgfapi way the VM will see the disk and can use it. So the underlying infra is capable of using libgf but oVirt isn't using it. Thats where the patch comes in I think but I can't get it to work. Correct. oVirt up until now didn't use libgfapi because of missing features (e.g. live snapshot). It seems that now all those gaps have been fixed and we're trying to re-enable libgfapi.
I just mentioned that I uploaded an el6 build here:
https://fsimonce.fedorapeople.org/vdsm-libgfapi/
and sources here (to rebuild on fedora):
https://fsimonce.fedorapeople.org/vdsm-libgfapi/source/
Let me know if the most of you are using fedora and I'll make a build on fedora as well.
Please let me know how it goes. Thanks, I did a quick setup of a nestedvt el6 host and, tried to, ran a vm on it with a disk on a glusterfs SD and the following is part of the output taken from vdsm.log when the VM starts up.
<disk device="disk" snapshot="no" type="network"> <address bus="0x00" domain="0x0000" function="0x0" slot="0x06" type="pci"/> <source name="GlusterTest/0a0db70d-40a7-4ccc-8a87-efeead3e01aa/images/730aac8b-3233-4d28-8245-6c2bb3269a97/8d997c07-1ac9-4d72-868c-3178c7d7c1f1" protocol="gluster"> <host name="st01.nieuwland.nl" port="0" transport="tcp"/> </source> <target bus="virtio" dev="vda"/> <serial>730aac8b-3233-4d28-8245-6c2bb3269a97</serial> <boot order="1"/> <driver cache="none" error_policy="stop" io="threads" name="qemu" type="raw"/> </disk> The VM doesn't start but that can be caused by my L2 virt OR that the <host name = .. port="0" ... > is wrong. Shouldn't there be a port in the 24007 or 49152 range? Will try the F20 build on my home system and see if that goes better. Thanks for the help sofar, Joop
On 21-11-2014 9:47, noc wrote:
The VM doesn't start but that can be caused by my L2 virt OR that the <host name = .. port="0" ... > is wrong. Shouldn't there be a port in the 24007 or 49152 range?
Sorry, forgot to install vdsm-gluster. Starting the VM on an el6 host now works and still the same line with the port=0 so that doesn't seem to matter. OK, back to setting up a el6 host except when you generate a el7 version too which would be awesome 8-) . Regards, Joop
----- Original Message -----
From: "noc" <noc@nieuwland.nl> To: users@ovirt.org Sent: Friday, November 21, 2014 10:01:30 AM Subject: Re: [ovirt-users] Status libgfapi support in oVirt
On 21-11-2014 9:47, noc wrote:
The VM doesn't start but that can be caused by my L2 virt OR that the <host name = .. port="0" ... > is wrong. Shouldn't there be a port in the 24007 or 49152 range?
Sorry, forgot to install vdsm-gluster. Starting the VM on an el6 host now works and still the same line with the port=0 so that doesn't seem to matter.
OK, back to setting up a el6 host except when you generate a el7 version too which would be awesome 8-) .
I updated the packages (rebasing on a newer master) and I provided an el7 build as well: https://fsimonce.fedorapeople.org/vdsm-libgfapi/ These rpms are less tested than the previous ones but the rebase was straight forward. -- Federico
On 21-11-2014 23:25, Federico Simoncelli wrote:
I updated the packages (rebasing on a newer master) and I provided an el7 build as well: https://fsimonce.fedorapeople.org/vdsm-libgfapi/ These rpms are less tested than the previous ones but the rebase was straight forward. Testing will be done first thing mondag morning.
Thanks, Joop
On 23-11-2014 10:23, Joop wrote:
On 21-11-2014 23:25, Federico Simoncelli wrote:
I updated the packages (rebasing on a newer master) and I provided an el7 build as well: https://fsimonce.fedorapeople.org/vdsm-libgfapi/ These rpms are less tested than the previous ones but the rebase was straight forward. Testing will be done first thing mondag morning.
Install went fine, starting vdsm too but running a VM doesn't work on el7, error: libvirtError: internal error: process exited while connecting to monitor: Warning: option deprecated, use lost_tick_policy property of kvm-pit instead. Thread-67::DEBUG::2014-11-24 14:02:52,955::vm::2200::vm.Vm::(setDownStatus) vmId=`7c7e68b2-6e25-4008-9a8e-857026562ee6`::Changed state to Down: internal error: process exited while connecting to monitor: Warning: option deprecated, use lost_tick_policy property of kvm-pit instead. Joop
On 24-11-2014 14:05, noc wrote:
On 23-11-2014 10:23, Joop wrote:
On 21-11-2014 23:25, Federico Simoncelli wrote:
I updated the packages (rebasing on a newer master) and I provided an el7 build as well: https://fsimonce.fedorapeople.org/vdsm-libgfapi/ These rpms are less tested than the previous ones but the rebase was straight forward. Testing will be done first thing mondag morning.
Install went fine, starting vdsm too but running a VM doesn't work on el7, error: libvirtError: internal error: process exited while connecting to monitor: Warning: option deprecated, use lost_tick_policy property of kvm-pit instead. Thread-67::DEBUG::2014-11-24 14:02:52,955::vm::2200::vm.Vm::(setDownStatus) vmId=`7c7e68b2-6e25-4008-9a8e-857026562ee6`::Changed state to Down: internal error: process exited while connecting to monitor: Warning: option deprecated, use lost_tick_policy property of kvm-pit instead.
A bit more info was in /var/log/libvirt/qemu/foreman02.log 2014-11-24 15:09:12.897+0000: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name foreman02 -S -machine rhel6.5.0,accel=kvm,usb=off -cpu Conroe,+vmx -m 2048 -realtime mlock=off -smp 2,maxcpus=32,sockets=16,cores=2,threads=1 -uuid 7c7e68b2-6e25-4008-9a8e-857026562ee6 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=7-0.1406.el7.centos.2.5,serial=435A4336-3437-435A-4336-343732315044,uuid=7c7e68b2-6e25-4008-9a8e-857026562ee6 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/foreman02.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2014-11-24T15:09:12,driftfix=slew -no-kvm-pit-reinjection -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x5 -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x6 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=gluster://st01.nieuwland.nl/GlusterTest/0a0db70d-40a7-4ccc-8a87-efeead3e01aa/images/7801a3f5-0815-41c5-9c8c-b500e8927c7b/0552eafc-522e-4c06-b3eb-8f6a7dab0f68,if=none,id=drive-virtio-disk0,format=raw,serial=7801a3f5-0815-41c5-9c8c-b500e8927c7b,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:cf:cf:bc,bus=pci.0,addr=0x3,bootindex=2 -netdev tap,fd=27,id=hostnet1,vhost=on,vhostfd=28 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=00:1a:4a:cf:cf:c9,bus=pci.0,addr=0x4,bootindex=3 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/7c7e68b2-6e25-4008-9a8e-857026562ee6.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/7c7e68b2-6e25-4008-9a8e-857026562ee6.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0 -vnc 192.168.216.153:0,password -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 Warning: option deprecated, use lost_tick_policy property of kvm-pit instead. [2014-11-24 15:09:13.069041] E [rpc-clnt.c:362:saved_frames_unwind] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x186)[0x7f0f46d79396] (--> /lib64/libgfrpc.so.0(saved_frames_unwind+0x1de)[0x7f0f49e30fce] (--> /lib64/libgfrpc.so.0(saved_frames_destroy+0xe)[0x7f0f49e310de] (--> /lib64/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x82)[0x7f0f49e32a42] (--> /lib64/libgfrpc.so.0(rpc_clnt_notify+0x48)[0x7f0f49e331f8] ))))) 0-GlusterTest-client-0: forced unwinding frame type(GF-DUMP) op(DUMP(1)) called at 2014-11-24 15:09:13.055308 (xid=0x3) qemu-kvm: -drive file=gluster://st01.nieuwland.nl/GlusterTest/0a0db70d-40a7-4ccc-8a87-efeead3e01aa/images/7801a3f5-0815-41c5-9c8c-b500e8927c7b/0552eafc-522e-4c06-b3eb-8f6a7dab0f68,if=none,id=drive-virtio-disk0,format=raw,serial=7801a3f5-0815-41c5-9c8c-b500e8927c7b,cache=none,werror=stop,rerror=stop,aio=threads: Gluster connection failed for server=st01.nieuwland.nl port=0 volume=GlusterTest image=0a0db70d-40a7-4ccc-8a87-efeead3e01aa/images/7801a3f5-0815-41c5-9c8c-b500e8927c7b/0552eafc-522e-4c06-b3eb-8f6a7dab0f68 transport=tcp qemu-kvm: -drive file=gluster://st01.nieuwland.nl/GlusterTest/0a0db70d-40a7-4ccc-8a87-efeead3e01aa/images/7801a3f5-0815-41c5-9c8c-b500e8927c7b/0552eafc-522e-4c06-b3eb-8f6a7dab0f68,if=none,id=drive-virtio-disk0,format=raw,serial=7801a3f5-0815-41c5-9c8c-b500e8927c7b,cache=none,werror=stop,rerror=stop,aio=threads: could not open disk image gluster://st01.nieuwland.nl/GlusterTest/0a0db70d-40a7-4ccc-8a87-efeead3e01aa/images/7801a3f5-0815-41c5-9c8c-b500e8927c7b/0552eafc-522e-4c06-b3eb-8f6a7dab0f68: Could not open 'gluster://st01.nieuwland.nl/GlusterTest/0a0db70d-40a7-4ccc-8a87-efeead3e01aa/images/7801a3f5-0815-41c5-9c8c-b500e8927c7b/0552eafc-522e-4c06-b3eb-8f6a7dab0f68': No data available 2014-11-24 15:09:13.163+0000: shutting down I also had forgotten to install vdsm-gluster but even after installing and rebooting the host, still the same error. Joop
On 11/24/2014 08:44 PM, noc wrote:
Warning: option deprecated, use lost_tick_policy property of kvm-pit instead. [2014-11-24 15:09:13.069041] E [rpc-clnt.c:362:saved_frames_unwind] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x186)[0x7f0f46d79396] (--> /lib64/libgfrpc.so.0(saved_frames_unwind+0x1de)[0x7f0f49e30fce] (--> /lib64/libgfrpc.so.0(saved_frames_destroy+0xe)[0x7f0f49e310de] (--> /lib64/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x82)[0x7f0f49e32a42] (--> /lib64/libgfrpc.so.0(rpc_clnt_notify+0x48)[0x7f0f49e331f8] ))))) 0-GlusterTest-client-0: forced unwinding frame type(GF-DUMP) op(DUMP(1)) called at 2014-11-24 15:09:13.055308 (xid=0x3)
This seems to indicate that the handshake with glusterfs server failed. Can you please post glusterfs logs from the server specified in the gluster:// URI? Thanks, Vijay
On 24-11-2014 19:43, Vijay Bellur wrote:
On 11/24/2014 08:44 PM, noc wrote:
Warning: option deprecated, use lost_tick_policy property of kvm-pit instead. [2014-11-24 15:09:13.069041] E [rpc-clnt.c:362:saved_frames_unwind] (--> /lib64/libglusterfs.so.0(_gf_log_callingfn+0x186)[0x7f0f46d79396] (--> /lib64/libgfrpc.so.0(saved_frames_unwind+0x1de)[0x7f0f49e30fce] (--> /lib64/libgfrpc.so.0(saved_frames_destroy+0xe)[0x7f0f49e310de] (--> /lib64/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x82)[0x7f0f49e32a42] (--> /lib64/libgfrpc.so.0(rpc_clnt_notify+0x48)[0x7f0f49e331f8] ))))) 0-GlusterTest-client-0: forced unwinding frame type(GF-DUMP) op(DUMP(1)) called at 2014-11-24 15:09:13.055308 (xid=0x3)
This seems to indicate that the handshake with glusterfs server failed. Can you please post glusterfs logs from the server specified in the gluster:// URI?
Thanks, Vijay Stopped all gluster processes and removed all logs, restarted gluster and tried to start the VM. All logs from /var/log/glusterfs are here: http://en.file-upload.net/download-9899941/gluster-logs.tar.gz.html
Thanks, Joop
Thanks to Vijay its working now. Big omission on my side for not double checking the options on the volumes used. So bottom line: both el6 and el7 builds pass the 'startup VM' test, now to some more serious testing. Thanks to all, Joop
Any chance of an update for the 4.16.10 build from ybrohoni yesterday? Or has this made it into the nightlies yet?
On Nov 21, 2014, at 4:25 PM, Federico Simoncelli <fsimonce@redhat.com> wrote:
I updated the packages (rebasing on a newer master) and I provided an el7 build as well:
https://fsimonce.fedorapeople.org/vdsm-libgfapi/
These rpms are less tested than the previous ones but the rebase was straight forward.
-- Federico _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
----- Original Message -----
From: "Joop" <jvdwege@xs4all.nl> To: users@ovirt.org Sent: Monday, November 17, 2014 9:39:36 AM Subject: [ovirt-users] Status libgfapi support in oVirt
I have been trying to use libgfapi glusterfs support in oVirt but can't get it to work. After talks on IRC it seems I should apply a patch (http://gerrit.ovirt.org/33768) to enable libgf BUT I can't get it to work. Systems used: - hosts Centos7 or Fedora20 (so upto date qemu/libvirt/oVirt(3.5)) - glusterfs-3.6.1 - vdsm-4.16.0-524.gitbc618a4.el7.x86_64 (snapshot master 14-nov) - vdsm-4.16.7-1.gitdb83943.el7.x86_64 (official ovirt-3.5 vdsm, seems newer than master snapshot?? )
Just adding the patch to vdsm-4.16.7-1.gitdb83943.el7.x86_64 doesn't work, vdsm doesn't start anymore due to an error in virt/vm.py.
Q1: what is de exact status of libgf and oVirt. Q2: how do I test that patch?
Rebasing and applying patches could be tricky sometimes and if you got an error in virt/vm.py it is most likely because the patch didn't apply cleanly. I prepared a build (el6) here: https://fsimonce.fedorapeople.org/vdsm-libgfapi/ In case you want to try it on fedora you just need to get the source rpm here: https://fsimonce.fedorapeople.org/vdsm-libgfapi/source/ and rebuild it on fedora. Let me know if you have any problem. -- Federico
participants (7)
-
Christopher Young -
Daniel Helgenberger -
Darrell Budic -
Federico Simoncelli -
Joop -
noc -
Vijay Bellur