|Anonymous | Login | Signup for a new account||2016-05-04 15:27 UTC|
|My View | View Issues | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005334||CentOS-6||virt-manager||public||2011-12-22 10:23||2015-04-21 16:10|
|Target Version||Fixed in Version|
|Summary||0005334: virt-manager doesn't launch anymore|
|Description||After the first launch of virt-manager, which worked as expected, i can not launch it again. I have to launch it with the dbus-launch command.|
# virt-manager --no-fork --debug
(same problem if i don't provide the "--no-fork --debug" options...)
2011-12-21 14:12:40,943 (virt-manager:175): Application startup
2011-12-21 14:12:40,943 (virt-manager:352): Launched as: /usr/share/virt-manager/virt-manager.py --no-fork --debug
2011-12-21 14:12:41,015 (config:34): Error importing spice: No module named SpiceClientGtk
2011-12-21 14:12:41,024 (virt-manager:462): Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ [^] for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-XaCLCqyiHN: Connection refused)
Traceback (most recent call last):
File "/usr/share/virt-manager/virt-manager.py", line 455, in <module>
File "/usr/share/virt-manager/virt-manager.py", line 390, in main
File "/usr/share/virt-manager/virtManager/config.py", line 99, in __init__
GError: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ [^] for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-XaCLCqyiHN: Connection refused)
I can lauch virt-manager with the following command.
# dbus-launch --exit-with-session virt-manager
|Steps To Reproduce||- launch virt-manager for the first time|
- close the application an try to launch it again
|Additional Information||I manage my kvm server from a windows xp client via putty + X11 forwarding and a cygwin xserver.|
The kvm server's X DISPLAY is exported to my windows client.
There's no desktop enviroment installed on the kvm server.
|Tags||No tags attached.|
Sorry, the product version is 6.2!
# cat /etc/redhat-release
CentOS release 6.2 (Final)
# uname -r
# rpm -qa | grep virt
|Same here and I can confirm the issue. Thanks for the workaround.|
|I have the same problem here.|
|Is the problem also there in 6.3?|
|yes it is|
|dbus-uuidgen > /var/lib/dbus/machine-id solved this issue for me, probably a dbus bug.|
|Maybe related to https://bugzilla.redhat.com/show_bug.cgi?id=598200 [^] .|
same problem here after fresh install, Problem occurred directly after the fresh install.
Hardware: Dell Poweredge 1950, 2 x XEON 5160
CentOS 6.3 via 'CentOS-6.3-x86_64-bin-DVD1.iso'
Select 'Virtual Host' during the Install-Package Group Selection.
After Install only eth1 activated, one run of 'yum update' and ntfs-3g installed (via EPEL).
One virtual guest created (WinXP fresh install from iso) and some start/stop playing with the new installed guest-OS.
Guest-OS shutdown, Host-OS (CentOS 6.3) reboot, and after the reboot of the Host-OS the descripted error occurred.
libvertd working correct (also able to start the guest-OS via virsh), only the virt-manager (and also virt-viewer) don't work.
The Problem was solved after the command given by demo007 (dbus-uuidgen > /var/lib/dbus/machine-id).
X-Server: Xming running on Windows7, virt-manager started via SSH Connection.
Maybe someone change the 'Product Version' to 6.3 ??
I am using 6.5 and 6.4, depending on the server. Both have the same problem. The "demo007" solution did not work. Any other suggestions would be appreciated.
Our configuration used xCAT, GPFS, NFS. I do an "ssh -Y" to get to the KVM host so that X can be forwarded. I had been periodically unable to run virt-manager directly, so ran started it via dbus-launch virt-manager. I am, however, able to use virt-viewer, and the problem with running virt-manager is now a solid failure.
I do have a 389-ds server running on a virtual client, and I can forward X from it. I just can't do it from this server.
|2011-12-22 10:23||dirk12345||New Issue|
|2011-12-22 10:48||dirk12345||Note Added: 0014006|
|2011-12-22 13:19||toracat||Product Version||6.1 => 6.2|
|2012-02-06 12:41||lhecking||Note Added: 0014410|
|2012-08-11 02:11||dcabot||Note Added: 0015626|
|2012-08-11 07:05||tigalch||Note Added: 0015627|
|2012-08-12 17:28||dcabot||Note Added: 0015628|
|2012-08-28 17:46||demo007||Note Added: 0015712|
|2012-08-29 01:40||toracat||Note Added: 0015713|
|2012-12-13 19:20||ta.innok||Note Added: 0016145|
|2015-04-21 16:10||snidley||Note Added: 0022853|
|Copyright © 2000 - 2016 MantisBT Team|