[SOLVED] Virtualbox stopped working after updating to 7.2.4 using akmod on 6.18.8-200 using X11

Ask Fedora
1

I’m on Fedora 43 KDE. I installed my nvidia, multimedia and other things including Virtualbox via RPM Fusion as instructed. Everything has been working great. I’m using X11 and the kernel is 6.18.8-200.

Today there was an update in Discover. So I updated Virtualbox:

User           : 0 Super User <root>
Status         : Ok
Releasever     : 43
Description    : dnf -y install --nogpgcheck --disablerepo=* /tmp/akmods.x1mnZJeP/results/kmod-VirtualBox-6.18.8-200.fc43.x86_64-7.2.6-1.fc43.x86_64.rpm
  Action   Package                                                      Reason Repository
  Upgrade  kmod-VirtualBox-6.18.8-200.fc43.x86_64-0:7.2.6-1.fc43.x86_64 User   @commandline
  Replaced kmod-VirtualBox-6.18.8-200.fc43.x86_64-0:7.2.4-1.fc43.x86_64 User   @System

Now I can’t start Virtualbox. I get the error:

Failed to load R0 module /usr/lib64/virtualbox/VMMR0.r0: Unable to locate imported symbol 'RTSystemGetPageShift' for module 'VMMR0.r0' (VERR_SYMBOL_NOT_FOUND).

Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND).

|Result Code:|NS_ERROR_FAILURE (0x80004005)|
| --- | --- |
|Result Detail:|-609 (0xfffffd9f)|
|Component:|ConsoleWrap|
|Interface:|IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}|

Is there anyone who can help?

2

After a lot of searching online, it seems there was a mismatch causing USB errors as the extension pack was on the old version yet VB was on the newest version. So:

Updated the Extension Pack from 7.2.4 to 7.2.6 to match VirtualBox - this solved the USB driver name clash.

wget https://download.virtualbox.org/virtualbox/7.2.6/Oracle_VirtualBox_Extension_Pack-7.2.6.vbox-extpack
sudo VBoxManage extpack uninstall "Oracle VirtualBox Extension Pack"
sudo VBoxManage extpack install Oracle_VirtualBox_Extension_Pack-7.2.6.vbox-extpack

But by then I had screwed it all up trying so many things, and I was getting network errors trying to start VB, so, reconfigured the bridged network adapter - switching to NAT and back to bridged cleared whatever was corrupted.

VBoxManage modifyvm "Windows PC Law" --nic1 nat
VBoxManage startvm "Windows PC Law" --type gui

Ran, but no internet.

VBoxManage controlvm "Windows PC Law" poweroff`
VBoxManage modifyvm "Windows PC Law" --nic1 bridged --bridgeadapter1 enp10s0
VBoxManage startvm "Windows PC Law" --type gui

So, I guess this should not happen. RPM fusion did not provide the extension pack.

1 Like
3

This is still a problem that:

  • This is not documented in the RPM Fusion wiki
  • This is not advertised, like if you have an extension kit version missmatch that will lead to error that there is no advertising message to update it or something else to prevent the error.

(that might be a virtualbox.org issue)

Care to report to them ?

At least there is a mention in the RPM Fusion wiki at least: