VirtualBox

Ticket #20904 (closed defect: fixed)

Opened 4 weeks ago

Last modified 3 weeks ago

Error "Failed to load R0 module /usr/lib/virtualbox/VBoxDDR0.r0: Unable to locate imported symbol 'memset' for module 'VBoxDDR0.r0' (VERR_SYMBOL_NOT_FOUND)." running a machine

Reported by: carles Owned by:
Component: other Version: VirtualBox 6.1.34
Keywords: Cc:
Guest type: all Host type: Linux

Description

Debian Bullseye (version 11.3) with its standard kernel "Linux pinux 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) x86_64 GNU/Linux"

I've installed virtualbox-6.1_6.1.34-150636~Debian~bullseye_amd64.deb and on starting new machines or existing machines I get this error message:

Failed to load R0 module /usr/lib/virtualbox/VBoxDDR0.r0: Unable to locate imported symbol 'memset' for module 'VBoxDDR0.r0' (VERR_SYMBOL_NOT_FOUND).
Failed to load ring-0 module 'VBoxDDR0.r0' for device 'pci' (VERR_SYMBOL_NOT_FOUND).


Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I've attached a log file.

Using virtualbox-6.1_6.1.32-149290~Debian~bullseye_amd64.deb all works well.

There isn't any extension pack installed when the problem happens.

Attachments

error-failed-to-load-r0-module-Windows 10-2022-04-20-00-13-38.log Download (42.6 KB) - added by carles 4 weeks ago.
VBox.log Download (46.3 KB) - added by robatino 4 weeks ago.
log file for Fedora 35 host attempting to start a Fedora 36 guest

Change History

comment:1 Changed 4 weeks ago by autopr3z

Having the same issue on two different Bullseye machines. Guests were both Windows and Linux. Each host is running at least 5.15 or higher Linux kernel. It doesn't seem to matter whether the extensions pack is installed.

comment:2 Changed 4 weeks ago by robatino

Same problem with a Fedora 35 host. Attaching log file for when I attempt to start a Fedora 36 guest.

Changed 4 weeks ago by robatino

log file for Fedora 35 host attempting to start a Fedora 36 guest

comment:3 Changed 4 weeks ago by birdy

This is a critical issue which warrants a new bugfix release or a rerelease ASAP.

As it is 6.1.34 on Linux hosts is outright broken.

comment:4 Changed 4 weeks ago by birdy

00:00:00.636222 VBoxDDR0.r0 is importing memset which we couldn't find
00:00:00.636226 AssertLogRel /home/vbox/vbox-6.1.34/src/VBox/HostDrivers/Support/SUPLibLdr.cpp(263) int supLoadModuleResolveImport(RTLDRMOD, const char*, const char*, unsigned int, RTUINTPTR*, void*): <NULL>
00:00:00.636227 VBoxDDR0.r0 is importing memset which we couldn't find
00:00:00.636229 SUP: RTLdrGetBits failed for VBoxDDR0.r0 (/usr/lib/virtualbox/VBoxDDR0.r0). rc=VERR_SYMBOL_NOT_FOUND
00:00:00.636234 PDMLdr: pdmR3LoadR0U: pszName="VBoxDDR0.r0" rc=VERR_SYMBOL_NOT_FOUND szErr="Unable to locate imported symbol 'memset' for module 'VBoxDDR0.r0'"
00:00:00.636242 VMSetError: /home/vbox/vbox-6.1.34/src/VBox/VMM/VMMR3/PDMLdr.cpp(733) int pdmR3LoadR0U(PUVM, const char*, const char*, const char*); rc=VERR_SYMBOL_NOT_FOUND
00:00:00.636243 VMSetError: Failed to load R0 module /usr/lib/virtualbox/VBoxDDR0.r0: Unable to locate imported symbol 'memset' for module 'VBoxDDR0.r0'
00:00:00.636247 VMSetError: /home/vbox/vbox-6.1.34/src/VBox/VMM/VMMR3/PDMDevice.cpp(340) int pdmR3DevInit(PVM); rc=VERR_SYMBOL_NOT_FOUND
00:00:00.636248 VMSetError: Failed to load ring-0 module 'VBoxDDR0.r0' for device 'pci'
00:00:00.637164 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to load R0 module /usr/lib/virtualbox/VBoxDDR0.r0: Unable to locate imported symbol 'memset' for module 'VBo
xDDR0.r0' (VERR_SYMBOL_NOT_FOUND).
00:00:00.637167 Failed to load ring-0 module 'VBoxDDR0.r0' for device 'pci' (VERR_SYMBOL_NOT_FOUND)}, preserve=false aResultDetail=-609
00:00:00.637220 Console: Machine state changed to 'PoweredOff'
00:00:00.642236 Power up failed (vrc=VERR_SYMBOL_NOT_FOUND, rc=NS_ERROR_FAILURE (0X80004005))

comment:5 Changed 4 weeks ago by Renda

Just confirming, the same issue in this configuration:

  • Debian 11 incl. backports updates
  • virtualbox-6.1 6.1.34-150636~Debian~bullseye
$ uname -a
Kernel 5.16.0-0.bpo.4-amd64 #1 SMP PREEMPT Debian 5.16.12-1~bpo11+1 (2022-03-08) x86_64 GNU/Linux

Version 6.1.32 worked fine incl. the Extension pack on the same OS level.

Last edited 4 weeks ago by Renda (previous) (diff)

comment:6 Changed 4 weeks ago by jamezrr

Having the same issue with Kernel: Linux 5.10.0-13-amd64 and same error message above.

comment:7 Changed 4 weeks ago by aureo

Just adding the same issue here on Debian Bullseye , virtual box Version 6.1.34 r150636

comment:8 follow-ups: ↓ 10 ↓ 13 Changed 4 weeks ago by galitsyn

Hi guys,

Thanks for pointing to the issue. As a temporary workaround I would suggest to use VirtualBox-6.1.34-150636-Linux_amd64.run installer from  https://download.virtualbox.org/virtualbox/6.1.34/.

Last edited 4 weeks ago by galitsyn (previous) (diff)

comment:9 Changed 4 weeks ago by dubai

Same error on all my Linux guests (Debian 11, Kali) on Linux gues (Debian 11). None of them open now. Started happening after a routine system restart.

comment:10 in reply to: ↑ 8 ; follow-up: ↓ 11 Changed 4 weeks ago by jamezrr

Replying to galitsyn:

Hi guys,

Thanks for pointing to the issue. As a temporary workaround I would suggest to use VirtualBox-6.1.34-150636-Linux_amd64.run installer from  https://download.virtualbox.org/virtualbox/6.1.34/.

Version 6.1.34 r150636 (Qt5.15.2) but it is not working

comment:11 in reply to: ↑ 10 Changed 4 weeks ago by robatino

Replying to jamezrr:

Replying to galitsyn:

Hi guys,

Thanks for pointing to the issue. As a temporary workaround I would suggest to use VirtualBox-6.1.34-150636-Linux_amd64.run installer from  https://download.virtualbox.org/virtualbox/6.1.34/.

Version 6.1.34 r150636 (Qt5.15.2) but it is not working

Using Fedora 35, same Qt version, the .run file works fine for me and is a cleaner workaround.

comment:12 follow-ups: ↓ 14 ↓ 15 Changed 4 weeks ago by zetneteork

Downgrade back to version 6.1.32-149290~Debian~bullseye was only solution to fix the issue.

comment:13 in reply to: ↑ 8 Changed 4 weeks ago by bittin-

Replying to galitsyn:

Hi guys,

Thanks for pointing to the issue. As a temporary workaround I would suggest to use VirtualBox-6.1.34-150636-Linux_amd64.run installer from  https://download.virtualbox.org/virtualbox/6.1.34/.

That work around worked for me, when i had the same problem with the Arch Linux package updates of Virtualbox this morning

comment:14 in reply to: ↑ 12 Changed 4 weeks ago by CharlieRAnimaMX

Confirmed, Same problem Here (Fresh Install of Debian 11- with Testing Repositories "Bullseye-Bookworm").

Installer pakage Method for 6.1.34 Doesn't Work, But Back to Version : virtualbox-6.1_6.1.32-149290~Debian~bullseye_amd64.deb. Yes, temporarily solves the problem

Download here ->  https://download.virtualbox.org/virtualbox/6.1.32/

Replying to zetneteork:

Downgrade back to version 6.1.32-149290~Debian~bullseye was only solution to fix the issue.

comment:15 in reply to: ↑ 12 Changed 4 weeks ago by jamezrr

Replying to zetneteork:

Downgrade back to version 6.1.32-149290~Debian~bullseye was only solution to fix the issue.

thanks this the solution to fix the issue.

comment:16 Changed 4 weeks ago by acastan

Same is true for Debian Testing, with kernel 5.16. VirtualBox 6.1.32 was working fine, but when upgraded to 6.1.34 , VirtualBox virtual machines stop working, with the same error messages:

Failed to load R0 module /usr/lib/virtualbox/VBoxDDR0.r0: Unable to locate imported symbol 'memset' for module 'VBoxDDR0.r0' (VERR_SYMBOL_NOT_FOUND).

Failed to load ring-0 module 'VBoxDDR0.r0' for device 'pci' (VERR_SYMBOL_NOT_FOUND).

comment:17 Changed 4 weeks ago by carles

There also is some information also in  https://forums.virtualbox.org/viewtopic.php?f=7&t=105815 (for for debugging / workaround, which I haven't tried:  https://forums.virtualbox.org/viewtopic.php?f=7&t=105815#p516517, which I haven't tried).

comment:18 Changed 4 weeks ago by tekstryder

Downstream Arch Linux bug report:  https://bugs.archlinux.org/task/74526

Confirmed Virtualbox is completely broken on both Arch with kernel 5.17.4, and Debian Bullseye with kernels 5.17.4, 5.15.35, and 5.10.0-13.

comment:19 Changed 4 weeks ago by galitsyn

Hi guys,

This issue should now be fixed. We just updated https://www.virtualbox.org/wiki/Linux_Downloads and now download links point to proper packages. Please feel free to give it a try.

Thank you!

comment:20 Changed 4 weeks ago by eworm

But the source tarball is unmodified. Where to find updated source tarball or patch?

comment:22 Changed 4 weeks ago by eworm

Thanks a lot, klaus! Just pushed a fixed version to Arch Linux repositories.

comment:23 in reply to: ↑ 21 Changed 4 weeks ago by carles

Replying to klaus:

You should be able to use this as the patch: https://www.virtualbox.org/changeset?reponame=vbox&format=diff&new=94318%40trunk%2FConfig.kmk&old=94252%40trunk%2FConfig.kmk

Thanks very much - It works for me! (Debian Bullseye)

Last edited 4 weeks ago by carles (previous) (diff)

comment:24 Changed 4 weeks ago by acastan

This morning upgrade fix the problem in Debian Testing with Kernel 5.16

comment:26 Changed 3 weeks ago by galitsyn

  • Status changed from new to closed
  • Resolution set to fixed

The issue is now fixed. Closing.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use