Activity log for bug #1999885

Date Who What changed Old value New value Message
2022-12-16 12:19:46 bugproxy bug added bug
2022-12-16 12:19:48 bugproxy tags architecture-s39064 bugnameltc-200901 severity-high targetmilestone-inin---
2022-12-16 12:19:49 bugproxy ubuntu: assignee Skipper Bug Screeners (skipper-screen-team)
2022-12-16 12:19:52 bugproxy affects ubuntu linux (Ubuntu)
2022-12-16 12:37:00 Frank Heimes affects linux (Ubuntu) qemu (Ubuntu)
2022-12-16 12:37:56 Frank Heimes bug task added ubuntu-z-systems
2022-12-16 12:38:06 Frank Heimes qemu (Ubuntu): importance Undecided High
2022-12-16 12:38:09 Frank Heimes ubuntu-z-systems: importance Undecided High
2022-12-16 12:38:27 Frank Heimes ubuntu-z-systems: assignee Skipper Bug Screeners (skipper-screen-team)
2022-12-16 12:39:50 Frank Heimes nominated for series Ubuntu Lunar
2022-12-16 12:39:50 Frank Heimes bug task added qemu (Ubuntu Lunar)
2022-12-16 12:39:50 Frank Heimes nominated for series Ubuntu Jammy
2022-12-16 12:39:50 Frank Heimes bug task added qemu (Ubuntu Jammy)
2022-12-16 12:39:50 Frank Heimes nominated for series Ubuntu Focal
2022-12-16 12:39:50 Frank Heimes bug task added qemu (Ubuntu Focal)
2022-12-16 12:39:50 Frank Heimes nominated for series Ubuntu Kinetic
2022-12-16 12:39:50 Frank Heimes bug task added qemu (Ubuntu Kinetic)
2022-12-16 12:40:02 Frank Heimes qemu (Ubuntu Lunar): importance High Low
2022-12-16 12:40:19 Frank Heimes ubuntu-z-systems: status New Triaged
2022-12-16 12:43:59 Frank Heimes qemu (Ubuntu Lunar): assignee Skipper Bug Screeners (skipper-screen-team) Ubuntu Server (ubuntu-server)
2022-12-16 12:44:11 Frank Heimes bug added subscriber Christian Ehrhardt 
2023-01-25 11:03:12 Launchpad Janitor merge proposal linked https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/435185
2023-01-25 12:09:10 Frank Heimes qemu (Ubuntu Lunar): status New In Progress
2023-01-25 12:09:13 Frank Heimes ubuntu-z-systems: status Triaged In Progress
2023-02-16 12:45:34 Frank Heimes qemu (Ubuntu Lunar): status In Progress Fix Committed
2023-03-06 17:25:14 Launchpad Janitor qemu (Ubuntu Lunar): status Fix Committed Fix Released
2023-03-06 17:25:14 Launchpad Janitor bug watch added https://sourceware.org/bugzilla/show_bug.cgi?id=29514
2023-03-06 17:25:14 Launchpad Janitor cve linked 2020-14394
2023-03-06 17:25:14 Launchpad Janitor cve linked 2021-3507
2023-03-06 17:25:14 Launchpad Janitor cve linked 2022-0216
2023-03-06 17:25:14 Launchpad Janitor cve linked 2022-1050
2023-03-06 17:25:14 Launchpad Janitor cve linked 2022-2962
2023-03-06 17:25:14 Launchpad Janitor cve linked 2022-3165
2023-03-06 17:25:14 Launchpad Janitor cve linked 2022-35414
2023-03-06 17:25:14 Launchpad Janitor cve linked 2022-4172
2023-03-07 11:00:04 bugproxy attachment added Proposed backport for Ubuntu Focal https://bugs.launchpad.net/bugs/1999885/+attachment/5652377/+files/lp-1999885-s390x-tod-kvm-don-t-save-restore-the-TOD-in-PV-guest.patch
2023-03-23 07:04:22 Christian Ehrhardt  qemu (Ubuntu Kinetic): status New In Progress
2023-03-23 07:15:40 Christian Ehrhardt  description Description: KVM: s390: pv: don't allow userspace to set the clock under PV Symptom: Timer issues and RCU stalls after suspending and resuming an IBM Secure Execution guest Problem: KVM and QEMU try to set the guest's TOD clock after resume under PV, even though that is not permitted under SE. Hence, their view of the guest clock may deviate from the ultravisor's, possibly causing KVM to re-dispatch the guest too late on clock comparator interrupts. Solution: Don't set the clock after resume under PV. Note that kernel and QEMU patches are required in lockstep, to avoid a warning message in QEMU. Reproduction: 1. Start SE guest using libvirt. 2. Pause the guest using "virsh suspend", wait for a few seconds, resume using "virsh resume". 3. Run "time sleep 1" in the guest. 4. The sleep will sleep much longer than one second. Component: qemu Upstream-ID: 38621181ae3cbec62e3490fbc14f6ac01642d07a Preventive: yes Author: Nico Boehr <nrb@linux.ibm.com> Please note that fixing the described problem requires patches for the kernel as well as for QEMU. This bug covers the qemu part, whereas the required kernel part is described and handled in the following related bug: Bug 200889 - [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part Both parts, the kernel and the qemu patches should be applied / released at the same time to avoid problems resulting in the following warning message for customers: 'warning: Unable to set KVM guest TOD clock: Operation not supported' [ Impact ] * suspend and resume (and other situations that cause vm state change) lead to situations where the hipervisor wants to change the clock. Now the s390x clock can be considered staged with offsets potentially added at each level of virtualization. In the secure execution mode on s390x the hipervisor is not allowed to touch this, leading to wrong timing. * The fix skips changing the tod (time of day -> clock) on a kvm_s390_tod_vm_state_change [ Test Plan ] * 1. Start SE guest using libvirt.    2. Pause the guest using "virsh suspend", wait for a few       seconds, resume using "virsh resume".    3. Run "time sleep 1" in the guest.    4. The sleep will sleep much longer than one second. [ Where problems could occur ] * This is gladly very isolated to s390x clock handling, so that (and only that) would be the place to look out for problems or regressions. [ Other info ] * s390x secure execution needs HW feature my machine lacks, this will need IBM to verify the case once accepted to proposed. --- original report --- Description: KVM: s390: pv: don't allow userspace to set the clock under PV Symptom: Timer issues and RCU stalls after suspending and resuming an IBM                Secure Execution guest Problem: KVM and QEMU try to set the guest's TOD clock after resume                under PV, even though that is not permitted under SE. Hence,                their view of the guest clock may deviate from the ultravisor's,                possibly causing KVM to re-dispatch the guest too late on clock                comparator interrupts. Solution: Don't set the clock after resume under PV. Note that kernel and                QEMU patches are required in lockstep, to avoid a warning message                in QEMU. Reproduction: 1. Start SE guest using libvirt.                2. Pause the guest using "virsh suspend", wait for a few                   seconds, resume using "virsh resume".                3. Run "time sleep 1" in the guest.                4. The sleep will sleep much longer than one second. Component: qemu Upstream-ID: 38621181ae3cbec62e3490fbc14f6ac01642d07a Preventive: yes Author: Nico Boehr <nrb@linux.ibm.com> Please note that fixing the described problem requires patches for the kernel as well as for QEMU. This bug covers the qemu part, whereas the required kernel part is described and handled in the following related bug:    Bug 200889 - [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under PV - kernel part Both parts, the kernel and the qemu patches should be applied / released at the same time to avoid problems resulting in the following warning message for customers:    'warning: Unable to set KVM guest TOD clock: Operation not supported'
2023-03-23 07:20:42 Launchpad Janitor merge proposal linked https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/439453
2023-03-27 06:26:12 Launchpad Janitor merge proposal linked https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/439681
2023-03-27 06:28:02 Launchpad Janitor merge proposal linked https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/439682
2023-03-27 06:28:27 Launchpad Janitor merge proposal linked https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/439683
2023-03-27 07:27:41 Frank Heimes qemu (Ubuntu Jammy): status New In Progress
2023-03-27 07:27:44 Frank Heimes qemu (Ubuntu Focal): status New In Progress
2023-04-14 20:15:00 Steve Langasek qemu (Ubuntu Kinetic): status In Progress Fix Committed
2023-04-14 20:15:02 Steve Langasek bug added subscriber Ubuntu Stable Release Updates Team
2023-04-14 20:15:05 Steve Langasek bug added subscriber SRU Verification
2023-04-14 20:15:09 Steve Langasek tags architecture-s39064 bugnameltc-200901 severity-high targetmilestone-inin--- architecture-s39064 bugnameltc-200901 severity-high targetmilestone-inin--- verification-needed verification-needed-kinetic
2023-04-14 20:16:40 Steve Langasek qemu (Ubuntu Jammy): status In Progress Fix Committed
2023-04-14 20:16:47 Steve Langasek tags architecture-s39064 bugnameltc-200901 severity-high targetmilestone-inin--- verification-needed verification-needed-kinetic architecture-s39064 bugnameltc-200901 severity-high targetmilestone-inin--- verification-needed verification-needed-jammy verification-needed-kinetic
2023-04-14 20:25:07 Steve Langasek qemu (Ubuntu Focal): status In Progress Fix Committed
2023-04-14 20:25:15 Steve Langasek tags architecture-s39064 bugnameltc-200901 severity-high targetmilestone-inin--- verification-needed verification-needed-jammy verification-needed-kinetic architecture-s39064 bugnameltc-200901 severity-high targetmilestone-inin--- verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic
2023-04-18 06:36:03 Frank Heimes ubuntu-z-systems: status In Progress Fix Committed
2023-04-18 14:09:51 bugproxy tags architecture-s39064 bugnameltc-200901 severity-high targetmilestone-inin--- verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic architecture-s39064 bugnameltc-200901 severity-high targetmilestone-inin2004 verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic
2023-04-19 08:20:21 bugproxy tags architecture-s39064 bugnameltc-200901 severity-high targetmilestone-inin2004 verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic architecture-s39064 bugnameltc-200901 severity-high targetmilestone-inin2004 verification-done-focal verification-done-jammy verification-needed verification-needed-kinetic
2023-04-19 09:49:48 bugproxy tags architecture-s39064 bugnameltc-200901 severity-high targetmilestone-inin2004 verification-done-focal verification-done-jammy verification-needed verification-needed-kinetic architecture-s39064 bugnameltc-200901 severity-high targetmilestone-inin2004 verification-done-focal verification-done-jammy verification-done-kinetic verification-needed
2023-04-19 11:14:33 Christian Ehrhardt  tags architecture-s39064 bugnameltc-200901 severity-high targetmilestone-inin2004 verification-done-focal verification-done-jammy verification-done-kinetic verification-needed architecture-s39064 bugnameltc-200901 severity-high targetmilestone-inin2004 verification-done verification-done-focal verification-done-jammy verification-done-kinetic
2023-04-26 08:10:35 Launchpad Janitor qemu (Ubuntu Focal): status Fix Committed Fix Released
2023-04-26 08:10:42 Chris Halse Rogers removed subscriber Ubuntu Stable Release Updates Team
2023-04-26 08:10:54 Launchpad Janitor qemu (Ubuntu Jammy): status Fix Committed Fix Released
2023-04-26 08:11:13 Launchpad Janitor qemu (Ubuntu Kinetic): status Fix Committed Fix Released
2023-04-26 09:53:52 Frank Heimes ubuntu-z-systems: status Fix Committed Fix Released