kernel panic with VirtualBox on -CURRENT

[Gary Jennejohn]

On Tue, 16 Jun 2009 20:23:31 -0400
Adam K Kirchhoff <adamk at voicenet.com> 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.

---
Gary Jennejohn