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:48:57 +0200 [thread overview]
Message-ID: <4F4E0299.9080800@redhat.com> (raw)
In-Reply-To: <20120229104449.GG24600@redhat.com>
On 02/29/2012 12:44 PM, Gleb Natapov wrote:
> > > >
> > > Yes, crash can be so severe that it is not even detected by a kernel
> > > itself, so not OOPS message even printed. But in most cases if kernel is
> > > functional enough to print OOPS it is functional enough to call single
> > > hypercall instruction.
> >
> > Why not print the oops to virtio-serial? Or even just a regular serial
> > port? That's what bare metal does.
> >
> The more interface is complex the more chances it will fail during
> panic. Regular serial is likely more reliable than virtio-serial.
> Hypercall is likely more reliable than uart. On serial user can
> fake panic notification.
The serial device is under control of the kernel, so the user can only
access it if the kernel so allows.
> Can this be problematic?
>From the point of view of the guest, yes, it can generate support calls
in fill up the admin's dump quota. From the point of view of the host,
there's no difference between the guest's admin and a random user.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-02-29 10:49 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
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 [this message]
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=4F4E0299.9080800@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).