From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=33948 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PrVyJ-0000rz-Iv
	for qemu-devel@nongnu.org; Mon, 21 Feb 2011 08:38:40 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Jes.Sorensen@redhat.com>) id 1PrVyI-0000eg-EN
	for qemu-devel@nongnu.org; Mon, 21 Feb 2011 08:38:39 -0500
Received: from mx1.redhat.com ([209.132.183.28]:26325)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Jes.Sorensen@redhat.com>) id 1PrVyH-0000eX-Q4
	for qemu-devel@nongnu.org; Mon, 21 Feb 2011 08:38:38 -0500
Message-ID: <4D626ACD.5040005@redhat.com>
Date: Mon, 21 Feb 2011 14:38:21 +0100
From: Jes Sorensen <Jes.Sorensen@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [RFC][PATCH v6 00/23] virtagent: host/guest RPC
	communication agent
References: <1295270117-24760-1-git-send-email-mdroth@linux.vnet.ibm.com>
	<4D5BF581.3050803@redhat.com> <4D5C07CB.4040709@linux.vnet.ibm.com>
	<4D5CDBD0.2060900@redhat.com> <4D5D3331.1000707@linux.vnet.ibm.com>
	<4D5E69EB.5040805@redhat.com> <4D5E7D35.7090207@linux.vnet.ibm.com>
	<4D5E8291.7020900@redhat.com> <4D5E88BD.3050006@linux.vnet.ibm.com>
	<4D62231F.9020901@redhat.com> <4D626A49.2020108@linux.vnet.ibm.com>
In-Reply-To: <4D626A49.2020108@linux.vnet.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: agl@linux.vnet.ibm.com, stefanha@linux.vnet.ibm.com, markus_mueller@de.ibm.com, marcel.mittelstaedt@de.ibm.com, qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>, Anthony Liguori <aliguori@linux.vnet.ibm.com>, ryanh@us.ibm.com, abeekhof@redhat.com

On 02/21/11 14:36, Michael Roth wrote:
> On 02/21/2011 02:32 AM, Jes Sorensen wrote:
>> Well that isn't really different from the current setup - if QEMU
>> migrates, the admin tool has to connect to the new QEMU process and
>> issue the fsthaw command there instead.
>>
> 
> Another thing to consider is that virtagent is bi-directional, and may
> be tracking the state of state-full RPCs on behalf of the guest client,
> just as the guest daemon may be tracking the state of stateful RPCs on
> behalf of the host client. We cannot maintain consistent state without
> migrating the host-side state information along with the guest.

What kinda of usages do you expect to need to preserve state like this?
It seems a bad solution to me for the guest to be able to rely on state
in the host like this.

Cheers,
Jes