Date: Sat, 10 Jun 2017 19:01:31 +0000 From: bugzilla-noreply@freebsd.org To: vbox@FreeBSD.org Subject: maintainer-feedback requested: [Bug 219913] emulators/virtualbox-ose-kmod: when MAXCPU option is not default for running kernel 'kldload vboxdrv.ko' will result in kernel panic Message-ID: <bug-219913-26505-upeFYsdOlM@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219913-26505@https.bugs.freebsd.org/bugzilla/> References: <bug-219913-26505@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Andriy Voskoboinyk <avos@freebsd.org> has reassigned Bugzilla Automation <bugzilla@FreeBSD.org>'s request for maintainer-feedback to vbox@FreeBSD.or= g: Bug 219913: emulators/virtualbox-ose-kmod: when MAXCPU option is not default for running kernel 'kldload vboxdrv.ko' will result in kernel panic https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219913 --- Description --- Due to ABI difference (vboxdrv passes cpuset_t parameter (bitfield with CPU_SETSIZE -> MAXCPU bits) into smp_rendezvous_cpus()) kernel panics with "ncpus is 0 with non-zero map" message. Manual "opt_global.h" inclusion from current kernel build into src/VBox/Runtime/r0drv/freebsd/mp-r0drv-freebsd.c seems to fix this issue w= hen MAXCPU is overridden; kern.smp.maxcpus may be used instead (in case if other 'global' options are not so problematic).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219913-26505-upeFYsdOlM>