qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Cc: Steve Fosdick <lists@pelvoux.nildram.co.uk>
Subject: Re: [Qemu-devel] Hardware watchdogs (patch for discussion only)
Date: Sat, 28 Feb 2009 21:34:10 +0000	[thread overview]
Message-ID: <20090228213410.GM20640@shareable.org> (raw)
In-Reply-To: <200902271219.54657.paul@codesourcery.com>

Paul Brook wrote:
> IMHO external watchdog (i.e. ones that monitor qemu itself) are out
> of scope.  We should restrict this to internal watchdog devices
> within a VM.

I agree.  The thing of interest is whether the guest is running, not
whether QEMU is running.

It would be good for the internal watchdog device to have the option
of no effect except for its status to be available in the QEMU
monitor, so management apps can see when the guest has crashed.

Steve's idea of a matrix (Guest event -> QEMU action) is a good one,
and could include "watchdog not pinged" as a guest event.

-- Jamie

  reply	other threads:[~2009-02-28 21:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25 23:37 [Qemu-devel] Hardware watchdogs (patch for discussion only) Richard W.M. Jones
2009-02-26 10:51 ` Daniel P. Berrange
2009-02-26 13:55   ` Richard W.M. Jones
2009-02-26 19:30     ` Blue Swirl
2009-02-26 14:31   ` Steve Fosdick
2009-02-26 14:45     ` Richard W.M. Jones
2009-02-27  9:55       ` Steve Fosdick
2009-02-26 17:50     ` Jamie Lokier
2009-02-27  9:50       ` Steve Fosdick
2009-02-27 12:19         ` Paul Brook
2009-02-28 21:34           ` Jamie Lokier [this message]
2009-02-28 22:00             ` Andreas Färber
2009-02-28 22:11           ` Richard W.M. Jones

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=20090228213410.GM20640@shareable.org \
    --to=jamie@shareable.org \
    --cc=lists@pelvoux.nildram.co.uk \
    --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).