From owner-freebsd-ports@FreeBSD.ORG Fri Apr 6 14:59:32 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4F1D516A403 for ; Fri, 6 Apr 2007 14:59:32 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by mx1.freebsd.org (Postfix) with ESMTP id 29B7D13C4C2 for ; Fri, 6 Apr 2007 14:59:32 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from gumby.homeunix.com (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 4215851931 for ; Fri, 6 Apr 2007 10:59:28 -0400 (EDT) Date: Fri, 6 Apr 2007 15:59:21 +0100 From: RW To: freebsd-ports@freebsd.org Message-ID: <20070406155921.229b6ec9@gumby.homeunix.com> In-Reply-To: References: X-Mailer: Claws Mail 2.8.1 (GTK+ 2.10.11; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: qemu: kqemu not compiled? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Apr 2007 14:59:32 -0000 On Fri, 06 Apr 2007 13:05:41 +0200 Ivan Voras wrote: > I've installed qemu 0.9 and kqemu 1.3, and I'm trying to run a i386 > FreeBSD guest under amd64 FreeBSD host, but there's a problem: "info > kqemu" command in qemu reports "kqemu not compiled". But it should be > - the KQEMU option is active on the port and the "configure" step in > the port reports "kqemu support: yes". > > Judging from the disk throughput in sysinstall (never going above > e.g. 900 KB/s), it looks like it really isn't enabled. > > Any ideas? > Would you expect to able to run kqemu, when the architecture is different between the host and guest? The point of kqemu is that some instructions in the guest can be run natively on the host cpu. Unless there's some special support in kqemu for switching backwards and forwards between 32 and 64 mode, that's not going to work.