Trying to instal Virtualbox 7.2 on 6.12.0-160000.20-default:
Tried using version Virtualization repo, … cannot install kernel modules
vboxconfig - not signed [by SuSE]
Signing fails - invalid key [not trusted by SuSE kernel]
Cannot disable Secureboot, no option in BIOS
Grabbed the rpm from Oracle, installs, but modules are not signed
So, … just how does one install Virtualbox kernel drivers on 16?
BTW - the 16 kernel would not accept a MOK signed kernel module when I tried last month, … any chance of notes FOR 16?
hui
November 4, 2025, 9:33pm
5
There are other users in the forum which successfully signed the VB kernel Module for Leap 16, following the mentioned wiki article. The procedure described in the wiki IS for Leap 16.
Leider funktioniert Virtualbox in Leap 16.0 bei aktiviertem Secure Boot nicht mehr. Über Google habe ich schon erfahren, dass man die Kernelmodule dafür selbst signieren muss. Das habe ich aber noch nicht geschafft.
Folgendes habe ich bereits gemacht:
Mit Openssl ein Schlüsselpaar erstellt und den öffentlichen Schlüssel mit Mokutil in die Secure Boot Datenbank importiert. Das hat geklappt.
Wenn ich nun aber versuche, die Kernelmodule mit diesem Schlüsselpaar mittels sign-file aus den Kernelqu…
To get Virtualbox running on Leap 16.0 with secure boot enabled:
I migrated last night from Leap 15.6 to Leap 16.0.
After migration, I added the Virtualization Repo:
zypper ar -f https://download.opensuse.org/repositories/Virtualization/16.0/ virtualization
and installed:
linux64:/home/stephan # LANG=C zypper se -si virtualbox
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+------------------------+---------+--------------------------------------+--------+---------------
i | virtualbox | package | 7.2.4-Virt.1600.2.2 | x86_64 | Virtualization
i+ | virtualbox-kmp-default | package | 7.2.4_k6.12.0_160000.5-Virt.1600.2.2 | x86_64 | Virtualization
i+ | virtualbox-qt | package | 7.2.4-Virt.1600.2.2 | x86_64 | Virtualization
Note: For an extended search including not yet activated remote resources please use 'zypper
search-packages'.
Now I donwloaded the ssl certificate from here:
converted the downloaded Virtualization_cert.pem to virt.crt, copy the virt.crt to /etc/uefi/certs/ and added it to mok database.
stephan@linux64:~/Downloads> openssl x509 -outform der -in Virtualization_cert.pem -out virt.crt
stephan@linux64:~/Downloads> su
Passwort:
linux64:/home/stephan/Downloads # cp virt.crt /etc/uefi/certs/virt.crt
linux64:/home/stephan/Downloads # mokutil --import virt.crt
input password:
input password again:
linux64:/home/stephan/Downloads #
On reboot, the blue mokscreen was opened and I added it to the database.
[key 6]
Owner: 605dab50-e046-4300-abb6-3dd810dd8b23
SHA1 Fingerprint: db:6c:75:e9:a1:8d:64:e4:5c:4a:b7:88:d7:cb:1d:25:5e:25:03:26
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
5b:64:b4:4d:94:b8:44:c2:69:7c:0f:8f:be:4b:99:4b:b1:cd:31:57
Signature Algorithm: sha256WithRSAEncryption
Issuer: CN=Virtualization OBS Project/emailAddress=Virtualization@build.opensuse.org