Page 1 of 2

Updated kernel => VirtualBox not working!

Posted: 3. Oct 2017, 18:22
by k07
I have been using OpenSUSE Leap 42.3 with Linux kernel 4.4 and everything seemed to work, but after updating the kernel to 4.14 VirtualBox refuses to open any VMs.
/sbin/vboxconfig doesn't work either.
How can I make VirtualBox find the new version of the kernel?

Kernel:

Code: Select all

uname -r
4.14.0-rc2-1.gb61ed0c-default
System:

Code: Select all

uname -a
Linux linux-xz3t 4.14.0-rc2-1.gb61ed0c-default #1 SMP PREEMPT Thu Sep 28 09:33:26 UTC 2017 (b61ed0c) x86_64 x86_64 x86_64 GNU/Linux
VirtualBox version:

Code: Select all

Version 5.1.28 r117968 (Qt5.6.2)
/sbin/vboxconfig output:

Code: Select all

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
                                                                                                                                      
There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.
/var/log/vbox-install.log output:

Code: Select all

make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /lib/modules/4.14.0-rc2-1.gb61ed0c-default/build -j4 modules
make[1]: warning: -jN forced in submake: disabling jobserver mode.
make -C /usr/src/linux-4.14.0-rc2-1.gb61ed0c-obj/x86_64/default KBUILD_SRC=/usr/src/linux-4.14.0-rc2-1.gb61ed0c \
-f /usr/src/linux-4.14.0-rc2-1.gb61ed0c/Makefile modules
/usr/src/linux-4.14.0-rc2-1.gb61ed0c/Makefile:946: "Cannot use CONFIG_STACK_VALIDATION, please install libelf-dev, libelf-devel or elfutils-libel$
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (                \
echo >&2;                                                       \
echo >&2 "  ERROR: Kernel configuration is invalid.";           \
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";      \
echo >&2 ;                                                      \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f /usr/src/linux-4.14.0-rc2-1.gb61ed0c/scripts/Makefile.build obj=/tmp/vbox.0
followed by 200 lines of gcc messages, then

Code: Select all

/tmp/vbox.0/linux/VBoxNetFlt-linux.c: In function ‘vboxNetFltLinuxSkBufFromSG’:
/tmp/vbox.0/linux/VBoxNetFlt-linux.c:726:24: error: ‘SKB_GSO_UDP’ undeclared (first use in this function)
             fGsoType = SKB_GSO_UDP;
                        ^
/tmp/vbox.0/linux/VBoxNetFlt-linux.c:726: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:1112: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:1612: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 ‘vboxNetFltLinuxForwardToIntNet’:
/tmp/vbox.0/linux/VBoxNetFlt-linux.c:1405: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))
                                               ^
/usr/src/linux-4.14.0-rc2-1.gb61ed0c/scripts/Makefile.build:312: recipe for target '/tmp/vbox.0/linux/VBoxNetFlt-linux.o' failed

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:1112: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:1612: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 ‘vboxNetFltLinuxForwardToIntNet’:
/tmp/vbox.0/linux/VBoxNetFlt-linux.c:1405: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))
                                               ^
/usr/src/linux-4.14.0-rc2-1.gb61ed0c/scripts/Makefile.build:312: recipe for target '/tmp/vbox.0/linux/VBoxNetFlt-linux.o' failed
make[4]: *** [/tmp/vbox.0/linux/VBoxNetFlt-linux.o] Error 1
/usr/src/linux-4.14.0-rc2-1.gb61ed0c/Makefile:1508: recipe for target '_module_/tmp/vbox.0' failed
make[3]: *** [_module_/tmp/vbox.0] Error 2
Makefile:145: recipe for target 'sub-make' failed
make[2]: *** [sub-make] Error 2
Makefile:24: recipe for target '__sub-make' failed
make[1]: *** [__sub-make] Error 2
Makefile:211: recipe for target 'vboxnetflt' failed
make: *** [vboxnetflt] Error 2


Re: Updated kernel => VirtualBox not working!

Posted: 3. Oct 2017, 19:24
by socratis
Try the test builds (https://www.virtualbox.org/wiki/Testbuilds) or 5.2.0_RC1 (http://download.virtualbox.org/virtualbox/5.2.0_RC1/). If I remember correctly they have fixed it. But I could be wrong, give it a try...

Re: Updated kernel => VirtualBox not working!

Posted: 3. Oct 2017, 20:37
by k07
Unfortunately, that didn't help.
Even after removing v5.1 and installing 5.2, I get the same error messages:

Code: Select all

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/sbin/vboxconfig'

as root.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. 
and:

Code: Select all

The virtual machine 'ubuntu16' has terminated unexpectedly during startup with exit code 1 (0x1).


Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {f50b24f0-0956-453c-d14c-8c27c683c295}

Re: Updated kernel => VirtualBox not working!

Posted: 3. Oct 2017, 20:38
by k07
/var/log/vbox-install.log output stays the same.

Re: Updated kernel => VirtualBox not working!

Posted: 3. Oct 2017, 21:48
by socratis
How old is the 4.14.0-rc2-1 kernel? Maybe the VirtualBox developers didn't have time to update VirtualBox to address some incompatibilities? So, either you'll have to wait for them to cover it, or downgrade?

Re: Updated kernel => VirtualBox not working!

Posted: 4. Oct 2017, 18:13
by k07
Thanks for the idea!
Turns out that 4.14 is the latest kernel, and it doesn't have a stable or long-term release.
Now, if I have multiple kernels installed (4.4 is still there), how I can I configure VirtualBox so that it uses one of the older kernels?

Re: Updated kernel => VirtualBox not working!

Posted: 4. Oct 2017, 18:27
by towo2099
how I can I configure VirtualBox so that it uses one of the older kernels?
Boot that older kernel!

Re: Updated kernel => VirtualBox not working!

Posted: 8. Oct 2017, 22:49
by k07
After downgrading back to VirtualBox 5.1 (didn't work with v.5.2), I have booted the older kernel (4.4) and everything works!

Many thanks.

Re: Updated kernel => VirtualBox not working!

Posted: 30. Oct 2017, 20:01
by burdi01
Slackware64 Current -- kernel 4.14-rc7 -- VB 5.2.0-118431-Linux_amd64.run fails to install.
Also the VB 5.2.1-118468-Linux_amd64.run test build fails to install.
5.2.1-118468 install log attached.

This is the first time I know of that late in the kernel development cycle installing VB fails.
Just reporting, not demanding ...
:D

Re: Updated kernel => VirtualBox not working!

Posted: 2. Nov 2017, 16:43
by burdi01
Slackware64 Current -- kernel 4.14-rc7 : Whereas installing the VB 5.2.1-118468-Linux_amd64.run test build failed downright (see my previous post), gave installing the the VB 5.2.1-118893-Linux_amd64.run test build only a warning: vboxdrv.sh: failed: modprobe vboxpci failed.
Running VB is successful and preliminary testing (running live CD's) does not reveal glaringly missing functionality.
:D

Re: Updated kernel => VirtualBox not working!

Posted: 2. Nov 2017, 16:48
by socratis
Great, thanks for the feedback, I'm sure it will be appreciated by the developers. Although 4.14 is not even out yet, it's good to have a VirtualBox release that works with that kernel.

PS. Funny thing that you used the same emoticon for when it wasn't working, as well as when it was working... :D

Re: Updated kernel => VirtualBox not working!

Posted: 2. Nov 2017, 17:05
by burdi01
PS. Funny thing that you used the same emoticon for when it wasn't working, as well as when it was working... :D
Whatever happens one should always remain positive.
:mrgreen:

Re: Updated kernel => VirtualBox not working!

Posted: 13. Nov 2017, 00:32
by sixpack13

Re: Updated kernel => VirtualBox not working!

Posted: 20. Nov 2017, 17:13
by burdi01
Slackware64 Current -- kernel 4.14.0 : Whereas installing the VB 5.2.1-118893_through_119001-Linux_amd64.run test builds succeeded, though with the warning: "vboxdrv.sh: failed: modprobe vboxpci failed", installing the VB 5.2.1-119163-Linux_amd64.run test build fails again, now with the error "vboxdrv: Unknown symbol VBoxHost_RTStrCat (err 0)".
:mrgreen:

Re: Updated kernel => VirtualBox not working!

Posted: 21. Nov 2017, 15:12
by burdi01
Slackware64 Current -- kernel 4.14.0/4.14.1: This is to report that the VB 5.2.1-119176-Linux_amd64.run test build builds without errors/messages other than the "invalid kernel configuration" and boots correctly.
:mrgreen: