qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	kvm list <kvm@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] kvm: notify host when guest paniced
Date: Wed, 29 Feb 2012 11:49:58 +0200	[thread overview]
Message-ID: <4F4DF4C6.90609@redhat.com> (raw)
In-Reply-To: <4F4D7F5E.5040202@cn.fujitsu.com>

On 02/29/2012 03:29 AM, Wen Congyang wrote:
> At 02/28/2012 07:23 PM, Avi Kivity Wrote:
> > On 02/27/2012 05:01 AM, Wen Congyang wrote:
> >> We can know the guest is paniced when the guest runs on xen.
> >> But we do not have such feature on kvm. This patch implemnts
> >> this feature, and the implementation is the same as xen:
> >> register panic notifier, and call hypercall when the guest
> >> is paniced.
> > 
> > What's the motivation for this?  "Xen does this" is insufficient.
>
> Another purpose is: management app(for example: libvirt) can do auto
> dump when the guest is crashed. If management app does not do auto
> dump, the guest's user can do dump by hand if he sees the guest is
> paniced.
>
> I am thinking about another status: dumping. This status tells
> the guest's user that the guest is paniced, and the OS's dump function
> is working.
>
> These two status can tell the guest's user whether the guest is pancied,
> and what should he do if the guest is paniced.
>

How about using a virtio-serial channel for this?  You can transfer any
amount of information (including the dump itself).

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2012-02-29  9:50 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27  3:01 [Qemu-devel] [PATCH] kvm: notify host when guest paniced Wen Congyang
2012-02-27  3:05 ` [Qemu-devel] [PATCH]qemu: deal with guest paniced event Wen Congyang
2012-02-27  8:59   ` Jan Kiszka
2012-03-01 16:51   ` Luiz Capitulino
2012-03-02  0:40     ` Wen Congyang
2012-02-27 15:08 ` [Qemu-devel] [PATCH] kvm: notify host when guest paniced Jan Kiszka
2012-02-28  5:26   ` Wen Congyang
2012-02-28  8:07     ` Wen Congyang
2012-02-28  8:23   ` Wen Congyang
2012-02-28  9:34     ` Jan Kiszka
2012-02-28  9:42       ` Wen Congyang
2012-02-28 10:19         ` Jan Kiszka
2012-02-28 10:45           ` Gleb Natapov
2012-02-29  1:08             ` Wen Congyang
2012-02-29  9:36               ` Gleb Natapov
2012-02-29 10:06                 ` Wen Congyang
2012-02-28 11:23 ` Avi Kivity
2012-02-29  1:29   ` Wen Congyang
2012-02-29  9:49     ` Avi Kivity [this message]
2012-02-29  9:55       ` Gleb Natapov
2012-02-29 10:00         ` Avi Kivity
2012-02-29 10:05           ` Gleb Natapov
2012-02-29 10:08             ` Avi Kivity
2012-02-29 10:17               ` Wen Congyang
2012-02-29 10:39                 ` Avi Kivity
2012-03-01  3:34                   ` Wen Congyang
2012-03-01  5:21                   ` Wen Congyang
2012-02-29 10:44               ` Gleb Natapov
2012-02-29 10:48                 ` Avi Kivity
2012-02-29 10:52                   ` Gleb Natapov
2012-02-29  9:58       ` Daniel P. Berrange
2012-02-29 10:05         ` Avi Kivity
2012-02-29 10:19           ` Daniel P. Berrange
2012-02-29 10:44             ` Avi Kivity
2012-02-29 10:31           ` Wen Congyang
2012-02-29 10:46             ` Avi Kivity

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=4F4DF4C6.90609@redhat.com \
    --to=avi@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).