Re: emulators/virtualbox-ose-kmod (was: 13.0 is not yet EOL)

From: Dale Scott <dalescott_at_shaw.ca>
Date: Tue, 02 Aug 2022 23:34:35 UTC 
> From: "Graham Perrin" <grahamperrin@freebsd.org>
> To: "questions" <questions@freebsd.org>
> Sent: Tuesday, August 2, 2022 12:55:30 PM
> Subject: emulators/virtualbox-ose-kmod (was: 13.0 is not yet EOL)

> On 02/08/2022 19:46, Dale Scott wrote:

>> Which is why pkg's that link to the kernel API need to temporarily be compiled
>> from source (until 13.0 is truly EOL and pkgs are built with 13.1, e.g.
>> virtualbox-ose-kmod) …

> I see [ https://www.freshports.org/emulators/virtualbox-ose-kmod/#history |
> <https://www.freshports.org/emulators/virtualbox-ose-kmod/#history> ] , IIRC
> packaged 6.1.34_1 did work with 13.1-RELEASE; the kernel module did load.

> I have not tested packaged 6.1.36 with 13.1-RELEASE.

>> On Aug 2, 2022 11:56 AM, Graham Perrin [ mailto:grahamperrin@freebsd.org |
>> <grahamperrin@freebsd.org> ] wrote:

>>> On 31/07/2022 18:08, Kevin Oberman wrote:

>>>> … 13.0 is EOL …
>>> Not yet; [ https://www.freebsd.org/security/#sup |
>>> <https://www.freebsd.org/security/#sup> ]

Curious. When I upgraded from 13.0 to 13.1 virtualbox-ose stopped running. I upgraded virtualbox-ose using pkg a while later (2022-07-19) and found a note in dmesg reporting the kmod wouldn't load due to a kernel version mismatch. I installed the kernel source tree and make installed virtualbox-ose-kmod from the ports tree to resolve the issue. 

These were the best references I found explaining how and why pkgs are built against 13.0 after 13.1 is released until 13.0 is EOL: 

[ https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264066 | https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264066 ] 

[ https://forums.freebsd.org/threads/virtualbox-kernel-module-fails-to-load-on-freebsd-13-1-release.85191/ | https://forums.freebsd.org/threads/virtualbox-kernel-module-fails-to-load-on-freebsd-13-1-release.85191/ ] 

Cheers, 
Dale