News for hackers. Stuff that matters.
Re:Trigger a Kernel Panic to Diagnose Unresponsive EC2 Insta... by amluto on Thursday August 15, 2019 @11:19PM (#20711884)
Total garbage in CR3 will likely triple fault. Garbage in the IDT, etc will also double or triple fault. Corruption of the NMI “don’t recurse now” state will likely just ignore the NMI. Corruption of various other things may cause the NMI handler to crash before it makes a useful dump.

A triple fault will reboot or do whatever else the hypervisor feels like doing.

Re:Trigger a Kernel Panic to Diagnose Unresponsive EC2 Insta... by anyfoo on Friday August 16, 2019 @01:34AM (#20712437)
Yeah, that was my point. No kernel panic on a triple fault.

Though arguably, a hypervisor can dump out some useful state on a triple fault, as they actually tend to do. But that's not an in-band kernel panic, and in VirtualBox at least you can get a dump of that state without sending an NMI or otherwise disturbing the VM.