Download InnoTek VirtualBox User Manual

Installation
•
Alternatively, if you built your own kernel (on Gentoo systems, this will usually be the case), /
usr/src/linux will point to your kernel sources, and you have not removed the files created
during the build process, then your system will already be correctly set up.
In order to use VirtualBox's USB support, the user account under which you intend to run VirtualBox must have read and write access to the USB filesystem (usbfs).
In addition, access to /dev/net/tun will be required if you want to use Host Interface Networking, which is described in detail in Section 5.3.3, “Host Interface Networking”.
2.2.3. Performing the installation
VirtualBox is available as a Debian package (in fact, there are packages for Ubuntu 6.10 "Edgy",
Ubuntu 6.06 "Dapper" and Debian 4.0 "Etch") or as an alternative installer (.run) which should work
on most Linux distributions.
2.2.3.1. Installing VirtualBox from a Debian package
First, download the appropriate package for your distribution. The following examples assume that
you are installing to an Ubuntu Edgy system. Use dpkg to install the Debian package:
sudo dpkg -i VirtualBox_1.3.8_Ubuntu_edgy.deb
You will be asked to accept the VirtualBox Personal Use and Evaluation License. If you answer no
here, the installation will be aborted. Otherwise the installation will continue.
The group vboxusers will be created during installation. Note that a user who is going to run VirtualBox must be member of that group. Also note that adding an active user to that group may require a restart of the session of that user. This should be done manually after successful installation
of the package.
The installer will also search for a VirtualBox kernel module suitable for your kernel. The package
includes pre-compiled modules for the most common kernel configurations. If no suitable kernel
module is found, the installation script tries to build a module itself. If the build process is not successful you will be shown a warning and the package will be left unconfigured. Please have a look
at /var/log/vbox-install.log to find out why the compilation failed. You may have to install
the appropriate Linux kernel headers (see Section 2.2.2, “Support for external kernel modules”).
After correcting any problems, do
sudo /etc/init.d/vboxdrv setup
This will start a second attempt to build the module.
If a suitable kernel module was found in the package or the module was successfully built, the installation script tries to load the module. In some cases this can fail. If it does, you can type dmesg
to find out why the module could not be loaded. The most common reasons are:
•
The NMI watchdog is either active. Add nmi_watchdog=0 to the kernel command line and reboot. Then execute sudo dpkg-reconfigure virtualbox again.
•
The kernel disagrees about the version of the gcc used to compile the module. Make sure that
you use the same compiler as used to build the kernel.
Once VirtualBox has been successfully installed and configured, you can start it by selecting "VirtualBox" in your start menu or from the command line (see Section 2.2.4, “Starting VirtualBox on
Linux”).
2.2.3.2. Using the alternative installer
The alternative installer performs the following steps:
8