summaryrefslogtreecommitdiffstats
path: root/results/classifier/accel-gemma3:12b/vmm/1731
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-03 16:27:09 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-03 16:27:09 +0000
commit4d9e26c0333abd39bdbd039dcdb30ed429c475ba (patch)
tree4010d5fb3e8bc48c110a2c1ff2a16b8648cb86bb /results/classifier/accel-gemma3:12b/vmm/1731
parent5541099586dbd6018574cb44e1934907c121526f (diff)
downloademulator-bug-study-4d9e26c0333abd39bdbd039dcdb30ed429c475ba.tar.gz
emulator-bug-study-4d9e26c0333abd39bdbd039dcdb30ed429c475ba.zip
add gemma accelerator classification results
Diffstat (limited to 'results/classifier/accel-gemma3:12b/vmm/1731')
-rw-r--r--results/classifier/accel-gemma3:12b/vmm/173113
1 files changed, 13 insertions, 0 deletions
diff --git a/results/classifier/accel-gemma3:12b/vmm/1731 b/results/classifier/accel-gemma3:12b/vmm/1731
new file mode 100644
index 00000000..c0453f3d
--- /dev/null
+++ b/results/classifier/accel-gemma3:12b/vmm/1731
@@ -0,0 +1,13 @@
+
+i440fx ide cdrom pathological slow on early win10 install screen
+Description of problem:
+if you choose i440fx virtual hardware (default in proxmox) for windows 10 instead of q35 , from power on to the windows boot logo is 10 times slower. you need to wait more then 1m45s on my hardware until the blinking cursor in the upper left goes away and the blue windows bootlogo appears. that leads to false assumption, that your setup hangs.
+
+what's causing this slownewss?
+
+is implementation really that bad?
+
+i did compare read performance of ide, sata and scsi cdrom in linux vm and cannot observe such a big difference.
+
+see
+https://forum.proxmox.com/threads/win10-installation-pathological-slowness-with-i440fx-ide-cdrom.129351/