summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/hypervisor/521202
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/gemma3:12b/hypervisor/521202
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloadqemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/hypervisor/521202')
-rw-r--r--results/classifier/gemma3:12b/hypervisor/5212028
1 files changed, 8 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/hypervisor/521202 b/results/classifier/gemma3:12b/hypervisor/521202
new file mode 100644
index 000000000..9b1e926f8
--- /dev/null
+++ b/results/classifier/gemma3:12b/hypervisor/521202
@@ -0,0 +1,8 @@
+
+Windows XP x64 / 2008 Server x64 broken on 32-bit hosts with QEMU > 0.9.0
+
+QEMU >0.9.0 fails to install/run 64-bit Windows XP guests on 32-bit hosts. This is mentioned here: http://qemu-forum.ipi.fi/viewtopic.php?f=5&t=4625 . As explained there, 0.9.0 manages to install and run XP64 fine, if somewhat slowly. The host is an actual 32-bit CPU (Athlon XP), although I've tested it and confirmed the bug to occur on a Core2 Duo CPU running in 32-bit mode with KVM disabled. It's impossible to test with KVM enabled, as this causes Windows to detect a 32-bit CPU and refuse to run.
+
+When installing, the installer hangs at the "Setup is starting Windows" step. An attempt at running a converted VBox image reveals the problem lies somewhere in the ACPI -- in safe mode, the boot sequence gets to loading ACPI tables, then hangs indefinitely. Interestingly enough, the emulator itself runs fine, you can interact with the monitor etc., but the virtual CPU appears to stop; there's a marked point in "log cpu" output after which nothing comes. Disabling ACPI predictably does nothing to help, as in this case Windows refuses to run.
+
+I've tested with several versions, and 0.9.1 is the first one to break. The bug is still present in 0.11 and 0.12 as packaged by Ubuntu.
\ No newline at end of file