Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am using a KVM host, while i execute "virt-manager",
i am unable to see it started.
Here is what i get it the virt-manager logs
[root@APP1 ~]# tail /root/.virt-manager/virt-manager.log
[Thu, 24 Dec 2015 12:39:08 virt-manager 26454] DEBUG (virt-manager:308) virtManager import: <module 'virtManager' from '/usr/share/virt-manager/virtManager/__init__.pyc'>
[Thu, 24 Dec 2015 12:39:34 virt-manager 26454] ERROR (virt-manager:407) 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: Could not send message to GConf daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Traceback (most recent call last):
File "/usr/share/virt-manager/virt-manager.py", line 400, in <module>
main()
File "/usr/share/virt-manager/virt-manager.py", line 329, in main
config = virtManager.config.vmmConfig(appname, appversion, glade_dir)
File "/usr/share/virt-manager/virtManager/config.py", line 98, in __init__
self.conf.add_dir(self.conf_dir, gconf.CLIENT_PRELOAD_NONE)
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: Could not send message to GConf daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
I would google for the error. There might be a bug, e.g. https://bugs.centos.org/view.php?id=5334. You don't say which distro or version you are using, perhaps you need to upgrade?
I am using a KVM host, while i execute "virt-manager",
i am unable to see it started.
Here is what i get it the virt-manager logs
[root@APP1 ~]# tail /root/.virt-manager/virt-manager.log
[Thu, 24 Dec 2015 12:39:08 virt-manager 26454] DEBUG (virt-manager:308) virtManager import: <module 'virtManager' from '/usr/share/virt-manager/virtManager/__init__.pyc'>
[Thu, 24 Dec 2015 12:39:34 virt-manager 26454] ERROR (virt-manager:407) 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: Could not send message to GConf daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Traceback (most recent call last):
File "/usr/share/virt-manager/virt-manager.py", line 400, in <module>
main()
File "/usr/share/virt-manager/virt-manager.py", line 329, in main
config = virtManager.config.vmmConfig(appname, appversion, glade_dir)
File "/usr/share/virt-manager/virtManager/config.py", line 98, in __init__
self.conf.add_dir(self.conf_dir, gconf.CLIENT_PRELOAD_NONE)
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: Could not send message to GConf daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Can anyone help please?
You're trying to run the GUI as root...which isn't allowed. This goes nicely with your unregistered RHEL thread...and this is why you pay for RHEL, since you could then call them for support.
In any event, running the GUI as root is NOT a good thing. And if you're logged in as a 'regular' user, and running that program from the terminal as root, root doesn't have access to the X system.
Thanks for your suggestions on this. I forgot to mention the distro, which is RHEL 6.6. I would not prefer an upgrade of RHEL.
Looking at the logs that are posted above, can anyone suggest any solutions?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
