| Summary: | virt-manager tries to connect to qemu and does not get connected at all times. | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Balaji G <balajig81> | ||||||||||||
| Component: | virt-manager | Assignee: | Cole Robinson <crobinso> | ||||||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | urgent | Docs Contact: | |||||||||||||
| Priority: | urgent | ||||||||||||||
| Version: | 16 | CC: | berrange, crobinso, dougsland, dpierce, hbrock, jforbes, matt, nandanlbhat, ronderode, Shurik, tcamuso, virt-maint | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2012-01-27 18:09:36 UTC | Type: | --- | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Balaji G
2011-11-28 03:16:54 UTC
I am seeing somewhat similar behaviour on my system. Virt-Manager remains frozen in perpetuity with a message: localhost(QEMU) - Connecting... With debugging messages enabled, I get the messages as in virt-manager-debug.txt (attached) With virsh, I get the messages as in virsh-debug.txt (attached). I have enabled logging in /etc/libvirt/libvirt.conf with the line log_outputs="1:file:/var/log/libvirt/libvirtd.log" libvirtd.log-201112121232 is attached. There is a line in /var/log/messages Dec 12 12:27:37 nandan libvirtd: Could not find keytab file: /etc/libvirt/krb5.tab: No such file or directory I have also observed the delayed shutdown behaviour. I have been shutting down using the hardware power button whenever that happens (intermittently). Created attachment 545605 [details]
Logging output from libvirt
Created attachment 545606 [details]
systemctl status libvirtd.service output
Created attachment 545607 [details]
debug output of virsh
Created attachment 545608 [details]
virt-manager --debug output
Similar problem. After some update and reboot I can not connect to libvirt neither virt-manager nor virsh. Restart of libvirt service or restart computer does not help. And, yes, computer can't correctly shutdown. My workaround. 1. Backup contents of /etc/libvirt 2. Total erase of virt-manager/qemu*/libvirt* (its overkill, but I am angry :) ) 3. reboot 4. Install qemu/virt-manager/libvirt 5. Start virt-manager 6. ??? 7. PROFIT!!! (I can manage my virtual machines from virt-manager/virsh and can correctly shutdown host machine.) Sorry... my soft config. Linux Host.bfg-10k.ru 3.1.5-2.fc16.x86_64 #1 SMP Mon Dec 12 21:25:51 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux virt-manager.noarch 0.9.0-7.fc16 virt-manager-common.noarch 0.9.0-7.fc16 libvirt.x86_64 0.9.6-2.fc16 libvirt-client.x86_64 0.9.6-2.fc16 libvirt-python.x86_64 0.9.6-2.fc16 Hmm, strange. Anyone still seeing this with latest f16 packages? Can everyone confirm that as root, virsh --connect qemu:///system is hanging as well? Yes, I am seeing virt-manager hang with all the latest f16 updates. The following command ... # virsh --connect qemu:///system ... gives the following warning. # virsh -vv --connect qemu:///system I have similar problems on Red Hat Enterprise Linux 6.2 which is running under Vmware Workstation 8.0. On version 6.1 everything works fine.
Linux maui.example.com 2.6.32-220.2.1.el6.x86_64 #1 SMP Tue Dec 13 16:21:34 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
qemu-kvm-0.12.1.2-2.209.el6_2.1.x86_64
libvirt-python-0.9.4-23.el6_2.4.x86_64
libvirt-0.9.4-23.el6_2.4.x86_64
libvirt-client-0.9.4-23.el6_2.4.x86_64
virt-manager-0.9.0-7.el6.x86_64
Virtual Machine Manager and virsh are unable to open a connection to the libvirt management daemon. So "virsh --connect qemu:///system" is hanging as well.
When initiation a connection the Virtual Machine Manager and virsh stay in a state of "connection" which doesn't finish. ("localhost (QEMU) - connecting...")
Another sympton is that after the previous has occurred, the server won't shutdown properly after initiating a shutdown and hangs at the following state: "Restarting...Running guests on default URI:"
When restarting the libvirtd service before shutting down, the server shuts down properly and doesn't hang on "Restarting...Running guests on default URI:"
This problem occurs as well as with the default RHEL 6.2 installation as with currently updated qemu, virt-manager and libvirt versions
The following reinstall method didn't resolve the problem:
"yum groupremove virtualization "virtualization client" "virtualization tools" "virtualization platform"
"yum groupinstall virtualization "virtualization client" "virtualization tools" "virtualization platform"
Can anyone provide the following info: - Desktop environment you are using (gnome, kde, lxde, etc) - While virsh --connect qemu:///system is hanging, please provide output of 'ps axwww' run from another terminal (note to self: looking for polkit running, or udevadm running) - Does running system-config-printer, and selecting the menu entry 'Server->Settings' similarly hang? That is also using polkit I'm running Gnome in 2D mode. I've been keeping up with updates, and it seems that a recent yum update sequence has somewhat mitigated the problem. I am now able to connect to qemu:///system from virt-manager, but it occasionally drops off and I have to reconnect. At least it's not hanging anymore. Thanks Tony, the dropped connection issue is another known issue that I'm working on. I'll close this bug as WORKSFORME, but if anyone else is still seeing this problem, please reopen this bug, providing the info in comment #11. Created attachment 564733 [details] ps axwww output Requested in Comment 11 Running FC16 x86_64 as guest in VMware Workstation 8 (with virtualised Intel VT-x/EPT) Desktop env is fallback gnome Attached output of ps axwww above system-config-printer polkit works as expected. I have tried setting the libvirtd auth settings to none - it still hangs on connect. Matt, what's the output of virsh --connect qemu:///system from a terminal? Hi Cole. There is no output when running that command (even with --debug). I am running the command as root. Matt Here's a backtrace of virsh as it tries to connect. This means nothing to me, but will hopefully be of some use to someone!
#0 0x00007f7b902c6ab8 in __GI___poll (fds=0x7fff7fd4ee20, nfds=2, timeout=<optimized out>)
at ../sysdeps/unix/sysv/linux/poll.c:83
#1 0x00007f7b92a35ab5 in virNetClientIOEventLoop (client=0x7f7b92f71010, thiscall=0x15ea470) at rpc/virnetclient.c:899
#2 0x00007f7b92a36f04 in virNetClientIO (thiscall=0x15ea470, client=0x7f7b92f71010) at rpc/virnetclient.c:1136
#3 virNetClientSend (client=0x7f7b92f71010, msg=<optimized out>, expectReply=true) at rpc/virnetclient.c:1218
#4 0x00007f7b92a37678 in virNetClientProgramCall (prog=0x15edc10, client=0x7f7b92f71010, serial=0, proc=66,
args_filter=0x7f7b90302940 <__GI_xdr_void>, args=0x0, ret_filter=0x7f7b92a324a0 <xdr_remote_auth_list_ret>,
ret=0x7fff7fd4f180) at rpc/virnetclientprogram.c:291
#5 0x00007f7b92a1bb23 in call (conn=<optimized out>, priv=0x15eb5f0, flags=<optimized out>, proc_nr=66,
args_filter=<optimized out>, args=<optimized out>, ret_filter=0x7f7b92a324a0 <xdr_remote_auth_list_ret>,
ret=0x7fff7fd4f180 "") at remote/remote_driver.c:4111
#6 0x00007f7b92a29a30 in remoteAuthenticate (authtype=0x0, auth=0x7f7b92db64c0, priv=0x15eb5f0, conn=0x15edaf0)
at remote/remote_driver.c:2405
#7 doRemoteOpen (conn=0x15edaf0, priv=0x15eb5f0, auth=0x7f7b92db64c0, flags=0) at remote/remote_driver.c:649
#8 0x00007f7b92a2de5b in remoteOpen (conn=0x15edaf0, auth=0x7f7b92db64c0, flags=<optimized out>)
at remote/remote_driver.c:828
#9 0x00007f7b929ee1b1 in do_open (name=0x15e86a0 "qemu:///system", auth=0x7f7b92db64c0, flags=0) at libvirt.c:1073
#10 0x00007f7b929f02a6 in virConnectOpenAuth (name=0x15e86a0 "qemu:///system", auth=0x7f7b92db64c0, flags=0)
at libvirt.c:1299
#11 0x0000000000409ca1 in vshInit (ctl=0x7fff7fd4f610) at virsh.c:15508
#12 main (argc=<optimized out>, argv=0x7fff7fd4f7b8) at virsh.c:16205
No output as in it just exits? Doesn't connect at all? Any different if trying that command as a regular user? If virsh isn't working, please open a new libvirt bug to track the issue there. Sorry - It hangs, until such time as you ^C - Same with normal user. Will open a new bug as directed, thanks. Libvirt bug raised: Bug 796451 |