kernel panic with VirtualBox on -CURRENT
matheus at eternamente.info
Wed Jun 17 13:29:47 UTC 2009
On Wed, June 17, 2009 04:33, Gary Jennejohn wrote:
> 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.
>> Reading symbols from /boot/modules/kqemu.ko...done.
>> Loaded symbols for /boot/modules/kqemu.ko
> 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 ...
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?
More information about the freebsd-emulation