1
2
3
4
5
6
7
8
9
10
11
|
<think>
Okay, so I'm trying to figure out which category this bug report falls into for QEMU. The user mentioned that when they attach a "-device usb-uas" to their Windows 10 VM, the device doesn't start and shows an error in the guest about not being able to start (Code 10). They also noticed that if the host controller is nec-usb-xhci, there are errors on the host side related to unhandled control requests. With other controllers like usb-ehci or ich9-usb-ehci1, the device still fails but without those specific host errors.
I need to classify this bug report into one of the given categories: mistranslation, assembly, other, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor.
Looking at the issue, it's related to USB devices not working correctly in a Windows guest. The error occurs when using usb-uas, and there are specific controller issues on the host side as well. Since this is about device handling within the VM, particularly with USB controllers (like UAS), which are hardware peripherals emulated by QEMU, it seems like a problem related to how devices are handled.
The error messages suggest that the control requests aren't being properly handled, which points towards an issue in the device emulation or handling rather than something like translation errors. Since the problem is about device functionality within the VM, "peripherals" seems appropriate because USB devices are peripherals.
</think>
device
|