This bug was fixed in the package linux - 4.15.0-163.171
---
linux (4.15.0-163.171) bionic; urgency=medium
* bionic/linux: 4.15.0-163.171 -proposed tracker (LP: #1949874)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update
This bug was fixed in the package linux - 5.4.0-91.102
---
linux (5.4.0-91.102) focal; urgency=medium
* focal/linux: 5.4.0-91.102 -proposed tracker (LP: #1949840)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
Verified for Focal according to test case from description. A standard
multipass VM with 8 vCPUs configured was able to capture a kernel dump
without errors.
Additionally, since the 5.4 kernel doesn't hit the MMU/reset bug
directly, I've done some additional testing to ensure we didn't
introduce
Performing verification for Bionic.
I installed the current 4.15.0-162-generic kernel from -updates to a
host in segmaas, and brought up my Bionic VM I installed for the
reproducer. The Bionic VM has linux-crashdump configured, with nr_cpus
configured to 8:
ubuntu@bionic-vm:~$ kdump-config show
This bug is awaiting verification that the linux/4.15.0-163.171 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-bionic' to 'verification-done-bionic'. If the
problem still exists,
This bug is awaiting verification that the linux/5.4.0-91.102 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal' to 'verification-done-focal'. If the problem
still exists, change
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a
For future reference, this bug has been reported in Ubuntu KVM hosts
outside of the specific kdump test scenario (i.e. when running actual
VMs in production-like setups). The "kdump with multiple CPUs" case was
discovered as an alternative that hits the same MMU context bug, without
needing
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948862
Title:
** Description changed:
[Impact]
When kexec'ing into a crash kernel with ncpus > 1, VMs can raise a KVM
emulation failure. This will cause the VM to go into the "paused" state, and
prevents it from being restored without a full VM restart.
This happens only when there are multiple
** Description changed:
[Impact]
When kexec'ing into a crash kernel with ncpus > 1, VMs can raise a KVM
emulation failure. This will cause the VM to go into the "paused" state, and
prevents it from being restored without a full VM restart.
This happens only when there are multiple
** Description changed:
[Impact]
- When kexec'ing into a crash kernel with `ncpus` > 1, VMs can raise a KVM
- emulation failure. This will cause the VM to go into the "paused" state, and
- prevents it from being restored without a full VM restart.
+ When kexec'ing into a crash kernel with ncpus
12 matches
Mail list logo
