Running FreeBSD 13.1-RELEASE-p0 as guest within a VBox (host is the Linux, supposedly RedHat, of a security OS, no further details known, VBox is 6.1.28), FreeBSD's X11 rejects to work since today's update of ports. Starting X11 results in a suspicous log entry, stating: (EE) vboxvideo: module ABI major version (24) doesn't match the server's version (25) I guess this reported mismathc is the culprit. Since I have not chance to change anything and any parameter for video setting of the host's VBox settings, nor is it lileky that the version of the used VBox will be pushed towards 6.1.36 as FreeBSD's ports, I desperately need a solution applicable from the guest itself (FreeBSD). Is there a workaround possible?
Additional info: Upgrade has performed via "latest" repo. Just now trying to revert everything to "quarterly", just checking whether this mitigates the reported problem.
Checked out "quarterly" and resinstalled ALL ports (pkg upgrade -f). Issue gone. Problem lies with "latest".
(In reply to O. Hartmann from comment #0) Hi, Looks like a possible issue due to the recent Xorg server upgrade in the latest package set. I guess the additions port needs a PORTREVISION bump to force being rebuilt. Ti fix it locally it should be enough for you to force the reinstallation of the additions in the FreeBSD guest.
(In reply to Guido Falsi from comment #3) Hello, no, the enforcement of reinstallation of ALL ports did not bring any salvation - I did so in the first place. I also forced the reinstallation of the guest additions alone, whch did also not solve the problem in the first place. Then I forced a reinstallation of ALL ports (still "latest"), which did not solve it, either. The salvation was to reinstall all ports from "quarterly" ports, since I did not knew what port caused the problems. With "quarterly" the problem is mitigated, so far. Kind regards oh
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=f5957f13490eee2d6764f40e74a45700f0c8ac11 commit f5957f13490eee2d6764f40e74a45700f0c8ac11 Author: Guido Falsi <madpilot@FreeBSD.org> AuthorDate: 2022-08-09 14:45:06 +0000 Commit: Guido Falsi <madpilot@FreeBSD.org> CommitDate: 2022-08-09 14:45:06 +0000 emulators/virtualbox-ose-additions*: Bump portrevision. Force update after xorg-server update. Sei PORTREVISION=0 on nox11 versions since those don't need reinstallation. PR: 265731 Reported by: O. Hartmann <ohartmann@walstatt.org> emulators/virtualbox-ose-additions-legacy/Makefile | 2 +- emulators/virtualbox-ose-additions-nox11-legacy/Makefile | 1 + emulators/virtualbox-ose-additions-nox11/Makefile | 1 + emulators/virtualbox-ose-additions/Makefile | 1 + 4 files changed, 4 insertions(+), 1 deletion(-)
I've bumped PORTREVISION on the affected ports. This should fix the issue for everyone once the cluster refreshes packages (I guess it can take 2-3 days)
As of today's pull of packages (pkg upgrade on repository "latest"), the problem as described still persists.
On a testbox running poudriere for 13.1-RELENG the update port with PORTREVISION "_1" is present: emulators/virtualbox-ose-additions is at 4.1.36_1 on the poudriere port, but it is still at 4.1.36 on the "latest" repository (pkg.freebsd.org/FreeBSD:13:amd64/latest). So, the official builder is behind ...
(In reply to O. Hartmann from comment #8) Unluckily I have no control on when the builders build packages and how long they will take. There have been many update to packages with many dependencies, so it is quite possible official builders will require some time to complete a new set. The port in the git repo has been bumped, and anyway a manual forced update of the installed package should fix the issue. If you think this should stay open until the official package of virtualbox-ose-additions-4.1.36_1 is available, please close it once that condition is fulfilled. Thanks!
Hi again. Have you had a chance to check? I think builders are now aligned and the ABI version issue should be fixed. Although, I'm experiencing a new issue, the virtualbox video driver for Xorg now fails to work for me, if using the latest packages in the virtual machine. It could be a local issue on my system though. Have you had a chance to test?
Hello, please don't worry, builders have already done their job - so the X11 server and vboxvideo are now aligned as it should be - and working as expected.