From owner-freebsd-emulation@FreeBSD.ORG Wed Jun 17 13:29:47 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 310EA106564A for ; Wed, 17 Jun 2009 13:29:47 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.24]) by mx1.freebsd.org (Postfix) with ESMTP id D187B8FC0C for ; Wed, 17 Jun 2009 13:29:46 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: by qw-out-2122.google.com with SMTP id 3so142257qwe.7 for ; Wed, 17 Jun 2009 06:29:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:received:received :message-id:in-reply-to:references:date:subject:from:to:user-agent :mime-version:content-type:content-transfer-encoding:x-priority :importance; bh=4MO0d7BEa7Z7XDDoQUn/exJ1uMgq654Vpyea6eFbgaQ=; b=b02aD9qLp1b5ctZIPTyZcs9akleitbtGmhlWxzRgOMYMIxO8lQd6ERG8iC8m9VmLCu fk91PlL3vUqV/iHUMW9YdG+tw8ZjHLtDjBv90YHUjq9qdCKLzS9J1njTnD0klc9VEeJ4 IDfgLgX46sxXbvTk5wXhk54QTjnfQ8nn57QhE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:in-reply-to:references:date:subject:from:to :user-agent:mime-version:content-type:content-transfer-encoding :x-priority:importance; b=rxO/MVkh8rdUjeU0FcM8Vc+HnMhXK2i4503Rok3KXy1gxEBp30/iotNTLYqcr4nE99 HSNdT38FuyQdMZOQAbMVukTtK3Ni6L/GKx9CoZIRANit0NqKW1TbPfbU3QqlQqpJ44GN yurDuP/XwApRlWP5JZAlHmiUxofUJ9mQZIVPk= Received: by 10.224.74.84 with SMTP id t20mr130460qaj.328.1245245386277; Wed, 17 Jun 2009 06:29:46 -0700 (PDT) Received: from cygnus.homeunix.com ([189.71.105.194]) by mx.google.com with ESMTPS id 6sm65755qwk.10.2009.06.17.06.29.45 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 17 Jun 2009 06:29:45 -0700 (PDT) Sender: Nenhum_de_Nos Received: by cygnus.homeunix.com (Postfix, from userid 80) id 07C91B8083; Wed, 17 Jun 2009 10:29:39 -0300 (BRT) Received: from 189.92.195.60 (SquirrelMail authenticated user matheus) by cygnus.homeunix.com with HTTP; Wed, 17 Jun 2009 10:29:39 -0300 (BRT) Message-ID: <79646d18c5e68a6a98445763eb8798e8.squirrel@cygnus.homeunix.com> In-Reply-To: <20090617093329.488f8f2f@ernst.jennejohn.org> References: <4A383783.3010800@voicenet.com> <20090617093329.488f8f2f@ernst.jennejohn.org> Date: Wed, 17 Jun 2009 10:29:39 -0300 (BRT) From: "Nenhum_de_Nos" To: freebsd-emulation@freebsd.org User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: kernel panic with VirtualBox on -CURRENT X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2009 13:29:47 -0000 On Wed, June 17, 2009 04:33, Gary Jennejohn wrote: > On Tue, 16 Jun 2009 20:23:31 -0400 > Adam K Kirchhoff wrote: > >> I recently updated my workstation at home to -CURRENT, and then noticed >> (thanks to some discussion on ##freebsd) that VirtualBox had made it >> into the ports tree. I installed it via ports, but upon trying to boot >> a VDI image created under Linux (where it works just fine), I ran into a >> kernel panic. When starting the VM, VirtualBox informs me of the key >> combination to grab/release the mouse and keyboard. I click "OK" and >> then the entire machine locks up. >> >> The VM is Windows XP. 256 megs of RAM, 1 processor, VT-x/AMD-V is >> enabled, with Nesting Paging disabled. The only option I changed was >> the memory. All the others were the defaults. >> >> I reproduced the panic quite easily by rebooting into single user mode, >> fsck'ing the filesystems manually, booting into X, and then starting up >> VirtualBox. Same thing happened when I launched the VM. >> > [snip] >> Reading symbols from /boot/modules/kqemu.ko...done. >> Loaded symbols for /boot/modules/kqemu.ko > [snip] > > I don't know whether this will help, but do you really have kqemu.ko > also installed? I'd try eliminating it before running VirtualBox. > > VirtualBox runs just fine for me, but I don't load kqemu.ko. > > Also, did you enable virtualization in the BIOS? I had to do that > before AMD-V really functioned. It made quite a bit of difference > in performance. yet on this topic. vbox in FreeBSD is just working on i386 current ? (the page says so). I got it running on 7.2-STABLE amd64 quite ok ( some crashes here and then), but never on amd64 from current ... thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style