kernel panic with VirtualBox on -CURRENT

[Adam K Kirchhoff]

Adam K Kirchhoff wrote:
> 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.
>>>
>>>     
>> [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.

So I decided to give the packages a shot.  When I went to 'kldunload 
vboxdrv' before installing the package version, I received another 
kernel panic:

panic: vm_page_dirty: page is invalid!
cpuid = 1
KDB: enter: panic
[thread pid 2138 tid 100282 ]
Stopped at      kdb_enter+0x3a: movl    $0,kdb_why
db> bt
Tracing pid 2138 tid 100282 td 0xc92546c0
kdb_enter(c0c5acef,c0c5acef,c0c83b8b,eb6a8a6c,1,...) at kdb_enter+0x3a
panic(c0c83b8b,eb6a8a94,c0b8aaed,c1b32c58,e94cb000,...) at panic+0x136
vm_page_dirty(c1b32c58,e94cb000,c0c91a17,9a0,e94cb000,...) at 
vm_page_dirty+0x42
pmap_remove_pte(eb6a8ad8,4,c0c91a17,9c0,c0f7cce0,...) at 
pmap_remove_pte+0xbd
pmap_remove_page(c0f7cce0,0,c0c91a17,9e0,c0f7cce0,...) at 
pmap_remove_page+0x94
pmap_remove(c0f7cce0,e94cb000,e94cc000,a2c,eb6a8b28,...) at pmap_remove+0xb2
vm_map_delete(c1890000,e94cb000,e94cc000,c6c72e10,fffffffc,...) at 
vm_map_delete+0x18c
vm_map_remove(c1890000,e94cb000,e94cc000,c72ce940,c6c72e10,...) at 
vm_map_remove+0x51
rtR0MemObjNativeFree(c6c72e10,c72dab20,0,eb6a8bac,c72d0e84,...) at 
rtR0MemObjNativeFree+0xae
RTR0MemObjFree(c6c72e10,1,0,eb6a8bd4,c72c5187,...) at RTR0MemObjFree+0xe2
supdrvGipDestroy(c6bd9510,c6bddc80,c6bddc80,eb6a8bf4,c72bf0d6,...) at 
supdrvGipDestroy+0x4c
supdrvDeleteDevExt(c72dab20,c6b8dae0,0,c6bddc80,c6bddc80,...) at 
supdrvDeleteDevExt+0x97
VBoxDrvFreeBSDModuleEvent(c6bddc80,1,0,109,0,...) at 
VBoxDrvFreeBSDModuleEvent+0xe6
module_unload(c6bddc80,c0c577d7,273,270,c0855a06,...) at module_unload+0x43
linker_file_unload(c6da4600,0,c0c577d7,437,c72b4000,...) at 
linker_file_unload+0x15e
kern_kldunload(c92546c0,9,0,eb6a8d2c,c0b8ed93,...) at kern_kldunload+0xd5
kldunloadf(c92546c0,eb6a8cf8,8,c0c61eb3,c0d41230,...) at kldunloadf+0x2b
syscall(eb6a8d38) at syscall+0x2a3
Xint0x80_syscall() at Xint0x80_syscall+0x20
--More--        --- syscall (444, FreeBSD ELF32, kldunloadf), eip = 
0x33cd561b, esp = 0xbfbfe41c, ebp = 0xbfbfec68 ---
db> cont
Uptime: 36m53s


Is anyone using VirtualBox on i386 -CURRENT from yesterday?

Adam