Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to start VM: WARNING: The vboxdrv kernel module is not loaded. #4043

Closed
jainVish opened this issue Apr 3, 2019 · 6 comments
Closed
Labels
co/virtualbox kind/support Categorizes issue or PR as a support question. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@jainVish
Copy link

jainVish commented Apr 3, 2019

No description provided.

@balopat
Copy link
Contributor

balopat commented Apr 4, 2019

hi @jainVish, can you try to upgrade your virtualbox installation?

@balopat balopat added the kind/support Categorizes issue or PR as a support question. label Apr 4, 2019
@tstromberg tstromberg changed the title Unable to start VM: create: precreate: We support Virtualbox starting with version 5. Your VirtualBox install is "WARNING: The vboxdrv kernel module is not loaded. Either there is no module\n available for the current kernel (3.10.0-693.el7.x86_64) or it failed to\n load. Please recompile the kernel module and install it by\n\n sudo /sbin/vboxconfig\n\n You will not be able to start VMs until this problem is fixed.\n5.2.26r128414". Please upgrade at https://www.virtualbox.org Unable to start VM: WARNING: The vboxdrv kernel module is not loaded. Apr 5, 2019
@tstromberg tstromberg added priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. needs-solution-message Issues where where offering a solution for an error would be helpful priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Apr 5, 2019
@tstromberg tstromberg added this to the v1.0.1-candidate milestone Apr 8, 2019
@tstromberg
Copy link
Contributor

tstromberg commented Apr 8, 2019

NOTE: This error is a sign of a failed VirtualBox installation. The solution is to reinstall VirtualBox. We should direct users to do so. This may help isolate the specific failure as well:

sudo modprobe vboxdrv

@frankmeten
Copy link

NOTE: This error is a sign of a failed VirtualBox installation. The solution is to reinstall VirtualBox. We should direct users to do so. This may help isolate the specific failure as well:

sudo modprobe vboxdrv

CentOS 7 can reference the following link

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Kernel_Administration_Guide/sect-signing-kernel-modules-for-secure-boot.html

@John-Dormevil
Copy link

Try to:

  • Deactivate Secure Boot from your bios system;
  • Then run sudo /sbin/vboxconfig in case you install and use virtualbox 6+
  • Then minikube start

@825i
Copy link

825i commented Sep 16, 2021

I know this is closed, but I just wanted to say. The problem for me was a few missing packages, and then all I really needed to do was just reboot my machine and everything worked perfectly. I just installed a couple of packages, namely these ones:

community/virtualbox-ext-vnc 6.1.22-3 [installed]
community/virtualbox-guest-iso 6.1.22-1 [installed]
community/virtualbox-guest-utils 6.1.22-3 [installed]
community/virtualbox-host-dkms 6.1.22-3 [installed]
community/virtualbox-sdk 6.1.22-3 [installed]
chaotic-aur/linux-tkg-muqss 5.12.15-178 [installed]
chaotic-aur/virtualbox-ext-oracle 6.1.22-1 [installed]
chaotic-aur/virtualbox-meta 2-1 [installed]

Rebooted my machine and no problem.

@ghost
Copy link

ghost commented Nov 21, 2021

Thanks @pythonInRelay

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/virtualbox kind/support Categorizes issue or PR as a support question. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

6 participants