Hi
Very likely the issue, since your running a bleeding edge kernel on your Leap system, you might want to ask direct with Larry as the openSUSE virtualbox maintainer?
The same error is here, I can not say if it is with Installation of kernel 5.8 or an update from 5.8.0-1 to 5.8.0-2, because I had not running it for a longer time.
My Virtualbox is build in my Repo as branch from Virtualization Repo.
When you install Virtualbox from an openSUSE repo, normally the kernel modules are pre-built against the kernel that’s provided by default (note how I tried to clarify by the specific wording).
I think I see you’re using Virtualbox from an openSUSE repo with a kernel that’s different than what is installed from the OSS which ordinarily won’t work.
If you insist on running your own kernel selection,
I’m pretty sure you have to install Virtualbox from the Oracle website so that your kernel modules are built on demand during your installation.
And, although not relevant to your current error, it looks like you haven’t been installing your Extension Pack as well.
@TSU
the kernel modules do match the running kernel of course:
[08:20:00 @ Fr Aug 07]mediapc@Rechenzwerg~/]$uname -a
Linux Rechenzwerg 5.8.0-lp152.2.g9bc0044-default #1 SMP Tue Aug 4 07:30:59 UTC 2020 (9bc0044) x86_64 x86_64 x86_64 GNU/Linux
[08:29:34 @ Fr Aug 07]mediapc@Rechenzwerg~/]$modinfo vboxdrv
filename: /lib/modules/5.8.0-lp152.2.g9bc0044-default/extra/vboxdrv.ko
version: 6.1.12_SUSE r139181 (0x002d0001)
license: GPL
description: Oracle VM VirtualBox Support Driver
author: Oracle Corporation
suserelease: openSUSE Tumbleweed
srcversion: BDEB9E7CD30684FC70310D2
depends:
retpoline: Y
name: vboxdrv
vermagic: 5.8.0-lp152.2.g9bc0044-default SMP mod_unload modversions
sig_id: PKCS#7
signer: home:Herbster0815 OBS Project
sig_key: 30:5D:31:26:30:24:06:03:55:04:03:0C:1D:68:6F:6D:65:3A:48:65:
72:62:73:74:65:72:30:38:31:35:20:4F:42:53:20:50:72:6F:6A:65:
63:74:31:33:30:31:06:09:2A:86:48:86:F7:0D:01:09:01:16:24:68:
6F:6D:65:3A:48:65:72:62:73:74:65:72:30:38:31:35:40:62:75:69:
6C:64:2E:6F:70:65:6E:73:75:73:65:2E:6F:72:67:02:09:00:FB:08:
D9:B6:7F:C7:78:6A
sig_hashalgo: sha256
signature: 70:C1:7C:36:93:5F:93:CC:EC:4B:7E:C0:BD:E0:55:AB:3E:8D:92:38:
AA:E7:02:25:F3:BA:EE:99:6F:52:98:C8:C1:20:F2:36:58:D8:77:3B:
18:40:21:64:95:AF:EB:B3:0E:ED:89:31:19:BD:FD:85:CB:A5:FE:59:
CE:3F:6E:12:02:49:E0:AD:29:3E:80:D9:0F:E8:0D:5B:8F:95:B2:3A:
37:67:FF:92:D7:87:5F:B2:B6:11:9D:56:29:5C:34:D8:D2:3E:A1:3F:
56:0D:3D:2E:51:4D:62:26:F3:B8:FF:07:12:39:B6:B1:B8:06:D1:F0:
D1:48:A4:80:0A:5E:0F:C3:E3:7B:DD:C5:92:5E:5B:25:C8:8E:62:54:
89:43:17:0E:FE:03:68:C4:FD:B5:E8:08:EE:02:D3:B6:6A:0F:7E:99:
1C:2E:A9:46:56:92:67:D6:97:75:6D:7A:AD:05:BA:6B:3D:60:2D:3C:
67:B7:1F:78:26:42:97:91:27:77:95:C8:86:B4:05:ED:0E:19:F2:26:
58:21:71:6C:63:BC:76:4D:17:C1:B5:F8:73:AE:6D:BD:20:A2:E6:04:
59:DF:94:DB:83:AC:1B:EF:DC:59:6E:88:60:53:B4:FB:2C:8D:D1:D3:
9D:60:FB:BC:FC:75:C2:11:94:AA:14:D0:22:30:A7:FE
parm: force_async_tsc:force the asynchronous TSC mode (int)
[08:30:15 @ Fr Aug 07]Herbie@Rosstheboss~/]$uname -a
Linux Rosstheboss 5.8.0-Own #2 SMP Fri Aug 7 07:49:21 CEST 2020 x86_64 x86_64 x86_64 GNU/Linux
[08:30:17 @ Fr Aug 07]Herbie@Rosstheboss~/]$modinfo vboxdrv
filename: /lib/modules/5.8.0-Own/misc/vboxdrv.ko
version: 6.1.12_SUSE r139181 (0x002d0001)
license: GPL
description: Oracle VM VirtualBox Support Driver
author: Oracle Corporation
suserelease: openSUSE Tumbleweed
srcversion: BDEB9E7CD30684FC70310D2
depends:
retpoline: Y
name: vboxdrv
vermagic: 5.8.0-Own SMP mod_unload modversions
parm: force_async_tsc:force the asynchronous TSC mode (int)
The extension pack is not needed to run a VM:
Support for USB 2.0 and USB 3.0 devices, VirtualBox RDP, disk encryption, NVMe and PXE boot for Intel cards. See this chapter from the User Manual for an introduction to this Extension Pack. The Extension Pack binaries are released under the VirtualBox Personal Use and Evaluation License (PUEL). Please install the same version extension pack as your installed version of VirtualBox.
Tried both, Tumbleweed and Leap. It works fine if you use the dev version. Yey, I have my pihole back
● ubuntu-pihole.service - VM Ubuntu-Pihole
Loaded: loaded (/etc/systemd/system/ubuntu-pihole.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2020-08-07 09:17:15 CEST; 4s ago
Process: 17989 ExecStart=/usr/bin/VBoxManage startvm Ubuntu-Pihole --type headless (code=exited, status=0/SUCCESS)
Tasks: 38
CGroup: /system.slice/ubuntu-pihole.service
├─18003 /opt/VirtualBox/VBoxXPCOMIPCD
├─18009 /opt/VirtualBox/VBoxSVC --auto-shutdown
└─18025 /opt/VirtualBox/VBoxHeadless --comment Ubuntu-Pihole --startvm 119106e6-3f31-46da-b1c4-ee4e3b3528c5 --vrde config
Aug 07 09:17:15 Rechenzwerg systemd[1]: Starting VM Ubuntu-Pihole...
Aug 07 09:17:15 Rechenzwerg VBoxManage[17989]: Waiting for VM "Ubuntu-Pihole" to power on...
Aug 07 09:17:15 Rechenzwerg VBoxManage[17989]: VM "Ubuntu-Pihole" has been successfully started.
Aug 07 09:17:15 Rechenzwerg systemd[1]: Started VM Ubuntu-Pihole.
Unfortunately I had to do do a rollback on the Leap system. The machine froze or went in a reboot loop. So I disabled my repo conatining virtualbox- and kernel-packages and installed the ones shipped with Leap by default:
Same problem here on Tumbleweed. zypper dup installed kernel 5.8.0-1.1 and also an update for Virtual Box (virtualbox-kmp-default-6.1.12_k5.8.0_1-1.6), but trying to start a VM also results in “Failed to load R0 module” message. Since I need the VM while in Home Office I rolled back to kernel 5.7.11 and locked Kernel and VBox updates for now.
Yes, and should be able to run on older 5.7 kernel (if you have it).
Looking up VBox bug reports, our (openSUSE) Lfinger who maintains the openSUSE version identified the kernel 5.8 problem about a month before 5.8 scheduled release and almost heroically pushed hard for a resolution but no resolution was found.
But, don’t blame this entirely (or maybe at all) on Virtualbox, apparently there is currently no resolution for VMware, either.
I read a hint that KVM has something special written into the kernel so it’s not broken.
The basic problem seems to be related to some extreme tightening in security between kernel modules and the initrd since approx kernel 5.5, apparently kernel 5.8 finally closed the “loophole” 3rd party virtualization products had been relying on.
I didn’t locate any discussion by kernel maintainers related to this, so there may be an impasse.
Since yesterday VMware went ahead and announced their next version will be released shortly, there is a suspicion that VMware figured out some solution.
