From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MlJ51-0004li-Fb
	for qemu-devel@nongnu.org; Wed, 09 Sep 2009 05:03:07 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MlJ4v-0004gy-W2
	for qemu-devel@nongnu.org; Wed, 09 Sep 2009 05:03:06 -0400
Received: from [199.232.76.173] (port=54643 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MlJ4u-0004gV-Sp
	for qemu-devel@nongnu.org; Wed, 09 Sep 2009 05:03:00 -0400
Received: from mx1.redhat.com ([209.132.183.28]:27619)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <mst@redhat.com>) id 1MlJ4t-00040L-DJ
	for qemu-devel@nongnu.org; Wed, 09 Sep 2009 05:02:59 -0400
Received: from int-mx01.intmail.prod.int.phx2.redhat.com
	(int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11])
	by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n8992wQC013488
	for <qemu-devel@nongnu.org>; Wed, 9 Sep 2009 05:02:58 -0400
Date: Wed, 9 Sep 2009 12:01:21 +0300
From: "Michael S. Tsirkin" <mst@redhat.com>
Message-ID: <20090909090121.GB18061@redhat.com>
References: <m3hbvcijxc.fsf@neno.mitica>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m3hbvcijxc.fsf@neno.mitica>
Subject: [Qemu-devel] Re: The State of the SaveVM format
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: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org

On Wed, Sep 09, 2009 at 10:47:27AM +0200, Juan Quintela wrote:
> Notice that there are plans for VMState to do more interesting things
> like:
> - Be able to show the values in a saved image
> - See if a VM is able to load a vmstate (i.e. it has the needed devices
>   at the needed versions)
> - .....
> 
> That ones are independent of what we decided for the previous problems.
> 
> Comments?  Things that I missed for the discussion?
> 
> Later, Juan.

Another idea was to switch to some standard format, like qdev machine
description format or xml, so we don't have to maintain our own.

All state besides the physical memory dump is normally very
small, so this won't have much overhead.

This is possible if we give up on backwards compatibility completely.

-- 
MST