Virtualbox 4.1.8 vboxdrv instantly panics on 8-stable i386

Doug Barton dougb at
Wed Feb 22 09:26:25 UTC 2012

On 02/22/2012 01:20, Andriy Gapon wrote:
> 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...

It's i386, no PAE, so you could be on to something. I do have more than
4G in the box though:

real memory  = 6442450944 (6144 MB)
avail memory = 3148255232 (3002 MB)

Meanwhile, the 4.0 version worked on this same system ...

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

patch?  I am sort of short on time atm.

Either way, thanks again for looking into it.


	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)

More information about the freebsd-ports mailing list