After upgrade to virtualbox 7.2.4-1 VM starts fail with VERR_SYMBOL_NOT_FOUND

General system Applications
1

After upgrading to virtualbox 7.2.4-1 I cannot start any VM. I’ve tried to start a Windows 11 VM and I get this error:

00:00:00.937491 VMMR0.r0 is importing SUPR0EnableHwvirt which we couldn't find
00:00:00.937493 AssertLogRel /build/virtualbox/src/VirtualBox-7.2.4/src/VBox/HostDrivers/Support/SUPLibLdr.cpp(273) int supLoadModuleResolveImport(RTLDRMOD, const char*, const char*, unsigned int, RTUINTPTR*, void*): <NULL>
00:00:00.937494 VMMR0.r0 is importing SUPR0EnableHwvirt which we couldn't find
00:00:00.937496 SUP: RTLdrGetBits failed for VMMR0.r0 (/usr/lib/virtualbox/VMMR0.r0). rc=VERR_SYMBOL_NOT_FOUND
00:00:00.937647 PDMLdr: pdmR3LoadR0U: pszName="VMMR0.r0" rc=VERR_SYMBOL_NOT_FOUND szErr="Unable to locate imported symbol 'SUPR0EnableHwvirt' for module 'VMMR0.r0'"
00:00:00.937652 VMSetError: /build/virtualbox/src/VirtualBox-7.2.4/src/VBox/VMM/VMMR3/PDMLdr.cpp(749) int pdmR3LoadR0U(PUVM, const char*, const char*, const char*); rc=VERR_SYMBOL_NOT_FOUND
00:00:00.937653 VMSetError: Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: Unable to locate imported symbol 'SUPR0EnableHwvirt' for module 'VMMR0.r0'
00:00:00.937661 VMSetError: /build/virtualbox/src/VirtualBox-7.2.4/src/VBox/VMM/VMMR3/VM.cpp(591) int vmR3CreateU(PUVM, uint32_t, PFNCFGMCONSTRUCTOR, void*); rc=VERR_SYMBOL_NOT_FOUND
00:00:00.937662 VMSetError: Failed to load VMMR0.r0
00:00:00.937856 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: Unable to locate imported symbol 'SUPR0EnableHwvirt' for module 'VMMR0.r0' (VERR_SYMBOL_NOT_FOUND).
00:00:00.937862 Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND)}, preserve=false aResultDetail=-609
00:00:00.937950 Console: Machine state changed to 'PoweredOff'

I’ve reinstalled the complete virtualbox packages but no change. I’ve checked that the virtualbox and the virtualbox-host-modules-lts are both on version 7.2.4.-1:

❯ pacman -Q | grep virtual
virtualbox 7.2.4-1
virtualbox-guest-iso 7.2.4-1
virtualbox-host-modules-arch 7.2.4-1
virtualbox-host-modules-lts 7.2.4-1

I have both the arch and the lts version of virtualbox-host-modules-… installed because I have the standard kernel and the lts kernel installed. I’ve checked that the correct module is loaded:

❯ uname -r
6.12.53-1-lts

❯ modinfo vboxdrvfilename:       /lib/modules/6.12.53-1-lts/extramodules/vboxdrv.ko.zstversion:        7.2.4 r170995 (0x00340001)license:        GPLdescription:    Oracle VirtualBox Support Driverauthor:         Oracle and/or its affiliatessrcversion:     093FA893C2464C5DFBB82FDdepends:name:           vboxdrvretpoline:      Yvermagic:       6.12.53-1-lts SMP preempt mod_unloadparm:           disabled:Disable automatic module loading (int)parm:           force_async_tsc:force the asynchronous TSC mode (int)

Has anyone experienced this error or can someone help me fix it?

Greetings, Jens

2

I’m running the same version and it starts up Linux boxes just fine. I don’t have a Windows licence to test that.

3

I have a Linux Mint VM and the error is the same when I try to start it.

4

The only thing I can see is that I’m using virtualbox-host-dkms. Maybe someone with more knowledge will come along.

5

I assume that I don’t need the virtualbox-host-dkms because https://wiki.archlinux.org/title/VirtualBox states:

Install the virtualbox package. You will also need to choose a package to provide host modules:

I’ve also looked in the /var/log/pacman.log but I don’t see any entry for virtualbox-host-dkms.

6

Yeah, it’s an either or. The dkms package rebuilds the modules after a virtualbox or kernel update.

7

Try rebuilding your kernel images. Reboot and test.

1 Like
8

i had the same issue.

remove and reinstalling virtualbox didn’t worked.

after i had read @MyNameIsRichard post i also tried with the dkms-moduls and it worked. so i switched back to the arch-modules to verify the issue BUT…surprisingly it also worked with them.

so this may be a little workaround for now until devs find the faulty bits.

cheers!

9

sudo reinstall-kernels

did the trick for me.

1 Like
10

Thank you for your solution to my problem. I marked the other answer as solution because he typed the command to rebuild the kernel.

11

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.