11.1-RELEASE virtualbox-ose panic: ncpus is 0 with non-zero map

[Craig Leres]

On 04/04/18 15:51, Allan Jude wrote:
> The official packages are built for the GENERIC kernel, I think
> specifically changing the MAXCPU will change the size of one of the
> structs used by the module, causing this issue.

I'm not so sure about that. I believe MAXCPU changes some data structure 
sizes and allows for kernels that have up to that many cores. I don't 
believe loadable drivers care what it is.

They system I built the virtualbox-ose-kmod package on was running the 
same 64 MAXCPU kernel at the time (I built and booted the custom kernel 
before building packages).

		Craig