Cant get virtualbox working/ NS ERROR FAILURE

[noob-buntu_orangeJoe]

(Apologies not terribly tech savvy but giving it a go)
Looking to run windows through an oracle virtualmachine... exept then i run into this.

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

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:

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

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

 

[ML_113]

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.

 

[Brickwizard]

but from the look of the information you gave, you have not enabled VT-x

agreed

 

[noob-buntu_orangeJoe]

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

 

[GatorsFan]

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

 

[jpnilson]

Second the previous disable secure boot. It is possible to use secure boot but in my opinion it isn't worth the effort

 

[dos2unix]

First see if you can disable it.

sudo mokutil --disable-validation

Then see if you can update it.

sudo apt-get --reinstall install virtualbox-dkms

You will likely have to rebuild the kernel module

sudo /sbin/vboxconfig

If none of that works...

cat /var/log/vbox-install.log

 

[KGIII]

This is a pretty old thread. OP has likely moved n at this point.

Also, all they needed to do was reboot and enter their password when prompted.