From: Hollis Blanchard <hollisb@us.ibm.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: libvir-list@redhat.com, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH] Hardware watchdog patch, version 6 (was: Re: [Qemu-devel] [PATCH] Hardware watchdog patch, version 5)
Date: Tue, 07 Apr 2009 16:19:42 -0500 [thread overview]
Message-ID: <1239139182.9183.121.camel@slate.austin.ibm.com> (raw)
In-Reply-To: <20090401084620.GA17093@amd.home.annexia.org>
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?
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2009-04-07 21:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 18:49 [Qemu-devel] [PATCH] Hardware watchdog patch, version 5 Richard W.M. Jones
2009-03-25 8:43 ` Richard W.M. Jones
2009-03-26 13:03 ` Anthony Liguori
2009-03-31 11:23 ` [PATCH] Hardware watchdog patch, version 6 (was: Re: [Qemu-devel] [PATCH] Hardware watchdog patch, version 5) Richard W.M. Jones
2009-03-31 11:24 ` Richard W.M. Jones
2009-03-31 16:07 ` Blue Swirl
2009-04-01 8:46 ` Richard W.M. Jones
2009-04-01 13:18 ` [Qemu-devel] Re: [PATCH] Hardware watchdog patch, version 6 Anthony Liguori
2009-04-25 12:56 ` [Qemu-devel] [PATCH] Hardware watchdog patch, version 7 Richard W.M. Jones
2009-04-07 21:19 ` Hollis Blanchard [this message]
2009-04-08 8:39 ` [PATCH] Hardware watchdog patch, version 6 (was: Re: [Qemu-devel] [PATCH] Hardware watchdog patch, version 5) Richard W.M. Jones
2009-04-08 9:22 ` [libvirt] " Daniel P. Berrange
2009-04-08 14:18 ` [Qemu-devel] Re: [libvirt] Re: [PATCH] Hardware watchdog patch, version 6 Anthony Liguori
2009-04-08 14:35 ` Daniel P. Berrange
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=1239139182.9183.121.camel@slate.austin.ibm.com \
--to=hollisb@us.ibm.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.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 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).