[Qemu-devel] Qemu terminating with SIGABRT

[Qemu-devel] Qemu terminating with SIGABRT

[David S. Ahern]

I realize this is a rather generic question, but what are typical
reasons Qemu would be killed by a SIGABRT? I am seeing this on a
somewhat regular (though not repeatable on demand) basis. I do not have
a core file, though I hope to capture one if I can get it repeat again.

Thanks,
-- 
David Ahern

[Qemu-devel] Re: Qemu terminating with SIGABRT

[Avi Kivity]

On 12/11/2009 07:08 PM, David S. Ahern wrote:
> I realize this is a rather generic question, but what are typical
> reasons Qemu would be killed by a SIGABRT? I am seeing this on a
> somewhat regular (though not repeatable on demand) basis. I do not have
> a core file, though I hope to capture one if I can get it repeat again.
>    

There's pretty much nothing we can do without a core.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

Re: [Qemu-devel] Qemu terminating with SIGABRT

[Stefan Weil]

David S. Ahern schrieb:
> I realize this is a rather generic question, but what are typical
> reasons Qemu would be killed by a SIGABRT? I am seeing this on a
> somewhat regular (though not repeatable on demand) basis. I do not have
> a core file, though I hope to capture one if I can get it repeat again.
>
> Thanks,
>   

Look for "abort" in QEMU's code to see the possible reasons.

In many cases, the reason will be printed to stderr before
aborting. Did you call QEMU from a console and get some
output there? Or maybe the stderr output went into a file?

Run "ulimit -c unlimited" before you run QEMU, then a
core file will be written automatically on SIGABRT.

Re: [Qemu-devel] Qemu terminating with SIGABRT

[David S. Ahern]

Thanks for the responses. I had forgotten that SIGABRT==abort() which
means I have to get the core file to get to the root cause. To date the
only information I have is a shell exit status of 134 which from the
bash man pages means it died due to SIGABRT.

David Ahern


On 12/12/2009 01:52 AM, Stefan Weil wrote:
> David S. Ahern schrieb:
>> I realize this is a rather generic question, but what are typical
>> reasons Qemu would be killed by a SIGABRT? I am seeing this on a
>> somewhat regular (though not repeatable on demand) basis. I do not have
>> a core file, though I hope to capture one if I can get it repeat again.
>>
>> Thanks,
>>   
> 
> Look for "abort" in QEMU's code to see the possible reasons.
> 
> In many cases, the reason will be printed to stderr before
> aborting. Did you call QEMU from a console and get some
> output there? Or maybe the stderr output went into a file?
> 
> Run "ulimit -c unlimited" before you run QEMU, then a
> core file will be written automatically on SIGABRT.
> 

Re: [Qemu-devel] Qemu terminating with SIGABRT

[Luiz Capitulino]

On Sat, 12 Dec 2009 11:09:38 -0700
"David S. Ahern" <daahern@cisco.com> wrote:

> Thanks for the responses. I had forgotten that SIGABRT==abort() which
> means I have to get the core file to get to the root cause. To date the
> only information I have is a shell exit status of 134 which from the
> bash man pages means it died due to SIGABRT.

 Are you using qemu-kvm or upstream qemu? Which version? Don't you
have any procedure which would make the bug more likely to happen?

 Thanks.

Re: [Qemu-devel] Qemu terminating with SIGABRT

[David S. Ahern]

I'm using a variant of the KVM source from RHEL5 plus a few
cherry-picked patches. Host OS is RHEL 5.3. The servers are using E5540
or E5504 processors. The host OS is running from a small USB key, and
there is no place to write a core file. Other accommodations have to be
made to get it. Hopefully by the end of the week I can get make to
reproducing the abort and capturing a core.

David Ahern


On 12/14/2009 09:04 AM, Luiz Capitulino wrote:
> On Sat, 12 Dec 2009 11:09:38 -0700
> "David S. Ahern" <daahern@cisco.com> wrote:
> 
>> Thanks for the responses. I had forgotten that SIGABRT==abort() which
>> means I have to get the core file to get to the root cause. To date the
>> only information I have is a shell exit status of 134 which from the
>> bash man pages means it died due to SIGABRT.
> 
>  Are you using qemu-kvm or upstream qemu? Which version? Don't you
> have any procedure which would make the bug more likely to happen?
> 
>  Thanks.