On Sat, 05 Mar 2016 11:16:21 +0100
Michal Privoznik wrote:
>>This looks like a dying session daemon to me. You can check if my
>suspicion is right by running the session daemon by hand. From a console
>run:
>
>$ /usr/sbin/libvirtd
>
>Usually, connecting to qemu:///session does the same, except it appends
>'--timeout=30' to tell the session daemon to die after 30 seconds of
>inactivity. And here's the problem - there should be a keepalive running
>preventing daemon from dying.
>
libvirt-1.3.1
root@deus:~/bin#> ps aux | grep libvirtd
pedja 3122 0.0 0.0 1027672 2376 ? Sl Mar03 0:03 /usr/sbin/libvirtd --timeout=30
root 19814 0.0 0.1 1298708 5500 ? Sl Mar03 0:00 /usr/sbin/libvirtd -d -v -f /etc/libvirt/libvirtd.conf -p /var/run/libvirt/libvirtd.pid
-------
libvirt-git-92ec2e5
root@deus:~/bin#> ps aux | grep libvirtd
root 13553 0.0 0.4 972948 16552 ? Sl 16:02 0:00 /usr/sbin/libvirtd -d -v -f /etc/libvirt/libvirtd.conf -p /var/run/libvirt/libvirtd.pid
pedja 13723 0.0 0.4 965248 18508 ? Sl 16:03 0:00 /usr/sbin/libvirtd --timeout=30
-------
libvirt-1.3.2
root@deus:~/bin#> ps aux | grep libvirtd
root 16778 0.3 0.3 383212 15700 ? Sl 17:10 0:00 /usr/sbin/libvirtd -d -v -f /etc/libvirt/libvirtd.conf -p /var/run/libvirt/libvirtd.pid
pedja 16975 3.2 0.4 637588 17964 ? Sl 17:11 0:00 /usr/sbin/libvirtd --timeout=30
Only the session daemon from libvirt-1.3.2 dies randomly, 1.3.1 and libvirt-git-92ec2e5 are stable (no disconnects).
I managed to hook gdb to session daemon above after a few tries, and gdb log ('thread apply all bt')
and virsh.log are attached.
I'll be running libvirt from git master for now, but I have both it and 1.3.2 built with debug symbols, if you need more information.
Pedja
Attachment:
libvirt-1.3.2-gdb.log.bz2
Description: application/bzip
Attachment:
virsh-1.3.2.log.bz2
Description: application/bzip
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
