Your message dated Wed, 27 May 2020 17:36:26 +0000
with message-id <[email protected]>
and subject line Bug#932759: fixed in xen 4.11.4-1
has caused the Debian Bug report #932759,
regarding After upgrade from stretch to buster, removal of obsolete xen 4.8
packages seems to trigger shutdown of xenconsoled
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.)
--
932759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932759
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xen-hypervisor-4.11-amd64
Version: 4.11.1+92-g6c33308a8d-2
System: Linux [host] 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u1
(2019-07-19) x86_64 GNU/Linux
Debian Release: 10
Codename: buster
In Reference To: Debian bug #851654 (archived)
> On Mon, 21 Jan 2019 00:48:09 +0100 Hans van Kranenburg
> <[email protected]> wrote:
>> reassign 851654 src:xen
>> thanks
>>
>> Hm!
>>
>> I think this is the same one that I've been observing during upgrade
>> tests from 4.8 -> 4.11 and 4.10 -> 4.11.
>>
>> In my IRC logs I can find myself complaining about xenconsoled that's
>> suddenly gone multiple times during 2018. I didn't manage to track this
>> issue down yet. The IRC logs contain some links to expired pastebin
>> entries. :|
>>
>> Also, in some cases xenconsoled just got shut down during the night,
>> during some systemd reload whatever was happening.
>>
>> I suspect more users are going to run into this issue when upgrading to
>> Buster.
>>
>> Hans
What happened:
- upgraded Debian Xen Dom0 from stretch to buster and rebooted, as
described in
https://www.debian.org/releases/buster/amd64/release-notes/ch-upgrading.en.html
- started some Linux pv domu without problems
- removed obsolete packages with 'apt autoremove'. This removed (among
others)
xen-hypervisor-4.8-amd64:amd64 (4.8.5+shim4.10.2+xsa282-1+deb9u11),
libxen-4.8:amd64 (4.8.5+shim4.10.2+xsa282-1+deb9u11),
xen-utils-4.8:amd64 (4.8.5+shim4.10.2+xsa282-1+deb9u11)
- starting another pv domu the next day using 'xl create -c [domu.cfg]'
raised an error message:
"xenconsole: Could not read tty from store: Success"
- opening a console for an already running domu raised another error
message that I believe was:
"xenconsole: Could not open tty `/dev/pts/2': No such file or directory"
- some internet searching hinted that this could be caused by
xenconsoled not running.
- xenconsoled was not running
- searching system logs revealed that xenconsoled seemed to have stopped
when 'apt autoremove' removed the obsolete xen 4.8
packages after upgrading to xen 4.11.
- this coincided with a systemd reload as seen in journalctl:
Jul 21 07:38:40 host systemd[1]: Reloading.
Jul 21 07:38:40 host systemd[1]: [email protected]: Current
command vanished from the unit file, execution of the command list won't
be resumed.
Jul 21 07:38:40 host systemd[1]: [email protected]: Current
command vanished from the unit file, execution of the command list won't
be resumed.
Jul 21 07:38:40 host systemd[1]: [email protected]: Current command
vanished from the unit file, execution of the command list won't be resumed.
Jul 21 07:38:41 host systemd[1]: Stopping LSB: Xen daemons...
Jul 21 07:38:41 host xen[9092]: Stopping Xen daemons: xenconsoled.
Jul 21 07:38:41 host systemd[1]: xen.service: Succeeded.
Jul 21 07:38:41 host systemd[1]: Stopped LSB: Xen daemons.
Note that at this time domu's where already running under xen4.11.
'systemctl restart xen.service' solved the issue. I report the issue
because it could affect others that are performing upgrades.
--- End Message ---
--- Begin Message ---
Source: xen
Source-Version: 4.11.4-1
Done: Hans van Kranenburg <[email protected]>
We believe that the bug you reported is fixed in the latest version of
xen, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Hans van Kranenburg <[email protected]> (supplier of updated xen package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 26 May 2020 13:33:17 +0200
Source: xen
Architecture: source
Version: 4.11.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xen Team <[email protected]>
Changed-By: Hans van Kranenburg <[email protected]>
Closes: 932759
Changes:
xen (4.11.4-1) unstable; urgency=medium
.
* Update to new upstream version 4.11.4, which also contains security fixes
for the following issues:
- arm: a CPU may speculate past the ERET instruction
XSA-312 (no CVE yet)
- multiple xenoprof issues
XSA-313 CVE-2020-11740 CVE-2020-11741
- Missing memory barriers in read-write unlock paths
XSA-314 CVE-2020-11739
- Bad error path in GNTTABOP_map_grant
XSA-316 CVE-2020-11743
- Bad continuation handling in GNTTABOP_copy
XSA-318 CVE-2020-11742
* xen-utils and xen-utils-common maint scripts: Replace the previous fix in
the xen init script with a better fix in the xen-utils package instead, to
prevent calling the init script stop action (resulting in a disappeared
xenconsoled) when removing a xen-utils package that belongs to a previous
(not currently runing) Xen version. Also prevent the xen-utils-common
package from inadvertently calling stop and start actions because
dh_installinit would add code for that. (Closes: #932759)
* debian/NEWS: Mention fixing #932759 and how to deal with the bug
Checksums-Sha1:
e443479743af4231086119b5ea93c6b3ffe29535 4087 xen_4.11.4-1.dsc
f0f20084be228476b282c20eea134dd083865acd 4248384 xen_4.11.4.orig.tar.xz
06bd6f927c31c3c0ab3742c4e9b348cc3fa39cda 134236 xen_4.11.4-1.debian.tar.xz
Checksums-Sha256:
357e856f63ce3ee0da77832514cb759218149e9e74e2003014834eb5d3d0a3ab 4087
xen_4.11.4-1.dsc
2973ecd949cbc83a822b9dc38700ee55b1ecab2159b76363a23bf2f2f4161fc4 4248384
xen_4.11.4.orig.tar.xz
c26b66a2a2b6df8b53ded1cb7255dcae58ad2bcefd106d454a3a5852d33b6ba3 134236
xen_4.11.4-1.debian.tar.xz
Files:
f2332d3b95d7a52922f9a5a6ee6580f7 4087 admin optional xen_4.11.4-1.dsc
d796fece69fa1de0c30776bda1474f3f 4248384 admin optional xen_4.11.4.orig.tar.xz
1ac766dd02dfa426a2230bed941407f2 134236 admin optional
xen_4.11.4-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEESWyddwNaG9637koYssHfcmNhX2wFAl7OobYACgkQssHfcmNh
X2wteBAAqjDRP4uZv7FVvoKLQ7P4cB2Iu5TyxsVDOy2KXhD8cYGzDuZfhmbfj+rg
DVTP7/diDknrmKCDRlT49sbqoHPz7NKSKJpT+p/NdzeU2I1IvoexDb1apCWKKQPL
+G4K8pLXPs/p9tvaR/IQJto99q0uMfmMWUobuXXgK5Wnd6wyhqFCL1UOZc3vIjo1
4jri3Ee8DybJ+uKkmZeoxWcShW5KZj6wSf+ITC5zMOgqJtPYdJCHCoXlv5SCezbk
iXxJ18qtvd5xIATYUAtElk87wb+ZcF7hFILWCkGtFA7FvSzcsBWUGgf4oG9KfUlC
NWUtSIiGuzxXglsiEYHaV01h9ihJL4lVEBhWCOJRhcDhDqwKCDjHoEiaR1tSr4FP
X24nTkCj1/5HbC16V4/u4hLIY1z1FAtnBqdjOJ+dYuKpYS7lbwg1jMpKPpAE92Xf
wHOMOfZKuHc2iMAIIt+xrcWcGYL9CpdAa9PVv3uyikjw6lwGhaZia0gWE5nfNJbf
b8WF/uJZ8tQx2HZ/Ajk1U0s5EHEuLH6+Y0aNm8qzlPBFlBY0FFxVyrJnGdURO404
vXMssaIgEcKkHcwMRpz1i5ZP5Q5RaaJjdWKA8XrHyAqa0LXgKLzrl1WWUreF+/bx
nnd37RemQg8NBUQjSk5axqzrrMA24cPk4eTfPbfARqHC4QVj9A0=
=cmnP
-----END PGP SIGNATURE-----
--- End Message ---
