Re: 13.1-STABLE vritualbox-ose-kmod panic

There is a period of time in the release engineering cycle when the version of virtualbox-ose-kmod in pkg works, but most of the time it will need to be compiled from the port. 

If you look at dmesg if you are rebooting to load the the kmod, you should see an error message that the kmod could be loaded due to a version incompatibitliy. You'll get the same error if you attempt to load the kmod manually. 

There is at least one relatively recent thread on this in the mailing list with more explanation, but personally I have found it simplest to just always build the kmod from ports when updating. 

> From: "Graham Perrin" <grahamperrin@freebsd.org>
> To: "FreeBSD questions" <freebsd-questions@freebsd.org>
> Cc: "VirtualBox on FreeBSD team" <vbox@freebsd.org>, "Virtualisation on FreeBSD"
> <freebsd-virtualization@freebsd.org>
> Sent: Tuesday, January 24, 2023 4:13:54 PM
> Subject: Re: 13.1-STABLE vritualbox-ose-kmod panic

> On 24/01/2023 23:07, Graham Perrin wrote:

>> On 24/01/2023 22:06, Tomek CEDRO wrote:

>>> … The first time I noticed that problem was beginning of January 2023. Before I
>>> was able to use virtualbox-ose(-kmod) on STABLE with no problem.

>>> How can I make things work again?

>>> Will virtualbox-ose-kmod work only with a RELEASE and not with STABLE?

> It works here with CURRENT.

>>> Do I need to rebuild both virtualbox-ose and virtualbox-ose-kmod from ports? …

> Tomek, please check that your copy of the ports tree is up-to-date.

> If you build from source, build (and install) the kernel module alone.