After upgrade to 19.10, Vbox failed

Asked by ealthuis

Yesterday 19.04 was upgraded to 19.10

Today I started Virtual Box and got the following messages:

The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing

'/sbin/vboxconfig'

as root.

If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.

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

THhe requirement to run that update is normal, as I have had that on every upgrade from one version to the next, it has never before failed to work.

There seem to be some bugs yet in 19.10???

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
ealthuis
Solved:
Last query:
Last reply:
Revision history for this message
ealthuis (ealthuis) said :
#1

Here are the results of running the above command:

ea@discovery:~$ sudo sbin/vboxconfig
[sudo] password for ea:
sudo: sbin/vboxconfig: command not found
ea@discovery:~$ sudo /sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.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. If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.
ea@discovery:~$

As far as I know this system is not running EFI Secure Boot

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#2

Did you read /var/log/vbox-setup.log?

Revision history for this message
ealthuis (ealthuis) said :
#3

Yes I did, the first two lines show an error, the last 13 also have errors, in between is a large volume of what is used for this compile:

Building the main VirtualBox module.
Error building the module:
make V=1 CONFIG_MODULE_SIG= -C /lib/modules/5.3.0-19-generic/build M=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j4 modules
make[1]: warning: -j4 forced in submake: resetting jobserver mode.
make -f ./scripts/Makefile.build obj=/tmp/vbox.0 need-modorder=1
  gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPDrv-linux.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/9/include

and the end:

DMODULE -DRT_WITHOUT_PRAGMA_ONCE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DSUPDRV_WITH_RELEASE_LOGGER -DVBOX_WITH_64_BITS_GUESTS -DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_AMD64 -DMODULE -DKBUILD_BASENAME='"rtStrFormatKernelAddress_r0drv_linux"' -DKBUILD_MODNAME='"vboxdrv"' -c -o /tmp/vbox.0/r0drv/linux/rtStrFormatKernelAddress-r0drv-linux.o /tmp/vbox.0/r0drv/linux/rtStrFormatKernelAddress-r0drv-linux.c
/tmp/vbox.0/r0drv/linux/mp-r0drv-linux.c: In function ‘VBoxHost_RTMpOnAll’:
/tmp/vbox.0/r0drv/linux/mp-r0drv-linux.c:287:18: error: void value not ignored as it ought to be
  287 | int rc = smp_call_function(rtmpLinuxAllWrapper, &Args, 0 /* wait */);
      | ^~~~~~~~~~~~~~~~~
/tmp/vbox.0/r0drv/linux/mp-r0drv-linux.c: In function ‘VBoxHost_RTMpOnOthers’:
/tmp/vbox.0/r0drv/linux/mp-r0drv-linux.c:341:8: error: void value not ignored as it ought to be
  341 | rc = smp_call_function(rtmpLinuxWrapper, &Args, 1 /* wait */);
      | ^
make[2]: *** [scripts/Makefile.build:290: /tmp/vbox.0/r0drv/linux/mp-r0drv-linux.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:1653: _module_/tmp/vbox.0] Error 2
make: *** [/tmp/vbox.0/Makefile-footer.gmk:111: vboxdrv] Error 2

Revision history for this message
Manfred Hampl (m-hampl) said :
#4

Which version of VirtualBox are you running?
As far as I know the problem that you see is caused by differences between the v5.3 kernel compared to previous versions, and you need to have at least VirtualBox version 6.0.14 to cater for that.

Revision history for this message
ealthuis (ealthuis) said :
#5

According to VB I have the latest version: 6.0

It is all going back to the upgrade to 19.10. With Virtual Box I never had a problem after an upgrade, I would be told to recompile (as now) and a few minutes later everything worked again.

I think that I am faced with some BUG in the upgrade....

Revision history for this message
Manfred Hampl (m-hampl) said :
#6

There are sub-versions.

What is the output of the command
VBoxManage --version
?

You need at least 6.0.14

Revision history for this message
ealthuis (ealthuis) said :
#7

ea@discovery:~$ VBoxManage --version
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
         available for the current kernel (5.3.0-19-generic) or it failed to
         load. Please recompile the kernel module and install it by

           sudo /sbin/vboxconfig

         You will not be able to start VMs until this problem is fixed.
6.0.8r130520
ea@discovery:~$
 I will get 6.0.14 or higher

Well that's one done, one to go

This problem is solved

Revision history for this message
ealthuis (ealthuis) said :
#8

Thanks for your help