Q: VirtualBox error: Kernel driver not installed (rc=-1908) (running ubuntu 20.04 on a chromebook through crouton) When I try to start a virtual machine in VirtualBox, I get the error above. I tried what it asked me to do, but it didn't work. My kernel version is 4.4.232. Also, here is the error message:
The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please reinstall virtualbox-dkms package and load the kernel module by executing

'modprobe vboxdrv'

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. 

Also, it gave me a second error message:
The virtual machine 'linux 2' has terminated unexpectedly during startup with exit code 1 (0x1).


Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

And yes, I am trying to run Linux within Linux, but I know it's not that because I have tried multiple different virtual machines. Also, I am running this Ubuntu 20.04 on my chromebook, so if that's the problem, I'd like a workaround for that. I set it up using crouton on howtogeek.com, if that helps.
I have had the same error messages on Ubuntu 16.04 and Ubuntu 18.04, so the version is not the problem. also, I noticed while reinstalling virtualbox the terminal mentions that my kernel version likely belongs to a chroot's host, so that might be a problem too. If I need a different version of the Linux kernel, I'd like directions to do that because it's probably different for me since I'm using my chromebook.
For anyone who tried running VirtualBox on their chromebook using crouton like I tried and got the same error, from what I've read is that on some devices the chrome OS kernel does not support running virtual machines.

A: I had the same problem after some updates on Ubuntu 20.04.
I solved this problem by manual installation of a recent version of VirtualBox 6.1.16. By default Ubuntu 20.04 is installing 6.1.10.
Go to https://www.virtualbox.org/wiki/Linux_Downloads and read chapter "Debian-based Linux distributions". In brief, you should:
Add a new line to the file /etc/apt/sources.list
deb [arch=amd64] https://download.virtualbox.org/virtualbox/debian focal contrib

Then type these commands:
sudo wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
sudo apt-get update
sudo apt-get install virtualbox-6.1

Probably you need to disable "Secure Boot" in the BIOS as well.

A: I had the exact issue. Fixed it with the following simple commands
sudo apt update
sudo apt install virtualbox

The good thing was that my existing machines were never affected; they still worked fine.

A: I faced this problem in Ubuntu 20.04.
My secure boot was already off and neither I updated my system or the Virtual Box and this issue came out of blue.
I fixed this issue by simply updating and upgrading my host machine -
sudo apt update
sudo apt upgrade


A: Sorry about not answering for so long (I forgot about the question) I was able to get VirtualBox working by installing Gallium OS through Mrchromebox's legacy firmware for my Chromebook.

A: Install VirtualBox 6.1.26 or greater for Linux.
There was a conflict between VirtualBox in previous versions and Ubuntu 20.04

A: I was able to fix the issue by disabling "Secure Boot" in the BIOS.  I am running an Asus Vivobook.  VMs quit working after the update to 20.04 (from 18.04).  They are working now.

A: I fixed this issue by only disabling "Secure Boot" in the BIOS.
( Ubuntu 20.04. and VirtualBox 6.1.18 )

A: I had the same issue and solved it by disabling the secure boot in BIOS settings.
