Your message dated Thu, 28 Jul 2016 08:33:30 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-libvirt-maintainers] Bug#832592: libvirt-daemon: KVM
is not recognized as supported virtualization
has caused the Debian Bug report #832592,
regarding fails to activate qemu hypervisor with error "libvirt_driver_qemu.so:
undefined symbol: virStorageFileCreatelibvirt-daemon"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
832592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832592
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
Best regards,
Jozsef
-- System Information:
Debian Release: 8.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14.34-grsec (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages libvirt-daemon depends on:
ii libapparmor1 2.9.0-3
ii libaudit1 1:2.4-1+b1
ii libavahi-client3 0.6.31-5
ii libavahi-common3 0.6.31-5
ii libblkid1 2.25.2-6
ii libc6 2.19-18+deb8u4
ii libcap-ng0 0.7.4-2
ii libdbus-1-3 1.8.20-0+deb8u1
ii libdevmapper1.02.1 2:1.02.90-2.2+deb8u1
ii libfuse2 2.9.3-15+deb8u2
ii libgnutls-deb0-28 3.3.8-6+deb8u3
ii libnetcf1 1:0.2.3-4.1
ii libnl-3-200 3.2.24-2
ii libnl-route-3-200 3.2.24-2
ii libnuma1 2.0.10-1
ii libparted2 3.2-7
ii libpcap0.8 1.6.2-2
ii libpciaccess0 0.13.2-3+b1
ii librados2 0.80.7-2+deb8u1
ii librbd1 0.80.7-2+deb8u1
ii libsasl2-2 2.1.26.dfsg1-13+deb8u1
ii libselinux1 2.3-2
ii libssh2-1 1.4.3-4.1+deb8u1
ii libsystemd0 215-17+deb8u4
ii libudev1 215-17+deb8u4
ii libvirt0 1.2.9-9+deb8u3
ii libxen-4.4 4.4.1-9+deb8u5
ii libxenstore3.0 4.4.1-9+deb8u5
ii libxml2 2.9.1+dfsg1-5+deb8u2
ii libyajl2 2.1.0-2
Versions of packages libvirt-daemon recommends:
ii libxml2-utils 2.9.1+dfsg1-5+deb8u2
ii netcat-openbsd 1.105-7
ii qemu 1:2.1+dfsg-12+deb8u6
ii qemu-kvm 1:2.1+dfsg-12+deb8u6
Versions of packages libvirt-daemon suggests:
ii libvirt-daemon-system 1.2.9-9+deb8u3
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, Jul 27, 2016 at 11:39:18PM +0200, Jozsef Kadlecsik wrote:
> 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,
No problem, thanks for reporting back.
-- Guido
--- End Message ---
