[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [BUG] qemu crash when using "lsilogic"
From: |
Wanlong Gao |
Subject: |
Re: [Qemu-devel] [BUG] qemu crash when using "lsilogic" |
Date: |
Tue, 20 Nov 2012 17:01:52 +0800 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 |
On 11/19/2012 05:43 PM, Wanlong Gao wrote:
> Hi all and Avi,
>
> I met the upstream qemu crash when using "lsilogic", my first sight is that I
> can't access the VNC view, it gave me a black screen, here is my command line,
>
> /work/git/qemu/x86_64-softmmu/qemu-system-x86_64 -name f17 -m 3096 -M pc-0.15
> -enable-kvm -smp 4,sockets=4,cores=1,threads=1 -drive
> file=/vm/f17.img,if=none,id=drive-virtio-disk0,format=qcow2 -device
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
> -vnc 127.0.0.1:7 -device lsi,id=scsi0,bus=pci.0,addr=0x8 -drive
> file=/vm/scsi-disks/scsi1.img,if=none,id=drive-scsi0-0-0,format=raw -device
> scsi-hd,bus=scsi0.0,scsi-id=0,drive=drive-scsi0-0-0,id=scsi0-0-0
>
> After that, I run a bisect, and here is my bisect log:
>
> $ git bisect log
> git bisect start
> # bad: [e24dc9feb0d68142d54dc3c097f57588836d1338] tci: Support deposit
> operations
> git bisect bad e24dc9feb0d68142d54dc3c097f57588836d1338
> # good: [8db972cfa469b4e4afd9c65e54e796b83b5ce3a2] Update version for 1.2.0
> git bisect good 8db972cfa469b4e4afd9c65e54e796b83b5ce3a2
> # good: [7762c2c1e02e44fdc473cbe75105faba08b906cc] memory: rename
> 'exec-obsolete.h'
> git bisect good 7762c2c1e02e44fdc473cbe75105faba08b906cc
> # bad: [f3cdbc329fa7621ece7e673f23c3101e6b0c952b] hw/vexpress.c: Don't
> prematurely explode QEMUMachineInitArgs
> git bisect bad f3cdbc329fa7621ece7e673f23c3101e6b0c952b
> # bad: [3cbc002c34aa85ea952ee9b169a3ff97d350516a] block: prepare code for
> adding block notifiers
> git bisect bad 3cbc002c34aa85ea952ee9b169a3ff97d350516a
> # good: [f354b1a1ee7a1c72d51b42808724a2b10eec315f] fix CONFIG_QEMU_HELPERDIR
> generation again
> git bisect good f354b1a1ee7a1c72d51b42808724a2b10eec315f
> # good: [aa723c23147e93fef8475bd80fd29e633378c34d] cpus: create
> qemu_in_vcpu_thread()
> git bisect good aa723c23147e93fef8475bd80fd29e633378c34d
> # bad: [90734e02bd2fb137346d4184cec6c5d26e68f29b] serial: add pci-serial
> documentation
> git bisect bad 90734e02bd2fb137346d4184cec6c5d26e68f29b
> # bad: [1d71148eace669827ba15101819b54b20fcca616] memory: move tcg flush into
> a tcg memory listener
> git bisect bad 1d71148eace669827ba15101819b54b20fcca616
> # bad: [975aefe011197453284a4ab777000183e6096d5b] memory: provide defaults
> for MemoryListener operations
> git bisect bad 975aefe011197453284a4ab777000183e6096d5b
> # bad: [12b40e471f33e552fa3d962887b416cf67831446] xen_pt: use separate
> MemoryListeners for memory and I/O
> git bisect bad 12b40e471f33e552fa3d962887b416cf67831446
> # bad: [d22b096ef6e0b20810193b68a1d472f3fb8a4f9e] kvm: use separate
> MemoryListeners for memory and I/O
> git bisect bad d22b096ef6e0b20810193b68a1d472f3fb8a4f9e
> # good: [0fada67420e29f389119ca6f44285203400e0730] vhost: use MemoryListener
> filtering to only monitor RAM address space
> git bisect good 0fada67420e29f389119ca6f44285203400e0730
>
>
> After the last bisect step, it showed below,
>
> $ git bisect good
> d22b096ef6e0b20810193b68a1d472f3fb8a4f9e is the first bad commit
> commit d22b096ef6e0b20810193b68a1d472f3fb8a4f9e
> Author: Avi Kivity <address@hidden>
> Date: Sun Sep 30 22:21:11 2012 +0200
>
> kvm: use separate MemoryListeners for memory and I/O
>
> The construct
>
> if (address_space == get_system_memory()) {
> // memory thing
> } else {
> // io thing
> }
>
> fails if we have more than two address spaces. Use a separate listener
> for memory and I/O, and utilize MemoryListener's address space filtering
> to
> fix this.
>
> Signed-off-by: Avi Kivity <address@hidden>
>
> :100644 100644 92a71374ed1e040cef5ad70a6cb00adabf671dd4
> c69e01200461c7a87440f7a915bd171a9fc8f318 M kvm-all.c
>
>
> Ooooops, I didn't find any error in above patch, can you guys help to
> investigate this bug?
I confirmed again and found that "lsi" can't work on the upstream qemu.
Any thoughts?
Thanks,
Wanlong Gao
>
>
> Thanks,
> Wanlong Gao
>
>