Virtualbox 4.1.8 vboxdrv instantly panics on 8-stable i386
avg at FreeBSD.org
Wed Feb 22 09:20:54 UTC 2012
on 22/02/2012 05:40 Doug Barton said the following:
> On 02/21/2012 15:51, Andriy Gapon wrote:
>> Could you please substitute the attached patch file for the corresponding file
>> in the port and re-test the port?
> Good news, the kernel didn't panic. Bad news:
> supdrvGipCreate: failed to allocate the GIP page. rc=-8
> vboxdrv: supdrvInitDevExt failed, rc=-8
> module_register_init: MOD_LOAD (vboxdrv, 0xc66f33e0, 0) error 12
Yeah, I kind of expected something like this, because the original panic was in
a memory allocation failure path.
As to why the memory allocation fails I have no immediate insights. Maybe you
genuinely don't have enough contiguous pages below 4GB boundary...
Perhaps you can add a printf in
src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c right after the
vm_phys_alloc_contig() call to examine/validate its input parameters and return
> and although kldstat shows the module as loaded, and the control panel
> starts, when I try to launch a vm I get this:
It's a long standing general FreeBSD issue that there is a disconnect between
module loading and module initialization errors.
> Kernel driver not installed (rc=-1908)
> Make sure the kernel module has been loaded successfully.
More information about the freebsd-ports