VirtualBox broke down after upgrage F37 to F38
VirtualBox itself starts.
When try start virtual machine
got
Kernel driver not installed (rc=-1908)
At my both systems - Cinnamon and LXQt
You need to rebuild the kernel module (“Kernel driver”) for the newly installed fc38 kernel…
sudo dnf install make gcc dkms kernel-devel kernel-headers
sudo /sbin/vboxconfig
You will have reboot after that…
sudo dnf install make gcc dkms kernel-devel kernel-headers
only install dkms-3.0.10-3.fc38.noarch
everything else was already there
$ sudo /sbin/vboxconfig
sudo: /sbin/vboxconfig: command not found
$ sudo dnf search vboxconfig
Last metadata expiration check: 0:25:34 ago on Thu Apr 20 16:42:27 2023.
No matches found.
$
reboot w/o vboxconfig don’t help
Rpmfusion
ah, sorry, that’s different then. let’s undo the dkms install first: sudo dnf remove dkms, or sudo dnf history undo last. (the rpmfusion package uses akmods, not dkms to build the required kernel module).
run sudo dnf install kernel-devel-$(uname -r) akmod-VirtualBox VirtualBox, and show the output of
systemctl restart vboxdrv, and
systemctl status vboxdrv?
1 Like
sudo dnf install VirtualBox kernel-devel-$(uname -r) akmod-VirtualBox
Last metadata expiration check: 0:59:36 ago on Thu Apr 20 16:42:27 2023.
Package VirtualBox-7.0.6-1.fc38.x86_64 is already installed.
Package kernel-devel-6.2.11-300.fc38.x86_64 is already installed.
Package akmod-VirtualBox-7.0.6-1.fc38.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
[archer@DELLV ~]$ systemctl restart vboxdrv
Failed to restart vboxdrv.service: Access denied
See system logs and 'systemctl status vboxdrv.service' for details.
$ sudo systemctl restart vboxdrv
Job for vboxdrv.service failed because the control process exited with error code.
See "systemctl status vboxdrv.service" and "journalctl -xeu vboxdrv.service" for details.
$ sudo systemctl status vboxdrv
x vboxdrv.service - Linux kernel module init script
Loaded: loaded (/usr/lib/systemd/system/vboxdrv.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
`-10-timeout-abort.conf
Active: failed (Result: exit-code) since Thu 2023-04-20 17:43:23 EEST; 35s ago
Process: 4872 ExecStart=/sbin/modprobe vboxdrv (code=exited, status=1/FAILURE)
Main PID: 4872 (code=exited, status=1/FAILURE)
CPU: 5ms
Apr 20 17:43:23 DELLV systemd[1]: Starting vboxdrv.service - Linux kernel module init script...
Apr 20 17:43:23 DELLV modprobe[4872]: modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/6.2.11-300.fc38.x>
Apr 20 17:43:23 DELLV systemd[1]: vboxdrv.service: Main process exited, code=exited, status=1/FAILURE
Apr 20 17:43:23 DELLV systemd[1]: vboxdrv.service: Failed with result 'exit-code'.
Apr 20 17:43:23 DELLV systemd[1]: Failed to start vboxdrv.service - Linux kernel module init script.
[archer@DELLV ~]$ journalctl -xeu vboxdrv.service
Apr 20 17:43:23 DELLV modprobe[4872]: modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/6.2.11-300.fc38.x>
Apr 20 17:43:23 DELLV 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 20 17:43:23 DELLV 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 20 17:43:23 DELLV 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 3052 and the job result is failed.
[archer@DELLV ~]$
run sudo akmods, restart
$ sudo dnf install VirtualBox kernel-devel-$(uname -r) akmod-VirtualBox
[sudo] password for archer:
Last metadata expiration check: 1:11:15 ago on Thu Apr 20 16:42:27 2023.
Package VirtualBox-7.0.6-1.fc38.x86_64 is already installed.
Package kernel-devel-6.2.11-300.fc38.x86_64 is already installed.
Package akmod-VirtualBox-7.0.6-1.fc38.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
$ sudo akmods
Checking kmods exist for 6.2.11-300.fc38.x86_64 [ OK ]
reboot
The same 
$ sudo systemctl status vboxdrv
× vboxdrv.service - Linux kernel module init script
Loaded: loaded (/usr/lib/systemd/system/vboxdrv.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Thu 2023-04-20 18:00:07 EEST; 1min 47s ago
Process: 2177 ExecStart=/sbin/modprobe vboxdrv (code=exited, status=1/FAILURE)
Main PID: 2177 (code=exited, status=1/FAILURE)
CPU: 4ms
кві 20 18:00:07 DELLV systemd[1]: Starting vboxdrv.service - Linux kernel module init script...
кві 20 18:00:07 DELLV modprobe[2177]: modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/6.2.11-300.fc38.x>
кві 20 18:00:07 DELLV systemd[1]: vboxdrv.service: Main process exited, code=exited, status=1/FAILURE
кві 20 18:00:07 DELLV systemd[1]: vboxdrv.service: Failed with result 'exit-code'.
кві 20 18:00:07 DELLV systemd[1]: Failed to start vboxdrv.service - Linux kernel module init script.
had it yesterday too:
I fixed it by reinstalling all VBox packages from rpmfusion
Hint:
AFAIK, you need to fetch the VBox extension pack by hand from VBox site, the correct one: “7.0.6” not “7.0.8”
- trick the download link !: copy/paste the link in a new Firefox Tab and adjust at 2 places -
guess addition ISO is already somewhere under /home/<user>/
I guess under .config/Virtualbox or so
no need to restart/-boot:
either the akmods or the vbox service will load the vbox modules
yesterday I had two systems with virtulbox
and today…
about VBox extension I know
Now
```
$ sudo dnf list installed virtualbox*
Installed Packages
VirtualBox.x86_64 7.0.6-1.fc38 @rpmfusion-free
VirtualBox-kmodsrc.noarch 7.0.6-1.fc38 @rpmfusion-free
VirtualBox-server.x86_64 7.0.6-1.fc38 @rpmfusion-free
$
```
Do you mean
`$ sudo dnf reinstall virtualbox*`
?
and what will happen to my virtual machines?nothing !
as long your VM’s are not created where VBox installer places it’s package content, what usually is:
- /usr/lib/virtualbox
- /usr/share/virtualbox
- /home/<username>/.config/VirtualBox
Hint: for backup cases you could export the VM and reimport it
packages:
I meant “reinstall”
what:
maybe figure it via “rpm -qa|grep rpmfusion”
and what is vbox related and akmods, kernel-devel, … too
think of: your box never run VBox
couldn’t assist more cause the box was my brothers, 700 km away
Once you have VirtualBox working again, I’d suggest you get familiar with the built in virtualization tools. If you’re running Fedora Workstation it already has Gnome Boxes which is basically a graphical front-end to LibVirt (very powerful). And if Gnome Boxes doesn’t give you as much control as you like, then you can install Virtual Machine Manager.
Benefits of Switching
- You don’t have to wait on a third party (To update it)
- Multiple choices of tools to manage it:
- Gnome Boxes
- Virtual Machine Manager
- ovirt (Web Interface)
- Cockpit (Less advanced web interface)
- It’s a production quality tool and you can list it as a skill on your job profile
- It’s open source
Install Virtual Machine Manager
sudo dnf install virt-manager
Add Yourself to the KVM Group
sudo usermod -aG libvirt <user name>
Install the Virtualization Tools Suite
sudo dnf group install "Virtualization"
1 Like
I agree 100%.
Although VirtualBox is a wonderful tool, it is not open source, comes from Oracle with the attendant potential for problems that cannot be fixed by FOSS developers, and may not remain current with kernel updates.
QEMU/KVM libvirt on the other hand has been in use for many years and is FOSS. It has kept up with all software growth and as Alys has said does all its updates with the system so things just work as they should.
I recommend it highly!
1 Like
thank you
I don’t use Workstation
My systems are LXQt and Cinnamon
(and in no hurry Testing Budgie Desktop)
I will definitely try LibVirt and Virtual Machine Manager
Kali has a Prebuilt Virtual Machine for QEMU
but machines from VulnHub will have to be converted from OVA to QCOW2
I will try…
if there will be free time and free disk space
I ran into the same problem. What ended up working for me was: dnf erase kmod-VirtualBox-6.2.11-300.fc38.x86_64.x86_64 (and all other version/kernel combinations) and then finally sudo dnf reinstall akmod-VirtualBox kmod-VirtualBox.
I hope that helps!
YES!!!
THANX!
$ rpm -qa kmod-VirtualBox-*
kmod-VirtualBox-6.2.9-200.fc37.x86_64-7.0.6-1.fc37.x86_64
kmod-VirtualBox-6.2.10-200.fc37.x86_64-7.0.6-1.fc37.x86_64
kmod-VirtualBox-6.2.11-300.fc38.x86_64-7.0.6-1.fc38.x86_64
sudo dnf erase kmod-VirtualBox-6.2.9-200.fc37.x86_64-7.0.6-1.fc37.x86_64 kmod-VirtualBox-6.2.10-200.fc37.x86_64-7.0.6-1.fc37.x86_64 kmod-VirtualBox-6.2.11-300.fc38.x86_64-7.0.6-1.fc38.x86_64
Вилучено:
kmod-VirtualBox-6.2.10-200.fc37.x86_64-7.0.6-1.fc37.x86_64
kmod-VirtualBox-6.2.11-300.fc38.x86_64-7.0.6-1.fc38.x86_64
kmod-VirtualBox-6.2.9-200.fc37.x86_64-7.0.6-1.fc37.x86_64
Завершено!
$ sudo dnf reinstall akmod-VirtualBox kmod-VirtualBox
Last metadata expiration check: 0:18:33 ago on Mon Apr 24 20:05:30 2023.
Package kmod-VirtualBox available, but not installed.
No match for argument: kmod-VirtualBox
Dependencies resolved.
Reinstalled:
akmod-VirtualBox-7.0.6-1.fc38.x86_64
Complete!
Note that this is counter-indicated.
It should have been sudo dnf reinstall akmod-VirtualBox and not include kmod-VirtualBox in that command. installing akmod-VirtualBox automatically builds the kmod-VirtualBox package for the user and installing it from rpmfusion can potentially cause problems since there can be slight differences between what the system would build and the package installed from rpmfusion.
The removal could be done with a simple dnf remove kmod-VirtualBox-* which would remove all versions currently installed.
1 Like
I do not know…
I had two machines with a broken virtualbox
I tried to fix one of them with tips on this topic
and yesterday I succeeded
I did not touch the other
did not exert any manual influence
A new kernel arrived today
and the virtualbox came to life automagically
Now I have
$ sudo dnf list installed *virtualbox*
Installed Packages
VirtualBox.x86_64 7.0.6-1.fc38 @rpmfusion-free
VirtualBox-kmodsrc.noarch 7.0.6-1.fc38 @rpmfusion-free
VirtualBox-server.x86_64 7.0.6-1.fc38 @rpmfusion-free
akmod-VirtualBox.x86_64 7.0.6-1.fc38 @rpmfusion-free
kmod-VirtualBox-6.2.10-200.fc37.x86_64.x86_64 7.0.6-1.fc37 @@commandline
kmod-VirtualBox-6.2.11-300.fc38.x86_64.x86_64 7.0.6-1.fc38 @@commandline
kmod-VirtualBox-6.2.12-300.fc38.x86_64.x86_64 7.0.6-1.fc38 @@commandline
$
conclusion:
just had to wait for the kernel update