summary refs log tree commit diff stats
path: root/results/classifier/118/none/810588
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/118/none/810588')
-rw-r--r--results/classifier/118/none/81058869
1 files changed, 69 insertions, 0 deletions
diff --git a/results/classifier/118/none/810588 b/results/classifier/118/none/810588
new file mode 100644
index 000000000..3193dadc4
--- /dev/null
+++ b/results/classifier/118/none/810588
@@ -0,0 +1,69 @@
+virtual: 0.760
+debug: 0.647
+KVM: 0.551
+device: 0.547
+semantic: 0.531
+architecture: 0.526
+mistranslation: 0.511
+PID: 0.481
+hypervisor: 0.477
+x86: 0.473
+graphic: 0.473
+performance: 0.461
+user-level: 0.452
+kernel: 0.404
+socket: 0.373
+ppc: 0.355
+boot: 0.338
+vnc: 0.337
+VMM: 0.333
+i386: 0.328
+files: 0.327
+register: 0.309
+network: 0.304
+peripherals: 0.301
+risc-v: 0.267
+permissions: 0.250
+assembly: 0.225
+TCG: 0.200
+arm: 0.170
+
+Unexpected crash of qemu-kvm with SCSI disk emulation.
+
+Virual machine with MS windows 2003 installed on the virtual scsi disk (-drive file=/my/path/myimage.qcow2.img,boot=on,if=scsi,media=disk,bus=0,unit=1) unexpectedly crashes without core dump. When the image is connected as an ide disk (-hda )  vm flies normally.
+Qemu-kvm version: 0.12.5
+Os/distr.: Debian squeeze, x86_64
+
+On Thu, Jul 14, 2011 at 5:43 PM, Constantine Chernov
+<email address hidden> wrote:
+> Virual machine with MS windows 2003 installed on the virtual scsi disk (-drive file=/my/path/myimage.qcow2.img,boot=on,if=scsi,media=disk,bus=0,unit=1) unexpectedly crashes without core dump. When the image is connected as an ide disk (-hda )  vm flies normally.
+> Qemu-kvm version: 0.12.5
+> Os/distr.: Debian squeeze, x86_64
+
+Please post your full QEMU command-line.
+
+Did you enable core dumps before launch QEMU?  Do "ulimit -c
+unlimited" in the same shell before running the QEMU command-line.
+
+If it is exiting instead of crashing I suggest launching QEMU from gdb
+and catching the exit:
+1. Install qemu-kvm-dbg to get the debuginfo for useful backtraces
+2. Start gdb with QEMU and its usual command-line arguments: gdb
+--args qemu-kvm ...
+3. Set breakpoints on exit(3) and abort(2):
+b exit
+b abort
+4. Run the VM and reproduce the exit:
+r
+5. When it exits you will hopefully be at an exit/abort breakpoint and
+can print the stack trace:
+bt
+
+Please post the backtrace so we have more information on how the exit happens.
+
+Thanks,
+Stefan
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+