guest additions do not build with 4.14 kernel -> fixed in builds after 1. November 2017, 5.2 and later

[Andre Robatino]

Got an error message while attempting to install guest additions in a Fedora Rawhide guest for the 4.14.0-0.rc0.git5.1.fc28.x86_64 kernel.

vboxadd.sh: failed: Look at /var/log/vboxadd-install.log to find out what went wrong.

[Andre Robatino]

/var/log/vboxadd-install.log

[Michael Thayer]

Is this still the case with VirtualBox 5.1.28?

[Andre Robatino]

/var/log/vboxadd-install.log with 5.1.28

[Andre Robatino]

Replying to michael:

Is this still the case with VirtualBox 5.1.28?

I didn't see any error when installing the GA for that kernel, but the vboxadd-install.log file still shows errors, so I'm guessing yes.

[DTI]

Hello,

problem is change in the linux kernel ​https://lkml.org/lkml/2017/8/29/254

I build my kernel with the vboxvideo module from the staging area.

I dont know if the problem is solved in 5.1.28

Best regards Damian

[Andre Robatino]

While installing a new 4.14 kernel in 5.1.28 after my last comment, I saw the same error messages as before, so definitely not solved.

[Andre Robatino]

/var/log/vboxadd-install.log with 5.1.30

[Andre Robatino]

Same error with 5.1.30 (see above 2 attachments).

[Andre Robatino]

In VirtualBox 5.2.0, I get an error message even with previously fixed kernels. The following message and logs are with a Fedora 27 guest installing the 4.13.8-300.fc27.x86_64 kernel.

VirtualBox Guest Additions: Look at /var/log/vboxadd-setup.log to find out what went wrong

It's not clear whether this is an error or just a warning or whether the Guest Additions are installed or not. Are they, and does this need to be filed as a new bug? Is it known already?

[Andre Robatino]

VBox.log for VirtualBox 5.2.0, Fedora 27 guest, 4.13.8-300.fc27.x86_64 kernel

[Andre Robatino]

vboxadd-setup.log for VirtualBox 5.2.0, Fedora 27 guest, 4.13.8-300.fc27.x86_64 kernel

[Michael Thayer]

Please try the updated images on the downloads page which should fix both problems.

[Andre Robatino]

The later of the two images mentioned (VBoxGuestAdditions_5.2.1-118452.iso) appears to fix the problem with recent kernels, but not experimental 4.14 kernels. (I didn't try 118447, hoping 118452 would fix both problems.) Attaching files for Rawhide guest.

[Andre Robatino]

vboxadd-setup.log for VirtualBox 5.2.0, Fedora Rawhide guest, 4.14 kernel

[DTI]

Hello,

the problem is the function pointer load_lut in the kernel struct drm_crtc_helper_func was removed.

Best regards Damian

[Andre Robatino]

I tested 118447, and it also appears to fix the problem with recent kernels, though with either image I see the following errors in vboxadd-setup.log.

At main.c:160:
- SSL error:02001002:system library:fopen:No such file or directory: crypto/bio/bss_file.c:74
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: crypto/bio/bss_file.c:81
sign-file: certs/signing_key.pem: No such file or directory

Since 118452 does not fix the problem with 4.14 kernels, the reference to it should be removed from https://www.215389.xyz/wiki/Downloads .

[Socratis]

I believe that the error you're seeing is due to the fact that you're loading signed kernel extensions, which VirtualBox doesn't provide. You will either need to disabled signed extensions or sign them with your own key.

I recently saw that comment from a developer, can't claim that as my own and I might be misquoting, but I think I'm really close. I'm trying to find the exact reference, but I can't at the moment...

[Valery Ushakov]

Replying to socratis:

I recently saw that comment from a developer, can't claim that as my own and I might be misquoting, but I think I'm really close. I'm trying to find the exact reference, but I can't at the moment...

#17206

[Socratis]

Hey... I was really, really close, if not spot-on! No checkup for my memory module needed... :D

Thanks vushakov!

[Andre Robatino]

It's not clear to me why you closed this bug. Does 17206 prevent building 4.14 Guest Additions?

[Socratis]

The building process fails due to your requirement for having signed kernel modules. Just like in #17205. So, it's a duplicate of #17205. Ergo, closed as a duplicate.

Or put in another way, it's not the 4.14 kernel that's the problem. The error that you're getting is due to the signed kernel modules requirement. You're focusing on the wrong parameter.

Too bad you chose to reopen the ticket without actually testing the proposed solution, or maybe you didn't realize what the nature of the "issue" was...

[Andre Robatino]

Just to be clear, I'm not talking about the error I mentioned offhand in comment 10. I'm talking about the 4.14-specific errors reported before that (such as those that appear in my vboxadd-setup.log attachment in comment 8) which are why I opened this ticket in the first place. Is there a fix for that, and if so, can you point me to a fixed image so I can test it?

Edit: BTW, the error from comment 10 does not appear to prevent me from building GA for 4.13. I do that regularly. The GA build only fails for 4.14.

[Socratis]

Well, that's what happens when you throw too many parameters and logs all lumped together, you throw people off. I was specifically replying to your comment 10 and that specific error message. And vushakov closed the ticket based on that. Simple.

There are so many tickets, threads in the forums and chats in the IRC that it's not humanly possible to review every single comment or history of a ticket every time. When you stir the waters with a new comment, I read the last comment. And your comment 10 was:

I tested 118447, and it also appears to fix the problem with recent kernels, though with either image I see the following errors in vboxadd-setup.log.

At main.c:160:
- SSL error:02001002:system library:fopen:No such file or directory: crypto/bio/bss_file.c:74
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: crypto/bio/bss_file.c:81
sign-file: certs/signing_key.pem: No such file or directory

So, do you see what you did there? You declared that build 118447 fixes the issues except your SSL ones. To which I replied to use non-signed kernel modules. To which vushakov (correctly) remembered the quoted text of mine and closed your bug as a duplicate.

Had you not changed and mixed the comments involved, none of that would have happened.

Is there a fix for that, and if so, can you point me to a fixed image so I can test it?

Always test the latest builds. I mean you are running an experimental kernel to begin with. The developers have barely enough time to fix existing kernel issues. Don't really push for the experimental ones until they're released. They deal with it, they simply don't have to support them before they are released, and even then it may take some time.

Try the latest release of VirtualBox (at revision 118468 as of this writing) from https://www.215389.xyz/wiki/Testbuilds at the "Development snapshots".

[Andre Robatino]

No, when I said it fixes the problem with recent kernels, I was repeating the language at https://www.215389.xyz/wiki/Downloads , which refers to fixing "recent Linux guest kernels". That language IS confusing, since it doesn't explain that 4.14 isn't included, but I thought that since it's still posted there, I could repeat it without being misunderstood. And given that this ticket is 6 weeks old, the only alternative to attaching all the logs to this ticket, is filing a new one, which I thought would be bad practice since the original isn't fixed yet. Let me know if I should do that.

Edit: Just checked using the Development snapshot 118468 of the GA. Building 4.14 GA still fails with the same error as before (the one mentioned in comment 9).

Edit: Regarding comment 21, I only tested 118468 because YOU asked me to (and I made it an Edit: so as not to generate an additional email). I'm not trying to get anyone's attention.

[Socratis]

Replying to robatino:

Just checked using the Development snapshot 118468 of the GA. Building 4.14 GA still fails with the same error as before (the one mentioned in comment 9).

OK, fine leave it at that, do not keep on commenting in the hopes that it will get more attention or a higher priority. I'm sure the developers already know about it. As it is stated in the Downloads:

For experimental Linux 4.14 support, please try this image.

So, you'll have to be a little bit more patient as they get around the issues. If you want to keep track of the changes and to know if the issue is being addressed in "real-time", check out the Timeline (https://www.215389.xyz/timeline) which shows you the patches that go into VirtualBox.

If you see something related, like "addresses 4.14 building issues" or "fixes the problem in the function pointer load_lut in the kernel struct drm_crtc_helper_func was removed, see #17080" or something similar, you can ask politely either here or in the IRC for a development build to try out. Like a "Hey there, I noticed a fix for XYZ in changeset 12345, can you create a test build to try it out?". They have never refused ;)

[Michael Thayer]

I have updated the link on the downloads page<1>. Please give the new build a try.

1. https://www.215389.xyz/wiki/Downloads

[Andre Robatino]

VBoxGuestAdditions_5.2.1-118868.iso works for building 4.14 GA! Thanks.