From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=40024 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PxJnD-0006a6-I9 for qemu-devel@nongnu.org; Wed, 09 Mar 2011 08:51:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PxJnC-00015N-Gn for qemu-devel@nongnu.org; Wed, 09 Mar 2011 08:51:11 -0500 Received: from e31.co.us.ibm.com ([32.97.110.149]:43462) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PxJnC-00014n-7n for qemu-devel@nongnu.org; Wed, 09 Mar 2011 08:51:10 -0500 Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by e31.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p29Da2hL007352 for ; Wed, 9 Mar 2011 06:36:02 -0700 Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p29Dp7av075536 for ; Wed, 9 Mar 2011 06:51:07 -0700 Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p29Dtp8f015101 for ; Wed, 9 Mar 2011 06:55:51 -0700 Message-ID: <4D7785C8.9090904@linux.vnet.ibm.com> Date: Wed, 09 Mar 2011 07:51:04 -0600 From: Michael Roth MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 00/22] QAPI Round 1 References: <1299460984-15849-1-git-send-email-aliguori@us.ibm.com> <4D7500C8.1080101@codemonkey.ws> <4D760F2B.7030004@redhat.com> <4D7630BA.4010609@us.ibm.com> <4D763311.5030905@redhat.com> <4D763525.2030700@codemonkey.ws> <4D763674.8000600@redhat.com> <4D7638BE.60808@codemonkey.ws> <4D763A61.2020809@redhat.com> <4D763F76.2020003@codemonkey.ws> <4D7642C1.90604@redhat.com> <4D764551.4000409@codemonkey.ws> <4D766B0E.9030908@redhat.com> <4D768134.9000006@codemonkey.ws> <4D773FAC.4090208@redhat.com> <4D777CD5.30403@codemonkey.ws> <4D777D40.4020000@redhat.com> In-Reply-To: <4D777D40.4020000@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Stefan Hajnoczi , qemu-devel@nongnu.org, Luiz Capitulino , Michael D Roth , Adam Litke , Markus Armbruster On 03/09/2011 07:14 AM, Avi Kivity wrote: > On 03/09/2011 03:12 PM, Anthony Liguori wrote: >> On 03/09/2011 02:51 AM, Avi Kivity wrote: >>> On 03/08/2011 09:19 PM, Anthony Liguori wrote: >>>>> Both the guest and the management agent (and both can listen for >>>>> events). I don't see why guest->qemu RPC is problematic for >>>>> migration - at least when qemu terminates it. >>>> >>>> >>>> If it's terminated in QEMU, it's fine, but then it's not QMP >>>> anymore. Let me think about whether there's a way to achieve this >>>> without a guest->qemu RPC. >>> >>> Why not? >>> >>> { execute: 'write-keystore' arguments: { 'key': 'foo', 'value': 'bar' >>> } } >> >> This is coming from the guest? > > Yes. > >> QMP doesn't do bidirectional RPC today. It could, but that is a >> fundamental change in the protocol. >> > > Could use a separate channel for talking to qemu. > That's a possibility. Might be tricky to do right though...we wouldn't want to have a guest get a normal QMP session over the channel, so we'd likely end up with a separate QMP server that uses a different guest-specific dispatch table for commands. Would be nice to not have to rely on multiple channels though...particularly in the case of isa-serial channels where available ports might be scarce. But I wouldn't consider that a showstopper either.