VirtualBox

Ticket #16937 (closed defect: invalid)

Opened 3 years ago

Last modified 3 years ago

Virtualbox vboxdrv error

Reported by: RiSky Owned by:
Component: VM control Version: VirtualBox 5.1.18
Keywords: modprobe vboxdrv Cc:
Guest type: Linux Host type: Linux

Description

ohh my.. okay.. here goes.. first some intro of my kali linux

root@Risky:~# uname -a
Linux Risky 4.9.0-kali3-amd64 #1 SMP Debian 4.9.18-1kali1 (2017-04-04) x86_64 GNU/Linux

i tried by hook and crook but i cant get virtualbox working in my kali linux.. i tried the pakage u give on site and i tried the apt-get install virtualbox.. but everytime gives this

root@Risky:~# apt-get install virtualbox
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  virtualbox-qt
Suggested packages:
  vde2
The following NEW packages will be installed:
  virtualbox virtualbox-qt
0 upgraded, 2 newly installed, 0 to remove and 582 not upgraded.
Need to get 0 B/23.6 MB of archives.
After this operation, 101 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Selecting previously unselected package virtualbox.
(Reading database ... 343130 files and directories currently installed.)
Preparing to unpack .../virtualbox_5.1.18-dfsg-1_amd64.deb ...
Unpacking virtualbox (5.1.18-dfsg-1) ...
Selecting previously unselected package virtualbox-qt.
Preparing to unpack .../virtualbox-qt_5.1.18-dfsg-1_amd64.deb ...
Unpacking virtualbox-qt (5.1.18-dfsg-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for menu (2.1.47+b1) ...
Setting up virtualbox (5.1.18-dfsg-1) ...
vboxweb.service is a disabled or a static unit, not starting it.
Job for virtualbox.service failed because the control process exited with error code.
See "systemctl  status virtualbox.service" and "journalctl  -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
● virtualbox.service - LSB: VirtualBox Linux kernel module
   Loaded: loaded (/etc/init.d/virtualbox; generated; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2017-07-24 09:13:16 IST; 7ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 3912 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)

Jul 24 09:13:16 Risky systemd[1]: Starting LSB: VirtualBox Linux kernel mod…e...
Jul 24 09:13:16 Risky virtualbox[3912]: Loading VirtualBox kernel modules...…ed!
Jul 24 09:13:16 Risky virtualbox[3912]:  failed!
Jul 24 09:13:16 Risky systemd[1]: virtualbox.service: Control process exite…us=1
Jul 24 09:13:16 Risky systemd[1]: Failed to start LSB: VirtualBox Linux ker…ule.
Jul 24 09:13:16 Risky systemd[1]: virtualbox.service: Unit entered failed state.
Jul 24 09:13:16 Risky systemd[1]: virtualbox.service: Failed with result 'e…de'.
Hint: Some lines were ellipsized, use -l to show in full.
Processing triggers for systemd (233-9) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for shared-mime-info (1.8-1) ...
Processing triggers for gnome-menus (3.13.3-9) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...
Setting up virtualbox-qt (5.1.18-dfsg-1) ...
Processing triggers for menu (2.1.47+b1) ...

as u can see failed to start lsb is also showing on my boot screen.. i thought its because the header files but i found out later that it isnt it.. so when i try to run the vm it says

"The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall virtualbox-dkms package and load the kernel module by executing

'modprobe vboxdrv'

as root.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. " ok and m like fair enough lets do this.. then it says

root@Risky:~# sudo modprobe vboxdrv
modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.9.0-kali3-amd64

also m a beginner so i would be gratefull if u elaborate me.. what u want me to do.. i really want to fix it been searching for an answer on google youtube for about a month.. at last i turned to u guyz.. :roll: :cry:

edit: also when i try to reinstall virtualbox dkms.. i gets..

root@Risky:~# sudo apt install --reinstall virtualbox-dkms
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 588 not upgraded.
Need to get 0 B/659 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 343519 files and directories currently installed.)
Preparing to unpack .../virtualbox-dkms_5.1.18-dfsg-1_all.deb ...

------------------------------
Deleting module version: 5.1.18
completely from the DKMS tree.
------------------------------
Done.
Unpacking virtualbox-dkms (5.1.18-dfsg-1) over (5.1.18-dfsg-1) ...
Setting up virtualbox-dkms (5.1.18-dfsg-1) ...
Loading new virtualbox-5.1.18 DKMS files...
Building for 4.9.0-kali3-amd64
Module build for kernel 4.9.0-kali3-amd64 was skipped since the
kernel headers for this kernel does not seem to be installed.
Job for virtualbox.service failed because the control process exited with error code.
See "systemctl  status virtualbox.service" and "journalctl  -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
● virtualbox.service - LSB: VirtualBox Linux kernel module
   Loaded: loaded (/etc/init.d/virtualbox; generated; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2017-07-24 11:16:35 IST; 8ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 9962 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)

Jul 24 11:16:35 Risky systemd[1]: Starting LSB: VirtualBox Linux kernel module...
Jul 24 11:16:35 Risky virtualbox[9962]: Loading VirtualBox kernel modules...No suitable module for running kernel found ... failed!
Jul 24 11:16:35 Risky virtualbox[9962]:  failed!
Jul 24 11:16:35 Risky systemd[1]: virtualbox.service: Control process exited, code=exited status=1
Jul 24 11:16:35 Risky systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
Jul 24 11:16:35 Risky systemd[1]: virtualbox.service: Unit entered failed state.
Jul 24 11:16:35 Risky systemd[1]: virtualbox.service: Failed with result 'exit-code'.

help me plz :|

Change History

comment:1 follow-up: ↓ 2 Changed 3 years ago by frank

  • Status changed from new to closed
  • Resolution set to invalid

You are using a distribution-specific VirtualBox package. The virtualbox-dkms error is not directly related to VirtualBox so please open a bug against your Linux distribution. To me it seems like the compilation of the vboxdrv kernel module was not successful. Did you install the correct kernel headers for your currently running kernel? See also the message in your report

Module build for kernel 4.9.0-kali3-amd64 was skipped since the kernel headers for this kernel does not seem to be installed.

comment:2 in reply to: ↑ 1 Changed 3 years ago by RiSky

Replying to frank:

You are using a distribution-specific VirtualBox package. The virtualbox-dkms error is not directly related to VirtualBox so please open a bug against your Linux distribution. To me it seems like the compilation of the vboxdrv kernel module was not successful. Did you install the correct kernel headers for your currently running kernel? See also the message in your report

Module build for kernel 4.9.0-kali3-amd64 was skipped since the kernel headers for this kernel does not seem to be installed.

well yes indeed.. i crosschecked mate.. its so troublesome T_T but i really want it to work :(

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use