From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Steve Fosdick <lists@pelvoux.nildram.co.uk>
Subject: Re: [Qemu-devel] Hardware watchdogs (patch for discussion only)
Date: Fri, 27 Feb 2009 12:19:53 +0000 [thread overview]
Message-ID: <200902271219.54657.paul@codesourcery.com> (raw)
In-Reply-To: <1235728224.5894.176.camel@ecrins.fosdick.home.net>
On Friday 27 February 2009, Steve Fosdick wrote:
> On Thu, 2009-02-26 at 17:50 +0000, Jamie Lokier wrote:
> > For real continuity of service you'd also want QEMU itself to have a
> > watchdog. Either a software watchdog internally (SIGALRM => kill/exec
> > self, or child process expecting regular pings over a pipe), or by
> > QEMU itself becoming a client of the host watchdog.
>
> So many possibilities - one, two, or three watchdogs?
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.
There already exist several solutions for external fencing. Traditionally
these are used in a clustered environment, where physical machines are
connected to remote power switches (or equivalent management cards). Making
these system kill/restart virtual machines seems like it should be a very
minor tweak.
Paul
next prev parent reply other threads:[~2009-02-27 12:20 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 [this message]
2009-02-28 21:34 ` Jamie Lokier
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=200902271219.54657.paul@codesourcery.com \
--to=paul@codesourcery.com \
--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).