Lin Lancaster schrieb:
Check some of the earlier posts. There is a problem with the /etc/hosts file not having the definition of the machine name for 127.0.0.1 stopping the virt-manager from opening after installing the updates.
Do you mean the thread with the subject "error when trying to connect with virt-manager"? The solution seems to be the same as in https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=216975.
Unfortunately, this does not resolve my issues. [root@ws2 fs]# cat /etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. ::1 ws2.schwarz.lokal localhost localhost.localdomain 127.0.0.1 ws2.schwarz.lokal localhost localhost.localdomain
I suspect, it has something to do with GCONF/D-Bus:
[root@ws2 fs]# virt-manager & [1] 14202 [root@ws2 fs]# ps u USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND (..) root 13675 0.0 0.0 65264 1612 pts/5 S 21:32 0:00 bash root 14202 19.0 0.6 316252 22648 pts/5 S 22:02 0:00 python /usr/share/virt-manager/virt-manager.py root 14204 10.5 0.1 87936 4972 pts/5 S 22:02 0:00 /usr/libexec/gconfd-2 8 root 14205 0.0 0.0 64684 952 pts/5 R+ 22:02 0:00 ps u [root@ws2 fs]#
So gconf is started but after that, it waits for something. Can the D-bus be blocked by some faulty application?
fs
On Fri, Dec 01, 2006 at 10:05:46PM +0100, Felix Schwarz wrote:
Lin Lancaster schrieb:
Check some of the earlier posts. There is a problem with the /etc/hosts file not having the definition of the machine name for 127.0.0.1 stopping the virt-manager from opening after installing the updates.
Do you mean the thread with the subject "error when trying to connect with virt-manager"? The solution seems to be the same as in https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=216975.
I will be pushing an update to fix this bug very shortly. I discovered the flaw in some code which did hostname lookups without dealing with possible errors which can be thrown.
Regards, Dan.
Daniel P. Berrange schrieb:
I will be pushing an update to fix this bug very shortly. I discovered the flaw in some code which did hostname lookups without dealing with possible errors which can be thrown.
My problems still exist with dbus 1.0.1-2.fc6. However, I hope it is solved by https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=216674.
fs
Felix Schwarz wrote:
My problems still exist with dbus 1.0.1-2.fc6. However, I hope it is solved by https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=216674.
The correct bug is https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=219257 and at least on my system dbus-glib-0.70-6 fixes the problem.