[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Hardware watchdog patch, version 6 (was: Re: [Qemu-devel] [P

From: Richard W.M. Jones
Subject: Re: [PATCH] Hardware watchdog patch, version 6 (was: Re: [Qemu-devel] [PATCH] Hardware watchdog patch, version 5)
Date: Wed, 8 Apr 2009 09:39:48 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

On Tue, Apr 07, 2009 at 04:19:42PM -0500, Hollis Blanchard wrote:
> Hi Rich, your watchdog qemu patch is working fine for me (i6300esb,
> default reset behavior),

Hi, first of all thanks for testing this.  I'm going to put forward an
updated/finalized patch but it won't be til next week.

> but I was wondering... how should libvirt find
> out about the watchdog firing?

Good question.  When we've talked about adding support for the
watchdog in libvirt, I've only been thinking about configuring it, not
about how to find out when it fires.  This is a bit tricky because we
have to both get qemu to generate an event (eg. a monitor message),
and then get libvirt to handle that event.

Thus I'll throw this open to libvir-list to see if anyone has
an idea how to implement that ...

Reply-To set to libvir-list ...

> At that point, I think the next step from libvirt is to send a
> VIR_DOMAIN_EVENT_STOPPED_CRASHED domain event, correct?


Richard Jones, Emerging Technologies, Red Hat  http://et.redhat.com/~rjones
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]