From owner-freebsd-ports@FreeBSD.ORG Tue Jul 26 22:35:49 2005 Return-Path: X-Original-To: ports@FreeBSD.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FBFD16A420; Tue, 26 Jul 2005 22:35:49 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C9A743D49; Tue, 26 Jul 2005 22:35:48 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id j6QMc4T4065413; Tue, 26 Jul 2005 18:38:05 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Juergen Lock Date: Tue, 26 Jul 2005 18:35:29 -0400 User-Agent: KMail/1.6.2 References: <20050725222608.A42815@saturn.kn-bremen.de> <200507251825.51540.jkim@FreeBSD.org> <20050726014207.A48961@saturn.kn-bremen.de> In-Reply-To: <20050726014207.A48961@saturn.kn-bremen.de> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200507261835.32168.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.85.1/993/Tue Jul 26 03:28:36 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: ports@FreeBSD.org, freebsd-emulation@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: need help with kqemu 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: Tue, 26 Jul 2005 22:35:49 -0000 On Monday 25 July 2005 07:42 pm, Juergen Lock wrote: > On Mon, Jul 25, 2005 at 06:25:50PM -0400, Jung-uk Kim wrote: > > Try the attachment. It seems to build and work on amd64 now, > > including kqemu. > > Hey, nice! So there wasnt actually that much wrong... One > question: Does this also work on 4.x? > > Here's my version: (I disabled a kqemu_vmalloc_to_phys(%p) printf > and added back use of the system cc for kqemu) BTW, I think KQEMU for amd64 is still unstable. VM crashes with error message like this: kqemu: aborting: Unexpected exception 0x0d in monitor space CS:EIP=f180:ffff900000001729 With `-no-kqemu' option, everything's fine. Actually somebody in Linux world also reported somthing similar. In his case, it was just hanging VM, though. Thanks, Jung-uk Kim