Hello,

Sorry, you can ignore this submission,
it is not supposed to be sent to the grub-devel mailing list.

Kind regards

On Wed, Sep 10, 2025 at 2:55 PM Hector Cao <[email protected]> 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.
>
> 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(-)
>
> --
> 2.45.2
>
>
> _______________________________________________
> Grub-devel mailing list
> [email protected]
> https://lists.gnu.org/mailman/listinfo/grub-devel
>


-- 
Hector CAO
Software Engineer – Server Team / Virtualization
[email protected]
https://launc <https://launchpad.net/~hectorcao>hpad.net/~hectorcao
<https://launchpad.net/~hectorcao>

<https://launchpad.net/~hectorcao>
_______________________________________________
Grub-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/grub-devel

Reply via email to