[Pkg-libvirt-maintainers] Bug#650711: Bug#650711: virt-manager gets stuck

[Guido Günther]

On Fri, Dec 02, 2011 at 09:20:29AM +0100, Harald Dunkel wrote:
> Package: virt-manager
> Version: 0.9.0-3
> 
> I have 7 remote hosts connected to virt-manager (using ssh).
> Problem: At start time virt-manager gets stuck for at least
> 20 minutes. During this time the GUI is completely unresponsive
> and doesn't refresh.
> 
> I see the ssh sessions in a local "ps -ef" while it is stuck:
> 
> % ps -ef | grep virt
> root      2382     1  0 Nov27 ?        00:00:00 /usr/sbin/libvirtd -d
> hdunkel  10411     1  0 15:58 ?        00:00:00 python /usr/share/virt-manager/virt-manager.py
> hdunkel  10415 10411  0 15:58 ?        00:00:00 ssh -l hdunkel srvl025 sh -c 'if nc -q 2>&1 | grep "requires an argument" >/dev/null 2>&1; then     ARG=-q0;fi;nc $ARG -U /var/run/libvirt/libvirt-sock'
> hdunkel  10418 10411  0 15:58 ?        00:00:00 ssh -l hdunkel srvl026 sh -c 'if nc -q 2>&1 | grep "requires an argument" >/dev/null 2>&1; then     ARG=-q0;fi;nc $ARG -U /var/run/libvirt/libvirt-sock'
> hdunkel  10419 10411  0 15:58 ?        00:00:00 ssh -l hdunkel srvl022 sh -c 'if nc -q 2>&1 | grep "requires an argument" >/dev/null 2>&1; then     ARG=-q0;fi;nc $ARG -U /var/run/libvirt/libvirt-sock'
> hdunkel  10422 10411  0 15:58 ?        00:00:00 ssh -l hdunkel srvl024 sh -c 'if nc -q 2>&1 | grep "requires an argument" >/dev/null 2>&1; then     ARG=-q0;fi;nc $ARG -U /var/run/libvirt/libvirt-sock'
> hdunkel  10424 10411  0 15:58 ?        00:00:00 ssh -l hdunkel srvl021 sh -c 'if nc -q 2>&1 | grep "requires an argument" >/dev/null 2>&1; then     ARG=-q0;fi;nc $ARG -U /var/run/libvirt/libvirt-sock'
> hdunkel  10425 10411  0 15:58 ?        00:00:00 ssh -l hdunkel srvl014 sh -c 'if nc -q 2>&1 | grep "requires an argument" >/dev/null 2>&1; then     ARG=-q0;fi;nc $ARG -U /var/run/libvirt/libvirt-sock'
> hdunkel  10427 10411  0 15:58 ?        00:00:00 ssh -l hdunkel srvl023 sh -c 'if nc -q 2>&1 | grep "requires an argument" >/dev/null 2>&1; then     ARG=-q0;fi;nc $ARG -U /var/run/libvirt/libvirt-sock'
> hdunkel  10429 10119  0 15:58 pts/0    00:00:00 grep virt
> 
> 
> On the remote side I see "nc -q0 -U /var/run/libvirt/libvirt-sock"
> running, as expected. /bin/nc is netcat-openbsd.
> 
> The socket is readable and writable on all remote hosts:
> 
> % ls -al /var/run/libvirt/libvirt-sock
> srwxrwx--- 1 root libvirt 0 Nov 27 11:02 /var/run/libvirt/libvirt-sock
> 
> The account I use for ssh is member of the libvirt group.
> 
> 
> This is a highly annoying problem, because I usually don't
> touch the virtual machines, unless there is an urgent issue.
> Having to wait for an unresponsive GUI when its urgent is
> extremely frustrating.
> 
> The virt-manager in Squeeze shows the same problem.
> 
> Any workaround or helpful comment would be highly appreciated.
The first thing would be

	http://wiki.debian.org/libvirt#Bugreports.2BAC8-Debugging

This might indicate a cause for the hang.
Cheers,
 -- Guido