diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2025-09-23 12:22:54 +0200 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2025-10-07 17:03:32 +0200 |
| commit | e9efa4a77168ac2816bf9471f878252ce6224710 (patch) | |
| tree | 45c510970c29b23bf501286f049a5caf3cacd780 /scripts/lib/kdoc/kdoc_parser.py | |
| parent | 2438f18ee01108ead65be81be056e5a5da69120c (diff) | |
| download | qemu-e9efa4a77168ac2816bf9471f878252ce6224710.zip qemu-e9efa4a77168ac2816bf9471f878252ce6224710.tar.gz qemu-e9efa4a77168ac2816bf9471f878252ce6224710.tar.bz2 | |
target/i386: add compatibility property for arch_capabilities
Prior to v10.1, if requested by user, arch-capabilities is always on
despite the fact that CPUID advertises it to be off/unvailable.
This causes a migration issue for VMs that are run on a machine
without arch-capabilities and expect this feature to be present
on the destination host with QEMU 10.1.
Add a compatibility property to restore the legacy behavior for all
machines with version prior to 10.1.
To preserve the functionality (added by 10.1) of turning off
ARCH_CAPABILITIES where Windows does not like it, use directly
the guest CPU vendor: x86_cpu_get_supported_feature_word is not
KVM-specific and therefore should not necessarily use the host
CPUID.
Co-authored-by: Hector Cao <hector.cao@canonical.com>
Signed-off-by: Hector Cao <hector.cao@canonical.com>
Fixes: d3a24134e37 ("target/i386: do not expose ARCH_CAPABILITIES on AMD CPU", 2025-07-17)
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_parser.py')
0 files changed, 0 insertions, 0 deletions