FS#57237 - [libvirt] Clients hang upon connecting to libvirtd

Attached to Project: Community Packages
Opened by Bart (pawn) - Friday, 26 January 2018, 23:27 GMT
Last edited by Christian Rebischke (Shibumi) - Friday, 16 February 2018, 06:37 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Rebischke (Shibumi)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:

I came across this bug when virt-manager was suddenly unable to connect to libvirtd. The connection doesn't fail, it just doesn't complete[1]. virsh hangs as well.

I spoke with the people over at #virt on irc.oftc.net, they never heard about this occuring while there is at least one other Arch user for which it occurs. This leads me to believe it is Arch-specific.

Additional info:
* verbose output of libvirtd, trying to connect does not result in more log entires, process ended with SIGTERM https://bpaste.net/raw/e73227067218
* gdb output of running libvirtd https://bpaste.net/raw/267ca94bddda
* strace output https://bpaste.net/raw/b3358b9d031d

Steps to reproduce:

1. Install libvirt
2. Add user to libvirt group as per https://wiki.archlinux.org/index.php/Libvirt#Set_up_authentication
3. Enable libvirtd service as per https://wiki.archlinux.org/index.php/Libvirt#Daemon
4. Reboot
5. Connect to libvirtd using virsh -c qemu:///system or by starting virt-manager

Connection will hang if the bug occurs.


[1]: https://bbs.archlinux.org/viewtopic.php?id=206050
This task depends upon

Closed by  Christian Rebischke (Shibumi)
Friday, 16 February 2018, 06:37 GMT
Reason for closing:  Not a bug
Comment by Bart (pawn) - Friday, 26 January 2018, 23:30 GMT
I put the wrong link to the forums, here is the correct one: https://bbs.archlinux.org/viewtopic.php?id=231728

Note that the user 'SOLVED' the issue by re-installing Arch Linux.
Comment by Christian Rebischke (Shibumi) - Sunday, 28 January 2018, 19:49 GMT
Hello,
Could you please update libvirt-python to libvirt-python 4.0.0-1?
I guess thats the reason for the issues.
Comment by Bart (pawn) - Monday, 29 January 2018, 13:10 GMT
$ pacman -Q | grep libvirt
libvirt 4.0.0-1
libvirt-glib 1.0.0-1
libvirt-python2 4.0.0-1

Thanks for the suggestion. The issue remains, alas.
I'm guessing it's not possible to reproduce then. Is there anything else I can try or provide?
Comment by John Doe (phanta) - Thursday, 08 February 2018, 04:01 GMT
I also have this issue.
Same symptoms as described in the forum, all packages are the newest versions.
Let me know if there's some way I can help.
Comment by NM (sttal) - Tuesday, 13 February 2018, 16:52 GMT
Same issue here.
When trying to connect with virt-manager it hangs on connecting.

libvirt 4.0.0-1
libvirt-glib 1.0.0-1
libvirt-python2 4.0.0-1
Comment by NM (sttal) - Friday, 16 February 2018, 00:32 GMT
Just noticed the strangest thing. I also cannot connect to firewalld with firewall-cmd and gui client having the same symptoms as when connecting to libvirt. Could it be ebtables or some other common dependency broken?

Edit:

Removed /var/lib/ebtables/lock and everything started working.
Comment by Christian Rebischke (Shibumi) - Friday, 16 February 2018, 06:37 GMT
Thanks.. So I guess this bug ticket can be closed.

Loading...