[Bug 219913] emulators/virtualbox-ose-kmod: if the MAXCPU option is not the default for the running kernel, then 'kldload vboxdrv.ko' will result in a kernel panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219913

--- Comment #13 from Craig Leres <leres@freebsd.org> ---
(In reply to Vladimir Druzenko from comment #12)
(Don't sweat your English, I don't even know more than one language!)

To my way of thinking the minimal fix is to prevent the crash that happens when
you run a custom kernel that is compiled with a MAXCPU that's different from
the default. That way if the user wants to run with a different MAXCPU they'll
find out that they need to build a matching custom vbox module.

Consider the case when the user has a working vbox setup but they build a
custom kernel to increase MAXCPU. When the reboot they'll have to mess with the
bootloader to avoid loading the problematic module before they can even boot
again.

What would be ideal is if the module could make a cpuset_t at runtime by
looking at mp_maxcpus instead of being hard-coded to use the MAXCPU define.

-- 
You are receiving this mail because:
You are on the CC list for the bug.