VirtualBox install has problems

[drzin69@gmail.com]

I have dealt with this issue on every system I have worked on. When something that should be so simple should be fixed. I have been dealing with this issue for years. I have even had Chatgpt try to fix it, and it can't. I do even know what to post about this issue.

Code: Select all

]$ journalctl -xeu vboxdrv.service
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit vboxdrv.service has begun execution.
░░ 
░░ The job identifier is 7630.
Apr 25 11:02:52 fedora modprobe[23231]: modprobe: ERROR: could not insert 'vboxdrv': Key was rejected by service
Apr 25 11:02:52 fedora systemd[1]: vboxdrv.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit vboxdrv.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 25 11:02:52 fedora systemd[1]: vboxdrv.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit vboxdrv.service has entered the 'failed' state with result 'exit-code'.
Apr 25 11:02:52 fedora systemd[1]: Failed to start vboxdrv.service - Linux kernel module init script.
░░ Subject: A start job for unit vboxdrv.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit vboxdrv.service has finished with a failure.
░░ 
░░ The job identifier is 7630 and the job result is failed.
Apr 25 11:29:14 fedora systemd[1]: Starting vboxdrv.service - Linux kernel module init script...
░░ Subject: A start job for unit vboxdrv.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit vboxdrv.service has begun execution.
░░ 
░░ The job identifier is 7964.
Apr 25 11:29:14 fedora modprobe[24328]: modprobe: ERROR: could not insert 'vboxdrv': Key was rejected by service
Apr 25 11:29:14 fedora systemd[1]: vboxdrv.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit vboxdrv.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 25 11:29:14 fedora systemd[1]: vboxdrv.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit vboxdrv.service has entered the 'failed' state with result 'exit-code'.
Apr 25 11:29:14 fedora systemd[1]: Failed to start vboxdrv.service - Linux kernel module init script.
░░ Subject: A start job for unit vboxdrv.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit vboxdrv.service has finished with a failure.
░░ 
░░ The job identifier is 7964 and the job result is failed.
lines 241-300/300 (END)

[scottgus1]

Installing Virtualbox on Linux is a bit out there, because there's so many distros doing their own thing.

Per https://www.virtualbox.org/manual/ch02. ... nux-prereq there are prerequisites to install official Virtualbox from https://www.virtualbox.org/wiki/Linux_Downloads. (We don't support the forks of Virtualbox that the distros put in their repo's, stuff has been changed in the forks. Roughly speaking, if anything in error messages mentions something about dkms, then you're using the fork; official Virtualbox doesn't use dkms.)

The prerequisites usually boil down to installing the distro's kernel headers.

Also, brand-new kernels require brand-new Virtualbox, and sometimes the devs need to tweak things when a new kernel comes out.

See if any of this can help you (I'm no Linux guru so this is all Greek to me). If you have any trouble, please report exactly what you did and what happened in response. A forum Linux guru may be able to help.

Edit: I write the above based in the concept of the Virtualbox "install" having problems. If something in the error message pertains to a problem after Virtualbox has been installed and is running VMs OK, then it did not stand out to me. Please make the problem more explicit so it can be diagnosed.