[libvirt-users] virt-manager slow to connect, hangs on new host dialog
Hello, I am using virt-manager 0.9.4 on a Debian unstable system (libvirt 0.9.12) to connect to a libvirtd via SSH running on a Debian testing system (also version 0.9.12), and I have a problem using virt-manager, which first takes ages to connect, then freezes. The SSH connection is top-quality, the hosts are next to each other and connected by Gigabit Ethernet. virsh connections work fine. Unfortunately, when I run virt-manager and connect to the host, the host's capabilities are fetched very quickly (according to virt-manager's debug output), but it then takes 20–30 seconds until the connection is established. Logging libvirtd with log_level=2 produces nothing useful. Hence I tried with log_level=1, which is mayhem. Attached is the log output from the moment I told virt-manager to connect until shortly after the connection has been established. Maybe someone can figure out what's going on? I cannot… The next problem is that when I then try to create a host, I am shown the dialog and can enter one or two characters into the name field, then the GUI completely freezes, and so does libvirtd on the other system (ctrl-c does not work anymore). I have also captured this part of the session in a second log file, which provides no clues for me. Does anyone else know what might be going on? Thanks, -- martin | http://madduck.net/ | http://two.sentenc.es/ "es ist immer etwas wahnsinn in der liebe. es ist aber auch immer etwas vernunft im wahnsinn." - friedrich nietzsche spamtraps: madduck.bogus@madduck.net
Hi Martin. Can you please share the string that you use to invoke virt-manager? I use this one: virt-manager -c qemu+ssh://user@kvm/system?netcat=netcatsocket And in the KVM hypervisor server I edited /bin/netcatsocket with below content: #!/bin/bash socat - unix-client:$2 2013/4/3 martin f krafft <madduck@madduck.net>
Hello,
I am using virt-manager 0.9.4 on a Debian unstable system (libvirt 0.9.12) to connect to a libvirtd via SSH running on a Debian testing system (also version 0.9.12), and I have a problem using virt-manager, which first takes ages to connect, then freezes.
The SSH connection is top-quality, the hosts are next to each other and connected by Gigabit Ethernet. virsh connections work fine.
Unfortunately, when I run virt-manager and connect to the host, the host's capabilities are fetched very quickly (according to virt-manager's debug output), but it then takes 20–30 seconds until the connection is established.
Logging libvirtd with log_level=2 produces nothing useful. Hence I tried with log_level=1, which is mayhem. Attached is the log output from the moment I told virt-manager to connect until shortly after the connection has been established. Maybe someone can figure out what's going on? I cannot…
The next problem is that when I then try to create a host, I am shown the dialog and can enter one or two characters into the name field, then the GUI completely freezes, and so does libvirtd on the other system (ctrl-c does not work anymore).
I have also captured this part of the session in a second log file, which provides no clues for me.
Does anyone else know what might be going on?
Thanks,
-- martin | http://madduck.net/ | http://two.sentenc.es/
"es ist immer etwas wahnsinn in der liebe. es ist aber auch immer etwas vernunft im wahnsinn." - friedrich nietzsche
spamtraps: madduck.bogus@madduck.net
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
also sprach Javi Legido <javi@legido.com> [2013.04.03.1659 +0200]:
Can you please share the string that you use to invoke virt-manager?
virt-manager --no-dbus --no-fork --debug --connect qemu+ssh://charade/system
virt-manager -c qemu+ssh://user@kvm/system?netcat=netcatsocket socat - unix-client:$2
I get exactly the same behaviour with this wrapper of socat. -- martin | http://madduck.net/ | http://two.sentenc.es/ "it always takes longer than you expect, even when you take into account hofstadter's law." -- douglas hofstadter spamtraps: madduck.bogus@madduck.net
Hi Martin. I assume that you: 1. Arranged netcatsocket on the KVM hypervisor 2. Tried virt-manager -c qemu+ssh://user@charade/system?netcat=netcatsocket, adjusting "user" and "charade" (your KVM hypervisor I assume) 3. You got the same behaviour In this case I'm sorry but I will not be useful, I would say something obvious: some kind of network problem. Regards. Javier 2013/4/3 martin f krafft <madduck@madduck.net>
also sprach Javi Legido <javi@legido.com> [2013.04.03.1659 +0200]:
Can you please share the string that you use to invoke virt-manager?
virt-manager --no-dbus --no-fork --debug --connect qemu+ssh://charade/system
virt-manager -c qemu+ssh://user@kvm/system?netcat=netcatsocket socat - unix-client:$2
I get exactly the same behaviour with this wrapper of socat.
-- martin | http://madduck.net/ | http://two.sentenc.es/
"it always takes longer than you expect, even when you take into account hofstadter's law." -- douglas hofstadter
spamtraps: madduck.bogus@madduck.net
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
also sprach Javi Legido <javi@legido.com> [2013.04.03.1722 +0200]:
In this case I'm sorry but I will not be useful, I would say something obvious: some kind of network problem.
Unfortunately, virsh works just fine. I cannot imagine where there would be a network problem and why it would manifest like this. Anyone else? -- martin | http://madduck.net/ | http://two.sentenc.es/ if god is perfect, why did he create discontinuous functions? spamtraps: madduck.bogus@madduck.net
also sprach martin f krafft <madduck@madduck.net> [2013.04.03.2005 +0200]:
Unfortunately, virsh works just fine. I cannot imagine where there would be a network problem and why it would manifest like this.
I just tried to reproduce my problem on another machine, which works fine and which also runs libvirt 0.9.12. I simulated very low bandwidth and high packet loss, but the problem did not appear. I also tried running virt-manager (0.9.4) on other machines, and the problem exists wrt the host in question from all clients, whether libvirt 0.9.12 or 1.0.4. The question remains: what is it about this Debian testing machine running libvirt 0.9.12 that exhibits this issue? -- martin | http://madduck.net/ | http://two.sentenc.es/ "politics is the entertainment branch of industry." -- frank zappa spamtraps: madduck.bogus@madduck.net
also sprach martin f krafft <madduck@madduck.net> [2013.04.03.1606 +0200]:
Unfortunately, when I run virt-manager and connect to the host, the host's capabilities are fetched very quickly (according to virt-manager's debug output), but it then takes 20–30 seconds until the connection is established.
This isn't fixed, but…
The next problem is that when I then try to create a host, I am shown the dialog and can enter one or two characters into the name field, then the GUI completely freezes, and so does libvirtd on the other system (ctrl-c does not work anymore).
This was apparently due to my definition of a default network (172.27.0.0/24) on the "any physical interface" using NAT. Once I removed this network, I could create test machines. This may or may not be due to the fact that one of my interfaces is slave to a bridge (eth0 slaves to the "wan" bridge). However, in the interfaces dropdown of the network creation dialog, only eth0 shows up. -- martin | http://madduck.net/ | http://two.sentenc.es/ a bachelor is a man who never made the same mistake once. spamtraps: madduck.bogus@madduck.net
also sprach martin f krafft <madduck@madduck.net> [2013.04.03.2055 +0200]:
The next problem is that when I then try to create a host, I am shown the dialog and can enter one or two characters into the name field, then the GUI completely freezes, and so does libvirtd on the other system (ctrl-c does not work anymore).
This was apparently due to my definition of a default network (172.27.0.0/24) on the "any physical interface" using NAT. Once I removed this network, I could create test machines.
Negative, the problem is back, but there are no networks defined currently. It was a red herring… :( -- martin | http://madduck.net/ | http://two.sentenc.es/ if god had meant for us to be naked, we would have been born that way. spamtraps: madduck.bogus@madduck.net
also sprach martin f krafft <madduck@madduck.net> [2013.04.03.2126 +0200]:
Negative, the problem is back, but there are no networks defined currently. It was a red herring…
Sorry for the flood. I just saw this in the virt-manager debug output, maybe it provides a clue? (engine:279): Tick is slow, not running at requested rate. Seems like this has something to do with it. But what? -- martin | http://madduck.net/ | http://two.sentenc.es/ "es ist gut, eine sache doppelt auszudrücken und ihr einen rechten und linken fuß zu geben. auf einem bein kann die wahrheit zwar stehen; mit zweien aber wird sie gehen und herumkommen." -- friedrich nietzsche spamtraps: madduck.bogus@madduck.net
participants (2)
-
Javi Legido -
martin f krafft