summary refs log tree commit diff stats
path: root/results/classifier/deepseek-2-tmp/output/hypervisor/722311
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:34:26 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:35:44 +0000
commit25f8033d556aa17afaea4a5196ea7a69fe248320 (patch)
tree0f056db167683be54ea1e5e72d29d6069af55e7d /results/classifier/deepseek-2-tmp/output/hypervisor/722311
parent8e6da29e4ee5fc14bc1cc816a24f21271f14090d (diff)
downloademulator-bug-study-25f8033d556aa17afaea4a5196ea7a69fe248320.tar.gz
emulator-bug-study-25f8033d556aa17afaea4a5196ea7a69fe248320.zip
add new temporary deepseek-r1:14b results
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/hypervisor/722311')
-rw-r--r--results/classifier/deepseek-2-tmp/output/hypervisor/7223118
1 files changed, 8 insertions, 0 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/hypervisor/722311 b/results/classifier/deepseek-2-tmp/output/hypervisor/722311
new file mode 100644
index 00000000..1b516eb8
--- /dev/null
+++ b/results/classifier/deepseek-2-tmp/output/hypervisor/722311
@@ -0,0 +1,8 @@
+
+Segmentation fault if started without -enable-kvm parameter
+
+I start qemu (Linux) from the same USB memory stick on several computers. Up to and including qemu 0.12.5, I could use or not use qemu's "-enable-kvm" command line parameter as appropriate for the hardware, and qemu would run. In contrast, qemu 0.13.0 and 0.14.0 segfault if started without "-enable-kvm". I get a black window appearing for fractions of a second, disappearing immediately, and then the error message "Segmentation fault".
+
+Hardware: Pentium 4, and Core 2 Duo.
+Command line: either "qemu" or "qemu -enable-kvm" (after manually loading the kvm-intel module on the Core 2 Duo).
+Reproducible: always.
\ No newline at end of file