VBoxManage is unable to start vm code NS_ERROR_FAILURE ubuntu 16.04

Question

I recently upgraded to virtualbox 5.2.4 and vagrant 2.0.1 because of this issue. Since then, I haven't been able to run any of my vagrant boxes (some ubuntu, some centos). I get the following error when running vagrant up:

There was an error while executing VBoxManage, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "ef47d1fc-4ed1-42cb-b564-09bc2bb43296", "--type", "headless"]

Stderr: VBoxManage: error: The virtual machine 'ishbook-centos' has terminated unexpectedly during startup with exit code 1 (0x1) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

When I just run vboxmanage without --type headless, I get a popup saying to run /sbin/vboxconfig.

RTR3InitEx failed with rc=-1912 (rc=-1912)

The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing

'/sbin/vboxconfig'

may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox.

where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.

No luck even after running sudo /sbin/vboxconfig multiple times.

I've tried reinstalling virtualbox and the extension pack multiple times and reinstalling linux-headers and dkms as seen in answers to questions similar to this one, but nothing has worked. Any ideas?

Edit: Just tried it out on 5.1, but it's the same error, 5.0 just hangs my computer

score 12 · Accepted Answer · answered Jan 16 '18 at 17:34

12

OK. Figured out the problem here. My kernel modules hadn't been deleted from the previous install of virtualbox when I uninstalled. So when I ran modinfo vboxdrv, it said I was using the kernel drivers for 5.0.4.

I deleted everything in the path to the filename given in the modinfo output and rebooted. Installing virtualbox and starting vms worked after that.

answered Jan 16 '18 at 17:34

1419636215

360

1

Same thing worked by uninstalling the package virtualbox-dkms and then force-reinstall (or uninstal and install) virtualbox-X.Y – tudor -Reinstate Monica- Jun 10 '19 at 03:35
This worked for me in an 5.2 >> 6.1 upgrade – sola Sep 29 '20 at 14:58

score 2 · Answer 2 · answered Sep 28 '18 at 12:30

2

I found that a simple uninstall and reinstall of both VirtualBox and Vagrant solved this issue.

Each of the installers come with a uninstall script for convenience. Run this before installing. Ideally from a fresh boot of your system to ensure VirtualBox is not running.

answered Sep 28 '18 at 12:30

kylewelsby

121

I believe this works in most cases, but kernel modules aren't deleted by default and can carry over from previous versions, which is what caused the issue in my case – 1419636215 Sep 28 '18 at 16:23

score 2 · Answer 3 · answered Apr 08 '20 at 17:11

2

I faced the same issue, I ran sudo /sbin/vboxconfig command in terminal and after its successful execution, I was able to start the vm.

answered Apr 08 '20 at 17:11

Mahendra B

121

score 0 · Answer 4 · answered Mar 29 '18 at 22:59

0

Just had an issue where a system update clobbered my Virtual XP, giving the "rc=-1912" error, the suggestion of reinstalling, etc. What I found worked was sudo apt-get update sudo apt-get upgrade Seemingly overly simple but worked here!

answered Mar 29 '18 at 22:59

BJM

31

score 0 · Answer 5 · answered Oct 10 '19 at 21:00

I had faced the same issue in macOS Mojave 10.14.6 and virtual box

Restart the Mac into Recovery Mode by rebooting and holding down COMMAND + R keys concurrently At the “Utilities” screen, pull down the ‘Utilities’ menu and choose “Terminal” to launch terminal from Recovery Mode Enter the following command:

spctl kext-consent add VB5E2TV963

Hit Return, then restart the Mac with a normal boot as usual

VB5E2TV963 this is the code for Oracle, found it raw but it worked for me...

score 0 · Answer 6 · edited Jun 14 '20 at 16:02

0

Run:

VBoxManage startvm name --type=headless

Found it here: The virtual machine has terminated unexpectedly during startup because of signal 6.

edited Jun 14 '20 at 16:02

Eliah Kagan

117,780

answered Jun 14 '20 at 12:27

bugz

21

1

I am not sure why the downvotes. You get the exact same error message if you tried to start a VM on a remote machine and forgot the --type=headless parameter. – iwarv Jun 07 '21 at 08:02

score 0 · Answer 7 · edited Jan 15 '18 at 06:25

0

Try running it with root permissions through sudo:

sudo /sbin/vboxconfig

It worked on my case.

edited Jan 15 '18 at 06:25

derHugo

3,356
5
31
51

answered Jan 14 '18 at 15:16

gerzenstl

101
2

I guess I didn't mention that I ran it with sudo in the question. BTW it prompts you for your password on each command anyway. – 1419636215 Jan 15 '18 at 16:18

VBoxManage is unable to start vm code NS_ERROR_FAILURE ubuntu 16.04

7 Answers7

Linked