VB 6.0.10 not working on Linux kernel 5.2.X (F30)

Discussions related to using VirtualBox on Linux hosts.
Post Reply
bgix
Posts: 1
Joined: 16. Aug 2019, 19:34

VB 6.0.10 not working on Linux kernel 5.2.X (F30)

Post by bgix »

The Fedora-30 distribution of Linux has upreved the kernel to 5.2.7 (and beyond) and I can no longer get VirtualBox 6.0.10 to work.
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
         available for the current kernel (5.2.7-200.fc30.x86_64) 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.
When running vboxconfig:
% sudo /sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: You must sign these kernel modules before using VirtualBox:
  vboxdrv vboxnetflt vboxnetadp vboxpci
See the documenatation for your Linux distribution..
I have tried various methods of "Signing" these modules, but I am not sure if I just don't have the permissions to do so, or what.

Has anyone else seen this yet? Can you point me towards a primer for this?
fabiog1901
Posts: 1
Joined: 21. Aug 2019, 18:10

Re: VB 6.0.10 not working on Linux kernel 5.2.X (F30)

Post by fabiog1901 »

Similar issue, I'm also on Fedora 30 with Secure Boot (I have dual boot installation with Win10). I have the same outcome:

Code: Select all

root@localhost: /lib/modules # /sbin/vboxconfig 
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: You must sign these kernel modules before using VirtualBox:
  vboxdrv vboxnetflt vboxnetadp vboxpci
See the documenatation for your Linux distribution..
I think I know how to sign modules with keys as I've done it with Centos7, however, in this case with Fedora 30, I can't find the modules!

Code: Select all

root@localhost: /lib/modules # find . -name "*vbox*"
./5.2.8-200.fc30.x86_64/kernel/drivers/virt/vboxguest
./5.2.8-200.fc30.x86_64/kernel/drivers/virt/vboxguest/vboxguest.ko.xz
./5.2.8-200.fc30.x86_64/kernel/drivers/gpu/drm/vboxvideo
./5.2.8-200.fc30.x86_64/kernel/drivers/gpu/drm/vboxvideo/vboxvideo.ko.xz
./5.0.9-301.fc30.x86_64/kernel/drivers/virt/vboxguest
./5.0.9-301.fc30.x86_64/kernel/drivers/virt/vboxguest/vboxguest.ko.xz
./5.0.9-301.fc30.x86_64/kernel/drivers/staging/vboxvideo
./5.0.9-301.fc30.x86_64/kernel/drivers/staging/vboxvideo/vboxvideo.ko.xz
./5.2.9-200.fc30.x86_64/kernel/drivers/virt/vboxguest
./5.2.9-200.fc30.x86_64/kernel/drivers/virt/vboxguest/vboxguest.ko.xz
./5.2.9-200.fc30.x86_64/kernel/drivers/gpu/drm/vboxvideo
./5.2.9-200.fc30.x86_64/kernel/drivers/gpu/drm/vboxvideo/vboxvideo.ko.xz
root@localhost: /lib/modules # 
root@localhost: /lib/modules # 
root@localhost: /lib/modules # 
root@localhost: /lib/modules # modinfo vboxdrv
modinfo: ERROR: Module vboxdrv not found.
Am I missing something? I can't find them! might be worth noticing that the rpm name is

Code: Select all

VirtualBox-6.0-6.0.10_132072_fedora29-1.x86_64
- that is - fedora29 not fedora30
PeterChastain
Posts: 5
Joined: 24. Sep 2019, 01:47

Re: VB 6.0.10 not working on Linux kernel 5.2.X (F30)

Post by PeterChastain »

we also face this challenge, can someone please help?
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: VB 6.0.10 not working on Linux kernel 5.2.X (F30)

Post by socratis »

PeterChastain,
Not with so few details. We need your exact "uname -a" and the VirtualBox version used.

If you want to use the latest version for your host/guests, you should also consider doing the same for VirtualBox. Download the latest VirtualBox. As of this writing, that would be version 6.0.12. If that doesn't work you should try the latest test builds.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
PeterChastain
Posts: 5
Joined: 24. Sep 2019, 01:47

Re: VB 6.0.10 not working on Linux kernel 5.2.X (F30)

Post by PeterChastain »

Thanks Socratis.
# uname -a
Linux localhost.localdomain 4.14.35-1818.3.3.el7uek.x86_64 #2 SMP Mon Sep 24 14:45:01 PDT 2018 x86_64 x86_64 x86_64 GNU/Linux

# yum info VirtualBox-6.0
Loaded plugins: langpacks, ulninfo
Installed Packages
Name        : VirtualBox-6.0
Arch        : x86_64
Version     : 6.0.13_133347_el7
I've tried everything.
Here is the error, though I already have all those packages (and more) installed:
# /sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
    kernel-uek-devel kernel-uek-devel-4.14.35-1818.3.3.el7uek.x86_64
Anything you can do to help would be greatly appreciated.
I thought this would be easy :^)
Just standard OEL7 and VirtualBox installs...

Thanks much.
Last edited by socratis on 25. Sep 2019, 02:54, edited 1 time in total.
Reason: Enclosed the information in [quote][pre] tags for better readability
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: VB 6.0.10 not working on Linux kernel 5.2.X (F30)

Post by socratis »

First of all, you're not facing the same issue.
PeterChastain wrote:
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
The error is pretty clear, don't you think? Read carefully the error message. Do as the error message says and get the matching headers for your kernel. Something like:
  • yum install kernel-headers-$(uname -r) kernel-devel-$(uname -r)
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
PeterChastain
Posts: 5
Joined: 24. Sep 2019, 01:47

Re: VB 6.0.10 not working on Linux kernel 5.2.X (F30)

Post by PeterChastain »

I think I have a mismatch in the versions of those two packages and the kernel. I'll try including the "uname -r" as you suggest. Thanks. It's non-obvious that the versions must match, if that's the solution. I definitely already tried installing those two packages (yes, the error message is clear, to that level at least). I'll let you know if that works. Thanks again.
PS I originally had the same unsigned error, but then disabled secure boot, for now at least. Signing the kernel drivers appears to be quite complicated.
PeterChastain
Posts: 5
Joined: 24. Sep 2019, 01:47

Re: VB 6.0.10 not working on Linux kernel 5.2.X (F30)

Post by PeterChastain »

Again, Socratis thank you for the help, very much appreciated.

You helped me realize for sure the kernel releases need to / should match, and ideally also the versions.
I had kernel-headers installed, though VirtualBox clearly depends on kernel-uek-headers (at least for the uek kernel).
It's weird, kernel-uek-devel is available in the latest oeluek release, but not kernel-uek-headers.
But not weird, as everybody seems to think kernel-uek-header is obsolete.
So then why does vbox depend on it?
The latest kernel-uek-headers version I could find was 1-3.el6.x86_64 !
So I installed that and then vbox was able to build the kernel modules.

I can't imagine this is anything but a Vbox bug. It's clearly relying on an obsolete package, see:
# yum info kernel-uek-headers.x86_64
Loaded plugins: langpacks, ulninfo
Installed Packages
Name        : kernel-uek-headers
Arch        : x86_64
Epoch       : 2
Version     : 1
Release     : 3.el6
Size        : 0.0  
Repo        : installed
From repo   : /kernel-uek-headers-1-3.el6.x86_64
Summary     : Obsolete UEK headers for the Linux kernel for use by glibc
License     : GPLv2
Description : Obsolete header files for the Linux kernel for use by glibc.
            : Use kernel-headers instead.
Well, I guess anything Linux is "not for the faint of heart" as they say.

To answer your question:
"The error is pretty clear, don't you think?"
I think it could be clearer, but apparently I threw a wrench in with UEK.
Though again thank you very much, you got me headed in the correct direction when I was about to give up and drop back to OEL6.

Thanks again and best regards.
Last edited by socratis on 25. Sep 2019, 08:45, edited 1 time in total.
Reason: Enclosed the information in [quote][pre] tags for better readability
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: VB 6.0.10 not working on Linux kernel 5.2.X (F30)

Post by socratis »

PeterChastain wrote:So then why does vbox depend on it?
VirtualBox needs to compile during installation the kernel modules. This requires the matching kernel headers for the currently running kernel. It's up to you to make sure that they match. If the current kernel is obsolete, then you got to figure out what's broken.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
PeterChastain
Posts: 5
Joined: 24. Sep 2019, 01:47

Re: VB 6.0.10 not working on Linux kernel 5.2.X (F30)

Post by PeterChastain »

Thanks again, very much appreciated.
Post Reply