Hi everyone. After latest update to next kernel 5.8 Virtualbox fails for me.
Am conscious (from previous post here) that this could be my impatience waiting to the new virtualbox updates for a new kernel but I thought I'd flag up the issue just in case.

Log looks like

00:00:00.945590 VirtualBox VM 6.1.12 r139181 linux.amd64 (Jul 27 2020 09:07:02) release log
00:00:00.945593 Log opened 2020-08-09T11:41:12.404328000Z
00:00:00.945594 Build Type: release
00:00:00.945597 OS Product: Linux
00:00:00.945599 OS Release: 5.8.0-1-next
00:00:00.945600 OS Version: #1 SMP PREEMPT Mon Aug 3 09:57:46 UTC 2020
00:00:00.945623 DMI Product Name: System Product Name
00:00:00.945632 DMI Product Version: System Version
00:00:00.945639 Firmware type: UEFI
00:00:00.946101 Secure Boot: Disabled
00:00:00.946149 Host RAM: 31037MB (30.3GB) total, 29234MB (28.5GB) available
00:00:00.946156 Executable: /usr/lib/virtualbox/VirtualBoxVM
00:00:00.946157 Process ID: 2491
00:00:00.946158 Package type: LINUX_64BITS_GENERIC (OSE)
00:00:00.947662 Installed Extension Packs:
00:00:00.947678   Oracle VM VirtualBox Extension Pack (Version: 6.1.12 r139181; VRDE Module: VBoxVRDP)
00:00:00.948977 Console: Machine state changed to 'Starting'
00:00:00.949374 Qt version: 5.15.0
00:00:00.949393 X11 Window Manager code: 3
00:00:00.958296 PDMLdr: pdmR3LoadR0U: pszName="VMMR0.r0" rc=VERR_NO_EXEC_MEMORY szErr="SUP_IOCTL_LDR_OPEN failed"
00:00:00.958327 VMSetError: /buildsys/apps/virtualbox-qt5/src/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.958329 VMSetError: Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: SUP_IOCTL_LDR_OPEN failed
00:00:00.958338 VMSetError: /buildsys/apps/virtualbox-qt5/src/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.958339 VMSetError: Failed to load VMMR0.r0
00:00:00.958440 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.958445 Failed to load VMMR0.r0 (VERR_NO_EXEC_MEMORY)}, preserve=false aResultDetail=-96
00:00:00.958958 Console: Machine state changed to 'PoweredOff'
00:00:00.961196 Power up failed (vrc=VERR_NO_EXEC_MEMORY, rc=NS_ERROR_FAILURE (0X80004005))
00:00:00.985769 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:00.986348 X Server details: vendor: The X.Org Foundation, release: 12008000, protocol version: 11.0, display string: :0
00:00:00.986374 Using XKB for keycode to scan code conversion
00:00:00.994726 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 0 work area is actually resized to: 0x0 x 1920x1080
00:00:01.461723 GUI: Aborting startup due to power up progress issue detected...

Thanks,
JJ

Known issue, and since Linux just works, it was not keeping linux-next from reaching all users any longer, see the commit:
https://github.com/KaOSx/apps/commit/a6ed74f861216114f2077de33fc089d12c249ae6
If you need virtualbox right now, boot in the linux kernel, the upcoming build of linux-next (5.8.1) has a possible patch for this already included (and link to upstream bug report):
https://github.com/KaOSx/core/commit/885910a9297097695aac21dd8bd4247aa4807459

PS:
Please use code tags for cli output (enclose with 3 backticks ```), done for you this time.

Not just KaOS that is effected:
https://www.virtualbox.org/ticket/19644
https://bugs.gentoo.org/735786
https://bugs.archlinux.org/task/67488?project=5&order=lastedit&sort=desc

9 days later

Thanks Demm. I have successfully used the standard kernel to fire up Vbox . I have one remaining application that is only available in Windoze which programs my home automation so still need Vbox.

Thanks also for changing tags.

JJ

To follow up why it is not fixed yet, if you check all the bug reports, fixes are causing all kinds of problems, so not breaking virtualbox for all users so it barely works in linux-next. Expect no further changes (so all keeps working as should for linux 5.7) until virtualbox themselves come out with a new release. There clearly is a reason why all the patches they have has not resulted yet in a new release....

My recent experience of VBox installation / Running, mainly focused on the kernel header rebuilding. Choose the right version.

As a reference for you.

19 days later

Linux-next can be used again for virtualbox, the newly released vbox 6.1.14 fixes incompatibilities with new kernel.
New vbox packages are up in the [build] repo, will move soon to all users.