From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=51139 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PsMVh-0007Ke-Jw for qemu-devel@nongnu.org; Wed, 23 Feb 2011 16:44:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PsMVb-0004Yc-5M for qemu-devel@nongnu.org; Wed, 23 Feb 2011 16:44:32 -0500 Received: from mail-vw0-f45.google.com ([209.85.212.45]:46357) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PsMVb-0004Xu-0H for qemu-devel@nongnu.org; Wed, 23 Feb 2011 16:44:31 -0500 Received: by vws19 with SMTP id 19so4238044vws.4 for ; Wed, 23 Feb 2011 13:44:30 -0800 (PST) Message-ID: <4D657F0A.20605@codemonkey.ws> Date: Wed, 23 Feb 2011 15:41:30 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [patch 2/3] Add support for live block copy References: <20110222230935.GA11082@amt.cnet> <4D644343.4050800@codemonkey.ws> <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> In-Reply-To: <20110223204440.GA7492@amt.cnet> 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: Marcelo Tosatti Cc: Jes.Sorensen@redhat.com, Avi Kivity , qemu-devel@nongnu.org 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? 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. Regards, Anthony Liguori