Description of problem: After latests updates: Vbox on M8 will no longer launchs a simple client Client name: M8 x86_64 Plasma Live-DVD Mageia-8-beta1-Live-Plasma-x86_64.iso md5sum: 8cea7b657a1bfee91b7fb709dcebfdfc Error window reported: Failed to open a session for the virtual machine M8 x86_64 Plasma Live-DVD. Failed to load R0 module /usr/lib64/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}
Summary: Vbox fails to launch client after latest updates => virtualbox fails to launch client after latest updates
This still occurs as of today's updates and latest kernel - 5.8.1-desktop-4.mga8 Virtualbox can not be used and this should be considered a release blocker if continues
CC: (none) => rfox
Sorry to have left this, Bill. No time... Thank you for the confirmation, Robert. Assigning to the kernel group.
Assignee: bugsquad => kernelSource RPM: virtualbox => virtualbox-6.1.12-8.mga8.src.rpm, kernel-desktop-5.8.1-4.mga8-1-1.mga8Priority: Normal => HighSeverity: normal => major
I add some info. Actually 6.1.12 doesn't work with kernel 5.8.x. It actually has two behaviours: one is the VERR_NO_EXEC_MEMORY you reported, and the second is a system freeze as soon as any virtual machine is started. There are no issues on older 5.7.x kernels. Actually the current solution (which yet doesn't work) is based on: a) include a patchset for kernel. I.e. this one: http://svnweb.mageia.org/packages/cauldron/kernel/current/SPECS/kernel.spec?r1=1613660&r2=1613700 we have to remember that this is a temporary workaround, and should be removed once the status upstream is stabilized. b) include also patch for virtualbox 6.1.12 for kernel 5.8. There are a few around (opensuse, fusion, arch, etc.), and we include one of them, but they are not yet working properly. A referring upstream bug, which the patch are derived from, is this one: https://www.virtualbox.org/ticket/19644 As experiment, I tried to build the current development version from trunk svn, which is 6.1.97. Resulting temporary RPMS are here: https://download.copr.fedorainfracloud.org/results/ghibo/kernel/mageia-cauldron-x86_64/01611810-virtualbox/ and they actually works with kernel 5.8.1, without any freeze or VERR_NO_EXEC_MEMORY error, but only if kernel patch as from point a) is included, otherwise a system freeze occurs. So probably a next upstream release (6.1.14 or 6.2.0) should fix this issue.
CC: (none) => ghibomgx
(In reply to Robert Fox from comment #1) > Virtualbox can not be used and this should be considered a release blocker > if continues Correct. Vbox is a vital tool in Mageia. I myself could not transition from M7 -> M8 without a working Vbox on M8. Thanks
CC: (none) => stephane.pontier
This is upstream bug Here is ticket: https://www.virtualbox.org/ticket/19644?cversion=0&cnum_hist=8
URL: (none) => https://www.virtualbox.org/ticket/19644?cversion=0&cnum_hist=8Source RPM: virtualbox-6.1.12-8.mga8.src.rpm, kernel-desktop-5.8.1-4.mga8-1-1.mga8 => virtualbox-6.1.12-8.mga8.src.rpm, kernel-5.8.4-1.mga8.src.rpmKeywords: (none) => UPSTREAM
Source RPM: virtualbox-6.1.12-8.mga8.src.rpm, kernel-5.8.4-1.mga8.src.rpm => virtualbox-6.1.12-8.mga8.src.rpm, kernel-5.8.5-1.mga8.src.rpmBlocks: (none) => 27219
There is a newer version 6.1.14-3.mga8 that should fix this.
Yeah. virtualbox-6.1.14-3.mga8 fixes this. Therefore, in my testing, on a M8 UEFI x86_64 install and under Plasma, All M7 ISO correctly boot in VM while VM configured in BIOS mode. In UEFI mode configured, VM always start to a EFI-shell, not to UEFI mode in ISO.
Target Milestone: --- => Mageia 8CC: (none) => ouaurelien
Resolved fixed. Cauldron is able to launch VM on 5.8.8 Kernel.
Status: NEW => RESOLVEDResolution: (none) => FIXED
(In reply to Aurelien Oudelet from comment #7) > virtualbox-6.1.14-3.mga8 fixes this. Agreed.