From: Peter Xu <peterx@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [PATCH 1/2] migration/multifd: Fix compat with QEMU < 9.0
Date: Mon, 16 Dec 2024 11:02:03 -0500 [thread overview]
Message-ID: <Z2BO-3vdEyNrMhhR@x1n> (raw)
In-Reply-To: <20241213160120.23880-2-farosas@suse.de>
On Fri, Dec 13, 2024 at 01:01:19PM -0300, Fabiano Rosas wrote:
> Commit f5f48a7891 ("migration/multifd: Separate SYNC request with
> normal jobs") changed the multifd source side to stop sending data
> along with the MULTIFD_FLAG_SYNC, effectively introducing the concept
> of a SYNC-only packet. Relying on that, commit d7e58f412c
> ("migration/multifd: Don't send ram data during SYNC") later came
> along and skipped reading data from SYNC packets.
>
> In a versions timeline like this:
>
> 8.2 f5f48a7 9.0 9.1 d7e58f41 9.2
>
> The issue arises that QEMUs < 9.0 still send data along with SYNC, but
> QEMUs > 9.1 don't gather that data anymore. This leads to various
> kinds of migration failures due to desync/missing data.
>
> Stop checking for a SYNC packet on the destination and unconditionally
> unfill the packet.
>
> From now on:
>
> old -> new:
> the source sends data + sync, destination reads normally
>
> new -> new:
> source sends only sync, destination reads zeros
>
> new -> old:
> source sends only sync, destination reads zeros
>
> CC: qemu-stable@nongnu.org
> Fixes: d7e58f412c ("migration/multifd: Don't send ram data during SYNC")
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2720
> Signed-off-by: Fabiano Rosas <farosas@suse.de>
Reviewed-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
next prev parent reply other threads:[~2024-12-16 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 16:01 [PATCH 0/2] migration: Fix regressions Fabiano Rosas
2024-12-13 16:01 ` [PATCH 1/2] migration/multifd: Fix compat with QEMU < 9.0 Fabiano Rosas
2024-12-16 16:02 ` Peter Xu [this message]
2024-12-13 16:01 ` [PATCH 2/2] s390x: Fix CSS migration Fabiano Rosas
2024-12-16 7:17 ` Thomas Huth
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=Z2BO-3vdEyNrMhhR@x1n \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.