You don't have the same kernel as the thread that you quoted (Fedora 29 - guest additions shared folders). That one was 4.16.3-200-fc27.x86_64, not the latest and greatest one. I assume that if you "followed" the thread you already did:
I would suggest to try the latest 5.2.x test build. I seem to recall a couple of issues being addressed with F29 and the 4.19 kernels...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
I'm getting the same thing with VB 6.0 (Fedora 29, kernel 4.19.8-300.fc29.x86_64). On the bright side, the VB Guest Additions that come with F29 (version 5.2.22) seem to work OK.
EDIT: I tried the test build of GA (version 5.2.23) and it did the same thing. The RPM version has no support for automatic screen resizing or shared folders.
I tested kernel 4.19 (4.19.12-1.el7.elrepo.x86_64) on my RHEL 7.6 guest. I do not see any issue there. All three vbox kernel modules were built fine. I am running VirtualBox 5.2.23.
Had the same problem here (Mac Mojave host, Fedora29 guest with kernel up to 4.19.12 using VB6 and GA6.0.0 GA,
updating to VB6.0.1 and GA 6.0.1 (from test-build VBoxGuestAdditions_6.0.1-127639.iso) didn't help either,
but upgrading the kernel to 4.19.13 yesterday seemed to have done the trick, vboxsf module loads again..
JeanR wrote:but upgrading the kernel to 4.19.13 yesterday seemed to have done the trick, vboxsf module loads again..
Thanks for the letting us know...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Moreover, stepping back to VB6.0 and recompiling GA6.0.0 with kernel 4.19.13 the problem with the unknown symbols for vboxsf is also gone,
I even checked that shared folders do work, so if someone else can confirm this, I think you can close(solved)/invalidate this thread.
NB: seems there's an even newer kernel out now (4.19.14 that is) which I'm gonna try out now.. - and yep! - this also works:
Two more remarks:
1) the thread title should be changed to e.g. 'Shared Folder support module fails to build', rather than GA failed to start, cause that's what the problem is all about
2) the fact that you need lsmod/dmsg to detect that/why the build fails is dissatisfactory, shouldn't this be visible in the build window as well?
[root@localhost VBox_GAs_6.0.0]# ./VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 6.0.0 Guest Additions for Linux........
VirtualBox Guest Additions installer
Removing installed version 6.0.0 of VirtualBox Guest Additions...
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules. This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: Building the modules for kernel 4.19.14-300.fc29.x86_64.
VirtualBox Guest Additions: Look at /var/log/vboxadd-setup.log to find out what went wrong
VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the modules for kernel 4.19.14-300.fc29.x86_64.
VirtualBox Guest Additions: Look at /var/log/vboxadd-setup.log to find out what went wrong
VirtualBox Guest Additions: modprobe vboxsf failed
Last edited by socratis on 17. Jan 2019, 20:38, edited 1 time in total.
Reason:Reason: Enclosed the information in [quote][code] tags for better readability.
could you please check/verify in /var/log/vboxadd-setup.log, that this is indeed the same problem?
That is the 'unknown symbols' problem described by the OP (DWF) ?
Cause to me it seems, that in your case it not only fails to build vboxsf.
Also, could you post the output of 'lsmod|grep vbox', 'modprobe vboxsf' and 'dmesg |grep vboxsf', respectively?
Finally found the root cause. It's not kernel 4.19.13+ that solves the problem, it's the kernel-devel package that supplies the necessary symbols.
What misled me was that I must have installed it together with the kernel-4.19.13 update and rechecking with the old 4.19.12 (which didn't get a kernel-devel because it was already installed) of course showed the problem again. Moreover the other modules (vboxguest,vboxvideo) build perfectly without it, and even for vboxsf this used to work without it in older times.
So to sum up for Fedora 'dnf install kernel-devel' and for RHEL/CentOS a 'yum install kernel-devel' is the fix.
For the various other threads with similar problems for other distros like Kali/Debian (e.g. viewtopic.php?f=3&t=91340 or viewtopic.php?f=3&t=91325), pls. find the appropriate package names on your own.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
The key here is that the version of the -devel package (or -headers in some OSs) must match the version of the running kernel. In the RHEL/CentOS land, what occasionally happens is that the user is running an earlier version of the kernel but 'yum install' finds the latest version of kernel-devel. This causes a mismatch in the version, which leads to the failure of module building.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.