Support for kdump
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nullboot (Ubuntu) |
Triaged
|
Wishlist
|
Chris Coulson | ||
Bug Description
Currently, there does not appear to be a way to enable kdump when using nullboot to secure boot a system. It would be useful to support this for debugging purposes.
I was doing testing on a cloud platform that provides secure boot VM images for confidential computing and while debugging a kernel issue, I was trying to trigger kdump to capture the state of the running system.
Ubuntu version: Jammy
Package version: 0.4.0-0ubuntu0.
Expected outcome:
Triggering kdump manually using the Magic SysRQ should result in kdump writing out the dump file
Actual outcome:
System crashes but kdump does not execute
Steps to reproduce:
1. Launch a confidential VM and follow the steps to configure kdump.
(https:/
2. Run echo c > /proc/sysrq-trigger
| Julian Andres Klode (juliank) wrote | #1 |
| Changed in nullboot (Ubuntu): | |
| status: | New → Incomplete |
| status: | Incomplete → Triaged |
| assignee: | nobody → Chris Coulson (chrisccoulson) |
| importance: | Undecided → Wishlist |
I'm not sure what nullboot can do here or how kdump works. It seems to me like this needs kexec stuff in the kernel and nullboot/secboot would have to seal stuff so that the root disk can be unlocked from the kexeced kernel?
I'll leave that to Chris.