Comment 3 for bug 198957

On Fri, Mar 07, 2008 at 01:47:11AM -0000, <email address hidden> wrote:
> I removed the libvirt-bin package and the error appeared again after
> starting virtual manager and trying to connect. An error window
> entitled "Virtual Machine Manager Connection Failure" pops up with the
> following text:
> ----------------------------------------------------------------------------------------------
> Verify that: - The 'libvirtd' daemon has been started
>
> Unable to open connection to hypervisor URI 'qemu:///session':
> <class 'libvirt.libvirtError'> virConnectOpenReadOnly() failed
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/connection.py", line 306, in _open_thread
> self.vmm = libvirt.openReadOnly(self.uri)
> File "/usr/lib/python2.5/site-packages/libvirt.py", line 144, in openReadOnly
> if ret is None:raise libvirtError('virConnectOpenReadOnly() failed')
> libvirtError: virConnectOpenReadOnly() failed
> ------------------------------------------------------------------------------------------------

The error message even explicitly tells you that you should check if
libvirtd is running. It's not a library that's missing, you're just
trying to connect to a local libvirtd instance, but you have no such
thing (as you don't have libvirtd running). virt-manager doesn't *need*
a local libvirtd instance, as it can be used to manage remote ones
instead.

> Also, I notice that the libvirt0 package description has a typo too:
> "library for interfacing with differeny virtualization systems"

Ah, thanks. I'll fix that.

--
Soren Hansen |
Virtualisation specialist | Ubuntu Server Team
Canonical Ltd. | http://www.ubuntu.com/