unable to connect to libvirt. no connection driver available for qemu:///system

English Virtualization
#1

I’ve installed xen from yast, When I try to create a new VM I get this error:


unable to connect to libvirt.

no connection driver available for qemu:///system

Libvirt URI is: qemu:///system

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 1054, in _open_thread
    self._backend.open(self._do_creds_password)
  File "/usr/share/virt-manager/virtinst/connection.py", line 158, in open
    open_flags)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 105, in openAuth
    if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: no connection driver available for qemu:///system

I have installed Qemu and more things about virtualization, but the error remains.

any help?

thank you

#2

I’ve found the most common solution is that you should update your system with the following command, then reboot.

zypper up

TSU

#3

I did the up and the error changed:


Unable to connect to libvirt.

internal error: Cannot find suitable emulator for x86_64

Libvirt URI is: qemu:///system

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 1111, in _open_notify
    logging.debug("conn version=%s", self._backend.conn_version())
  File "/usr/share/virt-manager/virtinst/connection.py", line 294, in conn_version
    self._conn_version = self._libvirtconn.getVersion()
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3697, in getVersion
    if ret == -1: raise libvirtError ('virConnectGetVersion() failed', conn=self)
libvirtError: internal error: Cannot find suitable emulator for x86_64

So, I’ve checked if libvirt daemon is running. Yast services manager says it is. Asking services manager “show details” of libvirt daemon


 libvirtd.service - Virtualization daemon    Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled)    Active: active (running) since Thu 2016-02-04 00:20:30 CET; 21min ago      Docs: man:libvirtd(8)            http://libvirt.org  Main PID: 1704 (libvirtd)    CGroup: /system.slice/libvirtd.service            `-1704 /usr/sbin/libvirtd --listen 
Feb 04 00:20:33 andromeda libvirtd[1704]: Failed to probe capabilities for /usr/bin/qemu-system-i386: internal error: Child process (LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /usr/bin/qemu-system-i386 -help) unexpected exit status 127: /usr/bin/qemu-system-i386: symbol lookup error: /usr/bin/qemu-system-i386: undefined symbol: libusb_free_ss_endpoint_companion_descriptor Feb 04 00:20:33 andromeda libvirtd[1704]: internal error: Child process (LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /usr/bin/qemu-kvm -help) unexpected exit status 127: /usr/bin/qemu-system-x86_64: symbol lookup error: /usr/bin/qemu-system-x86_64: undefined symbol: libusb_free_ss_endpoint_companion_descriptor Feb 04 00:20:33 andromeda libvirtd[1704]: Failed to probe capabilities for /usr/bin/qemu-kvm: internal error: Child process (LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /usr/bin/qemu-kvm -help) unexpected exit status 127: /usr/bin/qemu-system-x86_64: symbol lookup error: /usr/bin/qemu-system-x86_64: undefined symbol: libusb_free_ss_endpoint_companion_descriptor Feb 04 00:20:33 andromeda libvirtd[1704]: internal error: Child process (LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /usr/bin/qemu-system-x86_64 -help) unexpected exit status 127: /usr/bin/qemu-system-x86_64: symbol lookup error: /usr/bin/qemu-system-x86_64: undefined symbol: libusb_free_ss_endpoint_companion_descriptor Feb 04 00:20:33 andromeda libvirtd[1704]: Failed to probe capabilities for /usr/bin/qemu-system-x86_64: internal error: Child process (LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /usr/bin/qemu-system-x86_64 -help) unexpected exit status 127: /usr/bin/qemu-system-x86_64: symbol lookup error: /usr/bin/qemu-system-x86_64: undefined symbol: libusb_free_ss_endpoint_companion_descriptor Feb 04 00:20:33 andromeda libvirtd[1704]: internal error: Child process (LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /usr/bin/qemu-kvm -help) unexpected exit status 127: /usr/bin/qemu-system-x86_64: symbol lookup error: /usr/bin/qemu-system-x86_64: undefined symbol: libusb_free_ss_endpoint_companion_descriptor Feb 04 00:20:33 andromeda libvirtd[1704]: Failed to probe capabilities for /usr/bin/qemu-kvm: internal error: Child process (LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /usr/bin/qemu-kvm -help) unexpected exit status 127: /usr/bin/qemu-system-x86_64: symbol lookup error: /usr/bin/qemu-system-x86_64: undefined symbol: libusb_free_ss_endpoint_companion_descriptor Feb 04 00:38:46 andromeda libvirtd[1704]: internal error: Cannot find suitable emulator for x86_64 Feb 04 00:38:46 andromeda libvirtd[1704]: internal error: Cannot find suitable emulator for x86_64 Feb 04 00:38:47 andromeda libvirtd[1704]: internal error: Cannot find suitable emulator for x86_64

I read here same error in debian caused because MplabX (which I am also using) installed it own libusb in /usr/local/lib


andromeda:/usr/local/lib # ls -l |grep libusb
lrwxrwxrwx 1 root root     47 Sep 22  2014 libmchpusb-1.0.so -> /opt/microchip/mplabcomm1.0/libusb-1.0.so.0.0.0
lrwxrwxrwx 1 root root     17 Jan 30  2012 libusb-1.0.so.0 -> libmchpusb-1.0.so

yes, it is there in my system too.

I delete it


andromeda:/usr/local/lib # rm libusb-1.0.so.0
andromeda:/usr/local/lib #

restarting libvirt daemon didn’t fix the problem.

Here there is another solution for Opensuse, but


andromeda:/home/fernando # zypper --non-interactive in libusb-1_0-0
Loading repository data...
Reading installed packages...
'libusb-1_0-0' is already installed.
No update candidate for 'libusb-1_0-0-1.0.19-2.1.2.x86_64'. The highest available version is already installed.
Resolving package dependencies...

Nothing to do.
andromeda:/home/fernando #

and it continues failling

#4

Ideally, you should have done a system update immediately after your new install (assuming you’re using DVD source) and before installing virtualization. In fact that should always be SOP for all new installs.

You can try force re-installing libvirt

zypper in -f libvirt

Is this a brand new openSUSE 13.2 host? If it is, then I’d seriously considering a complete re-install from the beginning again, followed by the “zypper up” and only then install virtualization… That’s because even if you might eventually repair your current situation, there is always a possibility that some latent issue might continue to exist and pop up later.

When I build virtualization platforms, I apply an extremely high priority to Host stability and reliability because any insecurity or instability affects the Guests running on that machine.

TSU

#5

Hi
from fresh new first install on SLES
sp3 i got exactly the same error message !!
I have try the re install without succes
I saw in console network not available
regards ??
regards

#6

Hi
Network was avalaible when i stop inetd ???

Regards

#7

Although possible,
It’s problematic that a problem on a different version of openSUSE more than 2 years ago would be solved the same way.
It’s better to create a post starting your own new thread, and if you wish reference the older Forum thread.

Also,
Since this is an issue related to the HostOS (not Guest) and on SLES, this should be posted to the SLES Forums, not here in openSUSE.

TSU