From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCHv3 03/13] qemu: add routines to manage PCI capabilities Date: Wed, 10 Jun 2009 20:27:02 +0100 Message-ID: <20090610192702.GH7416@shareable.org> References: <20090610145540.GI19375@poweredge.glommer> <20090610150129.GC28601@redhat.com> <200906101624.30659.paul@codesourcery.com> <20090610174301.GC7416@shareable.org> <20090610182227.GN28601@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Paul Brook , qemu-devel@nongnu.org, Carsten Otte , kvm@vger.kernel.org, Glauber Costa , Rusty Russell , virtualization@lists.linux-foundation.org, Blue Swirl , Christian Borntraeger , Avi Kivity To: "Michael S. Tsirkin" Return-path: Received: from mail2.shareable.org ([80.68.89.115]:51301 "EHLO mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755410AbZFJT1F (ORCPT ); Wed, 10 Jun 2009 15:27:05 -0400 Content-Disposition: inline In-Reply-To: <20090610182227.GN28601@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Michael S. Tsirkin wrote: > > I think the right long term answer to all this is a way to get QEMU to > > dump it's current machine configuration in glorious detail as a file > > which can be reloaded as a machine configuration. > > And then we'll have the same set of problems there. We will, and the solution will be the same: options to create devices as they were in older versions of QEMU. It only needs to cover device features which matter to guests, not every bug fix. However with a machine configuration which is generated by QEMU, there's less worry about proliferation of obscure options, compared with the command line. You don't necessarily have to document every backward-compatibility option in any detail, you just have to make sure it's written and read properly, which is much the same thing as the snapshot code does. -- Jamie