On Wed, 27 Jul 2016, Guido Günther wrote: > control: retitle -1 fails to activate qemu hypervisor with error > "libvirt_driver_qemu.so: undefined symbol: > virStorageFileCreatelibvirt-daemon" > > On Wed, Jul 27, 2016 at 12:22:12PM +0200, Jozsef Kadlecsik wrote: > > Package: libvirt-daemon > > Version: 1.2.9-9+deb8u3 > > Severity: important > > > > Dear Maintainer, > > > > After upgrading from wheezy to jessie, libvirt-daemon stopped to recognize > > KVM as virtualization. All already defined guests are forgotten: > > > > root@atlas0:~# virsh list --all > > Id Name State > > ---------------------------------------------------- > > > > root@atlas0:~# virsh -c qemu:///sytem list --all > > error: failed to connect to the hypervisor > > error: no connection driver available for qemu:/sytem > > > > In /var/log/libvirt/libvirtd.log one can see the error message: > > > > 2016-07-26 09:33:39.997+0000: 27933: error : virDriverLoadModule:73 : failed > > to load module /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so > > /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so: undefined symbol: > > virStorageFileCreate > > > > One can find reports on "libvirt_driver_qemu.so: undefined symbol: > > virStorageFileCreate" from other distributions and those refer to an > > upgrade for the device-mapper as a fix. > > Can you do a > > ldd /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so > > Are you sure the daemon restarted properly after the update and there's > not hand built libvirt around in your library path?
It seems the problem was that PAX refused to enable PROT_WRITE for librados.so.2 and somehow that caused the failed load for the next module, ie. libvirt_driver_qemu.so. Sorry for the false report, Jozsef - E-mail : kad...@blackhole.kfki.hu, kadlecsik.joz...@wigner.mta.hu PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt Address : Wigner Research Centre for Physics, Hungarian Academy of Sciences H-1525 Budapest 114, POB. 49, Hungary
