VirtualBox Kernel Module no longer builds under -current kernel update of 17-Nov-2017

statguy · 11-17-2017, 01:17 PM

I just updated my kernel today but now the VirtualBox kernel module no longer builds. This affects 5.1.30 and 5.2.0 (at least).

The last messages in the log file are here:

Code:

/tmp/vbox.0/linux/VBoxNetFlt-linux.c:741:24: error: ‘SKB_GSO_UDP’ undeclared (first use in this function); did you mean ‘SKB_GSO_ESP’?
             fGsoType = SKB_GSO_UDP;
                        ^~~~~~~~~~~
                        SKB_GSO_ESP
/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); did you mean ‘SKB_GSO_ESP’?
     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); did you mean ‘SKB_GSO_ESP’?
         if (   (skb_shinfo(pBuf)->gso_type & (SKB_GSO_UDP | SKB_GSO_TCPV6 | SKB_GSO_TCPV4))
                                               ^~~~~~~~~~~
                                               SKB_GSO_ESP
make[2]: *** [scripts/Makefile.build:314: /tmp/vbox.0/linux/VBoxNetFlt-linux.o] Error 1
make[1]: *** [Makefile:1503: _module_/tmp/vbox.0] Error 2
make: *** [/tmp/vbox.0/Makefile.include.footer:97: vboxnetflt] Error 2

Any idea what is happening?

bassmadrigal · 11-17-2017, 01:35 PM

You can give the development snapshots for 5.2.1 a try. I could get it to build on my 14.2 system with the 4.14 kernel.

https://www.virtualbox.org/wiki/Testbuilds

statguy · 11-17-2017, 01:43 PM

Quote:

Originally Posted by bassmadrigal

You can give the development snapshots for 5.2.1 a try. I could get it to build on my 14.2 system with the 4.14 kernel.

https://www.virtualbox.org/wiki/Testbuilds

Thanks. I tried that and it compiled but there was an error on load. Here are the dmesg lines

Code:

[ 3811.889951] vboxdrv: loading out-of-tree module taints kernel.
[ 3811.894749] vboxdrv: Found 4 processor cores
[ 3811.910219] vboxdrv: TSC mode is Invariant, tentative frequency 2394456064 Hz
[ 3811.910221] vboxdrv: Successfully loaded version 5.2.1 (interface 0x00290000)
[ 3812.121024] VBoxNetFlt: Successfully started.
[ 3812.124343] VBoxNetAdp: Successfully started.
[ 3812.127311] vboxpci: Unknown symbol vfs_write (err 0)

ponce · 11-17-2017, 02:04 PM

you can also consider downgrading your kernel to a version supported by virtualbox.

Daedra · 11-17-2017, 02:36 PM

I can confirm problems with 5.2.0, but I was able to compile against 4.14/-current when I downgraded both virtualbox and addons to 5.1.30

statguy · 11-17-2017, 04:27 PM

Quote:

Originally Posted by Daedra

I can confirm problems with 5.2.0, but I was able to compile against 4.14/-current when I downgraded both virtualbox and addons to 5.1.30

On my installation, 5.1.30 did not compile. I got the same error as with 5.2.0.

bassmadrigal · 11-17-2017, 05:25 PM

Quote:

Originally Posted by statguy

Thanks. I tried that and it compiled but there was an error on load. Here are the dmesg lines

Code:

[ 3811.889951] vboxdrv: loading out-of-tree module taints kernel.
[ 3811.894749] vboxdrv: Found 4 processor cores
[ 3811.910219] vboxdrv: TSC mode is Invariant, tentative frequency 2394456064 Hz
[ 3811.910221] vboxdrv: Successfully loaded version 5.2.1 (interface 0x00290000)
[ 3812.121024] VBoxNetFlt: Successfully started.
[ 3812.124343] VBoxNetAdp: Successfully started.
[ 3812.127311] vboxpci: Unknown symbol vfs_write (err 0)

AFAIK, vboxpci is not required for VirtualBox to work. It seems to work on my computer with the same error. It might just prevent passthrough (if that's what it's used for).

upnort · 11-17-2017, 05:55 PM

I haven't compiled VB in Current, but today I successfully installed the 5.1.30 GA in Current after updating to the 4.14 kernel.

brobr · 11-17-2017, 06:25 PM

The version on www.virtualbox.org/wiki/Testbuilds is now VirtualBox 5.1.31 and that compiled fine on current with kernel 4.14.0 (incl guest additions and extension pack)

statguy · 11-17-2017, 07:03 PM

Quote:

Originally Posted by brobr

The version on www.virtualbox.org/wiki/Testbuilds is now VirtualBox 5.1.31 and that compiled fine on current with kernel 4.14.0 (incl guest additions and extension pack)

I get the same error in dmesg from vboxpci.

To the other poster, who said it would run without, in my case, my Win7 virtual machine will not start.

statguy · 11-17-2017, 08:02 PM

Quote:

Originally Posted by statguy

I get the same error in dmesg from vboxpci.

To the other poster, who said it would run without, in my case, my Win7 virtual machine will not start.

Correction. When I installed the 5.1.31 guest extensions the virtual machine started. This may mean the 5.2.1 version would have worked if I had done that (though I though I had).

Bottom line -- up and running.

Thanks for all the advice.

willysr · 11-17-2017, 08:25 PM

I have a working patch here https://github.com/willysr/SlackHack...box/5.2.0/4.14

frankbell · 11-17-2017, 09:15 PM

Wow! willysr, that was quick.

I look forward to trying it when I get a chance.

1337_powerslacker · 11-17-2017, 09:53 PM

Quote:

Originally Posted by willysr

I have a working patch here https://github.com/willysr/SlackHack...box/5.2.0/4.14

I have tried it, and it works marvelously. Thanks, Willy!

brobr · 11-18-2017, 05:12 PM

Ok, I checked dmesg and also had the vboxpci symbol not found error:

Code:

bash-4.4$ dmesg | grep vboxpci
[   29.387902] vboxpci: Unknown symbol vfs_write (err 0)
bash-4.4$ sudo dmesg | grep vbox
[   29.164508] vboxdrv: loading out-of-tree module taints kernel.
[   29.167423] vboxdrv: Found 8 processor cores
[   29.183188] vboxdrv: TSC mode is Invariant, tentative frequency 2807999980 Hz
[   29.183188] vboxdrv: Successfully loaded version 5.1.31 (interface 0x002a0000)
[   29.387902] vboxpci: Unknown symbol vfs_write (err 0)

Then only applied this part of Willy's patch changing vfs_write (the changes for /vboxnetflt/linux/VBoxNetFlt-linux.c did not need to be made for 5.1.31)

Quote:

diff -Npur a/vboxpci/linux/VBoxPci-linux.c b/vboxpci/linux/VBoxPci-linux.c
--- a/vboxpci/linux/VBoxPci-linux.c 2017-10-27 15:43:49.927830000 -0400
+++ b/vboxpci/linux/VBoxPci-linux.c 2017-10-28 08:23:54.946946774 -0400
@@ -357,7 +357,7 @@ static int vboxPciFileWrite(struct file*

fs_save = get_fs();
set_fs(get_ds());
- ret = vfs_write(file, data, size, &offset);
+ ret = kernel_write(file, data, size, &offset);
set_fs(fs_save);
if (ret < 0)
printk(KERN_DEBUG "vboxPciFileWrite: error %d\n", ret);

rerun setup and checked dmesg again:

Code:

bash-4.4$ /etc/init.d/vboxdrv setup
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.

bash-4.4$ dmesg | grep vboxpci
[28288.373195] vboxdrv: Found 8 processor cores
[28288.389318] vboxdrv: TSC mode is Invariant, tentative frequency 2808000074 Hz
[28288.389319] vboxdrv: Successfully loaded version 5.1.31 (interface 0x002a0000)
[28288.600171] vboxpci: IOMMU not found (not registered)
[28295.540547] vboxdrv: ffffffffc0d27020 VMMR0.r0
[28295.619362] vboxdrv: ffffffffc0988020 VBoxDDR0.r0

HTH