Sign-file error when signing key for VirtualBox

Ask Fedora
,
1

I installed Virtualbox through RPM repo and had the akmod installed with it:

$ sudo akmods
Checking kmods exist for 6.13.10-200.fc41.x86_64 [  OK  ]

I then succesfully create the key and enroll it, but when I try to sign the module it is always giving me:

$ sudo /usr/src/kernels/$(uname -r)/scripts/sign-file sha256 /lib/modules/6.13.10-200.fc41.x86_64/build/certs/MOK.key /lib/modules/6.13.10-200.fc41.x86_64/build/certs/MOK.crt vboxdrv.ko
At main.c:302:
- SSL error:FFFFFFFF80000002:system library::No such file or directory: crypto/bio/bss_file.c:67
- SSL error:10000080:BIO routines::no such file: crypto/bio/bss_file.c:75
sign-file: vboxdrv.ko

VirtualBox says:

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is probably not loaded.You may not have kernel driver installed for kernel that is runnig, if so you may do as root: dnf install akmod-VirtualBox kernel-devel-$(uname -r)If you installed VirtualBox packages and don’t want reboot the system, you may need load the kernel driver, doing as root: akmods; systemctl restart vboxdrv.service

If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp) before you can load them. Please see your Linux system’s documentation for more information.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.

Needless to say, I have secure boot on and don’t want to disable it. This didn’t cause an issue in my other system (intel laptop), but happened on this new system (AMD, if it matters).

I have tried generating the keys in different locations, checked openssl symlinks, checked file permissions, but nothing worked :frowning:

1 Like
2

If the issue persists, check the output:

sudo systemctl restart akmods.service
sudo systemctl status akmods.service
sudo mokutil -t /etc/pki/akmods/certs/public_key.der
sudo dnf remove kmod-VirtualBox-$(uname -r) -y
sudo akmods --force
1 Like
3

It didn’t give any error but didn’t resolve the issue:

$ sudo systemctl restart akmods.service
$ sudo systemctl status akmods.service
â—Ź akmods.service - Builds and install new kmods from akmod packages
     Loaded: loaded (/usr/lib/systemd/system/akmods.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf, 50-keep-warm.conf
     Active: active (exited) since Sat 2025-04-12 19:09:56 EDT; 17s ago
 Invocation: ea7d8719ca944313b2fdf57a4c7c4de8
    Process: 5469 ExecStart=/usr/sbin/akmods --from-init (code=exited, status=0/SUCCESS)
   Main PID: 5469 (code=exited, status=0/SUCCESS)
   Mem peak: 7.2M
        CPU: 32ms

Apr 12 19:09:56 fedora systemd[1]: Starting akmods.service - Builds and install new kmods from akmod packages...
Apr 12 19:09:56 fedora akmods[5469]: Checking kmods exist for 6.13.10-200.fc41.x86_64 [  OK  ]
Apr 12 19:09:56 fedora systemd[1]: Finished akmods.service - Builds and install new kmods from akmod packages.

$ sudo mokutil -t /etc/pki/akmods/certs/public_key.der
/etc/pki/akmods/certs/public_key.der is not enrolled

$ sudo dnf remove kmod-VirtualBox-$(uname -r) -y
Package                                                          Arch           Version                                                          Repository                               Size
Removing:
 kmod-VirtualBox-6.13.10-200.fc41.x86_64                         x86_64         7.1.6-1.fc41                                                     @commandline                        207.3 KiB

Transaction Summary:
 Removing:           1 package

After this operation, 207 KiB will be freed (install 0 B, remove 207 KiB).
Running transaction
[1/2] Prepare transaction                                                                                                                             100% |  15.0   B/s |   1.0   B |  00m00s
[2/2] Removing kmod-VirtualBox-6.13.10-200.fc41.x86_64-0:7.1.6-1.fc41.x86_64                                                                          100% |   1.0   B/s |   5.0   B |  00m04s
Complete!

$ sudo akmods --force
Checking kmods exist for 6.13.10-200.fc41.x86_64 [  OK  ]
Building and installing VirtualBox-kmod [  OK  ]
4

You need to enroll the MOK key:

1 Like
5

Yup, worked like a charm. Thanks a lot!

1 Like