From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MbGgR-0002CU-0u
	for qemu-devel@nongnu.org; Wed, 12 Aug 2009 12:28:15 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MbGgP-0002At-CN
	for qemu-devel@nongnu.org; Wed, 12 Aug 2009 12:28:14 -0400
Received: from [199.232.76.173] (port=58841 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MbGgP-0002Al-6D
	for qemu-devel@nongnu.org; Wed, 12 Aug 2009 12:28:13 -0400
Received: from alpha.arachsys.com ([91.203.57.7]:36538)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <chris@arachsys.com>) id 1MbGgO-0003Zc-Gy
	for qemu-devel@nongnu.org; Wed, 12 Aug 2009 12:28:12 -0400
Date: Wed, 12 Aug 2009 17:24:01 +0100
From: Chris Webb <chris@arachsys.com>
Message-ID: <20090812162401.GB8115@arachsys.com>
References: <20090812150159.GW5348@arachsys.com> <4A82E200.3040107@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A82E200.3040107@redhat.com>
Subject: [Qemu-devel] Re: qemu-kvm segfaults in qemu_del_timer (0.10.5 and
	0.10.6)
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org

Avi Kivity <avi@redhat.com> writes:

> I understand it's hard, but it's nearly impossible to work out the  
> problem from so little data, so please do make the effort to obtain 
> dumps.

We're trying for this at the moment, but since we can't change the rlimit
for the running qemu-kvm processes (?), we'll have to wait until one of the
new ones dies, which may take some time. I'll follow up when I do have
something.

Cheers,

Chris.