1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
debug: 0.647
KVM: 0.551
device: 0.547
semantic: 0.531
PID: 0.481
graphic: 0.473
performance: 0.461
other: 0.442
socket: 0.373
boot: 0.338
vnc: 0.337
files: 0.327
network: 0.304
permissions: 0.250
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.]
|