From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MlLsK-00005v-Qr for qemu-devel@nongnu.org; Wed, 09 Sep 2009 08:02:12 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MlLsH-00005N-Ru for qemu-devel@nongnu.org; Wed, 09 Sep 2009 08:02:11 -0400 Received: from [199.232.76.173] (port=55889 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MlLsG-00005B-L0 for qemu-devel@nongnu.org; Wed, 09 Sep 2009 08:02:09 -0400 Received: from mx1.redhat.com ([209.132.183.28]:28381) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MlLsF-0003uf-Sj for qemu-devel@nongnu.org; Wed, 09 Sep 2009 08:02:08 -0400 Received: from int-mx05.intmail.prod.int.phx2.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.18]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n89C273E019234 for ; Wed, 9 Sep 2009 08:02:07 -0400 Date: Wed, 9 Sep 2009 15:00:26 +0300 From: "Michael S. Tsirkin" Message-ID: <20090909120025.GA18473@redhat.com> References: <20090909090121.GB18061@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: [Qemu-devel] Re: The State of the SaveVM format List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Juan Quintela Cc: qemu-devel@nongnu.org On Wed, Sep 09, 2009 at 11:26:43AM +0200, Juan Quintela wrote: > "Michael S. Tsirkin" wrote: > > 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. > > Are you serious here? Qemu don't trust the avalavility > autoconf/automake/gnulib/glib/... and other useful libraries, and now we > are gonig to require an xml library or qdev machine format (a library > that don't do releases and is not packaged) for somethnig core of qemu? I mean the qdev that we have in qemu. We already know how to deserialize properties, and need to serialize them to dump machine description out. > > 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. > > If we give up on backwards compatiblity, we fix at least half of the > problems, independently of swiching to a new format :) > > Later, Juan.