Hello world :-) After upgrading from 13.1-RELEASE-p6 to 13.2-RELEASE-p0 VirtualBox does not work anymore, there are two problems: 1. pkg version is provided for 13.1. 2. port version kernel panics on 13.2. After system upgrade I have bootstrapped the pkg-static upgrade -f, updated and upgraded all packages. emulators/virtualbox-ose-kmod provided by pkg does not load as it is built for 13.1, see message: Message from virtualbox-ose-kmod-6.1.36: -- The vboxdrv kernel module uses internal kernel APIs. To avoid crashes due to kernel incompatibility, this module will only load on FreeBSD 13.1 kernels. Version from ports master builds fine but crashes the system on kldload / service start. I have already saw that situation on 13.2-STABLE and rolled back to 13.1-RELEASE but now I have no vbox again.
The /usr/src uses git branch releng/13.2 at: 525ecfdad597 (HEAD -> releng/13.2, tag: release/13.2.0, origin/releng/13.2) Update in preparation for 13.2-RELEASE a92e3fa2ade5 13.2: update to RC6 878cd9623c8e amd64 wakeup: recalculate mitigations after APICs are woken
The package builds via 13.2-RELEASE have not even started yet. Systems using/needing kernel-specific ports should wait to upgrade to 13.2-RELEASE until the packages are known to be available if they are updating via binary packages. This is normal when a new release happens. FreeBSD does not hold the release until after the packages are available. 13.1-RELEASE is still supported for some time but cannot use 13.2-RELEASE based packages generally.
(In reply to Mark Millard from comment #2) Quoting https://freebsdfoundation.org/blog/technology-roadmap/ (from 2021-Sept-17): QUOTE There are normally no problems building packages on a host that is one or more point releases behind the version of hosts targeted for the packages. Indeed, FreeBSD’s official package sets are built on the oldest supported release on each branch. However, problems do occur with packages such as graphics/drm-*-kmod, which include kernel modules. To prevent users from having newly updated systems with a non-functioning display server, per-release repositories have been proposed. Release-specific overlays could be used to, e.g., offer DRM packages simultaneously for 13.0 and 13.1 while both point releases are supported. END QUOTE
No problem with pkg built for 13.1 but port built on 13.2 kernel crashes on load :-( I am into bhyve "vm" utility as alternative to vbox..
(In reply to Tomasz "CeDeROM" CEDRO from comment #4) Sorry that I misinterpreted some of the context/wording. And nice to see that the 13.1-RELEASE build is rejected with a message, now that I look again.
no worries :-) i just report issues encountered on 13.2 i am sure this will be fixed soon :-)
(In reply to Tomasz "CeDeROM" CEDRO from comment #4) > … port built on 13.2 kernel crashes on load … Not reproducible here. From <https://reviews.freebsd.org/D39474#899539>: > … the module **does** load following build from source (in a jail that > is upgraded to 13.2-RELEASE): …
Thanks for the feedback Graham :-) What could be the problem then? Maybe using git branch releng/13.2 instead packaged src ? Maybe additional modules in conflict?
(In reply to Tomasz "CeDeROM" CEDRO from comment #8) Is the directory /usr/src updated ?
Is this PR still relevant? virtualbox-ose updated to 6.1.44.