Public bug reported:
During some tests I've encountered an issue with kdump through NMI SMP
and single core. After kdump configuration, when I trigger the crash
through an NMI call from the host, the VM will panic, however it will
not write the vmcore dump files and neither reboot.
REPRO STEPS:
1. configure kdump
- crashkernel=512M-:384M /boot/grub/grub.cfg
- USE_KDUMP=1 /etc/default/kdump-tools
2. after configuration reboot the VM
3. check kdump status
- cat /sys/kernel/kexec_*
- service kdump-tools status
4. configure NMI
- sysctl -w kernel.unknown_nmi_panic=1
5. trigger a crash from host
- Debug-VM -Name $vmName -InjectNonMaskableInterrupt -ComputerName $hvServer
-Force
This case also applies to:
-Ubuntu 16.10 generation 2(kernel version: 4.8.0-17-generic)
-Ubuntu 16.04.1(kernel: 4.4.0-38-generic)
-Ubuntu 14.04.5(kernel: 3.19.0-69-generic)
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630924
Title:
Kdump through NMI SMP and single core not working on Ubuntu16.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630924/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
