From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm list <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>,
linux-kernel@vger.kernel.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH] kvm: notify host when guest paniced
Date: Wed, 29 Feb 2012 12:00:41 +0200 [thread overview]
Message-ID: <4F4DF749.7060507@redhat.com> (raw)
In-Reply-To: <20120229095557.GE24600@redhat.com>
On 02/29/2012 11:55 AM, Gleb Natapov wrote:
> > >
> >
> > How about using a virtio-serial channel for this? You can transfer any
> > amount of information (including the dump itself).
> >
> Isn't it unreliable after the guest panicked?
So is calling hypercalls, or dumping, or writing to the screen. Of
course calling a hypercall is simpler and so is more reliable.
> Having special kdump
> kernel that transfers dump to a host via virtio-serial channel though
> sounds interesting. May be that's what you mean.
Yes. The "panic, starting dump" signal should be initiated by the
panicking kernel though, in case the dump fails.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-02-29 10:00 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
2012-02-29 9:55 ` Gleb Natapov
2012-02-29 10:00 ` Avi Kivity [this message]
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=4F4DF749.7060507@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).