From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nevoz-00011v-La for qemu-devel@nongnu.org; Tue, 09 Feb 2010 14:32:29 -0500 Received: from [199.232.76.173] (port=50223 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nevoy-00011n-BN for qemu-devel@nongnu.org; Tue, 09 Feb 2010 14:32:28 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Nevox-0002rU-5H for qemu-devel@nongnu.org; Tue, 09 Feb 2010 14:32:28 -0500 Received: from mail2.shareable.org ([80.68.89.115]:33901) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Nevow-0002rO-P7 for qemu-devel@nongnu.org; Tue, 09 Feb 2010 14:32:27 -0500 Date: Tue, 9 Feb 2010 19:32:22 +0000 From: Jamie Lokier Subject: Re: [Qemu-devel] Re: Two QMP events issues Message-ID: <20100209193222.GC946@shareable.org> References: <20100208114145.4bd64349@doriath> <20100208141218.GG17328@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100208141218.GG17328@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: armbru@redhat.com, aliguori@us.ibm.com, qemu-devel@nongnu.org, Luiz Capitulino Daniel P. Berrange wrote: > For further backgrou, the key end goal here is that in a QMP client, upon > receipt of the 'RESET' event, we need to reliably & immediately determine > why it occurred. eg, triggered by watchdog, or by guest OS request. There > are actually 3 possible sequences Note that some on hardware, the OS requests a normal reset by setting the watchdog to a short timeout and waiting :-) -- Jamie