VirtualBox fails to start VMs with error VERR_NO_EXEC_MEMORY

VirtualBox 6.1.12_SUSE r139181

All VMs fail to start with error “VERR_NO_EXEC_MEMORY”.

Recent problem. Was running fine. Broken sometime in past few weeks.

VirtualBox complained that Graphics Controller setting needed to be changed to “VBoxSVGA” from “VBoxVGA” which was working previously. Changing this setting does not fix the problem.


Failed to open a session for the virtual machine Windows 7.

Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: SUP_IOCTL_LDR_OPEN failed (VERR_NO_EXEC_MEMORY).

Failed to load VMMR0.r0 (VERR_NO_EXEC_MEMORY).

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

Example VBox.log

  00:00:00.860058 VirtualBox VM 6.1.12_SUSE r139181 linux.amd64 (no date no time) release log
 00:00:00.860060 Log opened 2020-08-17T19:02:36.195721000Z
 00:00:00.860061 Build Type: release
 00:00:00.860063 OS Product: Linux
 00:00:00.860064 OS Release: 5.8.0-1-default
 00:00:00.860065 OS Version: #1 SMP Tue Aug 4 07:30:59 UTC 2020 (9bc0044)
 00:00:00.860080 DMI Product Name: All Series
 00:00:00.860085 DMI Product Version: System Version
 00:00:00.860091 Firmware type: UEFI
 00:00:00.860332 Secure Boot: Disabled
 00:00:00.860358 Host RAM: 15937MB (15.5GB) total, 10419MB (10.1GB) available
 00:00:00.860361 Executable: /usr/lib/virtualbox/VirtualBoxVM
 00:00:00.860361 Process ID: 28557
 00:00:00.860361 Package type: LINUX_64BITS_GENERIC (OSE)
 00:00:00.865231 Installed Extension Packs:
 00:00:00.865245   Oracle VM VirtualBox Extension Pack (Version: 6.1.12 r139181; VRDE Module: VBoxVRDP)
 00:00:00.866207 Console: Machine state changed to 'Starting'
 00:00:00.866402 Qt version: 5.15.0
 00:00:00.866411 X11 Window Manager code: 3
 00:00:00.868000 PDMLdr: pdmR3LoadR0U: pszName="VMMR0.r0" rc=VERR_NO_EXEC_MEMORY szErr="SUP_IOCTL_LDR_OPEN failed"
 00:00:00.868000 VMSetError: /home/abuild/rpmbuild/BUILD/VirtualBox-6.1.12/src/VBox/VMM/VMMR3/PDMLdr.cpp(733) int pdmR3LoadR0U(PUVM, const char*, const char*, const char*); rc=VERR_NO_EXEC_MEMORY
 00:00:00.868000 VMSetError: Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: SUP_IOCTL_LDR_OPEN failed
 00:00:00.868000 VMSetError: /home/abuild/rpmbuild/BUILD/VirtualBox-6.1.12/src/VBox/VMM/VMMR3/VM.cpp(563) int vmR3CreateU(PUVM, uint32_t, PFNCFGMCONSTRUCTOR, void*); rc=VERR_NO_EXEC_MEMORY
 00:00:00.868000 VMSetError: Failed to load VMMR0.r0
 00:00:00.868000 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: SUP_IOCTL_LDR_OPEN failed (VERR_NO_EXEC_MEMORY).
 00:00:00.868000 Failed to load VMMR0.r0 (VERR_NO_EXEC_MEMORY)}, preserve=false aResultDetail=-96
 00:00:00.868000 Console: Machine state changed to 'PoweredOff'
 00:00:00.873937 GUI: UIMediumEnumerator: Medium-enumeration finished!
 00:00:00.875503 X Server details: vendor: The X.Org Foundation, release: 12008000, protocol version: 11.0, display string: :0
 00:00:00.875510 Using XKB for keycode to scan code conversion
 00:00:00.889605 Power up failed (vrc=VERR_NO_EXEC_MEMORY, rc=NS_ERROR_FAILURE (0X80004005))
 00:00:00.896491 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 0 work area is actually resized to: 1x1236 x 1920x1164

 00:00:00.901801 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 1 work area is actually resized to: 0x0 x 1920x1200
 00:00:01.390098 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 1280x1024
 00:00:01.390156 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
 00:00:01.390210 GUI: Aborting startup due to power up progress issue detected...

Stay on kernel 5.7 or wait for Oracle to fix their software.

or install manually
which works for 5.8 kernel

I wonder if the security hole has been fixed in this version…?

I don’t muddle with the kernel version. Whatever Tumbleweed installs is what I use.

Sounds like this is a “wait for it to be fixed” scenario.

You could be waiting awhile… even the maintainer suggests moving to kvm/qemu as a second option…

I have converted one of my laptops from VirtualBox to KVM - It went pretty smooth - You need a lot of space to convert vdi to qcow2.

I might post an how to guide - I had to figure out a lot of small issues - using NAT for guests had have some additional steps when I rebooted because I failed to autorestart the NAT bridge.

this is what I used to get KVM installed all as root

zypper -n install patterns-openSUSE-kvm_server patterns-server-kvm_tools
systemctl enable libvirtd
systemctl restart libvirtd
modprobe kvm-intel  (there is a different entry for AMD cpus)
(convert your VDI here and build your virtual machine with NAT then do the following to get it working)
(hint qemu-img convert -O qcow2 <image>.vdi <image>.qcow2)
zypper install bridge-utils
virsh net-start default
virsh net-list --all
virsh net-autostart --network default

you will need to set the disk type to SATA or the boot will hang.