From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NCU85-0007nr-JL
	for qemu-devel@nongnu.org; Mon, 23 Nov 2009 03:18:37 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NCU80-0007nG-1U
	for qemu-devel@nongnu.org; Mon, 23 Nov 2009 03:18:36 -0500
Received: from [199.232.76.173] (port=32861 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NCU7z-0007nD-RG
	for qemu-devel@nongnu.org; Mon, 23 Nov 2009 03:18:31 -0500
Received: from mx20.gnu.org ([199.232.41.8]:49451)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <gceq-qemu-devel@m.gmane.org>)
	id 1NCU7z-00066B-89
	for qemu-devel@nongnu.org; Mon, 23 Nov 2009 03:18:31 -0500
Received: from lo.gmane.org ([80.91.229.12])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <gceq-qemu-devel@m.gmane.org>) id 1NCU7y-00060J-8x
	for qemu-devel@nongnu.org; Mon, 23 Nov 2009 03:18:30 -0500
Received: from list by lo.gmane.org with local (Exim 4.50) id 1NCU7t-0006zE-Pq
	for qemu-devel@nongnu.org; Mon, 23 Nov 2009 09:18:25 +0100
Received: from 85.93.118.17 ([85.93.118.17])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <qemu-devel@nongnu.org>; Mon, 23 Nov 2009 09:18:25 +0100
Received: from pbonzini by 85.93.118.17 with local (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <qemu-devel@nongnu.org>; Mon, 23 Nov 2009 09:18:25 +0100
From: Paolo Bonzini <pbonzini@redhat.com>
Date: Mon, 23 Nov 2009 09:18:01 +0100
Message-ID: <hedgfp$i5p$1@ger.gmane.org>
References: <4B0952C9.9010803@redhat.com>
	<4B095D86.700@codemonkey.ws>	<hec6i6$j3r$1@ger.gmane.org>
	<4B09F0CA.3060705@codemonkey.ws>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
In-Reply-To: <4B09F0CA.3060705@codemonkey.ws>
Sender: news <news@ger.gmane.org>
Subject: [Qemu-devel] Re: Live migration protocol, device features,
 ABIs   and   other beasts
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.gnu.org/pipermail/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: qemu-devel@nongnu.org

On 11/23/2009 03:17 AM, Anthony Liguori wrote:
> You mean, each device would have multiple sections?  We already use
> chunks for each device state.

If they want to, yes.

> We only migrate things that are guest visible.  Everything else is left
> to the user to configure.  We wouldn't migrate the state of a RNG
> emulation provided that it doesn't have an impact on the guest.

The project doing lockstep virtualization would need to migrate it, for 
example.

> By definition, anything that is guest visible is important because it
> affects the guest's behavior.

Yes, but vendors want backwards-compatibility whenever possible. 
Anything that is guest visible is important, but some things are less 
important than others (or they wouldn't have been overlooked in the 
first place).

Paolo