From: "David S. Ahern" <daahern@cisco.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Stefan Weil <weil@mail.berlios.de>,
qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Qemu terminating with SIGABRT
Date: Mon, 14 Dec 2009 09:09:07 -0700 [thread overview]
Message-ID: <4B266323.2010007@cisco.com> (raw)
In-Reply-To: <20091214140405.493ecbba@doriath>
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.
WARNING: multiple messages have this Message-ID (diff)
From: "David S. Ahern" <daahern@cisco.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Qemu terminating with SIGABRT
Date: Mon, 14 Dec 2009 09:09:07 -0700 [thread overview]
Message-ID: <4B266323.2010007@cisco.com> (raw)
In-Reply-To: <20091214140405.493ecbba@doriath>
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.
next prev parent reply other threads:[~2009-12-14 16:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 17:08 Qemu terminating with SIGABRT David S. Ahern
2009-12-11 17:08 ` [Qemu-devel] " David S. Ahern
2009-12-11 18:11 ` Juan Quintela
2009-12-12 8:09 ` Avi Kivity
2009-12-12 8:09 ` [Qemu-devel] " Avi Kivity
2009-12-12 8:52 ` [Qemu-devel] " Stefan Weil
2009-12-12 18:09 ` David S. Ahern
2009-12-12 18:09 ` [Qemu-devel] " David S. Ahern
2009-12-14 16:04 ` Luiz Capitulino
2009-12-14 16:04 ` Luiz Capitulino
2009-12-14 16:09 ` David S. Ahern [this message]
2009-12-14 16:09 ` David S. Ahern
2009-12-21 14:16 ` David S. Ahern
2009-12-21 14:22 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B266323.2010007@cisco.com \
--to=daahern@cisco.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.