qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] kvm segfaulting


From: Stefan Priebe - Profihost AG
Subject: Re: [Qemu-devel] kvm segfaulting
Date: Mon, 11 Feb 2013 14:58:05 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2

Hi Paolo,

as the guest crashes i can't check the guest. On the host i just have
the segmentation fault line. Anything else is from the bootprocess or
enabling the tap device. So nothing suspicious.

Greets,
Stefan

Am 11.02.2013 14:56, schrieb Paolo Bonzini:
> Il 11/02/2013 14:35, Stefan Priebe - Profihost AG ha scritto:
>> Hi Stefan,
>>
>> yes i use virtio-scsi-pci in all my guests. As it is the only one where
>> i can use fstrim from guest to storage with rbd ;-)
> 
> Can you check for anything suspicious in the kernel console output?
> 
> Paolo
> 
>> Stefan
>> Am 11.02.2013 14:21, schrieb Stefan Hajnoczi:
>>> On Mon, Feb 11, 2013 at 2:08 PM, Stefan Priebe - Profihost AG
>>> <address@hidden> wrote:
>>>> Hi,
>>>> Am 11.02.2013 13:48, schrieb Paolo Bonzini:
>>>>> Il 11/02/2013 10:48, Stefan Priebe - Profihost AG ha scritto:
>>>>>>     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);
>>>>>> }
>>>>>
>>>>> Can you reproduce this?
>>>>
>>>> Sadly no - but i've seen this 3 times in the last 4 weeks. I checked all
>>>> addresses / dmesg messages and all crashes point to that line.
>>>
>>> Just for sanity, because I never trust addr2line, can you please
>>> confirm that you are using virtio-scsi in your guest?
>>>
>>> The kvm command-line should contain "-device virtio-scsi-pci".
> 
> 
> 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]