Cant get virtualbox working/ NS ERROR FAILURE

Joined
Nov 10, 2024
Messages
5
Reaction score
0
Credits
76
(Apologies not terribly tech savvy but giving it a go)
Looking to run windows through an oracle virtualmachine... exept then i run into this.


Screenshot from 2024-11-18 12-30-06.png



turns out efi secure boot is enabled i believe, when i run the /sbin/vboxconfig command i get taken to some other terminal screen :

Screenshot from 2024-11-18 12-59-16.png


Screenshot from 2024-11-18 13-00-05.png


I have no idea what "signing the kernel modules" in this case means or how im supposed to do that?

it asks me to choose a password, i choose a password, although for some reason its now let me choose a password multiple times.... and then it shows me this:
Screenshot from 2024-11-18 12-26-07.png


can't figure out why vboxdrv.sh failed. dmesg shows a huge block of code that doesnt help me cause i dont know what im looking at.

when i restart i get a blue screen "MOK Management" with four options
"continue boot"
"enroll MOK"
"Enroll Key From Disk"
"Enroll hash from Disk"

Enrolled MOK the way the terminal screen mentioned. put in the chosen password. There, however, was no "Change Secure Boot State" Menu as previously indicated i dont believe.
anyway i confirmed the password in the MOK enroll and rebooted linux. Went to run the VM, the initial error code box is no longer there however....
i get this as well

Screenshot from 2024-11-18 13-23-56.png

Im.... just trying to get the VM to work and uhhh idk what to do from here. halp? (thank u) ToT
 

Attachments

  • Screenshot from 2024-11-18 12-59-16.png
    Screenshot from 2024-11-18 12-59-16.png
    62.7 KB · Views: 26


I am not an expert here, but from the look of the information you gave, you have not enabled VT-x.
Let's hope some one going to jump in to help.
 
I am not an expert here, but from the look of the information you gave, you have not enabled VT-x.
Let's hope some one going to jump in to help.
prooooobably shouldve been obvious/self explanatory :I thanks for explaining anyway :)
 
The first error is related to unsigned Virtualbox modules that do not work in Linux host with Secure Boot enabled.
The problem is the requirement that all kernel modules must be signed by a key trusted by the UEFI system, which basically means Microsoft, otherwise loading will fail. Ubuntu does not sign the third party vbox* kernel modules, but rather gives the user the option to disable Secure Boot upon installation of the virtualbox package.

So bottom line is to disable Secure Boot and Fast Boot in the BIOS, and enable VT-x
 

Members online


Top