From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MWFCD-0006Oh-PB for qemu-devel@nongnu.org; Wed, 29 Jul 2009 15:52:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MWFC8-0006K8-By for qemu-devel@nongnu.org; Wed, 29 Jul 2009 15:52:17 -0400 Received: from [199.232.76.173] (port=45746 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MWFC8-0006Jp-14 for qemu-devel@nongnu.org; Wed, 29 Jul 2009 15:52:12 -0400 Received: from qw-out-1920.google.com ([74.125.92.144]:34012) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MWEvR-0007Yp-Pq for qemu-devel@nongnu.org; Wed, 29 Jul 2009 15:34:57 -0400 Received: by qw-out-1920.google.com with SMTP id 5so526515qwc.4 for ; Wed, 29 Jul 2009 12:34:51 -0700 (PDT) Message-ID: <4A70A459.30601@codemonkey.ws> Date: Wed, 29 Jul 2009 14:34:49 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH v2] make windows notice media change References: <20090729120719.GN30449@redhat.com> <20090729135057.GY30449@redhat.com> <5b31733c0907290735u5dd86d86i293f34df4ce09d10@mail.gmail.com> <200907292011.38879.paul@codesourcery.com> <5b31733c0907291218k624f97bbx62d8d6d49b8f0759@mail.gmail.com> <5b31733c0907291224h340921f0j72195618b0b6cd2a@mail.gmail.com> In-Reply-To: <5b31733c0907291224h340921f0j72195618b0b6cd2a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Filip Navara Cc: Paul Brook , Gleb Natapov , qemu-devel@nongnu.org Filip Navara wrote: > On Wed, Jul 29, 2009 at 9:18 PM, Filip Navara wrote: > >> On Wed, Jul 29, 2009 at 9:11 PM, Paul Brook wrote: >> >>>> Why shouldn't we support loading version 2 snapshots? Afterall that's >>>> why we had the versioning in the first place. >>>> >>> No it's not. Versioning was introduced to *prevent* loading old snapshots and >>> crashing or ending up with inconsistent guest state. I'm still unconvinced >>> that anything other than very short term backward compatibility is worthwhile >>> or even viable. >>> >> I see it as a way to migrate a running guest to newer QEMU version, possibly >> even with live migration. In fact I used it quite often back in the day when >> snapshots were not part of qcow2 yet and when kqemu was still in its heydays. >> >> > > BTW, why would there be the version parameter in the first place if it > wasn't supposed to load older versions?! > You can sometimes load older versions. When a new version fixes a bug in an older version, you cannot migrate. OTOH, if the new version adds a feature that was not exposed to the guest in the previous version, as long as you continue to not expose that feature to the guest, you can safely migrate. Regards, Anthony Liguori