From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LrYcN-0007fD-Ss for qemu-devel@nongnu.org; Wed, 08 Apr 2009 10:19:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LrYcJ-0007dB-7o for qemu-devel@nongnu.org; Wed, 08 Apr 2009 10:19:07 -0400 Received: from [199.232.76.173] (port=53562 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LrYcJ-0007d5-2R for qemu-devel@nongnu.org; Wed, 08 Apr 2009 10:19:03 -0400 Received: from wa-out-1112.google.com ([209.85.146.183]:5224) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LrYcI-0004zH-OQ for qemu-devel@nongnu.org; Wed, 08 Apr 2009 10:19:02 -0400 Received: by wa-out-1112.google.com with SMTP id m33so111973wag.18 for ; Wed, 08 Apr 2009 07:19:01 -0700 (PDT) Message-ID: <49DCB24F.1040009@codemonkey.ws> Date: Wed, 08 Apr 2009 09:18:55 -0500 From: Anthony Liguori MIME-Version: 1.0 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> In-Reply-To: <20090408092256.GD18076@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [libvirt] Re: [PATCH] Hardware watchdog patch, version 6 Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" , qemu-devel@nongnu.org Cc: libvir-list@redhat.com, "Richard W.M. Jones" , Hollis Blanchard 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. Regards, Anthony Liguori