Bug 1175246

Summary: Can't start any VMs in Virtualbox (VERR_NO_EXEC_MEMORY)
Product: [openSUSE] openSUSE Tumbleweed Reporter: Nathaniel Graham <nate>
Component: Virtualization:ToolsAssignee: virt-bugs list <virt-bugs>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: hfischer
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Nathaniel Graham 2020-08-13 19:00:13 UTC
I just installed Virtualbox in my TW installation. After creating a VM, attempting to start it always fails with the following error message:


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}



I have kernel-5.8.0-1.1 installed, along with the same versions of kernel-devel and kernel-macros. My system has 16 GB of RAM with over 12 GB currently free.
Comment 1 Helga Fischer 2020-08-13 19:42:25 UTC
Me too ;). Just updated Tumbleweed to kernel 5.7 to 5.8. Kernel 5.7 and Virtualbox didn't work together. It was possible to start a vm, but I loosed mouse and keyboard so the desktop was not usable. Had to kill vbox over a second pc and ssh-login. Hoped, that will be repaired with the update to kernel 5.8.

Now a get the message, if I want to copy the vm (no, I do not want) or 'OK'. For OK I got this message:


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).

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


I'm using virtualbox for many years on this maschine; 16 GB RAM and a own HD for the VMs.
Comment 2 Christophe Marin 2020-08-13 20:35:30 UTC
Known issue with kernel 5.8

*** This bug has been marked as a duplicate of bug 1175201 ***