qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: quintela@redhat.com
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] migration: remove subsections in fdc and rtl8139 and bump versions
Date: Tue, 02 Aug 2011 19:12:08 -0500	[thread overview]
Message-ID: <4E389258.6040007@us.ibm.com> (raw)
In-Reply-To: <m3ty9zjt09.fsf@neno.neno>

On 08/02/2011 06:25 PM, Juan Quintela wrote:
> Anthony Liguori<aliguori@us.ibm.com>  wrote:
>> As Paolo points out, the migration protocol is ambiguous when using subsections
>> today.  That means that even if we preserve subsections and change the protocol
>> accordingly, the old protocol w/subsections is still ambiguous.
>>
>> Remove subsection usage and bump any device using subsections.  This effectively
>> eliminates the amiguouity and allows for a clean transition to a new protocol
>> with unambiguous subsections.
>
> If you are doing that, you can just remove the old protocol altogether.

The fundamental problem is that newer QEMUs generate migration state 
that is ambiguous to older QEMUs.

No matter what, we have to change the migration protocol in some way as 
to make it impossible to migrate from newer QEMUs to older QEMUs.

Even with subsections in the older protocol, newer QEMUs (provided we 
don't add more subsections), can still read the old protocol.

Paolo's proposed changes make newer QEMUs use a new protocol.  It's 
still possible to read the older protocol.  This means that you can't 
migrate new to old, but can migrate old to new.

I've poured over these patches in great detail and the changes are just 
too much right now.  Just the ram_addr_t change which now conflicts has 
a non-trivial resolution due to a related Xen change.

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.

> You are missing also ide on your patch.

Thanks for catching that.

>  Only platform that
> ever cares about forward compatiblity is pc's.  And pc's always use
> floppies on qemu.
>
> I still think that improving the "subsection" match is the way to go for 0.15.

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.

Regards,

Anthony Liguori

>
> Later, Juan.
>
>

  reply	other threads:[~2011-08-03  0:12 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 [this message]
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
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=4E389258.6040007@us.ibm.com \
    --to=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).