Your message dated Tue, 18 Sep 2018 08:57:26 +0200
with message-id <20180918065726.ga2...@bogon.m.sigxcpu.org>
and subject line Re: Bug#900401: libvirt-daemon: Both virsh and virt-manager
hang on connection after dist-upgrade
has caused the Debian Bug report #900401,
regarding /usr/bin/virsh: After latest Debian upgrade many commands stopped
working
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.)
--
900401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900401
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvirt-clients
Version: 3.0.0-4+deb9u3
Severity: important
File: /usr/bin/virsh
Dear Maintainer,
virsh commands like
virsh list
virsh shutdown <domain>
hangs directly when issued. virsh can be started as a shell but when the
commands are executed it hangs. This happens even if virsh is run as
root. Nothing is seen in syslog. The commands did work before the latest
qemu sets of packages where installed. (I am following Debian stable) Maybe
this a problem of on of those packages instead?
-- System Information:
Debian Release: 9.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libvirt-clients depends on:
ii libapparmor1 2.11.0-3+deb9u2
ii libaudit1 1:2.6.7-2
ii libavahi-client3 0.6.32-2
ii libavahi-common3 0.6.32-2
ii libc6 2.24-11+deb9u3
ii libcap-ng0 0.7.7-3+b1
ii libdbus-1-3 1.10.26-0+deb9u1
ii libdevmapper1.02.1 2:1.02.137-2
ii libgnutls30 3.5.8-5+deb9u3
ii libnl-3-200 3.2.27-2
ii libnl-route-3-200 3.2.27-2
ii libnuma1 2.0.11-2.1
ii libreadline7 7.0-3
ii libsasl2-2 2.1.27~101-g0780600+dfsg-3
ii libselinux1 2.6-3+b3
ii libssh2-1 1.7.0-1
ii libvirt0 3.0.0-4+deb9u3
ii libxen-4.8 4.8.3+xsa262+shim4.10.0+comet3-1+deb9u7
ii libxml2 2.9.4+dfsg1-2.2+deb9u2
ii libyajl2 2.1.0-2+b3
libvirt-clients recommends no packages.
Versions of packages libvirt-clients suggests:
ii libvirt-daemon 3.0.0-4+deb9u3
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: libvirt-daemon/4.3.0-1
Hi,
On Mon, Sep 17, 2018 at 02:30:58PM -0400, Paul Sandulescu wrote:
> The way I solved this, and it's been a while now, is by building libvirt
> from apt-get source. No patch, same version, everything worked. Maybe some
> package corruption occurred, although symptoms were quite unusual. I think
> you can close this one.
Thanks for reportin back. Closing then.
Cheer,
-- Guido
--- End Message ---
