Virtualbox 4.1.8 vboxdrv instantly panics on 8-stable i386

Bernhard Froehlich decke at FreeBSD.org
Wed Feb 22 09:41:33 UTC 2012


On 22.02.2012 10:26, Doug Barton wrote:
> 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 ...

The 4.0.16 version is still available as 
emulators/virtualbox-ose-legacy and
doesn't include the memobj r0 patch so it should still work. (you will 
need to
switch to devel/kBuild for that)

-- 
Bernhard Froehlich
http://www.bluelife.at/


More information about the freebsd-ports mailing list