From owner-freebsd-emulation@FreeBSD.ORG Wed Feb 25 19:15:55 2009 Return-Path: Delivered-To: freebsd-emulation@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC0A7106566C; Wed, 25 Feb 2009 19:15:55 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout1.freenet.de (mout1.freenet.de [IPv6:2001:748:100:40::2:3]) by mx1.freebsd.org (Postfix) with ESMTP id 5190F8FC15; Wed, 25 Feb 2009 19:15:55 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.17] (helo=7.mx.freenet.de) by mout1.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #76) id 1LcPEW-0000DJ-O6; Wed, 25 Feb 2009 20:15:52 +0100 Received: from te437.t.pppool.de ([89.55.228.55]:16348 helo=ernst.jennejohn.org) by 7.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #76) id 1LcPEW-0000E0-FZ; Wed, 25 Feb 2009 20:15:52 +0100 Date: Wed, 25 Feb 2009 20:15:50 +0100 From: Gary Jennejohn To: Juergen Lock Message-ID: <20090225201550.3d3032b5@ernst.jennejohn.org> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-emulation@FreeBSD.org, freebsd-current@FreeBSD.org, qemu-devel@nongnu.org Subject: Re: testing qemu svn r6636 on FreeBSD; future of qemu on FreeBSD... X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2009 19:15:56 -0000 On Mon, 23 Feb 2009 22:19:33 +0100 Juergen Lock wrote: > You could try a few things: > a) the same with kqemu (userland), in case its a tcg bug (or indeed a > timeout; remember to rebuild qemu in case you built it without the > kqemu knob enabled or otherwise kqemu won't get used), and also > b) another time with -kernel-kqemu in case its a tcg bug affecting > guest kernel code (altho of course in both cases kqemu can cause its > own kind of failures, even more so with amd64 guests...) > Neither of these work. The only way I can get past loading the kernel is with -no-kqemu. I still see the segmentation fault in Yast.call. Now I know that it's in line 486, if that's of any interest. Sorry, I'm not going to invest any more time in this. --- Gary Jennejohn