On Wed, Apr 08, 2009 at 09:18:55AM -0500, Anthony Liguori wrote:
> Daniel P. Berrange wrote:
> >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), but I was wondering... how sho
Daniel P. Berrange wrote:
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), but I was wondering... how should libvirt find
out about the watchdog firing?
This falls into the gen
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), but I was wondering... how should libvirt find
> out about the watchdog firing?
This falls into the general problem space of how does Q
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
Hi Rich, your watchdog qemu patch is working fine for me (i6300esb,
default reset behavior), but I was wondering... how should libvirt find
out about the watchdog firing?
At that point, I think the next step from libvirt is to send a
VIR_DOMAIN_EVENT_STOPPED_CRASHED domain event, correct?
--
Hol
