From: "Daniel P. Berrange" <berrange@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: libvir-list@redhat.com, qemu-devel@nongnu.org,
Hollis Blanchard <hollisb@us.ibm.com>,
"Richard W.M. Jones" <rjones@redhat.com>
Subject: [Qemu-devel] Re: [libvirt] Re: [PATCH] Hardware watchdog patch, version 6
Date: Wed, 8 Apr 2009 15:35:32 +0100 [thread overview]
Message-ID: <20090408143532.GT18076@redhat.com> (raw)
In-Reply-To: <49DCB24F.1040009@codemonkey.ws>
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 should libvirt find
> >>out about the watchdog firing?
> >>
> >
> >This falls into the general problem space of how does QEMU notify its
> >management app of interesting events. We already really want the
> >ability to be notify of ENOSPC errors in disks, and also would like
> >to know if the VM is paused for any reason outside our control.
> >There have been proposals to just print an async message to the
> >monitor upon events, that mgmt app could then parse. This is a little
> >fragile though, so for a long term solutiuon we really need the generic
> >libqemumonitor.so type API with formal async notification support.
> >
>
> I just posted a patch series that demonstrate how I think it should
> work. FWIW, I think notifications are orthogonal to libqemumonitor.so
> and a non-human monitor mode.
If we get a way to have async events without waiting for libqemumonitor.so
that'd make me very happy :-)
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
prev parent reply other threads:[~2009-04-08 14:35 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 ` [PATCH] Hardware watchdog patch, version 6 (was: Re: [Qemu-devel] [PATCH] Hardware watchdog patch, version 5) Hollis Blanchard
2009-04-08 8:39 ` 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 [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=20090408143532.GT18076@redhat.com \
--to=berrange@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=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).