From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: rkrcmar@redhat.com, x86@kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Subject: Re: [PATCH] kvm/x86/vmx: report KVM_SYSTEM_EVENT_CRASH on triple fault
Date: Tue, 28 Mar 2017 06:46:17 -0500 [thread overview]
Message-ID: <20170328114617.zapicqltmtarv4jt@treble> (raw)
In-Reply-To: <2101391670.8452799.1490687461888.JavaMail.zimbra@redhat.com>
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':
https://libvirt.org/formatdomain.html#elementsEvents
--
Josh
next prev parent reply other threads:[~2017-03-28 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 19:25 Josh Poimboeuf
2017-03-28 7:51 ` Paolo Bonzini
2017-03-28 11:46 ` Josh Poimboeuf [this message]
2017-03-28 12:39 ` Paolo Bonzini
2017-03-28 15:51 ` Josh Poimboeuf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170328114617.zapicqltmtarv4jt@treble \
--to=jpoimboe@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®