[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

2024-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219913 Vladimir Druzenko changed: What|Removed |Added CC||v...@freebsd.org --- Comment #

[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

2024-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219913 Craig Leres changed: What|Removed |Added Attachment #244203|0 |1 is obsolete|

[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

2024-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219913 --- Comment #10 from Vladimir Druzenko --- (In reply to Craig Leres from comment #9) Is it work if emulators/virtualbox-ose-kmod was build with same MAXCPU as kernel? For example using something like -DMAXCPU=N during build emulators/virtua

[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

2024-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219913 --- Comment #11 from Craig Leres --- (In reply to Vladimir Druzenko from comment #10) Back when I was using virtualbox (six years ago), I had no issues using a custom kernel so long as mp_maxcpus == MAXCPU. -- You are receiving this mail

[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

2024-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219913 --- Comment #12 from Vladimir Druzenko --- (In reply to Craig Leres from comment #11) MAXCPU defined in /usr/include/machine/param.h, mp_maxcpus from running kernel from option MAXCPU. If you build emulators/virtualbox-ose-kmod without defi

[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

2024-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219913 --- Comment #13 from Craig Leres --- (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

[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

2024-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219913 --- Comment #14 from Vladimir Druzenko --- (In reply to Craig Leres from comment #13) Can you please explain: if I build kernel with non-default MAXCPU, boot it, then build virtualbox-ose-kmod without any patched - can it work or I must to

[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

2024-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219913 --- Comment #15 from Craig Leres --- First, I would not worry too much about supporting users who want to use a non-default MAXCPU, they'll be able to figure it out. But is it likely that anyone would even want to do this? The current defa