Frustrated with Virtualbox Error (rc-1908)

Torus detour

New Member
Credits
90
I've been trying to solve this problem for days now. When I try to launch my Virtual Machine in Virtualbox 6.0 I get an error message:

Failed to open a session for the virtual machine llllele.

The virtual machine 'llllele' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}


Furthermore:
Kernel driver not installed (rc=-1908)
The Virtualbox Linux kernel is either not loaded or not setup 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: sublibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED
(-1908) - The support driver is not installed. On linux, open returned
ENOENT.


can somebody please explain to me, how to sign these virtualbox modules, so my system doesn't think oracle products are viruses? I've looked in my BIOS and secure boot is disabled or more accurately, it's not even an option, but I definitely do run in Legacy mode. I've also tried:
Code:
sudo apt-get install linux-headers-$(uname -r)
Code:
sudo apt-get install dkms
Code:
sudo /usr/lib/virtualbox/vboxdrv.sh setup
But in that last command it said:
Code:
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: failed: Cannot change group vboxusers for device /dev/vboxdrv.
Any ideas, what I could try. I'm farely new to Linux and for now getting authentication keys setup, so my software has the access it needs is kind of above my level of knowledge.
 


jpnilson

Member
Credits
469
My gut feeling here is that your virtual box installation has some profound issues. If you have administrative control of the box you are trying to resolve this on I would uninstall and reinstall virtual box from scratch. I would point you toward some installation instructions but have no idea what flavor of linux you are using.
 

Torus detour

New Member
Credits
90
My gut feeling here is that your virtual box installation has some profound issues. If you have administrative control of the box you are trying to resolve this on I would uninstall and reinstall virtual box from scratch. I would point you toward some installation instructions but have no idea what flavor of linux you are using.
I'm using Linux Mint 18 and I've already reinstalled Virtualbox from scratch about five times and I'm still having the problem. I have read in a MacOS forum, that this issue is because the oracle software is unsigned and by signing it yourself, you can resolve this issue. I would try this next, but I don't know how to do it.
 

jpnilson

Member
Credits
469
I'm using Linux Mint 18 and I've already reinstalled Virtualbox from scratch about five times and I'm still having the problem. I have read in a MacOS forum, that this issue is because the oracle software is unsigned and by signing it yourself, you can resolve this issue. I would try this next, but I don't know how to do it.
I found some instructions here on how to install. I will have to poke around to see if i have some hardware to install this on. I would usually just spin up a VM but suspect attempting to run a hypervisor inside of a hypervisor may cause some problems... :) Actually sounds like a fun experiment
 

jpnilson

Member
Credits
469
After a bit more looking I think you have two options.
#Option 1: Use the options listed in the article above. I also found similar instructions in multiple other articles. Before executing these you would would to completely remove you virtual box installation using "sudo apt purge <virtual box version you have installed>

Step 1
echo "deb http://download.virtualbox.org/virtualbox/debian bionic contrib" | sudo tee -a /etc/apt/sources.list

Step 2
wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -

Step 3
wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -

Step 4
sudo apt update

Step 5
sudo apt install virtualbox-6.1

#Option 2 Install Mint 20 OS. Doing that you don't have to do all the business above. In version 20 the repository for virtualbox is native and you can simply use step 5.
 

Torus detour

New Member
Credits
90
My gut feeling here is that your virtual box installation has some profound issues. If you have administrative control of the box you are trying to resolve this on I would uninstall and reinstall virtual box from scratch. I would point you toward some installation instructions but have no idea what flavor of linux you are using.
I'm using Linux Mint 18 and I've already reinstalled Virtualbox from scratch about five times and I'm still having the problem. I have read in a MacOS forum, that this issue is because the oracle software is unsigned and by signing it yourself, you can resolve this issue. I would try this next, but I don't know how to do it.
Have you added yourself to the VBOX User Group?
Code:
sudo usermod -a -G vboxusers username
Reboot
Also have a look here
I can't:
Code:
usermod: group 'vboxusers' does not exist
 

Lord Boltar

Well-Known Member
Credits
5,958
The usermod command of some older Linux distributions does not support the -a option, which adds the user to the given group without affecting membership of other groups try it without the -a option
Code:
sudo usermod -G vboxusers username
You can find out the current group memberships with the groups command
Code:
groups username
and add all these groups in a comma-separated list to the command line after the -G option. For example: sudo usermod -G group1,group2,vboxusers username.
Also look under System for Users and Groups you can use that as well
 
Last edited:

Torus detour

New Member
Credits
90
After a bit more looking I think you have two options.
#Option 1: Use the options listed in the article above. I also found similar instructions in multiple other articles. Before executing these you would would to completely remove you virtual box installation using "sudo apt purge <virtual box version you have installed>

Step 1
echo "deb http://download.virtualbox.org/virtualbox/debian bionic contrib" | sudo tee -a /etc/apt/sources.list

Step 2
wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -

Step 3
wget -q https://www.virtualbox.org/download/oracle_vbox.asc -O- | sudo apt-key add -

Step 4
sudo apt update

Step 5
sudo apt install virtualbox-6.1

#Option 2 Install Mint 20 OS. Doing that you don't have to do all the business above. In version 20 the repository for virtualbox is native and you can simply use step 5.
Oh No...
That just made it worse. Now it's rc(-1912), the error message I had before -1908, to wich I didn't even find a forum thread discussing it anywhere.
 

Torus detour

New Member
Credits
90
The usermod command of some older Linux distributions does not support the -a option, which adds the user to the given group without affecting membership of other groups try it without the -a option
Code:
sudo usermod -G vboxusers username
You can find out the current group memberships with the groups command
Code:
groups username
and add all these groups in a comma-separated list to the command line after the -G option. For example: sudo usermod -G group1,group2,vboxusers username.
Also look under System for Users and Groups you can use that as well
After reinstalling vbox like @jpnilson suggested the usermod command now works, but as I said, now I have another problem.
 

Tolkem

Well-Known Member
Credits
8,516
I suggest you give try to QEMU, which, IMHO, works better than VBox. To install in Mint, launch a terminal and type
Code:
sudo apt install qemu qemu-utils
press Enter, type in your password when asked and press Enter again to start the installation. If you want a GUI, then install virt-manager too
Code:
sudo apt install libvirt-daemon-system libvirt-clients bridge-utils virt-manager
press Enter, type in your password when asked and press Enter again to start the installation. Then add your user to the ‘libvirt’ and ‘kvm’ groups
Code:
sudo usermod -aG libvirt your_username
press Enter, type in your password when asked and press Enter again, next type
Code:
sudo usermod -aG kvm your_username
press Enter, type in your password when asked and press Enter again. Replace your_username with, well, your Mint's username. This is how virt-manager looks like

I took that img from https://developers.redhat.com/blog/2020/03/06/configure-and-run-a-qemu-based-vm-outside-of-libvirt Which you can refer to for a basic understanding on how to run and configure VMs in virt-manager.
 

Lord Boltar

Well-Known Member
Credits
5,958
Oh No...
That just made it worse. Now it's rc(-1912), the error message I had before -1908, to wich I didn't even find a forum thread discussing it anywhere.
First remove Oracle virtualbox
I see where you are installing VirtualBox 6.1 on Mint 18 this may not compatible I think you are installing the one for Focal - Linux Mint 18 is based on Xenial and no longer supported but you can still get VirtualBox for Xenial - go here - https://www.virtualbox.org/wiki/Downloads - and first download VirtualBox 6.1.26 Oracle VM VirtualBox Extension Pack and click on "All supported platforms" after that is downloaded look up and you will see VirtualBox 6.1.26 platform packages and click on "Linux distributions" - next click on "Ubuntu 16.04" to download it will be a .deb file - once downloaded use Gdebi Package Installer to install the .deb file - Gdebi will also get any dependencies needed once finished you will have to install the Extension pack you can do this by double clicking it - then add yourself to the vbox user group
 

jpnilson

Member
Credits
469
Look at this article. https://askubuntu.com/questions/900794/virtualbox-rtr3initex-failed-with-rc-1912-rc-1912. Basically I think there are still remnants of your old virtualbox installation. When you do the purge of the old you need to read the warning messages. If you see something that was not removed because they still contains files. You will want to get rid of everything. Part of the article shows you how to diagnose the issue. If you can back up your data and upgrade the machine with a clean install of mint 20 I think you would have a lot fewer problems. I know its a pain but sometimes a clean start takes less time than poking around for the needle in a haystack
 
$100 Digital Ocean Credit
Get a free VM to test out Linux!

Staff online

Members online


Top