[lkml]   [2017]   [Mar]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] kvm/x86/vmx: report KVM_SYSTEM_EVENT_CRASH on triple fault
On Tue, Mar 28, 2017 at 03:51:01AM -0400, Paolo Bonzini wrote:
> > While debugging a kernel issue, I found that QEMU always reboots when an
> > x86 triple fault occurs, which complicates debugging. QEMU and libvirt
> > have a facility for creating a dump when KVM reports
> > KVM_SYSTEM_EVENT_CRASH. So change the VMX triple fault handler to do
> > that. This gives user space the ability to decide whether to dump,
> > pause, shutdown, or reboot.
> You probably want QEMU's -no-reboot option.
> Triple faults are already reported to userspace with KVM_EXIT_SHUTDOWN,
> and it's up to userspace to decide what to do with it. This patch cannot
> be applied, because there are guests that do a triple-fault intentionally
> in order to reset the machine.

Ok. Any idea how to force libvirt to create a dump? It has a
'coredump-destroy' option, but that only seems to work with 'on_crash':


 \ /
  Last update: 2017-03-28 13:49    [W:0.081 / U:0.076 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site