blob: 9c1e5bdf728cbc95aab0b2b3ecd06188de030370 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
<think>
Alright, let's figure out which category this bug report falls into. The user is talking about issues with XSAVES instructions in QEMU when using Hyper-V on KVM. They mentioned that during initialization, Hyper-V checks for XSAVES support via CPUID and MSR flags.
The problem arises because QEMU isn't correctly handling these features. Specifically, the XSAVES feature isn't added to the FEAT_VMX_SECONDARY_CTLS in target/i386/cpu.c, which causes KVM to mask off the feature. This leads Hyper-V to fail its initialization.
Looking at the provided categories: device, graphic, socket, network, KVM, etc., I need to determine where this issue fits. The bug is related to how QEMU handles CPU features and MSR settings for KVM virtualization. It's about incorrect mapping from the host's CPU features (like XSAVES) into the target VM configuration in QEMU/KVM.
Since the problem involves handling of specific CPU instructions and their support in the hypervisor (KVM), this relates more to how the hypervisor interacts with the hardware features through QEMU. Therefore, it falls under the 'hypervisor' category because the issue is about the interaction between KVM and QEMU regarding CPU feature flags.
</think>
hypervisor
|