1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Alright, let me try to figure out how to classify this bug report. The user provided a report about QEMU where neither keyboard nor mouse input works on Windows 10 Preview Build 18351. They mentioned that VNC, SPICE, and SDL were tested but no cursor was available. Interestingly, when all 'hv_*' flags are removed, the input works again.
First, I need to consider the categories given: mistranslation, assembly, other, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor.
The issue is related to input devices (keyboard and mouse) not working. The user also mentioned that removing certain flags makes it work again. Since the problem occurs in QEMU, which is a hypervisor, I should look into categories related to hardware virtualization or device management.
Hypervisor seems like a likely category because the issue might be related to how the hypervisor handles input devices. Alternatively, 'peripherals' could also fit since keyboards and mice are peripherals.
However, the fact that specific flags ('hv_*') affect the behavior points towards something in the hypervisor layer. These flags might control how the hypervisor interacts with hardware or emulates devices for the virtual machine.
So, considering all this, I think 'hypervisor' is the best category here because the issue likely stems from how the hypervisor manages input devices when certain flags are present.
</think>
hypervisor
|