Modules for Kernel 4.14 don't compile -> fixed in 5.2 releases after November 18 2017

[joeAverage]

vbox modules for kernel 4.14.0-rc8 don't compile

see attached vbox-install.log

[joeAverage]

module compile log

[joeAverage]

some remarks: I'm running Fedora 27 with gcc version 7.2.1 if this matters.

today I tried with new released Kernel 4.14 and found out I have to correct this bug report to: not all vbox modules for kernel 4.14 compile

Why ?

sudo systemctl restart vboxdrv.service outputs

Job for vboxdrv.service failed because the control process exited with error code. ...

but lsmod reveals that one module "vboxdrv" was compiled and loaded. vbox-install.log stays empty doing so.

means: vboxpci, vboxnetadp, vboxnetflt weren't compiled.

a VM (windows 7) runs anyhow with this single module "vboxdrv"

So only if I run sudo vboxconfig I get the attached vbox-install.log and none vbox module gets compiled, not even vboxdrv !

[michael]

This is already fixed in our subversion repository and in the current test builds. I am pretty sure there is a duplicate of this but no time to check just now.

[joeAverage]

yup, thanks for quick suppurt !

for the record:

"Development snapshots" did the job. "Latest 5.1.x test builds" didn't.

[hgf_m]

fyi,

development snapshot VirtualBox-5.2.1-119001 failed

dmesg vboxpci: Unknown symbol vfs_write (err 0) - the other modules are loaded

Leap 42.3 with kernel 4.14.0-1.gab9e909-default on GA-J3455-D3H

[hgf_m]

fyi,

sorry I did not notice

virtualbox-VirtualBox-5.2.1-119001 is running

ssh connections ok &  rdp:// is working  http:// &  https:// are failing

let me know if you need addition informations

thanks

[joeAverage]

well, spoke to soon. I vboxpci doesn't get build with 5.2.1-119001. some error as in coment #4.

VB runs anyhow

[kaputtzich]

Problem is also discussed here  https://github.com/manjaro/packages-core/issues/86 If files are patched with  https://github.com/manjaro/packages-extra/tree/master/linux414-extramodules/virtualbox-modules it's working. Tested with 5.2.1-119001 but had to remove vboxnetflt part in linux-4.14-host.patch Didn't tried with stable 5.2.0-118431

[Vasya V. Pupkin]

I confirm that current stable version in 5.2 branch can't build it's modules against 4.14.0 kernel headers. I see following errors:

/tmp/vbox.0/linux/VBoxNetFlt-linux.c: In function ‘vboxNetFltLinuxSkBufFromSG’:
/tmp/vbox.0/linux/VBoxNetFlt-linux.c:741:24: error: ‘SKB_GSO_UDP’ undeclared (first use in this function)
             fGsoType = SKB_GSO_UDP;
                        ^~~~~~~~~~~
/tmp/vbox.0/linux/VBoxNetFlt-linux.c:741:24: note: each undeclared identifier is reported only once for each function it appears in
In file included from /tmp/vbox.0/include/iprt/types.h:29:0,
                 from /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:34,
                 from /tmp/vbox.0/linux/VBoxNetFlt-linux.c:24:
/tmp/vbox.0/linux/VBoxNetFlt-linux.c: In function ‘vboxNetFltLinuxCanForwardAsGso’:
/tmp/vbox.0/linux/VBoxNetFlt-linux.c:1276:53: error: ‘SKB_GSO_UDP’ undeclared (first use in this function)
     if (RT_UNLIKELY( skb_shinfo(pSkb)->gso_type & ~(SKB_GSO_UDP | SKB_GSO_DODGY | SKB_GSO_TCPV6 | SKB_GSO_TCPV4) ))
                                                     ^
/tmp/vbox.0/include/iprt/cdefs.h:1631:53: note: in definition of macro ‘RT_UNLIKELY’
 #  define RT_UNLIKELY(expr)     __builtin_expect(!!(expr), 0)
                                                     ^~~~
/tmp/vbox.0/linux/VBoxNetFlt-linux.c: In function ‘vboxNetFltLinuxForwardToIntNetInner’:
/tmp/vbox.0/linux/VBoxNetFlt-linux.c:1526:47: error: ‘SKB_GSO_UDP’ undeclared (first use in this function)
         if (   (skb_shinfo(pBuf)->gso_type & (SKB_GSO_UDP | SKB_GSO_TCPV6 | SKB_GSO_TCPV4))
                                               ^~~~~~~~~~~
scripts/Makefile.build:314: recipe for target '/tmp/vbox.0/linux/VBoxNetFlt-linux.o' failed
make[2]: *** [/tmp/vbox.0/linux/VBoxNetFlt-linux.o] Error 1
Makefile:1509: recipe for target '_module_/tmp/vbox.0' failed
make[1]: *** [_module_/tmp/vbox.0] Error 2
/tmp/vbox.0/Makefile.include.footer:97: recipe for target 'vboxnetflt' failed
make: *** [vboxnetflt] Error 2

Dear Oracle, can you please fix this? Kernel 4.14 was released more than a week ago.

[joeAverage]

... tried patch from comment #7 with stable 5.2.0-118431

all modules (vboxdrv,vboxnetadp,vboxnetflt,vboxpci) were build !

THX @kaputtzich

[michael]

All errors mentioned above should be fixed as of revision 119148/public r69744.

[hgf_m]

virtualbox-VirtualBox-5.2.1-119001 is running correctly with r69744

[joeAverage]

@hgf_m

are you sure ?

5.2.1-119001 doesn't carry the Changeset 69744, so vboxpci furthermore won't get build.

VirtualBox-5.2.1-119001 is running however, but without vboxpci ! please double check this.

Error: "vboxdrv.sh: failed: modprobe vboxpci failed. Please use 'dmesg' to find out why."

dmesg: "vboxpci: Unknown symbol vfs_write (err 0)"

[michael]

The current test builds should contain all fixes.

[barcoboy]

Running Slackware64-current with the latest patches as of today, including kernel 4.14.0. Installed VirtualBox-5.2.1-119163, and although all modules compiled successfully, I am unable to load the vboxdrv module, with the following dmesg message:

vboxdrv: Unknown symbol VBoxHost_RTStrCat (err 0)

[michael]

Please try again.

[michael]

I mean please try the latest test builds, which I updated after I saw your comment.

[barcoboy]

Thanks Michael... I found it. :-)

119176 modules compile and run great.

[joeAverage]

confirmed, 119176 fixed this bug !

THX for quick support !!!

[Vasya V. Pupkin]

All errors mentioned above should be fixed as of revision 119148/public r69744.

I don't see any updates in this repo:

deb  http://download.virtualbox.org/virtualbox/debian zesty contrib

Can you please push the update to your Debian/Ubuntu repos?

[michael]

We only publish test builds on the test build web page<1>. Sorry about that.

<1> https://www.virtualbox.org/wiki/Testbuilds

[hgf_m]

sorry joeAverage I'm late

I fixed the VBoxPci-linux.c as described in r69774 and all modules were compiled

after a restarted all modules were loaded - and guests are running fine

I will try this afternoon version 119176

[Vasya V. Pupkin]

There should have been a release build by the time new kernel was released. I'm kinda disappointed with VirtualBox now. There were no such issues before. Now I can't use my VMs while running latest kernel for more than a week.

[hgf_m]

version VirtualBox-5.2.1-119176-Linux_amd64.run

all modules were compiled and loaded with Leap 42.3

running kernel 4.14.1-2.ga5bca71-default on on GA-J3455-D3H

[darkdragon]

It works by downloading the latest version 5.2.2 from the main webiste (.deb). Would be handy to have it in the repos though...

[tekstryder]

Is this fix also pushed to 5.1.x series? Can we be assured kernel 4.14.x will be supported in the next (5.1.32) maintenance release?