Date: Wed, 17 Jun 2009 11:11:19 -0400 From: Adam K Kirchhoff <adamk@voicenet.com> To: gary.jennejohn@freenet.de Cc: freebsd-emulation@freebsd.org Subject: Re: kernel panic with VirtualBox on -CURRENT Message-ID: <4A390797.3000102@voicenet.com> In-Reply-To: <20090617093329.488f8f2f@ernst.jennejohn.org> References: <4A383783.3010800@voicenet.com> <20090617093329.488f8f2f@ernst.jennejohn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Gary Jennejohn wrote: > On Tue, 16 Jun 2009 20:23:31 -0400 > Adam K Kirchhoff <adamk@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. > > Yes, kqemu was loaded, though not in use. I've made sure it is unloaded and tried again (even rebooted, just in case the fact that it had been loaded previously might be an issue). Unfortunately, I do not see an option in this computers' BIOS to enable virtualization. I'm actually trying on a machine at work now, rather than the one I tried at home yesterday, but the results are the same. This computer actually has as an Intel Core 2 Quad CPU (unlike yesterdays dualcore Xeon). Is there someway to check if the processors on these machines support the virtualization extensions? I also am not able to disable the AMD-V option in VirtualBox. The check box is selected but greyed out. Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A390797.3000102>