From: Anthony Liguori <anthony@codemonkey.ws>
To: Filip Navara <filip.navara@gmail.com>
Cc: Paul Brook <paul@codesourcery.com>,
Gleb Natapov <gleb@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] make windows notice media change
Date: Wed, 29 Jul 2009 14:34:49 -0500 [thread overview]
Message-ID: <4A70A459.30601@codemonkey.ws> (raw)
In-Reply-To: <5b31733c0907291224h340921f0j72195618b0b6cd2a@mail.gmail.com>
Filip Navara wrote:
> On Wed, Jul 29, 2009 at 9:18 PM, Filip Navara<filip.navara@gmail.com> wrote:
>
>> On Wed, Jul 29, 2009 at 9:11 PM, Paul Brook<paul@codesourcery.com> 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
next prev parent reply other threads:[~2009-07-29 19:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 12:07 [Qemu-devel] [PATCH] make windows notice media change Gleb Natapov
2009-07-29 13:50 ` [Qemu-devel] [PATCH v2] " Gleb Natapov
2009-07-29 14:22 ` Avi Kivity
2009-07-29 14:21 ` Gleb Natapov
2009-07-29 14:44 ` Avi Kivity
2009-07-29 14:35 ` Filip Navara
2009-07-29 14:40 ` Gleb Natapov
2009-07-29 14:59 ` Stefano Stabellini
2009-07-29 19:11 ` Paul Brook
2009-07-29 19:18 ` Filip Navara
2009-07-29 19:24 ` Filip Navara
2009-07-29 19:34 ` Anthony Liguori [this message]
2009-07-29 19:52 ` Paul Brook
2009-07-29 19:56 ` Filip Navara
2009-07-29 20:05 ` Paul Brook
2009-07-29 20:14 ` Gleb Natapov
2009-07-30 12:14 ` Stefano Stabellini
2009-07-30 12:27 ` Paul Brook
2009-07-29 19:33 ` Anthony Liguori
2009-07-29 19:44 ` [Qemu-devel] " Juan Quintela
2009-07-29 20:05 ` Anthony Liguori
2009-07-29 20:09 ` Juan Quintela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A70A459.30601@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=filip.navara@gmail.com \
--cc=gleb@redhat.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).