From: "David S. Ahern" <daahern@cisco.com>
Subject: Qemu terminating with SIGABRT
Date: Fri, 11 Dec 2009 10:08:14 -0700
Message-ID: <4B227C7E.3090807@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
To: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from sj-iport-5.cisco.com ([171.68.10.87]:47649 "EHLO
	sj-iport-5.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751022AbZLKRIL (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 11 Dec 2009 12:08:11 -0500
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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