VirtualBox

Opened 7 years ago

Last modified 4 years ago

#16287 closed defect

Error when starting a new VM — at Version 4

Reported by: Z Hopa Owned by:
Component: other Version: VirtualBox 5.1.10
Keywords: fail Cc:
Guest type: BSD Host type: Linux

Description (last modified by Frank Mehnert)

Just did a fresh vanilla install of Fedora 25. Once it was up, went to Oracle and downloaded VirtualBox 5.1.10 for Fedora 25. Installed it, installed the extension pack, and rebooted. Then created a new VM. This VM does not start and throws the following errors:

First error dialog:

Failed to open a session for the virtual machine FreeBSD 9.

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

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

Second error dialog (they pop up simultaneously):

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/sbin/vboxconfig'

as root.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. 

When I run the command it recommends, it prints the following:

[user0@host0 ~]$ sudo /sbin/vboxconfig
[sudo] password for use0: 
Created symlink /etc/systemd/system/multi-user.target.wants/vboxdrv.service → /usr/lib/systemd/system/vboxdrv.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxballoonctrl-service.service → /usr/lib/systemd/system/vboxballoonctrl-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxautostart-service.service → /usr/lib/systemd/system/vboxautostart-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb-service.service → /usr/lib/systemd/system/vboxweb-service.service.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:

  yum install kernel-core-devel-4.8.13-300.fc25.x86_64
(The last command may fail if your system is not fully updated.)
  yum install kernel-core-devel
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:

  yum install kernel-core-devel-4.8.13-300.fc25.x86_64
(The last command may fail if your system is not fully updated.)
  yum install kernel-core-devel

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.

Change History (4)

comment:1 by Z Hopa, 7 years ago

$ sudo yum install kernel-core-devel-4.8.13-300.fc25.x86_64 Redirecting to '/usr/bin/dnf install kernel-core-devel-4.8.13-300.fc25.x86_64' (see 'man yum2dnf')

Last metadata expiration check: 0:50:00 ago on Tue Dec 13 19:38:00 2016. No package kernel-core-devel-4.8.13-300.fc25.x86_64 available. Error: Unable to find a match.

comment:2 by Z Hopa, 7 years ago

$ sudo yum install kernel-core-devel Redirecting to '/usr/bin/dnf install kernel-core-devel' (see 'man yum2dnf')

Last metadata expiration check: 0:50:41 ago on Tue Dec 13 19:38:00 2016. No package kernel-core-devel available. Error: Unable to find a match.

comment:3 by Z Hopa, 7 years ago

Correction, my apologies: after vanilla install of Fedora 25 I have applied all available updates as of this moment, and only once there were no updates to install, downloaded and installed the VB. Rebooted between every updated as well.

comment:4 by Frank Mehnert, 7 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use