From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MliTK-0002VX-6B
	for qemu-devel@nongnu.org; Thu, 10 Sep 2009 08:09:54 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MliTF-0002Js-Mq
	for qemu-devel@nongnu.org; Thu, 10 Sep 2009 08:09:53 -0400
Received: from [199.232.76.173] (port=43880 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MliTF-0002JX-GR
	for qemu-devel@nongnu.org; Thu, 10 Sep 2009 08:09:49 -0400
Received: from mx1.redhat.com ([209.132.183.28]:17790)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <mst@redhat.com>) id 1MliTE-000250-KF
	for qemu-devel@nongnu.org; Thu, 10 Sep 2009 08:09:48 -0400
Date: Thu, 10 Sep 2009 15:08:03 +0300
From: "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] The State of the SaveVM format
Message-ID: <20090910120802.GA24530@redhat.com>
References: <m3hbvcijxc.fsf@neno.mitica> <4AA7BEA7.6080906@codemonkey.ws>
	<87my53lhd1.fsf@pike.pond.sub.org> <4AA85E1F.6000902@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4AA85E1F.6000902@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.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: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>, Juan Quintela <quintela@redhat.com>

On Wed, Sep 09, 2009 at 09:02:07PM -0500, Anthony Liguori wrote:
>>   If we complicate vmstate now to shoehorn pre-vmstate
>> formats into vmstate, that ancient history will continue to haunt us.
>> Complicating a program is far easier than the other direction.
>>   
>
> Let's take it one step at a time.  There is an awful lot of areas where  
> we can support older versions without adding complications.  Let's  
> approach the complicated ones one at a time.

I'm not sure I understand this talk about "pre-vmstate formats".
I thought vmstate patches were, at least for the most part, trying
to reimplement existing format with the table-driver design?

If that's not so and we are changing the format now, is it too late to
consider some standard serialization format rather than rolling our own?

-- 
MST