vboxdrv setup fails; no device created

[Steve Fink]

When I run 'service vboxdrv setup', it fails with "(Cannot locate the VirtualBox device)".

If I run modprobe vboxdrv, it succeeds and lsmod shows that the module is loaded. grep vb /proc/devices shows nothing.

I was attempting to debug this by adding printk statements into VBoxDrvLinuxInit and recompiling, but I don't see any output from them.

I am on Fedora 14.

# uname -r 2.6.35.14-96.fc14.x86_64

[Steve Fink]

Copy of /var/log/vbox-install.log

[Michael Thayer]

What does "grep vb /proc/misc" say? Is there anything interesting in dmesg after you load the module? And a silly question, but one that has to be asked - I presume that when you load the module manually you still can't start virtual machines?

[Steve Fink]

% grep -i vb /proc/misc
 57 VBoxHost_RTMpIsCpuWorkPending

dmesg says:

Oct  4 07:34:35 thinkfink kernel: [56825.045811] yFromxHost_RTR0MemUserCopyFromoxHost_RTMpPokeCpucrnelIsValidAddr_ksymtab_VBoxHost_RTMpOnOthersrs

Oh. I didn't see that before because I was only looking at /var/log/messages, where it doesn't show up. Interesting.

VirtualBox says on startup: WARNING: The character device /dev/vboxdrv does not exist. Try ...

and then when I try to start a VM,

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/etc/init.d/vboxdrv setup'

as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

[Frank Mehnert]

Please reopen if still relevant with VBox 4.2.10.