From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
Daniel Gollub <gollub@b1-systems.de>,
kvm@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH 0/2] Introduce panic hypercall
Date: Mon, 20 Jun 2011 17:59:19 +0200 [thread overview]
Message-ID: <4DFF6E57.7040109@siemens.com> (raw)
In-Reply-To: <4DFF6B20.7090107@redhat.com>
On 2011-06-20 17:45, Avi Kivity wrote:
>> This series does need to introduce a QMP event notification upon
>> crash, so that the crash notification can be propagated to mgmt
>> layers above QEMU.
>
> Yes.
I think the best way to deal with that is to stop the VM on guest panic.
There is already WIP to signal stop reasons via QMP. Maybe we need to
differentiate between hypervisor and guest triggered panics
(VMSTOP_GUEST_PANIC?), but the rest should come for free.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-06-20 15:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 13:38 [PATCH 0/2] Introduce panic hypercall Daniel Gollub
2011-06-20 13:38 ` [PATCH 1/2] Inroduce panic hypercall KVM_HC_PANIC (host) Daniel Gollub
2011-06-20 13:38 ` [PATCH 2/2] Call KVM_HC_PANIC if guest panics Daniel Gollub
2011-06-20 15:31 ` [PATCH 0/2] Introduce panic hypercall Avi Kivity
2011-06-20 15:38 ` Daniel P. Berrange
2011-06-20 15:45 ` Avi Kivity
2011-06-20 15:59 ` Jan Kiszka [this message]
2011-06-20 16:26 ` Daniel Gollub
2011-06-20 16:34 ` Avi Kivity
2011-06-20 17:13 ` Jan Kiszka
2011-06-20 17:23 ` Avi Kivity
2011-06-21 6:04 ` Gleb Natapov
2011-06-21 6:02 ` Gleb Natapov
2011-06-21 8:09 ` Avi Kivity
2011-06-21 8:41 ` Gleb Natapov
2011-06-21 8:56 ` Avi Kivity
2011-06-21 9:03 ` Gleb Natapov
2011-06-21 9:07 ` Avi Kivity
2011-06-21 9:30 ` shawn che
2011-06-20 19:28 ` Anthony Liguori
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=4DFF6E57.7040109@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=berrange@redhat.com \
--cc=gollub@b1-systems.de \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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