From: Anthony Liguori <anthony@codemonkey.ws>
To: quintela@redhat.com
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] migration: remove subsections in fdc and rtl8139 and bump versions
Date: Wed, 03 Aug 2011 12:49:56 -0500 [thread overview]
Message-ID: <4E398A44.8060507@codemonkey.ws> (raw)
In-Reply-To: <m3sjpidg4h.fsf@neno.neno>
On 08/03/2011 04:00 AM, Juan Quintela wrote:
> Anthony Liguori<aliguori@us.ibm.com> wrote:
>> So my thinking is to be a bit more conservative. If we bump the
>> version number for 0.15.0, we make sure that we don't allow new -> old
>> migration. We will break old -> new migration, but we can fix that
>> (including in the stable series) by adding special handling of the
>> previous version.
>>
>> Fixing new->old is the critical bit here. We can resolve old->new as
>> a stable update.
>
> We are making something that is incompatible.
Indeed.
> If we don't care about
> breaking 0.14 -> 0.15 migration. Just add Paolo version, and drop
> altogether the old protocol. It will give us exactly the same result,
> new versions work, old versions fail.
I don't have a problem with Paolo's new protocol. In fact, I'm strong
in favor of applying it to master. But I don't like the idea of adding
a new migration protocol with no testing in master before putting it in
a release.
>>
>> This series was just too late for 0.15. I can close to suggesting
>> that we delay 0.15 in order to give this time to be tested thoroughly
>> but I think my proposal is a reasonable compromise.
>
> I think it is anything except reasonable. From my point on view (and I
> am biased), it is the equivalent of finding a corner case broken on
> qcow2 and make all _OLD_ qcow2 images unreadable. It will work, but it
> is anything except reasonable. As said, everything uses an fdc.
> Furthermore, the _two_ things that you change don't matter in the big
> scheme of things. The subsections that fail are the ones that can
> appear in the middle of another section. The ones that appear at the
> end of a real section work perfectly well with this protocol (a.k.a. the
> ones that are broken are IDE), floppy and rtl8139 are ok with current
> protocol.
I can certainly limit the change to IDE if we think machine, floppy, and
rtl8139 are safe.
My main concern is fixing the corruption during migration for the
release. Once that is fixed, we can revisit compatibility for the
stable branch (by introducing a compatibility path for the older version).
Regards,
Anthony Liguori
>
> Later, Juan.
>
next prev parent reply other threads:[~2011-08-03 17:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 23:08 [Qemu-devel] [PATCH] migration: remove subsections in fdc and rtl8139 and bump versions Anthony Liguori
2011-08-02 23:17 ` Anthony Liguori
2011-08-02 23:25 ` Juan Quintela
2011-08-03 0:12 ` Anthony Liguori
2011-08-03 6:44 ` Paolo Bonzini
2011-08-03 17:44 ` Anthony Liguori
2011-08-04 7:17 ` Paolo Bonzini
2011-08-03 9:00 ` Juan Quintela
2011-08-03 17:49 ` Anthony Liguori [this message]
2011-08-03 21:42 ` Juan Quintela
2011-08-04 7:22 ` Paolo Bonzini
2011-08-04 13:20 ` Anthony Liguori
2011-08-04 14:09 ` Kevin Wolf
2011-08-04 14:30 ` Anthony Liguori
2011-08-04 15:07 ` Paolo Bonzini
2011-08-04 20:31 ` Anthony Liguori
2011-08-04 12:59 ` Kevin Wolf
2011-08-04 13:12 ` Anthony Liguori
2011-08-04 14:36 ` Paolo Bonzini
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=4E398A44.8060507@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aliguori@us.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).