Re: [Qemu-devel] kvm segfaulting

[Paolo Bonzini]

Il 13/02/2013 09:19, Stefan Priebe - Profihost AG ha scritto:
> Hi,
> 
> could this be this one?
> 
> commit 47a150a4bbb06e45ef439a8222e9f46a7c4cca3f
> Author: Paolo Bonzini <address@hidden>
> Date:   Thu Jan 10 15:49:08 2013 +0100
> 
>     virtio-scsi: abort in-flight I/O when the device is reset
> 
>     When the device is reset, the SCSI bus should also be reset so
>     that in-flight I/O is cancelled.
> 
>     Signed-off-by: Paolo Bonzini <address@hidden>
>     Signed-off-by: Anthony Liguori <address@hidden>

You can certainly try reverting it, but this patch is fixing a real bug.

Paolo

> Greets,
> Stefan
> Am 13.02.2013 09:01, schrieb Stefan Priebe - Profihost AG:
>> Another hint: I've never seens this using qemu 1.3.1
>>
>> Stefan
>>
>> Am 13.02.2013 08:49, schrieb Stefan Priebe - Profihost AG:
>>> Hi Paolo,
>>>
>>> sadly no luck. A VM crashed again.
>>>
>>> [ ~]# addr2line -e /usr/lib/debug/usr/bin/kvm -f 24040c
>>> virtio_scsi_command_complete
>>> hw/virtio-scsi.c:429
>>>
>>> Same point like last time:
>>> static void virtio_scsi_command_complete(SCSIRequest *r, uint32_t status,
>>>                                          size_t resid)
>>> {
>>>     VirtIOSCSIReq *req = r->hba_private;
>>>     uint32_t sense_len;
>>>
>>> 429   =====>    req->resp.cmd->response = VIRTIO_SCSI_S_OK;
>>>     req->resp.cmd->status = status;
>>>     if (req->resp.cmd->status == GOOD) {
>>>         req->resp.cmd->resid = tswap32(resid);
>>>     } else {
>>>         req->resp.cmd->resid = 0;
>>>         sense_len = scsi_req_get_sense(r, req->resp.cmd->sense,
>>>                                        VIRTIO_SCSI_SENSE_SIZE);
>>>         req->resp.cmd->sense_len = tswap32(sense_len);
>>>     }
>>>     virtio_scsi_complete_req(req);
>>>
>>> Greets
>>> Stefan
>>>
>>> Am 12.02.2013 15:34, schrieb Paolo Bonzini:
>>>> Il 12/02/2013 14:46, Stefan Priebe - Profihost AG ha scritto:
>>>>> Hi,
>>>>>
>>>>> thanks - i applied the patch to the latest master. I hope that this will
>>>>> solve my issue. Will this one get integrated in 1.4 final?
> 
>