Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Jun 2009 15:33:04 +0200
From:      Ivan Voras <ivoras@freebsd.org>
To:        freebsd-emulation@freebsd.org
Subject:   Re: kernel panic with VirtualBox on -CURRENT
Message-ID:  <h1arae$ej2$1@ger.gmane.org>
In-Reply-To: <79646d18c5e68a6a98445763eb8798e8.squirrel@cygnus.homeunix.com>
References:  <4A383783.3010800@voicenet.com>	<20090617093329.488f8f2f@ernst.jennejohn.org> <79646d18c5e68a6a98445763eb8798e8.squirrel@cygnus.homeunix.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Nenhum_de_Nos wrote:
> On Wed, June 17, 2009 04:33, Gary Jennejohn wrote:
>> On Tue, 16 Jun 2009 20:23:31 -0400
>> Adam K Kirchhoff <adamk@voicenet.com> wrote:

>> 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 ...

Works with basic functionality on amd64 on CURRENT but hardware support 
gor "VT-x" and such doesn't work.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?h1arae$ej2$1>