diff options
author | Paolo Bonzini <pbonzini@redhat.com> | 2025-07-14 10:19:36 +0200 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2025-07-17 15:50:45 +0200 |
commit | d3a24134e37d57abd3e7445842cda2717f49e96d (patch) | |
tree | 395acbcad67be3d40e53c3a51e687779036c337e /scripts/qapi/parser.py | |
parent | f96b157ebb93f94cd56ebbc99bc20982b8fd86ef (diff) | |
download | qemu-d3a24134e37d57abd3e7445842cda2717f49e96d.zip qemu-d3a24134e37d57abd3e7445842cda2717f49e96d.tar.gz qemu-d3a24134e37d57abd3e7445842cda2717f49e96d.tar.bz2 |
target/i386: do not expose ARCH_CAPABILITIES on AMD CPU
KVM emulates the ARCH_CAPABILITIES on x86 for both Intel and AMD
cpus, although the IA32_ARCH_CAPABILITIES MSR is an Intel-specific
MSR and it makes no sense to emulate it on AMD.
As a consequence, VMs created on AMD with qemu -cpu host and using
KVM will advertise the ARCH_CAPABILITIES feature and provide the
IA32_ARCH_CAPABILITIES MSR. This can cause issues (like Windows BSOD)
as the guest OS might not expect this MSR to exist on such cpus (the
AMD documentation specifies that ARCH_CAPABILITIES feature and MSR
are not defined on the AMD architecture).
A fix was proposed in KVM code, however KVM maintainers don't want to
change this behavior that exists for 6+ years and suggest changes to be
done in QEMU instead. Therefore, hide the bit from "-cpu host":
migration of -cpu host guests is only possible between identical host
kernel and QEMU versions, therefore this is not a problematic breakage.
If a future AMD machine does include the MSR, that would re-expose the
Windows guest bug; but it would not be KVM/QEMU's problem at that
point, as we'd be following a genuine physical CPU impl.
Reported-by: Alexandre Chartre <alexandre.chartre@oracle.com>
Suggested-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Xiaoyao Li <xiaoyao.li@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/qapi/parser.py')
0 files changed, 0 insertions, 0 deletions