/sbin/vboxconfig fails on Linux 5.4.8 and Mint 19.3

[realwuffi]

Hi all,
I installed the latest 5.4.8 Kernel using UKUU on Linux Mint 19.3.
I added the PPA for the latest Virtual Box 6.1 which has been installed before on a 5.3 kernel.

When I try to start Virtual Box I get the following message:
Kernel driver not installed (rc=-1908)

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.

The attached logfile contains similar error messages to threads I found in this forum.
But they all lead to the result that VB 6.1 should be used (which I have) where the bug Linux host and guest: Support Linux 5.4 (bug #18945) has been fixed.

So at the moment I don't know how to go on. Would be very happy if someone could give me a hand here.

Thanks
Wolfgang

[dacorsa]

same problem here:

UBUNTU 18.04 kernel installed with uuku (5.4.8) and virtualbox 6.1, module doesn't compile:
sudo /sbin/rcvboxdrv setup
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.

less /var/log/vbox-setup.log

./arch/x86/include/asm/bug.h:79:2: note: in expansion of macro ‘_BUG_FLAGS’
_BUG_FLAGS(ASM_UD2, BUGFLAG_WARNING|(flags)); \
^~~~~~~~~~
./include/asm-generic/bug.h:93:3: note: in expansion of macro ‘__WARN_FLAGS’
__WARN_FLAGS(BUGFLAG_NO_CUT_HERE | BUGFLAG_TAINT(taint));\
^~~~~~~~~~~~
./include/asm-generic/bug.h:124:3: note: in expansion of macro ‘__WARN_printf’
__WARN_printf(TAINT_WARN, format); \
^~~~~~~~~~~~~
./include/linux/debug_locks.h:31:4: note: in expansion of macro ‘WARN’
WARN(1, "DEBUG_LOCKS_WARN_ON(%s)", #c); \
^~~~
./arch/x86/include/asm/desc.h:329:2: note: in expansion of macro ‘DEBUG_LOCKS_WARN_ON’
DEBUG_LOCKS_WARN_ON(preemptible());
^~~~~~~~~~~~~~~~~~~
scripts/Makefile.build:265: recipe for target '/tmp/vbox.0/linux/SUPDrv-linux.o' failed
make[2]: *** [/tmp/vbox.0/linux/SUPDrv-linux.o] Error 1
make[2]: *** Attesa per i processi non terminati....
./tools/objtool/objtool check --module --retpoline --uaccess /tmp/vbox.0/SUPDrvGip.o
./tools/objtool/objtool check --module --retpoline --uaccess /tmp/vbox.0/SUPDrvTracer.o
/tmp/vbox.0/SUPDrvTracer.o: warning: objtool: .text+0x7: indirect jump found in RETPOLINE build
/tmp/vbox.0/SUPDrvTracer.o: warning: objtool: supdrvTracerProbeFireStub() is missing an ELF size annotation
./tools/objtool/objtool check --module --retpoline --uaccess /tmp/vbox.0/SUPDrv.o
Makefile:1652: recipe for target '/tmp/vbox.0' failed
make[1]: *** [/tmp/vbox.0] Error 2
/tmp/vbox.0/Makefile-footer.gmk:114: recipe for target 'vboxdrv' failed
make: *** [vboxdrv] Error 2

How can i solve?

best regards

[Wheaties]

I just ran into the same problem with the 5.4.7 kernel on the host. The host is Fedora 30. Virtualbox is 6.0.14

Matt

[Michael Couture]

I just ran into this issue as well. Running Mint 19.3 host and just updated to kernel 5.4.9 ....VBox won't compile so I had to back down to a pre-5.4 kernel.

[Wheaties]

It's been a week, but I was finally able to move over to a laptop running Fedora 31 that isn't as critical as the one where I found the problem. This is a Fedora 31 system running kernel 5.4.8. I should add that there is no problem if I boot the host into an older (5.3.16-300) kernel.
Running /sbin/vboxconfig I get the following output:

/sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
depmod: WARNING: could not open modules.order at /lib/modules/5.3.13-300.fc31.x86_64: No such file or directory
depmod: WARNING: could not open modules.builtin at /lib/modules/5.3.13-300.fc31.x86_64: No such file or directory
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.

[Wheaties]

Why is it looking for the 5.3.13-300 module if it's on the 5.4,8 kernel?

[marschall]

Why is it looking for the 5.3.13-300 module if it's on the 5.4,8 kernel?

Good question!

My error is the folowing:

Code: Select all   Expand viewCollapse view

Error building the module:
make V=1 CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/5.4.11-050411-generic/build M=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j4 modules
make[1]: warning: -jN forced in submake: disabling jobserver mode.
make -f ./scripts/Makefile.build obj=/tmp/vbox.0 single-build= need-builtin=1 need-modorder=1
  gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPDrv-linux.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/7/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/$
  gcc -Wp,-MD,/tmp/vbox.0/.SUPDrv.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/7/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi$
  gcc -Wp,-MD,/tmp/vbox.0/.SUPDrvGip.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/7/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/u$
  gcc -Wp,-MD,/tmp/vbox.0/.SUPDrvSem.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/7/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/u$
In file included from <command-line>:0:0:
./arch/x86/include/asm/page_64.h: In function ‘clear_page’:
././include/linux/compiler_types.h:210:24: error: expected ‘(’ before ‘__inline’

[Wheaties]

Okay, I have a solution for Fedora users:

For what it's worth, there is a new package of VirtualBox out there, VirtualBox-6.1 that fixes the starting issues with the 5.4.* kernel on the host. The install tool for Fedora (dnf) does not recognize it as the natural successor to VirtualBox-6.0 for some reason. You need to uninstall VirtualBox-6.0 and install VirtualBox-6.1

Once you've done that, all seems back to normal.

Matt

[Wheaties]

https://www.tecrobust.com/virtualbox-6- ... acle-team/

[dacorsa]

and for ubuntu ?? no solution?

booo

[myname1st]

Wasn't sure if I should make a different post for Ubuntu, but the rules say to answer on an existing post if it seems to be the same?

Anyway, I have been having this issues with all the 5.4.x kernel versions.
I just updated to VirtualBox 6.1.2 which was released yesterday, and I am currently on kernel 5.4.11, running on Ubuntu 18.04.3. The changelog says that it included support for 5.4 and 5.5, but no luck.
I have uninstalled and installed virtualbox and yes, I have all the headers.

I am attaching the log to see if it would help any of the devs. Please note that if I boot in 5.3.x (currently 5.3.18), there is no problem. It is only happening in the 5.4s.

THANK YOU in advance and please let me know if any other data is needed

PS: Kernels downloaded from kernel repo and VBox from the virtualbox page. So nothing is compiled from scratch.

[kinghat]

im also having issues with vbox on kernel 5.4(.12). updated to 6.1.2 today as well. i posted my log after running: sudo /sbin/vboxconfig like it told me.



not sure why the image tag isnt working but here are the errors in image: https://irc.kinghat.info/uploads/e7736f55c8e9a77a/image.png
and here is the link to log: https://paste.debian.net/hidden/eb9eb7bd/

[TerribleZ]

I have exactly the same problem with any 6.x version of virtualbox on
mint 19.3 kernel 5.4.12
Tried all 5.4 kernels none work

5.3.18 and lower work no problem

[scottgus1]

Has anyone here tried the Bugtracker?

Fixing this is quite beyond my Windows-guy capability, but the devs tend to hang out with the bugs, so they may not know.

[kinghat]

so this is a problem with Ukuu installing the kernels:

https://www.virtualbox.org/ticket/19209#comment:6
https://www.virtualbox.org/ticket/19244#comment:2

does anyone know how to fix the ukuu kernel install?