qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Yan Vugenfirer <yvugenfi@redhat.com>
Cc: kvm list <kvm@vger.kernel.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Gleb Natapov <gleb@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH v8] kvm: notify host when the guest is panicked
Date: Tue, 14 Aug 2012 12:42:37 -0300	[thread overview]
Message-ID: <20120814154237.GA21284@amt.cnet> (raw)
In-Reply-To: <86E2467F-0EA3-4A03-BD89-58E41F7DB808@redhat.com>

On Tue, Aug 14, 2012 at 05:55:54PM +0300, Yan Vugenfirer wrote:
> 
> On Aug 14, 2012, at 1:42 PM, Jan Kiszka wrote:
> 
> > On 2012-08-14 10:56, Daniel P. Berrange wrote:
> >> On Mon, Aug 13, 2012 at 03:21:32PM -0300, Marcelo Tosatti wrote:
> >>> On Wed, Aug 08, 2012 at 10:43:01AM +0800, Wen Congyang wrote:
> >>>> We can know the guest is panicked when the guest runs on xen.
> >>>> But we do not have such feature on kvm.
> >>>> 
> >>>> Another purpose of this feature is: management app(for example:
> >>>> libvirt) can do auto dump when the guest is panicked. If management
> >>>> app does not do auto dump, the guest's user can do dump by hand if
> >>>> he sees the guest is panicked.
> >>>> 
> >>>> We have three solutions to implement this feature:
> >>>> 1. use vmcall
> >>>> 2. use I/O port
> >>>> 3. use virtio-serial.
> >>>> 
> >>>> We have decided to avoid touching hypervisor. The reason why I choose
> >>>> choose the I/O port is:
> >>>> 1. it is easier to implememt
> >>>> 2. it does not depend any virtual device
> >>>> 3. it can work when starting the kernel
> >>> 
> >>> How about searching for the "Kernel panic - not syncing" string 
> >>> in the guests serial output? Say libvirtd could take an action upon
> >>> that?
> >> 
> >> No, this is not satisfactory. It depends on the guest OS being
> >> configured to use the serial port for console output which we
> >> cannot mandate, since it may well be required for other purposes.
> > 
> Please don't forget Windows guests, there is no console and no "Kernel Panic" string ;)
> 
> What I used for debugging purposes on Windows guest is to register a bugcheck callback in virtio-net driver and write 1 to VIRTIO_PCI_ISR register.
> 
> Yan. 

Considering whether a "panic-device" should cover other OSes is also 
something to consider. Even for Linux, is "panic" the only case which
should be reported via the mechanism? What about oopses without panic? 

Is the mechanism general enough for supporting new events, etc.

> 
> > Well, we have more than a single serial port, even when leaving
> > virtio-serial aside...
> > 
> > Jan
> > 
> > -- 
> > Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
> > Corporate Competence Center Embedded Linux
> > --
> > To unsubscribe from this list: send the line "unsubscribe kvm" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2012-08-14 15:48 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08  2:43 [Qemu-devel] [PATCH v8] kvm: notify host when the guest is panicked Wen Congyang
2012-08-08  2:44 ` [Qemu-devel] [PATCH v8 1/6] start vm after reseting it Wen Congyang
2012-08-08  2:45 ` [Qemu-devel] [PATCH v8 2/6] kvm: Update kernel headers Wen Congyang
2012-08-08  2:45 ` [Qemu-devel] [PATCH v8 3/6] add a new runstate: RUN_STATE_GUEST_PANICKED Wen Congyang
2012-08-08  2:46 ` [Qemu-devel] [PATCH v8 4/6] add a new qevent: QEVENT_GUEST_PANICKED Wen Congyang
2012-08-08  2:47 ` [Qemu-devel] [PATCH v8 5/6] introduce a new qom device to deal with panicked event Wen Congyang
2012-08-08 19:01   ` Blue Swirl
2012-08-22  7:30     ` Wen Congyang
2012-08-25  7:36       ` Blue Swirl
2012-08-08  2:47 ` [Qemu-devel] [PATCH v8 6/6] allower the user to disable pv event support Wen Congyang
2012-08-08  9:12 ` [Qemu-devel] [PATCH v8] kvm: notify host when the guest is panicked Andrew Jones
2012-08-08  9:28   ` Wen Congyang
2012-08-13 18:21 ` Marcelo Tosatti
2012-08-13 19:48   ` Eric Blake
2012-08-13 20:24     ` Marcelo Tosatti
2012-08-14  7:47       ` Gleb Natapov
2012-08-14 15:29         ` Marcelo Tosatti
2012-08-14 15:50           ` Gleb Natapov
2012-08-14  8:56   ` Daniel P. Berrange
2012-08-14 10:42     ` Jan Kiszka
2012-08-14 14:55       ` Yan Vugenfirer
2012-08-14 15:01         ` Jan Kiszka
2012-08-14 15:42         ` Marcelo Tosatti [this message]
2012-08-14 18:53           ` Anthony Liguori
2012-08-14 19:19             ` Marcelo Tosatti
2012-08-14 19:35               ` Anthony Liguori
2012-08-14 20:53                 ` Marcelo Tosatti
2012-08-14 22:59                   ` Anthony Liguori
2012-08-15  0:25                     ` [Qemu-devel] [PATCH v8] kvm: notify host when the guest is panicked\ Marcelo Tosatti
2012-08-22  6:33                   ` [Qemu-devel] [PATCH v8] kvm: notify host when the guest is panicked Wen Congyang
2012-08-15  9:56                 ` Gleb Natapov
2012-08-15 11:42                   ` Yan Vugenfirer
2012-08-15 11:38                 ` Yan Vugenfirer
2012-08-14 19:58             ` Peter Maydell

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=20120814154237.GA21284@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=avi@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=yvugenfi@redhat.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).