From: Paolo Bonzini <pbonzini@redhat.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: kvm list <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Avi Kivity <avi@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH 3/3] deal with guest panicked event
Date: Tue, 12 Jun 2012 15:29:43 +0200 [thread overview]
Message-ID: <4FD74447.2090906@redhat.com> (raw)
In-Reply-To: <4FB9E5CB.2020208@cn.fujitsu.com>
Il 21/05/2012 08:50, Wen Congyang ha scritto:
> +DEF("onpanic", HAS_ARG, QEMU_OPTION_onpanic, \
> + "-onpanic report|pause|quit\n" \
> + " action when the guest is panicked [default=report]",
> + QEMU_ARCH_ALL)
> +STEXI
> +@item -onpanic @var{action}
> +
> +The @var{action} controls what QEmu will do when the guest is panicked.
> +The default is @code{report} (emit QEVENT_GUEST_PANICKED only).
-watchdog-action just calls this "none".
> +Other possible actions are:
> +@code{pause} (emit QEVENT_GUEST_PANICKED and pause VM),
> +@code{quit} (emit QEVENT_GUEST_PANICKED and quit VM).
Rather than just "quit", there should be choices for "shutdown",
"poweroff" and "reset" for consistency with -watchdog-action.
Also, this option should also be accessible from "-machine", please.
Paolo
> +ETEXI
> +
> HXCOMM This is the last statement. Insert new options before this line!
> STEXI
> @end table
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Gleb Natapov <gleb@redhat.com>, kvm list <kvm@vger.kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel <qemu-devel@nongnu.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Avi Kivity <avi@redhat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH 3/3] deal with guest panicked event
Date: Tue, 12 Jun 2012 15:29:43 +0200 [thread overview]
Message-ID: <4FD74447.2090906@redhat.com> (raw)
In-Reply-To: <4FB9E5CB.2020208@cn.fujitsu.com>
Il 21/05/2012 08:50, Wen Congyang ha scritto:
> +DEF("onpanic", HAS_ARG, QEMU_OPTION_onpanic, \
> + "-onpanic report|pause|quit\n" \
> + " action when the guest is panicked [default=report]",
> + QEMU_ARCH_ALL)
> +STEXI
> +@item -onpanic @var{action}
> +
> +The @var{action} controls what QEmu will do when the guest is panicked.
> +The default is @code{report} (emit QEVENT_GUEST_PANICKED only).
-watchdog-action just calls this "none".
> +Other possible actions are:
> +@code{pause} (emit QEVENT_GUEST_PANICKED and pause VM),
> +@code{quit} (emit QEVENT_GUEST_PANICKED and quit VM).
Rather than just "quit", there should be choices for "shutdown",
"poweroff" and "reset" for consistency with -watchdog-action.
Also, this option should also be accessible from "-machine", please.
Paolo
> +ETEXI
> +
> HXCOMM This is the last statement. Insert new options before this line!
> STEXI
> @end table
next prev parent reply other threads:[~2012-06-12 13:29 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 6:46 [PATCH] kvm: notify host when guest panicked Wen Congyang
2012-05-21 6:46 ` [Qemu-devel] " Wen Congyang
2012-05-21 6:49 ` [PATCH 1/3] start vm after reseting it Wen Congyang
2012-05-21 6:49 ` [Qemu-devel] " Wen Congyang
2012-05-30 19:17 ` Luiz Capitulino
2012-05-30 19:17 ` [Qemu-devel] " Luiz Capitulino
2012-06-12 7:23 ` Wen Congyang
2012-06-12 7:23 ` Wen Congyang
2012-06-13 6:54 ` Wen Congyang
2012-06-13 6:54 ` [Qemu-devel] " Wen Congyang
2012-06-13 6:54 ` Wen Congyang
2012-05-21 6:50 ` [PATCH 2/3] update linux headers Wen Congyang
2012-05-21 6:50 ` [Qemu-devel] " Wen Congyang
2012-05-21 6:50 ` [PATCH 3/3] deal with guest panicked event Wen Congyang
2012-05-21 6:50 ` [Qemu-devel] " Wen Congyang
2012-05-22 11:32 ` Jan Kiszka
2012-05-22 11:32 ` [Qemu-devel] " Jan Kiszka
2012-05-22 11:32 ` Jan Kiszka
2012-05-30 19:23 ` Luiz Capitulino
2012-05-30 19:23 ` [Qemu-devel] " Luiz Capitulino
2012-06-12 6:55 ` Wen Congyang
2012-06-12 6:55 ` Wen Congyang
2012-06-12 12:35 ` Luiz Capitulino
2012-06-12 12:35 ` Luiz Capitulino
2012-06-12 12:40 ` Daniel P. Berrange
2012-06-12 12:40 ` Daniel P. Berrange
2012-06-12 13:21 ` Luiz Capitulino
2012-06-12 13:21 ` Luiz Capitulino
2012-06-12 13:29 ` Paolo Bonzini [this message]
2012-06-12 13:29 ` Paolo Bonzini
2012-06-13 7:02 ` Wen Congyang
2012-06-13 7:02 ` [Qemu-devel] " Wen Congyang
2012-06-13 7:53 ` Paolo Bonzini
2012-06-13 7:53 ` [Qemu-devel] " Paolo Bonzini
2012-06-13 7:53 ` Paolo Bonzini
2012-06-13 8:00 ` Wen Congyang
2012-06-13 8:00 ` [Qemu-devel] " Wen Congyang
2012-06-13 8:00 ` Wen Congyang
2012-06-12 6:47 ` [PATCH] kvm: notify host when guest panicked Wen Congyang
2012-06-12 6:47 ` [Qemu-devel] " Wen Congyang
2012-06-12 7:49 ` Christian Borntraeger
2012-06-12 7:49 ` [Qemu-devel] " Christian Borntraeger
2012-06-12 8:07 ` Wen Congyang
2012-06-12 8:07 ` [Qemu-devel] " Wen Congyang
2012-06-12 8:26 ` Wen Congyang
2012-06-12 8:26 ` [Qemu-devel] " Wen Congyang
2012-06-12 8:26 ` Wen Congyang
2012-06-12 9:49 ` Gleb Natapov
2012-06-12 9:49 ` [Qemu-devel] " Gleb Natapov
2012-06-12 9:49 ` Gleb Natapov
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=4FD74447.2090906@redhat.com \
--to=pbonzini@redhat.com \
--cc=avi@redhat.com \
--cc=berrange@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=wency@cn.fujitsu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.