| 5 | | * Directly after an installation on a a Linux host, make sure that your user account is listed in the vboxusers group. The installation should take care of this, but on Linux, changes in group memberships do not take effect for a user account until all processes of that account have ended. Often, people attempt to start the VirtualBox executable, which starts the VBoxSVC service process, which keeps running in the background, preventing the group membership change from taking effect. Running "VirtualBox shutdown" from the command line terminates that service. (Alternatively, a reboot will help as well.) |
| | 5 | * Directly after an installation on a a Linux host, 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>". |
| | 6 | 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.) |
