Your message dated Tue, 6 Aug 2013 08:09:51 +0200
with message-id <20130806060951.ga17...@bogon.sigxcpu.org>
and subject line Fixed in 1.1.1-1
has caused the Debian Bug report #715510,
regarding libvirt-bin: libvirtd locks up whenever touching storage storage pool
when related to systems's harddrive.
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 ow...@bugs.debian.org
immediately.)
--
715510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvirt-bin
Version: 1.1.0-1
Severity: grave
Justification: renders package unusable
With libvirt-bin version 1.1.0-1, libvirtd locks up whenever touching storage
storage pool when related to systems's harddrive. virt-clone causes libvirtd
to hang, attempting to clone a vm via virt-manager causes a hang, creating a
new vm via virt-manager causes a hang (once you reach the step at which
libvirt-bin would be creating the image). Reverting back to 1.0.6 fixes the
problem. As of now all disk images in my storage pool used as hdd images are
raw. Attempted to upgrade kernel version from 3.9-1 to no avail.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10-rc7-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages libvirt-bin depends on:
ii adduser 3.113+nmu3
ii gettext-base 0.18.2.1-1
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.5
ii libc6 2.17-7
ii libcap-ng0 0.7.3-1+b1
ii libdbus-1-3 1.6.12-1
ii libdevmapper1.02.1 2:1.02.77-3
ii libgcrypt11 1.5.2-3
ii libgnutls26 2.12.23-5
pn libnetcf1 <none>
ii libnl-3-200 3.2.21-1
ii libnl-route-3-200 3.2.21-1
ii libnuma1 2.0.8-3
ii libparted0debian1 2.3-13
ii libpcap0.8 1.4.0-2
ii libpciaccess0 0.13.1-2
ii libreadline6 6.2+dfsg-0.1
ii libsasl2-2 2.1.25.dfsg1-13
ii libudev0 175-7.2
ii libvirt0 1.1.0-1
ii libxenstore3.0 4.2.1-2
ii libxml2 2.9.1+dfsg1-2
ii libyajl2 2.0.4-4
ii logrotate 3.8.5-1
Versions of packages libvirt-bin recommends:
ii bridge-utils 1.5-6
ii dmidecode 2.12-1
ii dnsmasq-base 2.66-3
ii ebtables 2.0.10.4-3
ii gawk 1:4.0.1+dfsg-2.1
ii iproute 1:3.9.0-5
ii iptables 1.4.18-1
ii libxml2-utils 2.9.1+dfsg1-2
ii netcat-openbsd 1.105-7
ii parted 2.3-13
ii pm-utils 1.4.1-11
ii qemu-system-x86 [qemu-kvm] 1.5.0+dfsg-4
Versions of packages libvirt-bin suggests:
pn auditd <none>
ii policykit-1 0.105-3
pn radvd <none>
pn systemtap <none>
-- Configuration Files:
/etc/default/libvirt-guests changed [not included]
/etc/libvirt/libvirt.conf changed [not included]
/etc/libvirt/qemu-lockd.conf changed [not included]
/etc/libvirt/qemu-sanlock.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.1.1-1
Hi,
this was fixed in 1.1.1-1 but I screwed up the bug number in the
changelog
Cheers,
-- Guido
--- End Message ---
