From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LrYsR-00067y-5B for qemu-devel@nongnu.org; Wed, 08 Apr 2009 10:35:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LrYsM-00061E-8I for qemu-devel@nongnu.org; Wed, 08 Apr 2009 10:35:42 -0400 Received: from [199.232.76.173] (port=50497 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LrYsM-00060v-04 for qemu-devel@nongnu.org; Wed, 08 Apr 2009 10:35:38 -0400 Received: from mx1.redhat.com ([66.187.233.31]:49742) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LrYsL-0007JM-K9 for qemu-devel@nongnu.org; Wed, 08 Apr 2009 10:35:37 -0400 Date: Wed, 8 Apr 2009 15:35:32 +0100 From: "Daniel P. Berrange" Message-ID: <20090408143532.GT18076@redhat.com> References: <20090316184929.GA20955@amd.home.annexia.org> <49CB7D33.70002@us.ibm.com> <20090331112354.GA18048@amd.home.annexia.org> <20090401084620.GA17093@amd.home.annexia.org> <1239139182.9183.121.camel@slate.austin.ibm.com> <20090408092256.GD18076@redhat.com> <49DCB24F.1040009@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49DCB24F.1040009@codemonkey.ws> Subject: [Qemu-devel] Re: [libvirt] Re: [PATCH] Hardware watchdog patch, version 6 Reply-To: "Daniel P. Berrange" , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: libvir-list@redhat.com, qemu-devel@nongnu.org, Hollis Blanchard , "Richard W.M. Jones" 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 :|