From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HdZqm-0004V6-0q for qemu-devel@nongnu.org; Mon, 16 Apr 2007 18:39:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HdZqk-0004Uq-BR for qemu-devel@nongnu.org; Mon, 16 Apr 2007 18:39:07 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HdZqk-0004Un-6G for qemu-devel@nongnu.org; Mon, 16 Apr 2007 18:39:06 -0400 Received: from beau.lib.la.us ([199.80.85.4] helo=library.beau.org) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HdZm5-00054L-3Y for qemu-devel@nongnu.org; Mon, 16 Apr 2007 18:34:17 -0400 Received: from mjolnir.library.beau.org (mjolnir.library.beau.org [199.80.85.12]) (authenticated bits=0) by library.beau.org (8.12.11.20060308/8.12.11) with ESMTP id l3GL0ogC028241 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 16 Apr 2007 16:00:50 -0500 Subject: Re: [Qemu-devel] two repeatable kqemu-related crashes From: John Morris In-Reply-To: <20070413073110.DE0D21DBE8B@ravel.n2.net> References: <20070413073110.DE0D21DBE8B@ravel.n2.net> Content-Type: text/plain Message-Id: <1176757250.3325.38.camel@mjolnir> Mime-Version: 1.0 Date: Mon, 16 Apr 2007 16:00:50 -0500 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Fri, 2007-04-13 at 02:31, Don Kitchen wrote: > Hi all > > I've found two repeatable (possibly related) ways to crash kqemu with 0.9.0 > and several earlier versions also I think. It's under linux 2.6.9 fully > updated CentOS 4.4 (clone of RH enterprise linux 4.4) I'm running in a similar setting without a problem. Kqemu 1.3.0pre11 + a locally cooked rpm of qemu 0.9.0 based an earlier dag package of qemu. I running WBEL 4 instead of CentOS 4, but I really doubt that is where your problem is. I'm running on x86_64 and have to admit I haven't bothered going to the very latest kernel package, still running kernel-2.6.9-34.EL. The guest I have been playing with this past week is Debian 4.0 i386. Installed and have been running since with -kernel-kqemu. The only reliable way I have to nuke the machine is boot FC5 with -kernel-kqemu and start OO.o. Without -kernel-kqemu it only kills the VM. It is something with FC5 and GCJ, been reported on the list before. Btw, OO.o as supplied with Debian 4.0 starts up without a lockup, will be throwing some documents at it later to see if it holds up. -- John M. http://www.beau.org/~jmorris This post is 100% M$Free! Geekcode 3.1:GCS C+++ UL++++$ P++ L+++ W++ w--- Y++ b++ 5+++ R tv- e* r