1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Alright, I need to classify the bug report about exposing MDS_NO in the guest under QEMU. Let me start by understanding what the bug is about.
The description says that MDS_NO is bit 5 of ARCH_CAPABILITIES and it needs to be exposed to the guest. So, this seems related to how certain CPU capabilities are presented to the virtual machine.
Looking at the possible categories: mistranslation, assembly lowering, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor, and other.
MDS stands for Microarchitectural Data Sampling, which is a CPU vulnerability. Exposing this bit likely involves how QEMU handles CPU features and capabilities when running a guest OS. Since it's about exposing a specific capability bit to the guest, this probably relates to how QEMU presents CPU information to the virtualized environment.
In QEMU/KVM, there are mechanisms like kvm_setarch that expose CPU capabilities. If MDS_NO is part of ARCH_CAPABILITIES, it might be about correctly setting or passing this capability so the guest can handle it, possibly for mitigating vulnerabilities.
Looking at the categories, "hypervisor" seems fitting because it's about how QEMU (as a hypervisor) exposes hardware features to the guest. Alternatively, it could relate to device handling, but I think hypervisor is more precise here since it's about CPU capabilities exposed through KVM.
</think>
hypervisor
|