Hai All,
I tried again to install virtual box from official website(https://download.virtualbox.org/virtualbox/rpm/fedora/36/x86_64/. )
In fedora 35 virtual box installed from official site is working well. Since I upgraded to fedora 36 virtualbox won’t works. but in the last tried the error message is different, now virtualbox can install in fedora 36 but won’t run because failed building kernel module?
How to solve this problem? because I want use vagrant with virtualbox.
I don’t enable secure boot in BIOS.
uname -r
5.18.5-200.fc36.x86_64
systemctl status vboxdrv
× vboxdrv.service - VirtualBox Linux kernel module
Loaded: loaded (/usr/lib/virtualbox/vboxdrv.sh; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2022-06-21 15:35:18 WIB; 2min 29s ago
Process: 792 ExecStart=/usr/lib/virtualbox/vboxdrv.sh start (code=exited, status=1/FAILURE)
CPU: 5min 6.785s
Jun 21 15:32:53 fedora-linux systemd[1]: Starting vboxdrv.service - VirtualBox Linux kernel module...
Jun 21 15:32:57 fedora-linux vboxdrv.sh[792]: vboxdrv.sh: Starting VirtualBox services.
Jun 21 15:32:58 fedora-linux vboxdrv.sh[792]: vboxdrv.sh: Building VirtualBox kernel modules.
Jun 21 15:32:58 fedora-linux vboxdrv.sh[1056]: Building VirtualBox kernel modules.
Jun 21 15:35:18 fedora-linux vboxdrv.sh[792]: vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.
Jun 21 15:35:18 fedora-linux systemd[1]: vboxdrv.service: Control process exited, code=exited, status=1/FAILURE
Jun 21 15:35:18 fedora-linux systemd[1]: vboxdrv.service: Failed with result 'exit-code'.
Jun 21 15:35:18 fedora-linux systemd[1]: Failed to start vboxdrv.service - VirtualBox Linux kernel module.
Jun 21 15:35:18 fedora-linux systemd[1]: vboxdrv.service: Consumed 5min 6.785s CPU time.
[afiadi@fedora-linux ~]$ vboxmanage --version
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (5.18.5-200.fc36.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.
6.1.34r150636
[afiadi@fedora-linux ~]$ sudo /sbin/vboxconfig
[sudo] password for afiadi:
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.
It seems virtualbox will not run with the 5.18 kernels on Fedora.I’m having the same issue.The work around seems to either download and install the test version from virtualbox or wait for a newer version to be released.
Indeed. To be clear, this isn’t a problem with Fedora itself, but Oracle needing to add support for newer kernel. Fedora doesn’t provide VirtualBox, itself, though RPMFusion packages the open source bits, and while it may not have all the same features as the PUEL version, it will likely have better testing/integration with Fedora in general and it’s less creepy.
I’m sorry bro, you wrong, you don’t need to do anything if your fedora system upgrade kernel. It’s just works like virtual box official in Fedira Linux 35. Look at my SS below:
In my SS before this SS above, I use kernel version 5.18.6-200, but in my SS above I already update my Fedora system to the lastest kernel, and Virtual box still running smoothly and properly.
I already said in this thread I don’t use secure boot enabled.
The problem is basically because secure boot requires VirtualBox kernel modules signed to run, you need to sign and compile. I found the solution here.
Also, y translate and put additional details in Spanish here: