From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=39002 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PscyJ-0003xB-Cx
	for qemu-devel@nongnu.org; Thu, 24 Feb 2011 10:19:16 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mtosatti@redhat.com>) id 1PscyH-0004xF-GL
	for qemu-devel@nongnu.org; Thu, 24 Feb 2011 10:19:15 -0500
Received: from mx1.redhat.com ([209.132.183.28]:29446)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mtosatti@redhat.com>) id 1PscyH-0004x2-6S
	for qemu-devel@nongnu.org; Thu, 24 Feb 2011 10:19:13 -0500
Date: Thu, 24 Feb 2011 11:39:34 -0300
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [Qemu-devel] Re: [patch 2/3] Add support for live block copy
Message-ID: <20110224143934.GA2613@amt.cnet>
References: <4D65051A.6070707@redhat.com> <4D651B20.70405@codemonkey.ws>
	<4D652852.60505@redhat.com> <4D652F73.3000305@codemonkey.ws>
	<4D65324A.5080408@redhat.com> <4D65359E.3040008@codemonkey.ws>
	<4D65416D.8040803@redhat.com> <4D656B97.5030301@codemonkey.ws>
	<20110223204440.GA7492@amt.cnet> <4D657F0A.20605@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D657F0A.20605@codemonkey.ws>
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: Anthony Liguori <anthony@codemonkey.ws>
Cc: Jes.Sorensen@redhat.com, Avi Kivity <avi@redhat.com>, qemu-devel@nongnu.org

On Wed, Feb 23, 2011 at 03:41:30PM -0600, Anthony Liguori wrote:
> On 02/23/2011 02:44 PM, Marcelo Tosatti wrote:
> >
> >>Any indirect qemu state.  Block migration is an example, but other
> >>examples would be VNC server information (like current password),
> >>WCE setting (depending on whether we modelled eeprom for the
> >>drivers), and persisted device settings (lots of devices have eeprom
> >>these days).
> >Agreed.
> >
> >Why a separate location for this "stateful non-config" section, however?
> >
> >The state in question (backing image property, device presence, VNC
> >info, etc) is already represented in either host or guest configuration,
> >so why not simply expose that?
> 
> Hrm, are you suggesting that the "stateful non-config" be hidden
> directly from the user such that only existing monitor interfaces
> are used to query it's contents?

Yes. So that the guest can be restarted with the same VM parameters.

> I'll have to think about that a bit.  Obviously, the existing
> commands would still be authoritative even with a query-state
> command.  I think the only question is whether there's value in
> making this totally opaque.

Why you need a query-state command at all?

> 
> Regards,
> 
> Anthony Liguori
>