Your message dated Mon, 16 Mar 2020 00:37:11 +0000 (UTC)
with message-id <pine.bsm.4.64l.2003160035380.2...@herc.mirbsd.org>
and subject line Re: [Pkg-libvirt-maintainers] Bug#939983: error: Unable to
read from '/sys/fs/cgroup/unified/machine/cgroup.controllers'
has caused the Debian Bug report #939983,
regarding error: Unable to read from
'/sys/fs/cgroup/unified/machine/cgroup.controllers'
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.)
--
939983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvirt-daemon
Version: 5.6.0-2
Severity: serious
Justification: unusable, no working workaround
tglase@tglase:~ $ alias wirrsh
wirrsh='virsh -c qemu:///system'
tglase@tglase:~ $ wirrsh start MirBSD
error: Failed to start domain MirBSD
error: Unable to read from '/sys/fs/cgroup/unified/machine/cgroup.controllers':
No such file or directory
This might be related to #935734, but the workaround from there, to add…
cgroup_controllers = [ ]
… to /etc/libvirt/qemu.conf, does not work any more.
-- System Information:
Debian Release: bullseye/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'),
(100, 'experimental')
Architecture: x32 (x86_64)
Foreign Architectures: i386, amd64
Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)
Versions of packages libvirt-daemon depends on:
ii libblkid1 2.34-0.1
ii libc6 2.28-10
ii libcap-ng0 0.7.9-2+b1
ii libdbus-1-3 1.12.16-1
ii libdevmapper1.02.1 2:1.02.155-3
ii libfuse2 2.9.9-2
ii libgcc1 1:9.2.1-7
ii libgnutls30 3.6.9-4
ii libnetcf1 1:0.2.8-1+b2
ii libparted2 3.2-26
ii libpcap0.8 1.9.0-2
ii libpciaccess0 0.14-1
ii libselinux1 2.9-2+b2
ii libudev1 242-7
ii libvirt0 5.6.0-2
ii libxml2 2.9.4+dfsg1-7+b3tarent1
Versions of packages libvirt-daemon recommends:
ii libxml2-utils 2.9.4+dfsg1-7+b3tarent1
ii netcat-openbsd 1.203-2
ii qemu 1:4.1-1+b1
Versions of packages libvirt-daemon suggests:
pn libvirt-daemon-driver-storage-gluster <none>
pn libvirt-daemon-driver-storage-rbd <none>
pn libvirt-daemon-driver-storage-zfs <none>
ii libvirt-daemon-system 5.6.0-2
pn numad <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 6.0.0-2
>>> tried version 6.0.0-1 from experimental and problem is solved.
Now in sid, thanks! (The NEWS entry comes too late btw — after apt
first had tried to remove elogind entirely, until one things of just
running a-g i libvirt0… might wish to add to the release notes for
bullseye…)
bye,
//mirabilos
--
(gnutls can also be used, but if you are compiling lynx for your own use,
there is no reason to consider using that package)
-- Thomas E. Dickey on the Lynx mailing list, about OpenSSL
--- End Message ---
