diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
| commit | d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch) | |
| tree | f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/deepseek-2-tmp/reasoning/device/1826422 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/deepseek-2-tmp/reasoning/device/1826422')
| -rw-r--r-- | results/classifier/deepseek-2-tmp/reasoning/device/1826422 | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/results/classifier/deepseek-2-tmp/reasoning/device/1826422 b/results/classifier/deepseek-2-tmp/reasoning/device/1826422 deleted file mode 100644 index 16a5ee5f..00000000 --- a/results/classifier/deepseek-2-tmp/reasoning/device/1826422 +++ /dev/null @@ -1,13 +0,0 @@ -<think> -Okay, I need to classify this bug report for QEMU into one of the given categories. Let me read through the problem carefully. - -The user reports that after a specific commit (b2fc91db...), QEMU 4.0 causes their host system to hang. They mention using GPU passthrough, which worked fine before but now leads to both guest and host hanging. Without GPU passthrough, QEMU runs fine. - -Looking at the command line arguments, they're using vfio-pci devices for what seems like their GPU and other hardware, along with USB hosts. The regression happens when these are included. - -Possible categories include 'device', 'graphic', 'socket', etc. Since the issue is related to GPU passthrough, which involves VFIO (Virtual Function I/O) andpci devices, this points towards a device-related problem._GPU passthrough falls under device management by QEMU, so the bug is likely in how devices are handled. - -Other categories like 'network' or 'hypervisor' don't seem as relevant here since the issue occurs with GPU setup, not network interfaces or hypervisor functions. -</think> - -device
\ No newline at end of file |