summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/kvm/1366836
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/kvm/1366836
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloadqemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/kvm/1366836')
-rw-r--r--results/classifier/gemma3:12b/kvm/136683617
1 files changed, 17 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/kvm/1366836 b/results/classifier/gemma3:12b/kvm/1366836
new file mode 100644
index 000000000..25c000f88
--- /dev/null
+++ b/results/classifier/gemma3:12b/kvm/1366836
@@ -0,0 +1,17 @@
+
+Core2Duo and KVM may not boot Win8 properly on 3.x kernels
+
+When I start up QEMU w/ KVM 1.7.0 on a Core2Duo machine running a vanilla kernel
+3.4.67 or 3.10.12 to run a Windows 8.0 guest, the guest freezes at Windows 8 boot without any error.
+When I dump the CPU registers via "info registers", nothing changes, that means
+the system really stalled. Same happens with QEMU 2.0.0 and QEMU 2.1.0.
+
+But - when I run the very same guest using Kernel 2.6.32.12 and QEMU 1.7.0 or 2.0.0 on
+the host side it works on the Core2Duo. Also the system above but just with an
+i3 or i5 CPU it works fine.
+
+I already disabled networking and USB for the guest and changed the graphics
+card - no effect. I assume that some mean bits and bytes have to be set up
+properly to get the thing running.
+
+Seems to be related to a kvm/progressor incompatibility.
\ No newline at end of file