[Pkg-libvirt-maintainers] Bug#593365: Bug#593365: Virt-manager with libvirt 0.8.2-1 can't connect to server running Lenny anymore

Jeroen Dekkers jeroen at dekkers.ch
Thu Oct 7 19:51:12 UTC 2010


Hi Guido,

At Fri, 1 Oct 2010 10:00:45 +0200,
Guido Günther wrote:
> It checks three error conditions but only sets an error message for one
> of them. Can I ask you to try the attached patch against 0.4.6 and see
> if it changes the error message? This should get us closer to the cause.

I get this error (from virt-manager.log): 

libvirtError: internal error Cannot find suitable hypervisor
 
> What version of kvm are you running on the Lenny system? I assume the
> one from Lenny? Could you also check if deinstalling it and running qemu
> instead does any difference?

When I remove kvm and install qemu it works. If I install kvm again
it works too. But when I remove qemu, I get the same error again.

This small script gives the same error:

===
#!/usr/bin/python

import libvirt
import sys

conn = libvirt.open("qemu+ssh://root@beppe/system")
if conn == None:
    print 'Failed to open connection to the hypervisor'
    sys.exit(1)

print conn.getVersion()
===

That outputs:

===
libvir: QEMU error : internal error Cannot find suitable hypervisor
Traceback (most recent call last):
  File "./test.py", line 11, in <module>
    ret = conn.getVersion()
  File "/usr/lib/python2.6/dist-packages/libvirt.py", line 1784, in getVersion
    if ret == -1: raise libvirtError ('virConnectGetVersion() failed', conn=self)
libvirt.libvirtError: internal error Cannot find suitable hypervisor
===

The strange thing is that when I run the script with 0.8.1, I get:

===
libvir: Remote error : unmarshalling remote_error
Traceback (most recent call last):
  File "./test.py", line 11, in <module>
    print conn.getVersion()
  File "/usr/lib/python2.6/dist-packages/libvirt.py", line 1681, in getVersion
    if ret == -1: raise libvirtError ('virConnectGetVersion() failed', conn=self)
libvirt.libvirtError: unmarshalling remote_error
===

Googling for that error message turns up that it's a bug in 0.8.1 that
should be fixed in 0.8.2. But virt-manager works fine with 0.8.1...


Regards,

Jeroen





More information about the Pkg-libvirt-maintainers mailing list