From: "David S. Ahern" Subject: Re: [Qemu-devel] Qemu terminating with SIGABRT Date: Mon, 14 Dec 2009 09:09:07 -0700 Message-ID: <4B266323.2010007@cisco.com> References: <4B227C7E.3090807@cisco.com> <4B2359BB.9070703@mail.berlios.de> <4B23DC62.5090301@cisco.com> <20091214140405.493ecbba@doriath> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Stefan Weil , qemu-devel@nongnu.org, kvm-devel , Avi Kivity To: Luiz Capitulino Return-path: Received: from sj-iport-5.cisco.com ([171.68.10.87]:61940 "EHLO sj-iport-5.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757644AbZLNQJM (ORCPT ); Mon, 14 Dec 2009 11:09:12 -0500 In-Reply-To: <20091214140405.493ecbba@doriath> Sender: kvm-owner@vger.kernel.org List-ID: 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" 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.