[Testing Update] 2020-09-02 - Kernels, Xorg-Server, Systemd, Firefox, Thunderbird, Wine

I observed how to move existing vbox VM-s to Gnome Boxes, and I don’t like labour…

Yeah, it‘s labor on the hand hand, education on the other. I would like to try KVM + virt-manager, but didn‘t find an easy cookbook for installing the necessary stuff, converting an existing VB vdi and running it yet. So I‘ll continue studying … Of course, the Arch Linux Wiki is one‘s best friend.

BTW, any suggestions regarding going from VB to KVM/appropriate GUI are very welcome.

I have read several peoples’ comments “did the switch and never looked back“, but no cookbook…

When I used KVM/libvirt there was no GUI. Now we have Gnome Boxes.

I also think of switching to qemu because VMware doesn’t support 5.8 otherwise switch to LTS :woman_shrugging:

Maybe this?:

Converting between image formats

6 posts were split to a new topic: How do I have 20.1 installed when it’s not released yet?

A post was merged into an existing topic: How do I have 20.1 installed when it’s not released yet?

A post was merged into an existing topic: How do I have 20.1 installed when it’s not released yet?

All OK (Kernel 5.8.5-2, Xfce, nvidia v450.66)
Also Virtualbox 6.1.12-3 works without problems.
As @michaldybczak stated :

Possibly missing firmware for module: xhci_pci

with no influence at system.

Good Work !!

VirtualBox does not work with Kernel 5.8 on any native nvidia driver: it hard-freezes the whole system with both 440xx and 450xx shortly after spawning the guest OS (I think, when it starts to tickle the GPU).

1 Like

@chainofflowers Can u try booting kernel 5.8 with pcie_aspm=off intel_idle.max_cstate=1 and see if you still have problem with virtualbox ?

Get this Error VirtualBox DKMS install fails on 5.8 Kernel on my System AMD Only (CPU and GPU)

[2020-09-03T21:27:39+0200] [ALPM] running '30-systemd-update.hook'...
[2020-09-03T21:27:39+0200] [ALPM] running '60-depmod.hook'...
[2020-09-03T21:27:47+0200] [ALPM] running '70-dkms-install.hook'...
[2020-09-03T21:27:47+0200] [ALPM-SCRIPTLET] ==> dkms install --no-depmod -m vmware-workstation14 -v 14.1.7_12989993 -k 5.8.5-2-MANJARO
[2020-09-03T21:27:56+0200] [ALPM-SCRIPTLET] Error! Bad return status for module build on kernel: 5.8.5-2-MANJARO (x86_64)
[2020-09-03T21:27:56+0200] [ALPM-SCRIPTLET] Consult /var/lib/dkms/vmware-workstation14/14.1.7_12989993/build/make.log for more information.
[2020-09-03T21:27:56+0200] [ALPM-SCRIPTLET] ==> Warning, `dkms install --no-depmod -m vmware-workstation14 -v 14.1.7_12989993 -k 5.8.5-2-MANJARO' returned 10
[2020-09-03T21:27:56+0200] [ALPM-SCRIPTLET] ==> dkms install --no-depmod -m vboxhost -v 6.1.12_OSE -k 5.8.5-2-MANJARO
[2020-09-03T21:28:03+0200] [ALPM-SCRIPTLET] Error! Bad return status for module build on kernel: 5.8.5-2-MANJARO (x86_64)
[2020-09-03T21:28:03+0200] [ALPM-SCRIPTLET] Consult /var/lib/dkms/vboxhost/6.1.12_OSE/build/make.log for more information.
[2020-09-03T21:28:03+0200] [ALPM-SCRIPTLET] ==> Warning, `dkms install --no-depmod -m vboxhost -v 6.1.12_OSE -k 5.8.5-2-MANJARO' returned 10
[2020-09-03T21:28:03+0200] [ALPM-SCRIPTLET] ==> depmod 5.8.5-2-MANJARO
[2020-09-03T21:28:11+0200] [ALPM] running '90-mkinitcpio-install.hook'...

Just upgraded and getting the same error for Virtualbox DKMS for 5.8. This has happened for the last 2 testing updates and to use Virtualbox have to roll back to 5.7

AMD CPU/GPU here as well.

1 Like

Works as expected on 5.4 and 5.7 (nvm because EOL)

I’m at home with i7 only, i’ll check it tomorrow on AMD.
Can you post

/var/lib/dkms/vboxhost/6.1.12_OSE/build/make.log

and also give a try to linux58-virtualbox-host-modules?

Do you have any Exec format error on nvidia or virtualbox modules

I can’t even start virtual system on Intel GPU. It shows errors:

The virtual machine ‘test’ has terminated unexpectedly during startup with exit code 1 (0x1).

Result code (RC): NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

and other one I can’t copy. I miss ability post screenshots! This is so frustrating! Few days more and it still is PITA. Anyway, it shows something about driver version mismatch.

This is my make.log which I’m receiving the same error.

DKMS make.log for vboxhost-6.1.12_OSE for kernel 5.8.5-2-MANJARO (x86_64)
Thu Sep  3 02:36:56 PM CDT 2020
make: Entering directory '/usr/lib/modules/5.8.5-2-MANJARO/build'
  AR      /var/lib/dkms/vboxhost/6.1.12_OSE/build/built-in.a
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxnetflt/linux/VBoxNetFlt-linux.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxnetadp/linux/VBoxNetAdp-linux.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxnetflt/VBoxNetFlt.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxnetadp/VBoxNetAdp.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxnetflt/SUPR0IdcClient.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxnetflt/SUPR0IdcClientComponent.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/SUPDrvSem.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/SUPDrvGip.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxnetflt/linux/SUPR0IdcClient-linux.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/SUPDrvTracer.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/SUPLibAll.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/alloc-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/initterm-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/memobj-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/mpnotification-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/powernotification-r0drv.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o
  CC [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/memuserkernel-r0drv-linux.o
In file included from ./include/asm-generic/percpu.h:7,
                 from ./arch/x86/include/asm/percpu.h:556,
                 from ./arch/x86/include/asm/preempt.h:6,
                 from ./include/linux/preempt.h:78,
                 from ./include/linux/spinlock.h:51,
                 from /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/linux/../SUPDrvInternal.h:79,
                 from /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/linux/SUPDrv-linux.c:32:
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/linux/SUPDrv-linux.c: In function ‘supdrvOSChangeCR4’:
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/linux/SUPDrv-linux.c:760:38: error: ‘cpu_tlbstate’ undeclared (first use in this function); did you mean ‘cpuhp_state’?
  760 |     RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
      |                                      ^~~~~~~~~~~~
./include/linux/percpu-defs.h:318:9: note: in definition of macro ‘__pcpu_size_call_return’
  318 |  typeof(variable) pscr_ret__;     \
      |         ^~~~~~~~
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/linux/SUPDrv-linux.c:760:24: note: in expansion of macro ‘this_cpu_read’
  760 |     RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
      |                        ^~~~~~~~~~~~~
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/linux/SUPDrv-linux.c:760:38: note: each undeclared identifier is reported only once for each function it appears in
  760 |     RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
      |                                      ^~~~~~~~~~~~
./include/linux/percpu-defs.h:318:9: note: in definition of macro ‘__pcpu_size_call_return’
  318 |  typeof(variable) pscr_ret__;     \
      |         ^~~~~~~~
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/linux/SUPDrv-linux.c:760:24: note: in expansion of macro ‘this_cpu_read’
  760 |     RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
      |                        ^~~~~~~~~~~~~
make[2]: *** [scripts/Makefile.build:281: /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/linux/SUPDrv-linux.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.c: In function ‘rtR0MemAllocExecVmArea’:
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.c:171:15: error: implicit declaration of function ‘__get_vm_area’; did you mean ‘get_vm_area’? [-Werror=implicit-function-declaration]
  171 |     pVmArea = __get_vm_area(cbAlloc, VM_ALLOC, MODULES_VADDR, MODULES_END);
      |               ^~~~~~~~~~~~~
      |               get_vm_area
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.c:171:13: warning: assignment to ‘struct vm_struct *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
  171 |     pVmArea = __get_vm_area(cbAlloc, VM_ALLOC, MODULES_VADDR, MODULES_END);
      |             ^
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.c:204:14: error: implicit declaration of function ‘map_vm_area’; did you mean ‘get_vm_area’? [-Werror=implicit-function-declaration]
  204 |         if (!map_vm_area(pVmArea, PAGE_KERNEL_EXEC,
      |              ^~~~~~~~~~~
      |              get_vm_area
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/SUPDrvTracer.o: warning: objtool: .text+0x7: indirect jump found in RETPOLINE build
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/SUPDrvTracer.o: warning: objtool: supdrvTracerProbeFireStub() is missing an ELF size annotation
cc1: some warnings being treated as errors
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeFree’:
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:596:43: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’?
  596 |                     down_read(&pTask->mm->mmap_sem);
      |                                           ^~~~~~~~
      |                                           mmap_base
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:611:41: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’?
  611 |                     up_read(&pTask->mm->mmap_sem);
      |                                         ^~~~~~~~
      |                                         mmap_base
make[2]: *** [scripts/Makefile.build:280: /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o] Error 1
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeLockUser’:
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1079:31: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’?
 1079 |         down_read(&pTask->mm->mmap_sem);
      |                               ^~~~~~~~
      |                               mmap_base
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1165:33: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’?
 1165 |             up_read(&pTask->mm->mmap_sem);
      |                                 ^~~~~~~~
      |                                 mmap_base
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1192:29: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’?
 1192 |         up_read(&pTask->mm->mmap_sem);
      |                             ^~~~~~~~
      |                             mmap_base
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeMapUser’:
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1607:36: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’?
 1607 |             down_write(&pTask->mm->mmap_sem);
      |                                    ^~~~~~~~
      |                                    mmap_base
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1724:34: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’?
 1724 |             up_write(&pTask->mm->mmap_sem);
      |                                  ^~~~~~~~
      |                                  mmap_base
make[2]: *** [scripts/Makefile.build:280: /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o] Error 1
  LD [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxnetadp/vboxnetadp.o
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/memuserkernel-r0drv-linux.o: warning: objtool: VBoxHost_RTR0MemKernelCopyTo()+0x13: redundant CLD
/var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv/r0drv/linux/memuserkernel-r0drv-linux.o: warning: objtool: VBoxHost_RTR0MemKernelCopyFrom()+0x13: redundant CLD
  LD [M]  /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxnetflt/vboxnetflt.o
make[1]: *** [scripts/Makefile.build:497: /var/lib/dkms/vboxhost/6.1.12_OSE/build/vboxdrv] Error 2
make: *** [Makefile:1756: /var/lib/dkms/vboxhost/6.1.12_OSE/build] Error 2
make: Leaving directory '/usr/lib/modules/5.8.5-2-MANJARO/build'

Similar weirdness with vboxhost as reported, but otherwise no issues on 4 machines. (Don’t have Nvidia, don’t have any VMs at the moment.)

Regarding VirtualBox with kernels 5.8.x: You might find lots of clarification here
https://bugzilla.suse.com/show_bug.cgi?id=1175201
Larry Finger is one of the essential persons who made many versions of Oracle VirtualBox work with Linux. To prove that, just look at the VB changelogs; you will find dozens of “thanks to Larry Finger“.

He explains why VB 6.1.12 doesn‘t work with vanilla kernels 5.8.x. My understanding is that kernel patches exist; it is up to a Linux distribution to go that route or not. On the VB side of this issue, Oracle has not released a functioning version yet; developmental versions 6.1.13 seem to be on the right track, but maybe not completely.

BTW, VMWare is suffering from the same principal issue as VirtualBox.

As mentioned above and reflected by some of you, switching to KVM is a viable option. I just discovered a post in the Support > Virtualization compartment on this forum which points to


Maybe this one and other blogs quoted therein provide the cookbook am looking for. Of course, the Arch Wiki would be considered the primary source of information.

Remark: I am not allowed to insert links on the new forum yet. Need to replace _ above with /.

4 Likes