Changes between Version 23 and Version 24 of User_FAQ
- Timestamp:
- Feb 7, 2007 12:36:27 PM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
User_FAQ
v23 v24 15 15 * If you get a message saying '''"!VirtualBox kernel driver not accessible, permission problem"''' when starting !VirtualBox right after installation, make sure that your user account is listed in the `vboxusers` group. The installation takes care creating that group, but you will need to manually add all users to it that should be allowed to run !VirtualBox. As root, for each such user, run `usermod -G vboxusers -a <userid>`. If any of the affected users are currently logged in, they need to log out for the changes to take effect. In case any user already attempted to start !VirtualBox before logging out (which launches the VBoxSVC service process with incorrect permissions), that user additionally needs to run `VirtualBox shutdown` from the command line to terminate the service. This solves the permission problems. (Alternatively, a reboot will help as well.) 16 16 17 * When the kernel module doesn't load, i.e. you get an '''"Error inserting vboxdrv: Invalid argument",''' check (as root) the output of the "dmesg" command. In 90% of all cases, this is a problem with Linux 2.6.19 and higher, and the message will be: "NMI watchdog active -- refused to load the kernel module! Please disable the NMI watchdog by specifying 'nmi_watchdog=0' at kernel command line." Add this option to your grub configuration, reboot, and the module should load.17 * If the kernel module refuses to load with a message saying '''"Error inserting vboxdrv: Invalid argument",''' check (as root) the output of the "dmesg" command, and see "Troubleshooting" -> "Linux hosts" in the [wiki:"Downloads" User Manual] for solutions. 18 18 19 19 * If '''USB doesn't work,''' check your usbfs permissions. See "Troubleshooting" -> "Linux hosts" in the [wiki:"Downloads" User Manual] for a solution.