From: Paolo Bonzini <pbonzini@redhat.com>
To: Hector Cao <hector.cao@canonical.com>, qemu-devel@nongnu.org
Subject: Re: [RFC PATCH 0/2] Fix cross migration issue with missing features: pdcm, arch-capabilities
Date: Tue, 23 Sep 2025 09:53:20 +0200 [thread overview]
Message-ID: <b2fb1e8c-4b30-4bde-9b16-b9a0cd314b70@redhat.com> (raw)
In-Reply-To: <20250910115733.21149-1-hector.cao@canonical.com>
On 9/10/25 13:57, Hector Cao wrote:
> Hello,
>
> Since it is a blocking issue for us, we went further and ended up with a solution along [1]
> that allows us to get out of this situation.
>
> The idea is to add compatibility properties to restore legacy behaviors for machine types
> with older versions of QEMU (<10.1). 2 compatiblity properties have been added to address
> respectively the 2 missing features, each one is done in a separate patch.
>
> We know that 10.1 has been released and it's final, but working on a solution towards 11.0
> would allow everyone to settle on the fix and even consider backporting where not yet released
> like Ubuntu 25.10 for us.
Thanks, I have applied the patch. It's better to have the fix in 10.1.1.
Sorry for the delay, I was on vacation for one week and working reduced
hours the next.
Paolo
> It is important to have upstream support going forward in this or any other way
> and therefore reach out with this RFC to ask you to think about it with us.
>
> [1] https://gitlab.com/qemu-project/qemu/-/blob/master/docs/devel/migration/compatibility.rst
>
> Hector Cao (2):
> target/i386: add compatibility property for arch_capabilities
> target/i386: add compatibility property for pdcm feature
>
> hw/core/machine.c | 2 ++
> migration/migration.h | 23 +++++++++++++++++++++++
> migration/options.c | 6 ++++++
> target/i386/cpu.c | 17 ++++++++++++++---
> target/i386/kvm/kvm.c | 5 ++++-
> 5 files changed, 49 insertions(+), 4 deletions(-)
>
next prev parent reply other threads:[~2025-09-23 7:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 11:52 Issues with pdcm in qemu 10.1-rc on migration and save/restore Christian Ehrhardt
2025-08-06 12:00 ` Daniel P. Berrangé
2025-08-06 17:57 ` Christian Ehrhardt
2025-08-06 19:18 ` Daniel P. Berrangé
2025-08-07 3:38 ` Xiaoyao Li
2025-08-07 6:37 ` Christian Ehrhardt
2025-08-07 8:09 ` Xiaoyao Li
2025-08-10 13:07 ` Christian Ehrhardt
2025-08-19 14:51 ` Paolo Bonzini
2025-08-20 5:11 ` Christian Ehrhardt
2025-08-20 9:10 ` Christian Ehrhardt
2025-09-03 8:38 ` Christian Ehrhardt
2025-09-03 11:26 ` Hector Cao
2025-09-04 14:35 ` Hector Cao
2025-09-10 11:57 ` [RFC PATCH 0/2] Fix cross migration issue with missing features: pdcm, arch-capabilities Hector Cao
2025-09-10 11:57 ` [PATCH 1/2] target/i386: add compatibility property for arch_capabilities Hector Cao
2025-09-16 8:12 ` Daniel P. Berrangé
2025-09-16 8:28 ` Hector Cao
2025-09-23 7:25 ` Christian Ehrhardt
2025-09-10 11:57 ` [PATCH 2/2] target/i386: add compatibility property for pdcm feature Hector Cao
2025-09-23 7:53 ` Paolo Bonzini [this message]
2025-09-23 10:08 ` [RFC PATCH 0/2] Fix cross migration issue with missing features: pdcm, arch-capabilities Hector Cao
2025-09-23 10:15 ` Paolo Bonzini
2025-09-23 10:31 ` Hector Cao
-- strict thread matches above, loose matches on Subject: below --
2025-09-12 13:35 Hector Cao
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=b2fb1e8c-4b30-4bde-9b16-b9a0cd314b70@redhat.com \
--to=pbonzini@redhat.com \
--cc=hector.cao@canonical.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).