libvirt does not start because libusb_get_port_numbers symbol is undefined

[Florian]

When trying to use kvm, in particular creating VM with virt-manager, i get in the GUI the error message "Error:No hypervisor options were found for this connection."

When looking into /var/log/libvirt/libvirtd.log, I see
info : libvirt version: 1.2.2
error : virCommandWait:2399 : internal error: Child process (LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/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_get_port_numbers
(see attachment for more details)

when trying to identify the libusb version, I get:

> ls -la $(ldd /usr/bin/qemu-system-x86_64 | grep usb)
lrwxrwxrwx 1 root root 19 May 6 2014 /lib/libusb-1.0.so.0 -> libusb-1.0.so.0.1.0
lrwxrwxrwx 1 root root 26 Jan 3 2014 /usr/lib/x86_64-linux-gnu/libusbredirparser.so.1 -> libusbredirparser.so.1.0.0

>apt-cache policy libusb-1.0-0
libusb-1.0-0:
  Installed: 2:1.0.17-1ubuntu2
  Candidate: 2:1.0.17-1ubuntu2
  Version table:
 *** 2:1.0.17-1ubuntu2 0
        500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

I got the same with an Ubuntu Server 14.04LTS.
I am using an up-to-date Ubuntu 14.04LTS (desktop).
qemu was installed with
>sudo apt-get install qemu-kvm libvirt-bin bridge-utils virt-manager

details:
>lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04
> uname -sr
Linux 3.8.0-19-generic
>sudo kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used

>apt-cache policy qemu-kvm
qemu-kvm:
  Installed: 2.0.0+dfsg-2ubuntu1.10
  Candidate: 2.0.0+dfsg-2ubuntu1.10
  Version table:
 *** 2.0.0+dfsg-2ubuntu1.10 0
        500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.0.0+dfsg-2ubuntu1.9 0
        500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
     2.0.0~rc1+dfsg-0ubuntu3 0
        500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

[Serge Hallyn (serge-hallyn)]

Thanks for reporting this bug. Could you please show the results of:

ldd /usr/bin/qemu-system-i386 |grep usb

dpkg -l | grep libusb

[Florian (florian-perrodin)]

Here are the requested informations:

$ ldd /usr/bin/qemu-system-i386 |grep usb
 libusb-1.0.so.0 => /lib/libusb-1.0.so.0 (0x00007fdcf11e6000)
 libusbredirparser.so.1 => /usr/lib/x86_64-linux-gnu/libusbredirparser.so.1 (0x00007fdcf0fde000)

$ dpkg -l | grep libusb
ii libgusb2:amd64 0.1.6-5 amd64 GLib wrapper around libusb1
ii libusb-0.1-4:amd64 2:0.1.12-23.3ubuntu1 amd64 userspace USB programming library
ii libusb-1.0-0:amd64 2:1.0.17-1ubuntu2 amd64 userspace USB programming library
ii libusb-1.0-0-dev:amd64 2:1.0.17-1ubuntu2 amd64 userspace USB programming library development files
ii libusb-1.0-doc 2:1.0.17-1ubuntu2 all documentation for userspace USB programming
ii libusbredirparser1:amd64 0.6-2ubuntu1 amd64 Parser for the usbredir protocol (runtime)

[Serge Hallyn (serge-hallyn)]

Could you show the results of:

strings /lib/x86_64-linux-gnu/libusb-1.0.so.0.1.0 | grep libusb_get_p

[Serge Hallyn (serge-hallyn)]

Just to be sure you do also get this error if you just type

/usr/bin/qemu-system-x86_64 -vnc :1

?

[Florian (florian-perrodin)]

Thank you for your answers, Serge. Hereafter are the information:

> strings /lib/x86_64-linux-gnu/libusb-1.0.so.0.1.0 | grep libusb_get_p
libusb_get_port_number
libusb_get_parent
libusb_get_port_numbers
libusb_get_port_path
libusb_get_pollfds
libusb_get_port_numbers

> /usr/bin/qemu-system-x86_64 -vnc :1
/usr/bin/qemu-system-x86_64: symbol lookup error: /usr/bin/qemu-system-x86_64: undefined symbol: libusb_get_port_numbers

but strangely:
strings /lib/libusb-1.0.so.0.1.0 | grep libusb_get_p
libusb_get_port_number
libusb_get_parent
libusb_get_port_path
libusb_get_pollfds

By checking the modified date, and finding all files that have been modified the exact same day, it turns out that it was a third-party software ( XIMEA video camera) that installed this library... (installed on all my computers)
Thanks for the help, and sorry for wasting your time...