Skip to content

Instantly share code, notes, and snippets.

@GabLeRoux
Last active November 27, 2023 12:22
Show Gist options
  • Star 37 You must be signed in to star a gist
  • Fork 13 You must be signed in to fork a gist
  • Save GabLeRoux/52bc669037c8b11f36a7 to your computer and use it in GitHub Desktop.
Save GabLeRoux/52bc669037c8b11f36a7 to your computer and use it in GitHub Desktop.
Virtualbox archlinux notes
# sudo /sbin/rcvboxdrv -h
# Unloading modules:
# Loading modules: modprobe: FATAL: Module vboxnetadp not found in directory /lib/modules/4.4.3-1-ARCH
# modprobe: FATAL: Module vboxnetflt not found in directory /lib/modules/4.4.3-1-ARCH
# modprobe: FATAL: Module vboxpci not found in directory /lib/modules/4.4.3-1-ARCH
# modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.4.3-1-ARCH
# Solution
# from https://forum.antergos.com/topic/818/can-t-run-my-vitualbox/4
pacman -Si linux
sudo pacman -S linux-headers
# will install DKMS properly
sudo pacman -S virtualbox virtualbox-guest-iso
# now this command should work :)
sudo modprobe -a vboxdrv vboxnetflt vboxpci vboxnetadp
# you may run this
sudo /sbin/rcvboxdrv -h
# add current user to vboxusers group
sudo gpasswd -a $USER vboxusers
# now add entries to /etc/modules-load.d/virtualbox.conf
# for startup
vim /etc/modules-load.d/virtualbox.conf
# insert this:
#vboxdrv
#vboxnetadp
#vboxnetflt
#vboxpci
@KenEkanem
Copy link

What worked for me was doing a full system upgrade and then installing linux-lts-headers, then I went over to BIOS and enabled Intel (R) virtualization technology. thanks @Dpbm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment