|
From: | Avi Kivity |
Subject: | Re: [Qemu-devel] [PATCH 00/22] QAPI Round 1 |
Date: | Wed, 09 Mar 2011 15:14:40 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.7 |
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. -- error compiling committee.c: too many arguments to function
[Prev in Thread] | Current Thread | [Next in Thread] |