New kernel 5.8.3-towo.1-siduction-amd64 fails to build virtualbox-6.1.12 modules

paco · 2020/08/21, 21:45:28

Be careful,the new kernel 5.8.3-towo.1-siduction-amd64 fails to build virtualbox-6.1.12 modules!

Building module:cleaning build area...
make -j12 KERNELRELEASE=5.8.3-towo.1-siduction-amd64 -C /lib/modules/5.8.3-towo.1-siduction-amd64/build M=/var/lib/dkms/virtualbox/6.1.12/build....(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.8.3-towo.1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.12/build/make.log for more information.
.
Setting up linux-image-5.8.3-towo.1-siduction-amd64 (5.8-3) ...
I: /vmlinuz is now a symlink to boot/vmlinuz-5.8.3-towo.1-siduction-amd64
I: /initrd.img is now a symlink to boot/initrd.img-5.8.3-towo.1-siduction-amd64
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 5.8.3-towo.1-siduction-amd64:
Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j12 KERNELRELEASE=5.8.3-towo.1-siduction-amd64 -C /lib/modules/5.8.3-towo.1-siduction-amd64/build M=/var/lib/dkms/virtualbox/6.1.12/build....(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.8.3-towo.1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.12/build/make.log for more information.

sunrat · 2020/08/22, 02:08:21

This often happens with major point upgrades eg. 5.7 to 5.8. Nvidia drivers almost always have the same problem.
Lucky you still have the 5.7 kernel to boot while you are waiting for VBox to catch up.

axt · 2020/08/22, 18:57:00

Zitat von: sunratThis often happens with major point upgrades

Right. But this time, kernel 5.8, it takes a long time until a fixed VBox appears.

Zitat von: pacofails to build virtualbox-6.1.12 modules

As long as not even the original has completely usable fixes (they don't really take it seriously here), nothing will be solved. Nevertheless you should use the original, but current 6.1.13 test builds.

Linux host with kernel 5.8.3 (in my case Arch based) and Linux VMs →OK

But Win10 20h1 in a VM not only freezes the VM, but brutally freezes the entire system. Reproducible, after one minute at the latest (logs or workloads show nothing abnormal). No matter which settings or tricks are used for testing.

The same VM runs without issues with kernel 5.4 (LTS kernel) and before with 5.7.

In short words: You can use Linux/Linux.

samoht · 2020/08/23, 20:03:56

@axt,

Zitat... But Win10 20h1 in a VM not only freezes the VM, but brutally freezes the entire system ...

Bad luck for you, with your arch kernel.
I use the latest towo kernel, as usual in siduction.
Here Win 10 runs stable in a current Oracle vbox testbuild.

Mte90 · 2020/08/24, 17:02:02

I had to remove the 5.8.3 kernel and also

Code Auswählen

linux-headers-siduction-amd64 package to be able to

Code Auswählen

apt install virtualbox-dkms --reinstallSo the modules is compiled right also for the other kernel versions.

devil · 2020/09/05, 08:19:46

VirtualBox 6.1.14 works with Kernel 5.8. https://www.phoronix.com/scan.php?page=news_item&px=Oracle-VirtualBox-6.1.14

vilde · 2020/09/05, 10:23:18

Zitat von: devil in 2020/09/05, 08:19:46
VirtualBox 6.1.14 works with Kernel 5.8. https://www.phoronix.com/scan.php?page=news_item&px=Oracle-VirtualBox-6.1.14

Tank you devil, good news
Edited, not in the repos yet.

devil · 2020/09/05, 21:42:04

I use the .run straight from Oracle.

vilde · 2020/09/06, 00:31:51

Zitat von: devil in 2020/09/05, 21:42:04
I use the .run straight from Oracle.

Yes, I found it, I will install that, thanks

bevo · 2020/09/06, 10:03:54

I get this message

Code Auswählen

root@x230:/home/bevo# /home/bevo/VirtualBox-6.1.14-140239-Linux_amd64.run 
bash: /home/bevo/VirtualBox-6.1.14-140239-Linux_amd64.run: Keine Berechtigung

What I am doing wrong?
bevo

dpanter · 2020/09/06, 14:04:22

Most likely missing execute permission.

Code Auswählen

sudo chmod +x VirtualBox-6.1.14-140239-Linux_amd64.run

sunrat · 2020/09/07, 01:01:00

An alternative would be to use KVM/QEMU with Virt-Manager instead. No module problems! It's quite easy to use although different from VBox so has a small learning curve.

bevo · 2020/09/07, 08:58:12

updated to virtualbox 6.1.14-dfsg-1 also not working.

Code Auswählen

virtualbox.service - LSB: VirtualBox Linux kernel module
     Loaded: loaded (/etc/init.d/virtualbox; generated)
     Active: failed (Result: exit-code) since Mon 2020-09-07 08:41:14 CEST; 10ms ago
       Docs: man:systemd-sysv-generator(8)
    Process: 8589 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)

towo · 2020/09/07, 09:54:21

Code Auswählen

dpkg -l | grep dkms
dkms status

show that

bevo · 2020/09/07, 11:35:47

Code Auswählen

root@x230:/home/bevo# dpkg -l | grep dkms
ii  dkms                                          2.8.3-4                        all          Dynamic Kernel Module Support Framework
ii  virtualbox-dkms                               6.1.14-dfsg-1                  amd64        x86 virtualization solution - kernel module sources for dkms
ii  virtualbox-guest-dkms                         6.1.14-dfsg-1                  all          x86 virtualization solution - guest addition module source for dkms
root@x230:/home/bevo# dkms status
virtualbox, 6.1.14: added
virtualbox-guest, 6.1.14: added
root@x230:/home/bevo#