From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M3cWT-0006iP-1v for qemu-devel@nongnu.org; Mon, 11 May 2009 16:54:53 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M3cWN-0006i8-OF for qemu-devel@nongnu.org; Mon, 11 May 2009 16:54:51 -0400 Received: from [199.232.76.173] (port=50359 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M3cWN-0006i3-FE for qemu-devel@nongnu.org; Mon, 11 May 2009 16:54:47 -0400 Received: from e8.ny.us.ibm.com ([32.97.182.138]:59004) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M3cWN-0000pN-5Q for qemu-devel@nongnu.org; Mon, 11 May 2009 16:54:47 -0400 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e8.ny.us.ibm.com (8.13.1/8.13.1) with ESMTP id n4BKisQw010482 for ; Mon, 11 May 2009 16:44:54 -0400 Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n4BKsgFP099798 for ; Mon, 11 May 2009 16:54:42 -0400 Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n4BKsfYH000776 for ; Mon, 11 May 2009 16:54:41 -0400 Subject: Re: [Qemu-devel] [PATCH 1/6] Allow multiple monitor devices (v2) From: Hollis Blanchard In-Reply-To: <1239215702-23818-1-git-send-email-aliguori@us.ibm.com> References: <1239215702-23818-1-git-send-email-aliguori@us.ibm.com> Content-Type: text/plain Date: Mon, 11 May 2009 15:54:40 -0500 Message-Id: <1242075280.29194.117.camel@slate.austin.ibm.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: libvir-list@redhat.com, Anthony Liguori , Jan Kiszka , Avi Kivity , "Richard W.M. Jones" On Wed, 2009-04-08 at 13:34 -0500, Anthony Liguori wrote: > Right now only one monitor device can be enabled at a time. In order to support > asynchronous notification of events, I would like to introduce a 'wait' command > that waits for an event to occur. This implies that we need an additional > monitor session to allow commands to still be executed while waiting for an > asynchronous notification. Was there any consensus reached in this thread? I'm once again looking for ways to communicate qemu watchdog events to libvirt. With these patches, libvirt could open a second monitor connection to qemu, and in the second one execute "wait_event". When the watchdog triggers, the wait command would print the event, libvirt would get the fd "data available" notification, and create a domain event. Right? -- Hollis Blanchard IBM Linux Technology Center