VBox Machine Won't Start

English Virtualization
1

Hi,
I installed Virtualbox 7.1.4 on my laptop, and then tried to install WinXP to run a simulator program. When I try to start WinXP to install it, I receive this message:

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing

‘/sbin/vboxconfig’

as root.

If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) 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.

I went to /sbin/vboxconfig but find /sbin/vboxconfig isn’t installed on the computer. I’m not sure why it didn’t get installed, nor what to do next. I will need assistance to resolve this problem.

Thanks
Mark

2

Try:

# /usr/sbin/vboxconfig
3

The first question is: from where did you install VB? From the official openSUSE repos?

@larryr might help here.

4

I installed Virtualbox from the official repos using yast2. I selected virtualbox and installed it with all the auto selected dependencies.

I went to /usr/sbin/vboxconfig and executed it. I received this error message when I executed vboxconfig. The virtual machine still doesn’t start, providing the same message as I provided in my first post.

Building kernel modules…
Kernel modules built correctly. They will now be installed.
insmod /lib/modules/6.4.0-150600.23.30-default/weak-updates/extra/vboxdrv.ko
modprobe: ERROR: could not insert ‘vboxnetflt’: Key was rejected by service
insmod /lib/modules/6.4.0-150600.23.30-default/weak-updates/extra/vboxdrv.ko
modprobe: ERROR: could not insert ‘vboxnetadp’: Key was rejected by service
Kernel modules are installed and loaded.

5

Try to disable secure boot in bios.

Is it working?

6

Is package openSUSE-signkey-cert installed?

7

In the bios there are three options 1. Windows secure boot 2. Opensuse secure boot 3. Disable
Option 2 was selected, when I selected 3. Disable the computer won’t boot to any OS nor grub2. I reselected 2. Opensuse secure boot and the computer will boot to grub and then the OS of my choice.

Opensuse-signkey-cert is installed, yes.

8

And have you enrolled the openSUSE certificate too after installing this package? Show

mokutil --list-enrolled
9 
# mokutil --list-enrolled
[key 1]
SHA1 Fingerprint: bc:a4:e3:8e:d1:84:2b:c8:6f:f7:6d:4d:a7:49:51:f1:62:88:59:f8
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number: 1 (0x1)
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: CN=SUSE Linux Enterprise Secure Boot CA, C=DE, L=Nuremberg, O=SUSE Linux Products GmbH, OU=Build Team/emailAddress=build@suse.de
        Validity
            Not Before: Apr 18 14:33:41 2013 GMT
            Not After : Mar 14 14:33:41 2035 GMT
        Subject: CN=SUSE Linux Enterprise Secure Boot CA, C=DE, L=Nuremberg, O=SUSE Linux Products GmbH, OU=Build Team/emailAddress=build@suse.de
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (2048 bit)
                Modulus:
                    00:cd:fd:ab:d7:2a:84:f8:81:c3:36:35:50:35:2c:
                    c7:ec:04:f1:f4:d6:cc:60:4b:c8:13:b3:74:9b:bd:
                    f6:c4:3f:63:3e:66:51:f2:7e:3f:6e:7c:76:7b:71:
                    9d:69:21:2a:15:9b:aa:a5:e5:56:c8:79:98:12:35:
                    cd:7b:63:8c:b8:37:29:ee:77:50:bc:b7:64:8f:fe:
                    26:4a:e5:83:18:1c:6c:5d:b4:87:ef:d7:33:c4:f8:
                    1a:3f:29:9a:84:5a:01:e0:d9:81:6d:31:77:62:29:
                    f5:c1:65:14:df:4a:1d:fb:b7:4a:46:3b:f3:90:8b:
                    a2:b8:26:2a:0a:c3:9e:54:b5:03:60:81:e3:d9:58:
                    35:ed:b0:0b:e2:4f:6b:ef:69:ba:8b:47:df:a4:c5:
                    da:d0:d2:25:aa:85:63:3e:2f:05:db:4c:69:02:a6:
                    0e:35:b3:c2:ae:70:b0:ff:25:80:31:c7:0d:39:74:
                    a3:c0:a4:50:cd:9f:3f:85:b7:62:fb:7b:92:6d:c8:
                    1e:12:d2:ee:0f:96:f4:01:30:d1:ed:e2:10:ec:d2:
                    b2:b8:a1:e1:c5:2d:b3:b1:1e:f8:c5:fa:79:68:9d:
                    e5:a1:92:0f:5e:4f:45:42:7e:90:18:55:8c:fe:c2:
                    13:31:b8:21:de:ac:30:9d:99:e1:6b:44:61:0c:43:
                    3d:75
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Basic Constraints: critical
                CA:TRUE
            X509v3 Subject Key Identifier: 
                EC:AB:0D:42:C4:56:CF:77:04:36:B9:73:99:38:62:96:5E:87:26:2F
            X509v3 Authority Key Identifier: 
                keyid:EC:AB:0D:42:C4:56:CF:77:04:36:B9:73:99:38:62:96:5E:87:26:2F
                DirName:/CN=SUSE Linux Enterprise Secure Boot CA/C=DE/L=Nuremberg/O=SUSE Linux Products GmbH/OU=Build Team/emailAddress=build@suse.de
                serial:01
            X509v3 Key Usage: critical
                Digital Signature, Certificate Sign, CRL Sign
    Signature Algorithm: sha256WithRSAEncryption
    Signature Value:
        12:be:2c:85:85:5a:94:59:cd:49:51:08:17:c1:d9:63:27:29:
        d3:9e:9d:3f:15:03:99:24:14:9e:ed:77:41:18:f9:b2:f7:5f:
        b7:21:3a:ab:5e:0c:aa:a3:fd:b5:f0:a2:12:89:09:79:dd:09:
        70:a6:af:9c:22:21:91:02:26:b5:0f:ba:7b:c1:b8:3b:c2:c8:
        3e:4e:bb:74:cd:91:57:7a:cd:f4:c1:f6:2a:e6:98:df:59:a7:
        44:04:08:0d:09:f7:e4:07:3d:74:4d:28:cb:8d:0a:d5:c1:6e:
        4d:fb:25:09:32:8a:be:af:ce:37:4f:35:79:e8:7b:b2:e8:b0:
        4e:56:12:39:c9:3c:fb:5f:b8:b6:ad:22:58:7f:24:16:33:ca:
        1e:1c:b8:fc:62:5e:4c:ac:e0:7d:83:24:ee:9b:10:78:98:e2:
        e6:4a:ac:0a:cc:98:94:07:4a:69:18:fa:21:74:b5:12:48:42:
        83:76:8e:8a:48:7f:c6:8d:1e:cc:ee:e0:62:73:09:f3:c0:90:
        f7:49:57:d3:f6:7c:7d:1c:a1:76:9d:76:65:1e:fb:39:56:24:
        10:ae:ed:ea:3f:5b:5c:ea:2d:1e:5c:49:cf:4d:85:b6:fb:39:
        19:70:dd:1e:e6:21:f2:a3:31:19:1e:c3:b4:ae:f7:35:a7:a1:
        b4:61:6b:4e
10

You see how others are posting computer text, do not you? What stops you from doing the same and making it more convenient for others to read your posts?

Anyway - you did not enroll openSUSE certificate which is required to verify the signature of the VirtualBox drivers.

https://en.opensuse.org/openSUSE:UEFI#Secure_Boot

11

Hi,
thank you for your reply to my post. In response to your question about posting computer text, no, I don’t know what you are reacting to. Would you please be more instructive and I will correct the issue.

Regarding enrolling the openSUSE certificate, thank you for determining the issue. In the link to the information that you sent, I don’t find instructions to enable the openSUSE certificate if it was not enabled via the blue screen that presents on initial start after installation. How does one enable it now? Please provide specific instructions.

Thanks.

12

Install it:
zypper in -f openSUSE-signkey-cert

reboot and go to the blue MOK Screen.

13

See:
Code-Tags

14

Thanks for the response. Where does one obtain the password required on the blue screen to accept the sign key?

15

Its the root password

16

https://en.opensuse.org/SDB:NVIDIA_drivers#Secureboot

17

Please, to make the pieces of computer code in your posts better consumable by technical oriented people:

And post as complete as possible. That is starting with the line with the prompt and the command, then all output, and ending with the new prompt line.
When you really feel you need to change anything in such a copy, then add that in a comment, else we take all characters literally.

When the text is very long, then you can upload to https://paste.opensuse.org/ .
Or you can use the tool susepaste by piping the output to it ind posting the URL you get.

18

Virtualbox works now. Thanks to everyone for their help.