6

Running VirtualBox 6.1.12 r139181 on Fedora 32 and it is working fine. But after update to kernel 5.8.4-200.fc32.x86_64 on Fedora, I get the following error when trying to load a VM.

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.

7
  • How did you install VirtualBox?
    – rickhg12hs
    Commented Sep 1, 2020 at 9:28
  • After downloading it from the https://www.virtualbox.org/ and install it using sudo dnf install ./[PACKAGE NAME].rpm. Commented Sep 1, 2020 at 13:39
  • same problem. But it never worked with the previous kernel. I run the config, but the compile fails deep in the bellys. Looks like 6.1.12 was compiled against an older kernel and the headers changes too much
    – Torsten
    Commented Sep 1, 2020 at 15:38
  • Have you found any solution? Commented Sep 1, 2020 at 16:08
  • This VirtualBox Ticket may be of interest. It seems this is a known problem that is being worked on.
    – rickhg12hs
    Commented Sep 2, 2020 at 3:24

3 Answers 3

1

The issue is resolved in version 6.1.14 of VirtualBox.

2
  • 2
    For whoever needs to know, do systemctl restart vboxdrv after the upgrade, or reboot.
    – anlag
    Commented Sep 12, 2020 at 19:36
  • still have it on 6.1.22 but @anlag s trick did it.
    – cnstlungu
    Commented May 27, 2021 at 20:51
1
  1. Install some dependencies for vbox:

    sudo dnf install kernel-devel kernel-headers dkms qt5-qtx11extras  elfutils-libelf-devel zlib-devel
    

    If dnf is throwing some error like these packages are not found, then add the keys and try again.

    wget https://www.virtualbox.org/download/oracle_vbox.asc && \
    sudo rpm --import oracle_vbox.asc
    
  2. Execute /sbin/vboxconfig as root.

  3. Now try launching the VM.

1
  • AMAZING! Thx a lot :D
    – JsonKody
    Commented Mar 17, 2023 at 22:15
0

I found that by turning off UEFI Boot in the system BIOS solved the issue after running sudo /sbin/vboxconfig. This allowed VBOX to build the appropriate kernel modules.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .