summary refs log tree commit diff stats
path: root/results/scraper/launchpad-without-comments/722311
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:24:58 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:27:06 +0000
commit33606b41d35115f887ea688b1a16f2ff85bf2fe4 (patch)
tree406b2c7b19a087ba437c68f3dbf0b589fa1d6150 /results/scraper/launchpad-without-comments/722311
parentadedf8771bc4de3113041ca21bd4d0d1c0014b6a (diff)
downloadqemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.tar.gz
qemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.zip
add launchpad bug reports without comments
Diffstat (limited to 'results/scraper/launchpad-without-comments/722311')
-rw-r--r--results/scraper/launchpad-without-comments/7223117
1 files changed, 7 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/722311 b/results/scraper/launchpad-without-comments/722311
new file mode 100644
index 000000000..fa3d4ccaf
--- /dev/null
+++ b/results/scraper/launchpad-without-comments/722311
@@ -0,0 +1,7 @@
+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