![](https://seccdn.libravatar.org/avatar/aebdf31d465b04113cd13a6bffde8527.jpg?s=120&d=mm&r=g)
On 08. 06. 20, 21:06, Larry Finger wrote:
Hi,
In kernel 5.8, the routine used by VirtualBox to map an area of virtual memory "(__get_vm_area()" has been replaced. By itself, thet is not serious, but the replacement is not exported, thus VB will cannot be built.
Try this: Index: VirtualBox-6.1.8/src/VBox/Runtime/r0drv/linux/alloc-r0drv-linux.c =================================================================== --- VirtualBox-6.1.8.orig/src/VBox/Runtime/r0drv/linux/alloc-r0drv-linux.c +++ VirtualBox-6.1.8/src/VBox/Runtime/r0drv/linux/alloc-r0drv-linux.c @@ -38,7 +38,7 @@ #if (defined(RT_ARCH_AMD64) || defined(DOXYGEN_RUNNING)) && !defined(RTMEMALLOC_EXEC_HEAP) -# if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 23) +# if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 23) && LINUX_VERSION_CODE < KERNEL_VERSION(5, 8, 0) /** * Starting with 2.6.23 we can use __get_vm_area and map_vm_area to allocate * memory in the moduel range. This is preferrable to the exec heap below.
Ultimately, I think the only solution for Oracle will be to rewrite their module vboxdrv for inclusion in the kernel
+1. thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org