Commit 6973091d1b50 got upstream accepted with v6.1-rc5,
so lunar will have the fix incl., once it's on its target kernel 6.2.
Marking kinetic, jammy and focal as affected releases.
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Status: New => Triaged
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: High
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: Triaged
** Changed in: linux (Ubuntu Lunar)
Status: Triaged => Confirmed
** Changed in: linux (Ubuntu Focal)
Status: New => Triaged
** Changed in: linux (Ubuntu Jammy)
Status: New => Triaged
** Changed in: linux (Ubuntu Kinetic)
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1999882
Title:
[UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock
under PV - kernel part
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Triaged
Status in linux source package in Jammy:
Triaged
Status in linux source package in Kinetic:
Triaged
Status in linux source package in Lunar:
Confirmed
Bug 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.
Upstream-ID: 6973091d1b50ab4042f6a2d495f59e9db3662ab8
Preventive fix: yes
Author: Nico Boehr <n...@linux.ibm.com>
Please note that fixing the described problem requires patches for the kernel
as well as for QEMU.
This bug covers the kernel part, whereas the required QEMU part is described
and handled in the following related bug:
Bug?200901 - [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to
set the clock under PV - qemu 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'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1999882/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
