Hi, I'm sure if here is the right place to ask this but let me go ... I'm running a Xen server (version 3.1 compiled) on Linux Debian Lenny that I'd install virt-manager by package of lenny repository. I've installed 'libvirt-bin, libvirt0 and python-libvirt' version 0.4.0-2. At '/etc/xen/xend-config.sxp' I had : <config> #(xend-http-server no) (xend-unix-server yes) #(xend-tcp-xmlrpc-server no) (xend-unix-xmlrpc-server yes) #(xend-relocation-server no) (xend-relocation-server yes) </config> When I try to connect to xen server, on localhost, I get back the error bellow. My question is if I have to enable something on xen server to get this working. <error> Unable to open connection to hypervisor URI 'xen:///': libvirt.libvirtError virConnectOpenReadOnly() failed could not connect to xen:/// Traceback (most recent call last): File "/usr/local/share/virt-manager/virtManager/connection.py", line 305, in _open_thread self.vmm = libvirt.openReadOnly(self.uri) File "/usr/local/lib/python2.4/site-packages/libvirt.py", line 132, in openReadOnly if ret is None:raise libvirtError('virConnectOpenReadOnly() failed') libvirtError: virConnectOpenReadOnly() failed could not connect to xen:/// </error> Looking at /root/.virt-manager/virt-manager.log I get these mensagens: <virt-manager.log> [Wed, 23 Jan 2008 19:06:50 virt-manager 5070] INFO (virt-manager:126) Application startup [Wed, 23 Jan 2008 19:06:52 virt-manager 5071] DEBUG (engine:74) About to connect to uris ['xen:///'] [Wed, 23 Jan 2008 19:06:52 virt-manager 5071] WARNING (virt-manager:282) Could not get connection to session bus, disabling DBus service dbus.exceptions.DBusException org.freedesktop.DBus.Error.NoReply: 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. [Wed, 23 Jan 2008 19:07:00 virt-manager 5071] DEBUG (connection:292) Scheduling background open thread for xen:/// [Wed, 23 Jan 2008 19:07:00 virt-manager 5071] DEBUG (connection:299) Background thread is running [Wed, 23 Jan 2008 19:07:00 virt-manager 5071] ERROR (connection:324) Unable to open connection to hypervisor URI 'xen:///': libvirt.libvirtError virConnectOpenReadOnly() failed could not connect to xen:/// Traceback (most recent call last): File "/usr/local/share/virt-manager/virtManager/connection.py", line 306, in _open_thread self.vmm = libvirt.openReadOnly(self.uri) File "/usr/local/lib/python2.4/site-packages/libvirt.py", line 132, in openReadOnly if ret is None:raise libvirtError('virConnectOpenReadOnly() failed') libvirtError: virConnectOpenReadOnly() failed could not connect to xen:/// [Wed, 23 Jan 2008 19:07:00 virt-manager 5071] DEBUG (connection:328) Background open thread complete, scheduling notify [Wed, 23 Jan 2008 19:07:00 virt-manager 5071] DEBUG (connection:337) Notifying open result </virt-manager.log> -- "o animal satisfeito dorme". - Guimarăes Rosa