#vboxconfig
Sources for building host modules are not present,
Use ‘sudo zypper install virtualbox-host-source kernel-devel kernel-default-devel’ to install them. Quitting …
So I follow the instruction and try again.
#vboxconfig
Building kernel modules…
Kernel modules built correctly. They will now be installed.
insmod /lib/modules/5.3.18-59.37-default/weak-updates/extra/vboxdrv.ko
modprobe: ERROR: could not insert ‘vboxnetflt’: Key was rejected by service
insmod /lib/modules/5.3.18-59.37-default/weak-updates/extra/vboxdrv.ko
modprobe: ERROR: could not insert ‘vboxnetadp’: Key was rejected by service
Kernel modules are installed and loaded.
I can’t get VBox running, what would I do to “Key was rejected by service”?
Need I reinstall VBox?
I don’t like to disable secure boot to loss secure, and there are guides for VBox on signing kernel on debian, how’s on opensuse?
You use mokutil to enroll your own certificate and use scripts/sign-file to sign your modules. If your Debian guide suggests something different, you could at least post link to it.
VirtualBox is available for openSUSE in default repositories and these modules are signed by openSUSE key, so no manual steps are required at all. You could start with explaining why you need to compile your own modules for default openSUSE kernel in the first place.
You use mokutil to enroll your own certificate and use scripts/sign-file to sign your modules. If your Debian guide suggests something different, you could at least post link to it.
At main.c:291:
- SSL error:02001002:system library:fopen:No such file or directory: crypto/bio/bss_file.c:69
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: crypto/bio/bss_file.c:76
sign-file: vboxdrv.ko: No such file or directory
Does not work on my Dell 7490 with BIOS 1.21.0. No machine will start.
Secureboot had to be off for VirtualBox on my laptops. It did work with secureboot back in 6.1.14, then it stopped - BIOS back then was 1.16.0. That was a few kernel ago.
My 2 cents.
I did try again last light - no virtualbox machine started - said no virtualbox support in kernel.
Not worth the trouble to diagnose as Larry Finger suggested I turn off secure boot. He is VirtualBox support.
Ensured that the package openSUSE-signkey-cert is installed
Checked already stored keys
mokutil -l
One of CN=openSUSE Secure Boot CA [FONT=arial]or [/FONT][FONT=monospace]CN=SUSE Linux Enterprise Secure Boot CA [FONT=arial]was missing. I don’t remember which one it was.
[/FONT]3. Made
[/FONT]
mokutil -i /etc/uefi/certs/BDD31A9E-kmp.crt
[FONT=arial]
4. [/FONT][FONT=arial]Rebooted and chose to enroll the new key.
LLR1:~ # mokutil -l
[key 1]
Issuer: CN=SUSE Linux Enterprise Secure Boot CA, C=DE, L=Nuremberg, O=SUSE Linux Products GmbH, OU=Build Team/emailAddress=build@suse.de
This is default SUSE certificate used to sign kernel which is embedded in SUSE shim. You do not have openSUSE certificate. KMP built for openSUSE Leap 15.3 are signed by openSUSE key, corresponding certificate is available as /etc/uefi/certs/BDD31A9E-kmp.crt which is included in package openSUSE-signkey-cert. This package is Recommended by Base pattern and should normally be present. During installation it creates certificate enrollment request. Unfortunately, users often miss or ignore MokManager screen on next reboot so this enrollment request does not complete.
Interesting attitude. Instead of solving the cause you work around symptoms.
as Larry Finger suggested I turn off secure boot. He is VirtualBox support.
vboxconfig recreates modules and immediately tries to load them which if course fails because modules are not yet signed. If you used vboxconfig again after having signed modules, you need to sign them again.