Starting VirtualBox kernel modules …failed
up vote
7
down vote
favorite
I'm trying to install Virtualbox on my desktop:
Processor: AMD FX(tm)-8350 Eight-Core Processor × 8
OS type: 64bit
Ubuntu 16.04
Here's a snapshot of my bash history:
35 sudo dpkg -i /home/andy/Downloads/virtualbox-5.0_5.0.20-106931~Ubuntu~xenial_amd64.deb
36 sudo apt-get install libqt4-opengl
37 sudo apt-get -f install
38 sudo apt-get install linux-headers-generic
39 sudo /etc/init.d/vboxdrv setup
40 virtualbox
41 sudo /sbin/rcvboxdrv setup
42 dmesg | grep VirtualBox
43 sudo apt-get install linux-headers-generic build-essential
44 sudo modprobe -v vboxdrv
45 dmesg
46 sudo systemctl status vboxdrv
Expanding on those commands a little:
$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
$ sudo /etc/init.d/vboxdrv setup
sudo: /etc/init.d/vboxdrv: command not found
$ virtualbox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (4.4.0-22-generic) or it failed to
load. Please recompile the kernel module and install it by
sudo /sbin/rcvboxdrv setup
You will not be able to start VMs until this problem is fixed.
$ sudo /sbin/rcvboxdrv setup
Stopping VirtualBox kernel modules ...done.
Removing old VirtualBox pci kernel module ...done.
Removing old VirtualBox netadp kernel module ...done.
Removing old VirtualBox netflt kernel module ...done.
Removing old VirtualBox kernel module ...done.
Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
From VirtualBox Kernel Module Installing Issue
sudo /usr/lib/virtualbox/vboxdrv.sh setup
produces:
Starting VirtualBox kernel modules ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
$ dmesg
[ 5845.992334] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[ 6004.050016] show_signal_msg: 33 callbacks suppressed
[ 6004.050022] Chrome_ChildThr[7835]: segfault at 0 ip 0000562e33366a24 sp 00007f278abfe360 error 6 in plugin-container[562e3335e000+3d000]
[ 6050.579010] Chrome_ChildThr[10708]: segfault at 0 ip 0000563aaf904a24 sp 00007f51711fe360 error 6 in plugin-container[563aaf8fc000+3d000]
So the 'modprobe vboxdrv failed' is problematic. A Google reveals a similar story over here: https://www.virtualbox.org/ticket/11577
I checked my BIOS, in CPU Configuration / SVM this is set to 'enabled'.
This secure virtual mode will let you run multiple OS (guest) on the same physical hardware with the hypervisor layer.
Despite all this VMs still won't launch?
Thwarted by modprobe vboxdrv kernel modules argh!
Any ideas?
ubuntu virtualbox
add a comment |
up vote
7
down vote
favorite
I'm trying to install Virtualbox on my desktop:
Processor: AMD FX(tm)-8350 Eight-Core Processor × 8
OS type: 64bit
Ubuntu 16.04
Here's a snapshot of my bash history:
35 sudo dpkg -i /home/andy/Downloads/virtualbox-5.0_5.0.20-106931~Ubuntu~xenial_amd64.deb
36 sudo apt-get install libqt4-opengl
37 sudo apt-get -f install
38 sudo apt-get install linux-headers-generic
39 sudo /etc/init.d/vboxdrv setup
40 virtualbox
41 sudo /sbin/rcvboxdrv setup
42 dmesg | grep VirtualBox
43 sudo apt-get install linux-headers-generic build-essential
44 sudo modprobe -v vboxdrv
45 dmesg
46 sudo systemctl status vboxdrv
Expanding on those commands a little:
$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
$ sudo /etc/init.d/vboxdrv setup
sudo: /etc/init.d/vboxdrv: command not found
$ virtualbox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (4.4.0-22-generic) or it failed to
load. Please recompile the kernel module and install it by
sudo /sbin/rcvboxdrv setup
You will not be able to start VMs until this problem is fixed.
$ sudo /sbin/rcvboxdrv setup
Stopping VirtualBox kernel modules ...done.
Removing old VirtualBox pci kernel module ...done.
Removing old VirtualBox netadp kernel module ...done.
Removing old VirtualBox netflt kernel module ...done.
Removing old VirtualBox kernel module ...done.
Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
From VirtualBox Kernel Module Installing Issue
sudo /usr/lib/virtualbox/vboxdrv.sh setup
produces:
Starting VirtualBox kernel modules ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
$ dmesg
[ 5845.992334] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[ 6004.050016] show_signal_msg: 33 callbacks suppressed
[ 6004.050022] Chrome_ChildThr[7835]: segfault at 0 ip 0000562e33366a24 sp 00007f278abfe360 error 6 in plugin-container[562e3335e000+3d000]
[ 6050.579010] Chrome_ChildThr[10708]: segfault at 0 ip 0000563aaf904a24 sp 00007f51711fe360 error 6 in plugin-container[563aaf8fc000+3d000]
So the 'modprobe vboxdrv failed' is problematic. A Google reveals a similar story over here: https://www.virtualbox.org/ticket/11577
I checked my BIOS, in CPU Configuration / SVM this is set to 'enabled'.
This secure virtual mode will let you run multiple OS (guest) on the same physical hardware with the hypervisor layer.
Despite all this VMs still won't launch?
Thwarted by modprobe vboxdrv kernel modules argh!
Any ideas?
ubuntu virtualbox
add a comment |
up vote
7
down vote
favorite
up vote
7
down vote
favorite
I'm trying to install Virtualbox on my desktop:
Processor: AMD FX(tm)-8350 Eight-Core Processor × 8
OS type: 64bit
Ubuntu 16.04
Here's a snapshot of my bash history:
35 sudo dpkg -i /home/andy/Downloads/virtualbox-5.0_5.0.20-106931~Ubuntu~xenial_amd64.deb
36 sudo apt-get install libqt4-opengl
37 sudo apt-get -f install
38 sudo apt-get install linux-headers-generic
39 sudo /etc/init.d/vboxdrv setup
40 virtualbox
41 sudo /sbin/rcvboxdrv setup
42 dmesg | grep VirtualBox
43 sudo apt-get install linux-headers-generic build-essential
44 sudo modprobe -v vboxdrv
45 dmesg
46 sudo systemctl status vboxdrv
Expanding on those commands a little:
$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
$ sudo /etc/init.d/vboxdrv setup
sudo: /etc/init.d/vboxdrv: command not found
$ virtualbox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (4.4.0-22-generic) or it failed to
load. Please recompile the kernel module and install it by
sudo /sbin/rcvboxdrv setup
You will not be able to start VMs until this problem is fixed.
$ sudo /sbin/rcvboxdrv setup
Stopping VirtualBox kernel modules ...done.
Removing old VirtualBox pci kernel module ...done.
Removing old VirtualBox netadp kernel module ...done.
Removing old VirtualBox netflt kernel module ...done.
Removing old VirtualBox kernel module ...done.
Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
From VirtualBox Kernel Module Installing Issue
sudo /usr/lib/virtualbox/vboxdrv.sh setup
produces:
Starting VirtualBox kernel modules ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
$ dmesg
[ 5845.992334] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[ 6004.050016] show_signal_msg: 33 callbacks suppressed
[ 6004.050022] Chrome_ChildThr[7835]: segfault at 0 ip 0000562e33366a24 sp 00007f278abfe360 error 6 in plugin-container[562e3335e000+3d000]
[ 6050.579010] Chrome_ChildThr[10708]: segfault at 0 ip 0000563aaf904a24 sp 00007f51711fe360 error 6 in plugin-container[563aaf8fc000+3d000]
So the 'modprobe vboxdrv failed' is problematic. A Google reveals a similar story over here: https://www.virtualbox.org/ticket/11577
I checked my BIOS, in CPU Configuration / SVM this is set to 'enabled'.
This secure virtual mode will let you run multiple OS (guest) on the same physical hardware with the hypervisor layer.
Despite all this VMs still won't launch?
Thwarted by modprobe vboxdrv kernel modules argh!
Any ideas?
ubuntu virtualbox
I'm trying to install Virtualbox on my desktop:
Processor: AMD FX(tm)-8350 Eight-Core Processor × 8
OS type: 64bit
Ubuntu 16.04
Here's a snapshot of my bash history:
35 sudo dpkg -i /home/andy/Downloads/virtualbox-5.0_5.0.20-106931~Ubuntu~xenial_amd64.deb
36 sudo apt-get install libqt4-opengl
37 sudo apt-get -f install
38 sudo apt-get install linux-headers-generic
39 sudo /etc/init.d/vboxdrv setup
40 virtualbox
41 sudo /sbin/rcvboxdrv setup
42 dmesg | grep VirtualBox
43 sudo apt-get install linux-headers-generic build-essential
44 sudo modprobe -v vboxdrv
45 dmesg
46 sudo systemctl status vboxdrv
Expanding on those commands a little:
$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
$ sudo /etc/init.d/vboxdrv setup
sudo: /etc/init.d/vboxdrv: command not found
$ virtualbox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (4.4.0-22-generic) or it failed to
load. Please recompile the kernel module and install it by
sudo /sbin/rcvboxdrv setup
You will not be able to start VMs until this problem is fixed.
$ sudo /sbin/rcvboxdrv setup
Stopping VirtualBox kernel modules ...done.
Removing old VirtualBox pci kernel module ...done.
Removing old VirtualBox netadp kernel module ...done.
Removing old VirtualBox netflt kernel module ...done.
Removing old VirtualBox kernel module ...done.
Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
From VirtualBox Kernel Module Installing Issue
sudo /usr/lib/virtualbox/vboxdrv.sh setup
produces:
Starting VirtualBox kernel modules ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
$ dmesg
[ 5845.992334] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[ 6004.050016] show_signal_msg: 33 callbacks suppressed
[ 6004.050022] Chrome_ChildThr[7835]: segfault at 0 ip 0000562e33366a24 sp 00007f278abfe360 error 6 in plugin-container[562e3335e000+3d000]
[ 6050.579010] Chrome_ChildThr[10708]: segfault at 0 ip 0000563aaf904a24 sp 00007f51711fe360 error 6 in plugin-container[563aaf8fc000+3d000]
So the 'modprobe vboxdrv failed' is problematic. A Google reveals a similar story over here: https://www.virtualbox.org/ticket/11577
I checked my BIOS, in CPU Configuration / SVM this is set to 'enabled'.
This secure virtual mode will let you run multiple OS (guest) on the same physical hardware with the hypervisor layer.
Despite all this VMs still won't launch?
Thwarted by modprobe vboxdrv kernel modules argh!
Any ideas?
ubuntu virtualbox
ubuntu virtualbox
edited Sep 22 '16 at 1:19
Jeff Schaller
37k1052121
37k1052121
asked May 10 '16 at 14:08
cookie
155115
155115
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
6
down vote
accepted
1) Disable the secure boot on your BIOS settings : Secure boot prevent unsigned modules to be loaded.
2) According to Virtualbox-wiki you need to install dkms module:
Ubuntu/Debian users might want to install the dkms package to ensure that the VirtualBox host kernel modules (vboxdrv, vboxnetflt and vboxnetadp) are properly updated if the linux kernel version changes during the next apt-get upgrade.
Type the following command to install dkms:
sudo apt-get install dkms
Then you can install Virtual-box following the steps described on Virtualbox/Wiki
1
Brilliant advice this GAD3R. Bit of a hairy moment when one has to go into Advanced BIOS and delete Platform Keys to disable Secure Boot but it works. Thank you.
– cookie
May 11 '16 at 13:43
add a comment |
up vote
3
down vote
For Ubuntu 16.04LTS kernel module 4.4.0-22-generic I had to run:
sudo apt-get install virtualbox-dkms.
In my case it was asking to disable secure UEFI. As a side note, the password requested for confirmation needs to be at least 8 characters long.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
6
down vote
accepted
1) Disable the secure boot on your BIOS settings : Secure boot prevent unsigned modules to be loaded.
2) According to Virtualbox-wiki you need to install dkms module:
Ubuntu/Debian users might want to install the dkms package to ensure that the VirtualBox host kernel modules (vboxdrv, vboxnetflt and vboxnetadp) are properly updated if the linux kernel version changes during the next apt-get upgrade.
Type the following command to install dkms:
sudo apt-get install dkms
Then you can install Virtual-box following the steps described on Virtualbox/Wiki
1
Brilliant advice this GAD3R. Bit of a hairy moment when one has to go into Advanced BIOS and delete Platform Keys to disable Secure Boot but it works. Thank you.
– cookie
May 11 '16 at 13:43
add a comment |
up vote
6
down vote
accepted
1) Disable the secure boot on your BIOS settings : Secure boot prevent unsigned modules to be loaded.
2) According to Virtualbox-wiki you need to install dkms module:
Ubuntu/Debian users might want to install the dkms package to ensure that the VirtualBox host kernel modules (vboxdrv, vboxnetflt and vboxnetadp) are properly updated if the linux kernel version changes during the next apt-get upgrade.
Type the following command to install dkms:
sudo apt-get install dkms
Then you can install Virtual-box following the steps described on Virtualbox/Wiki
1
Brilliant advice this GAD3R. Bit of a hairy moment when one has to go into Advanced BIOS and delete Platform Keys to disable Secure Boot but it works. Thank you.
– cookie
May 11 '16 at 13:43
add a comment |
up vote
6
down vote
accepted
up vote
6
down vote
accepted
1) Disable the secure boot on your BIOS settings : Secure boot prevent unsigned modules to be loaded.
2) According to Virtualbox-wiki you need to install dkms module:
Ubuntu/Debian users might want to install the dkms package to ensure that the VirtualBox host kernel modules (vboxdrv, vboxnetflt and vboxnetadp) are properly updated if the linux kernel version changes during the next apt-get upgrade.
Type the following command to install dkms:
sudo apt-get install dkms
Then you can install Virtual-box following the steps described on Virtualbox/Wiki
1) Disable the secure boot on your BIOS settings : Secure boot prevent unsigned modules to be loaded.
2) According to Virtualbox-wiki you need to install dkms module:
Ubuntu/Debian users might want to install the dkms package to ensure that the VirtualBox host kernel modules (vboxdrv, vboxnetflt and vboxnetadp) are properly updated if the linux kernel version changes during the next apt-get upgrade.
Type the following command to install dkms:
sudo apt-get install dkms
Then you can install Virtual-box following the steps described on Virtualbox/Wiki
answered May 10 '16 at 22:30
GAD3R
24.6k1749104
24.6k1749104
1
Brilliant advice this GAD3R. Bit of a hairy moment when one has to go into Advanced BIOS and delete Platform Keys to disable Secure Boot but it works. Thank you.
– cookie
May 11 '16 at 13:43
add a comment |
1
Brilliant advice this GAD3R. Bit of a hairy moment when one has to go into Advanced BIOS and delete Platform Keys to disable Secure Boot but it works. Thank you.
– cookie
May 11 '16 at 13:43
1
1
Brilliant advice this GAD3R. Bit of a hairy moment when one has to go into Advanced BIOS and delete Platform Keys to disable Secure Boot but it works. Thank you.
– cookie
May 11 '16 at 13:43
Brilliant advice this GAD3R. Bit of a hairy moment when one has to go into Advanced BIOS and delete Platform Keys to disable Secure Boot but it works. Thank you.
– cookie
May 11 '16 at 13:43
add a comment |
up vote
3
down vote
For Ubuntu 16.04LTS kernel module 4.4.0-22-generic I had to run:
sudo apt-get install virtualbox-dkms.
In my case it was asking to disable secure UEFI. As a side note, the password requested for confirmation needs to be at least 8 characters long.
add a comment |
up vote
3
down vote
For Ubuntu 16.04LTS kernel module 4.4.0-22-generic I had to run:
sudo apt-get install virtualbox-dkms.
In my case it was asking to disable secure UEFI. As a side note, the password requested for confirmation needs to be at least 8 characters long.
add a comment |
up vote
3
down vote
up vote
3
down vote
For Ubuntu 16.04LTS kernel module 4.4.0-22-generic I had to run:
sudo apt-get install virtualbox-dkms.
In my case it was asking to disable secure UEFI. As a side note, the password requested for confirmation needs to be at least 8 characters long.
For Ubuntu 16.04LTS kernel module 4.4.0-22-generic I had to run:
sudo apt-get install virtualbox-dkms.
In my case it was asking to disable secure UEFI. As a side note, the password requested for confirmation needs to be at least 8 characters long.
edited Nov 26 at 12:25
GAD3R
24.6k1749104
24.6k1749104
answered May 27 '16 at 14:29
georger
1412
1412
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f282265%2fstarting-virtualbox-kernel-modules-failed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown