I was in the process of installing Virtualbox and because I have secure boot activated, the system does not provide the tools for the automatic generation of keys needed for module signing, which is why I had to generate these keys manually from the command line. commands:
The commands used to create the keys were:
However, I forgot (according to me not) the MOK password to be able to correctly add the keys, so I have not been able to return to the form to enter the password since I got tired of trying and left the menu, however now when I restart it does not return me to that menu again but it takes me directly to the desktop (as it normally did), and I don’t know how to try to enter the password again, is it necessary to import the key again? or what can I do in this case? I summarize my questions:
How can I return to the form where it asks me for the MOK password to continue correctly to try again.
In case you cannot return to that menu with the MOK password form, is it necessary to import the key again? Is it overwritten or what would happen?
If I can return to the form and the MOK password does not work again, how can I change it?
Unstated, but useful, is that if you installed virtualbox from rpmfusion then the instructions in the file /var/share/doc/akmods/README.secureboot give all the steps to create and enroll the key with mokutil. Following that initial enrollment then akmods does the automatic updates required to compile and sign the modules with every kernel upgrade.
I used the command you provided, however when I run it, I receive the following error as output:
Job for vboxdrv.service failed because the control process exited with error code.
Since it hasn’t worked, should I revert the changes made with the command? or it is not problematic
using systemctl status vboxdrv.service I receive the following information:
vboxdrv.service - VirtualBox Linux kernel module
Loaded: loaded (/usr/lib/virtualbox/vboxdrv.sh; enabled; preset: disabled)
Active: failed (Result: exit-code) since Mon 2023-10-09 09:37:18 -05; 6min ago
Process: 13871 ExecStart=/usr/lib/virtualbox/vboxdrv.sh start (code=exited, status=1/FAILURE)
oct 09 07:37:17 hrq vboxdrv.sh: vboxdrv.sh: Starting VirtualBox services.
oct 09 07:37:17 hrq vboxdrv.sh: vboxdrv.sh: You must sign these kernel modules before using VirtualBox:
oct 09 07:37:17 hrq vboxdrv.sh: vboxdrv vboxnetflt vboxnetadp
oct 09 07:37:17 hrq vboxdrv.sh: See the documentation for your Linux distribution..
oct 09 07:37:17 hrq vboxdrv.sh: You must sign these kernel modules before using VirtualBox:
vboxdrv vboxnetflt vboxnetadp
See the documentation for your Linux distribution..
oct 09 07:37:18 hrq vboxdrv.sh: vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
oct 09 07:37:18 hrq systemd: vboxdrv.service: Control process exited, code=exited, status=1/FAILURE
oct 09 07:37:18 hrq systemd: vboxdrv.service: Failed with result 'exit-code'.
oct 09 07:37:18 hrq systemd: Failed to start vboxdrv.service - VirtualBox Linux kernel module.
oct 09 07:37:18 hrq systemd: vboxdrv.service: Consumed 1.745s CPU time.