Package: libvirt-daemon Version: 1.2.9-6~bpo70+1 Severity: important Dear Maintainer,
It is not possible to use the libvirtd locking debain with libvirt, as libvirt is unable to start when setting lock_manager = "lockd" in /etc/libvirt/qemu.conf Libvirt is unable to start and the error below is show in the libvirtd.log Initialization of QEMU state driver failed: Plugin /usr/lib/libvirt/lock- driver/lockd.so not accessible: No such file or directory A quick search of the filesystem for lockd.so show that it is not present. Architecture: amd64 Source: libvirt Version: 1.2.9-6~bpo70+1 Could you advise? Kind regards, Gavin -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i686 i386 Kernel: Linux 3.12-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libvirt-daemon depends on: ii libapparmor1 2.7.103-4 ii libaudit0 1:1.7.18-1.1 ii libavahi-client3 0.6.31-2 ii libavahi-common3 0.6.31-2 ii libblkid1 2.20.1-5.3 ii libc6 2.13-38+deb7u4 ii libcap-ng0 0.6.6-2 ii libdbus-1-3 1.6.8-1+deb7u4 ii libdevmapper1.02.1 2:1.02.74-8 ii libfuse2 2.9.0-2+deb7u1 ii libgcrypt11 1.5.0-5+deb7u1 ii libgnutls26 2.12.20-8+deb7u2 ii libnetcf1 0.1.9-2 ii libnl1 1.1-7 ii libnuma1 2.0.8~rc4-1 ii libparted0debian1 2.3-12 ii libpcap0.8 1.3.0-1 ii libpciaccess0 0.13.1-2 ii libsasl2-2 2.1.25.dfsg1-6+deb7u1 ii libselinux1 2.1.9-5 ii libssh2-1 1.4.2-1.1 ii libsystemd-daemon0 44-11+deb7u4 ii libudev0 175-7.2 ii libvirt0 1.2.9-6~bpo70+1 ii libxenstore3.0 4.1.4-3+deb7u2 ii libxml2 2.8.0+dfsg1-7+wheezy1 ii libyajl2 2.0.4-2 Versions of packages libvirt-daemon recommends: ii libxml2-utils 2.8.0+dfsg1-7+wheezy1 ii netcat-openbsd 1.105-7 ii qemu 1.1.2+dfsg-6a+deb7u3 ii qemu-kvm 1.1.2+dfsg-6+deb7u3 Versions of packages libvirt-daemon suggests: ii libvirt-daemon-system 1.2.9-6~bpo70+1 -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
