From: Charles Duffy <cduffy@spamcop.net>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Basic xenstore questions (building a watchdog)
Date: Fri, 13 Jan 2006 09:16:41 -0600 [thread overview]
Message-ID: <43C7C459.1070107@spamcop.net> (raw)
In-Reply-To: <200601131451.02874.mark.williamson@cl.cam.ac.uk>
Mark Williamson wrote:
>> I'm looking at building a xenstore-based watchdog, as described at
>> http://lists.xensource.com/archives/html/xen-users/2005-07/msg00597.html
>>
>
> Sounds cool!
>
> I knocked up a little prototype of one some time last year. The Xend code was
> surprisingly tricky (couldn't get rebooting the domain to behave right,
> although I didn't try very hard). You'd be welcome to the kernel code if you
> want to take a look, although it's very simple - the hacks required to the
> softdog device in Linux were minimal.
>
I would be very much interested in looking at what you've got so far, as
an example if not a base.
> I'd suggest as an alternative to using the store, you might like to think
> about adding watchdog functionality to Xen itself... The advantage here is
> that it also allows you to watchdog dom0, without requiring watchdog
> hardware. Timing out dom0 would reboot the system, a domU would just result
> in its destruction (and the tools recreating it).
>
It's a thought, yes -- but I'm already outside the realm of
stuff-I-know, and I'd like to get at least *something* in working
condition before I stray much further. Also, I'm under the impression
that running softdog in dom0 with nowayout set should provide similar
functionality -- perhaps I saw someone mentioning on the ML that they
were doing just that?
prev parent reply other threads:[~2006-01-13 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 21:46 Basic xenstore questions (building a watchdog) Charles Duffy
2006-01-13 13:34 ` Ewan Mellor
2006-01-16 18:35 ` Charles Duffy
2006-01-13 14:51 ` Mark Williamson
2006-01-13 15:16 ` Charles Duffy [this message]
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=43C7C459.1070107@spamcop.net \
--to=cduffy@spamcop.net \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.