summary refs log tree commit diff stats
path: root/results/classifier/deepseek-2/reasoning/hypervisor/1385934
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
commitd0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
treef8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/deepseek-2/reasoning/hypervisor/1385934
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloademulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/deepseek-2/reasoning/hypervisor/1385934')
-rw-r--r--results/classifier/deepseek-2/reasoning/hypervisor/138593411
1 files changed, 11 insertions, 0 deletions
diff --git a/results/classifier/deepseek-2/reasoning/hypervisor/1385934 b/results/classifier/deepseek-2/reasoning/hypervisor/1385934
new file mode 100644
index 00000000..ccf6135e
--- /dev/null
+++ b/results/classifier/deepseek-2/reasoning/hypervisor/1385934
@@ -0,0 +1,11 @@
+<think>
+Alright, let me try to figure out the category for this bug report. The user is having trouble with USB passthrough in QEMU. They followed a guide but the device isn't showing up on the guest. 
+
+Looking at the logs, the guest sees a hub but no other devices. There are repeated errors about invalid ep0 maxpacket and unable to enumerate devices. On the host, the USB device is present. So it's not that the device isn't being passed through at all.
+
+The problem seems related to how QEMU handles USB devices in KVM. Since they're using the `-usb` and `-device usb-host` options correctly, the issue might be with how the device is being exposed or handled by the hypervisor or the guest's USB stack.
+
+Possible categories include 'hypervisor' since it's a KVM issue, but other options like 'device' or 'graphic' don't fit. The problem isn't about assembly or permissions directly. Considering that the issue affects device enumeration within the virtual machine, it likely falls under the hypervisor category.
+</think>
+
+hypervisor
\ No newline at end of file