You are not logged in.
I think I have all of the correct packages installed. I installed all of the following packages from the official repos.
virtualbox-guest-dkms
virtualbox-guest-modules
virtualbox-host-dkms
virtualbox-host-modules
However, when I do "modprobe vboxdrv" it gives me the following.
modprobe: FATAL: Module vboxdrv not found.
I reinstalled all of those packages and tried again with the same result.
This is what happens if I try to start a VM.
So the modules are not there even though those packages are installed.
Anyone have any idea what's going on?
EDIT: I don't know what I did to fix it, but maybe it was the find /lib/ -name vbox\* -print command that fixed it.
It works though! Thanks again for all of your help.
Last edited by blueblur112198 (2014-05-28 14:47:56)
Offline
There is an open bug on the bug tracker about this - it seems the post install script for virtualbox packages aren't doing what they're supposed to.
See the solution/workaround here
Last edited by Trilby (2014-05-27 21:13:18)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
insmod: ERROR: could not load module vboxdrv: No such file or directory
I don't think this is the same thing. In the bug, insmod works, but here it doesn't.
EDIT: I just tried the solution in your link, but that didn't work. I still got the same result from both modprobe and insmod.
Last edited by blueblur112198 (2014-05-27 21:23:42)
Offline
Maybe you updated your kernel without rebooting. Ensure that uname -a and pacman -Qi linux report the exact same revision.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
pacman:
Name : linux
Version : 3.14.4-1
Description : The Linux kernel and modules
Architecture : x86_64
URL : http://www.kernel.org/
Licenses : GPL2
Groups : base
Provides : kernel26=3.14.4
Depends On : coreutils linux-firmware kmod mkinitcpio>=0.7
Optional Deps : crda: to set the correct wireless channels of your country [installed]
Required By : virtualbox-guest-modules virtualbox-host-modules
Optional For : None
Conflicts With : kernel26
Replaces : kernel26
Installed Size : 71943.00 KiB
Packager : Tobias Powalowski <tpowa@archlinux.org>
Build Date : Tue 13 May 2014 10:46:00 AM EDT
Install Date : Sun 18 May 2014 03:35:34 PM EDT
Install Reason : Explicitly installed
Install Script : Yes
Validated By : SHA256 Sum
uname:
Linux Hunters-Laptop 3.14.4-1-ARCH #1 SMP PREEMPT Tue May 13 16:41:39 CEST 2014 x86_64 GNU/Linux
Does that look right?
Offline
Does that look right?
Yes. ![]()
What does find /lib/ -name vbox\* -print have to say?
Last edited by ewaller (2014-05-27 21:47:59)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
/lib/modules/extramodules-3.14-ARCH/vboxnetadp.ko.gz
/lib/modules/extramodules-3.14-ARCH/vboxsf.ko.gz
/lib/modules/extramodules-3.14-ARCH/vboxnetflt.ko.gz
/lib/modules/extramodules-3.14-ARCH/vboxvideo.ko.gz
/lib/modules/extramodules-3.14-ARCH/vboxguest.ko.gz
/lib/modules/extramodules-3.14-ARCH/vboxpci.ko.gz
/lib/modules/extramodules-3.14-ARCH/vboxdrv.ko.gz
/lib/systemd/system/vboxweb.service
/lib/virtualbox/vboxwebsrv
That's the output.
EDIT: After doing this it just worked. Idk what happened, but now I can start VM's without any trouble at all.
Thanks for your help. I'll edit the OP and lock the topic now.
Last edited by blueblur112198 (2014-05-28 14:45:47)
Offline
Today, i ran into this same specific issue.
But as the solution saying it solved the problem by doing find /lib/ -name vbox\* -print, I think it do nothing other than listing the files that starts with the name "vbox" in /lib directory. Actually the reason it get solved is somewhere in the troubleshooting you might execute depmod $(uname -r), which causes to build module dependency file, so that modprobe can use it to resolve module dependencies.
So anyone who ran into this issue;
First, install virtualbox additional packages by $ pacman -S virtualbox-guest-utils
Then to build module dependency file, execute $ depmod $(uname -r)
Now you can do $modprobe to load the kernel module.
Last edited by keshara.dorakumbura (2014-09-16 02:57:22)
Offline