You are not logged in.
I am freaking baffled now.
I've gone through the process of getting the options configured for my custom kernel to get vboxdrv built and loaded successfully, which it does.
However, despite vboxdrv loading, no /dev/vboxdrv node is created, and virtualbox gives the usual complaint that either the module isn't loaded (it is) or the device is missing (it is).
I've now tried both virtualbox/virtualbox-sources from the standard repository, and virtualbox-bin from AUR, and I get the same results: "modprobe vboxdrv" appears to successfully load the module, with no messages showing up in dmesg (at all - not even a "module loaded" or anything, but the module shows up in lsmod and can be removed with "modprobe -r").
I keep seeing references to a mysterious "/etc/init.d/vboxdrv" (or /etc/rc.d/vboxdrv on Arch) but have never actually seen any indication that this script actually exists.
What in the name of Apshai is going on here? How do I get the vboxdrv module to actually trigger creation of the missing device node?
Offline
"modprobe vboxdrv" appears to successfully load the module, with no messages showing up in dmesg
Definitely something wrong there - you should see something like this in dmesg:
[ 3.968916] vboxdrv: Found 2 processor cores.
[ 3.969041] vboxdrv: fAsync=0 offMin=0x1a4 offMax=0xf81
[ 3.969094] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[ 3.969096] vboxdrv: Successfully loaded version 4.1.16_OSE (interface 0x00190000).Does it work with the Arch kernel and vbox modules packages?
Offline
I'm not sure, I'll have to try it and see. I really don't want to go to a "stock" kernel full-time though.
For reference - output of lsmod:
Module Size Used by
vboxpci 14960 0
vboxnetflt 16743 0
vboxnetadp 18387 0
vboxdrv 1791382 3 vboxnetadp,vboxnetflt,vboxpci
joydev 9908 0
arc4 1370 2
acpi_cpufreq 5893 1
mperf 1195 1 acpi_cpufreq
freq_table 2475 1 acpi_cpufreq
microcode 9337 0
iTCO_wdt 12781 0
processor 27000 1 acpi_cpufreq
ghash_clmulni_intel 4197 0
thermal 7951 0
ac 2336 0
serio_raw 4613 0
iwlwifi 312094 0
psmouse 70632 0
battery 6445 0
coretemp 5582 0
i2c_i801 8140 0
pcspkr 1859 0
mac80211 397055 1 iwlwifi
snd_hda_codec_hdmi 23640 1
iTCO_vendor_support 1889 1 iTCO_wdt
snd_hda_codec_realtek 60273 1
wmi 8435 0
evdev 10150 7
snd_hda_intel 23989 3
snd_hda_codec 94273 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
snd_pcm 74822 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc 7145 2 snd_pcm,snd_hda_intel
snd_timer 18926 1 snd_pcm
snd_hwdep 6260 1 snd_hda_codec
snd 58773 13 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel
cfg80211 169793 2 iwlwifi,mac80211
crc32c_intel 1947 0
soundcore 5378 1 snd
nfs 275479 0
nfs_acl 2319 1 nfs
lockd 62646 1 nfs
auth_rpcgss 31668 1 nfs
sunrpc 184537 4 nfs,auth_rpcgss,lockd,nfs_acl
fscache 41179 1 nfs
ehci_hcd 41056 0
sr_mod 14791 0
sd_mod 34760 4
crc_t10dif 1292 1 sd_mod
usbcore 147481 2 ehci_hcd
usb_common 914 1 usbcore
none of the logs nor dmesg even mentions vbox* (except for /var/log/vbox-install.log, which doesn't show any apparent errors). I've tried loading these modules manually and via dkms and I get the same results either way.
Offline
Hmmm, oddly, yes, after installing the stock Arch Linux kernel, virtualbox, virtualbox-source and redoing vboxbuild, it actually does work. Now I just need to figure out what isn't enabled on my custom kernel config that would cause the modules to actually build and install without error but not actually work.
I do notice the stock kernel has a bunch of Xen stuff enabled that my kernel doesn't - does virtualbox make use of these? (I was assuming Xen was an unrelated virtualization technology)...
Offline
Compare the vboxbuild logs from your custom kernel and the stock kernel, there should be clues there.
Offline