[SOLVED] guest additions failed to compile with kernel 4.16

pourpier · Apprentice Joined: 27 Sep 2017 Posts: 166

Hello!
I did compile the kernel 4.16 without any issue. Normally, this kernel should have the guest additions included in the kernel. I tried the command emerge @module-rebuild and I had the following error messages: https://paste.pound-python.org/show/uDJgHLvPTGGnoDRQ8QEJ/
I think this is due to the fact that the version 5.2.8 of VBox doesn't support the version 4.16 of the kernel.
Is there a workaround? I can donwgrade the kernel but I wouldn't like to do it.
Best regards,
pourpier

C5ace · Posted: Tue Apr 10, 2018 9:46 am Post subject:

Try app-emulation/virtualbox-5.1.32 (stable) etc. with kernel sys-kernel/gentoo-sources-4.9.72 or 4.9.76-r1 (stable). use sys-devel/gcc-6.4.0-r1 and sys-libs/glibc-2.25-r11.

pourpier · Apprentice Joined: 27 Sep 2017 Posts: 166

if · n00b Joined: 15 Jun 2010 Posts: 23

I tried 5.2.10 and it failed as well.

pourpier · Apprentice Joined: 27 Sep 2017 Posts: 166

if · n00b Joined: 15 Jun 2010 Posts: 23

^ Thank you for your input. I ignored the new option. After making it as a module and rebooting the kernel, virtualbox-guest-additions-5.2.10 still failed.
lsmod shows five modules related to vbox. They are vboxpci, vboxnetadp, vboxnetflt, vboxdrv, and vboxguest.
Strangely, warnings shown up before when starting X disappeared.
Do I need to emerge virtualbox-guest-additions with this option change? Or can I simply emerge -C this package?

Nope. Removing virtualbox-guest-additions does no good for display. Now I have much smaller screen.
I noticed there is a warning to enable VBOXVIDEO option as well as VBOXGUEST in its help.
But I cannot find this VBOXVIDEO line in .config file or in menuconfig.
Since the emerge error occurs under /tmp/.../work/vboxvideo, I assume making VBOXVIDEO option on is the key.
Where can I find it? :roll:

Got it!
Device Drivers -> Staging drivers -> Virtual Box Graphics Card

Hmm... but I still get the same error message with the package. :cry:

pourpier · Apprentice Joined: 27 Sep 2017 Posts: 166

if · n00b Joined: 15 Jun 2010 Posts: 23

The error message I had got is... this (from another post).
I booted into 4.15.10, which I safely used, and emerged vbox guest addition against 4.16.3 and 4.16.5, both of which failed with the above same error in vbox_ttm.c.

Then I tried the patch solution.
It seemed to be emerged OK this time on 4.15.10 against 4.16.5 except that there are warnings telling me vboxsf.ko needs unknown symbol VBoxGuestsomething and something.
Sure enough, when I try to boot into 4.16.5, the boot stops after showing messages relating to VBox module load errors and right after setting framebuffer console images.

Is there any kernel setting about vboxsf? I think it is file system related, but I see no setting for vbox in file system section.

pourpier · Apprentice Joined: 27 Sep 2017 Posts: 166

if · n00b Joined: 15 Jun 2010 Posts: 23

Thank you for every kind helps!

I always do not mount guest drive on boot, but mount it after launching X.
So I do not think mount timing is the issue here.

What I do not understand is... emerging the same virtualbox-guest-additions-5.2.10 on kernel 4.5.10 went totally fine without the patch, but failed on kernel 4.15.15, 4.16.3 and 4.16.5 even with the patch (as for 4.16.5, emerging went fine with the patch but it does not boot fine).
emerge environment is the same on each kernel. Only kernel version is different.

With the patch integrated into original virtualbox-guest-additions-5.2.10 ebuild file, now virtualbox-guest-additions-5.2.10 emerges fine.

The problem now is virtualbox-modules-5.2.10, which emerges fine, but has unknown symbol issue.
The exact warning message is below.

pourpier · Apprentice Joined: 27 Sep 2017 Posts: 166