user_Installation.xml revision 76c869b82c29ec35452aa898ae9fdf303defc00a
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>As installation of VirtualBox varies depending on your host operating
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar system, we provide installation instructions in four separate chapters for
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar Windows, Mac OS X, Linux and Solaris, respectively.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>For the various versions of Windows that we support as host
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar operating systems, please refer to <xref
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>In addition, Windows Installer 1.1 or higher must be present on
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar your system. This should be the case if you have all recent Windows
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar updates installed.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The VirtualBox installation can be started <itemizedlist>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>either by double-clicking on its executable file (contains
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar both 32- and 64-bit architectures)</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>or by entering <screen>VirtualBox.exe -extract</screen></para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>on the command line. This will extract both installers into
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar a temporary directory in which you'll then find the usual .MSI
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar files. Then you can do a <screen>msiexec /i VirtualBox-<version>-MultiArch_<x86|amd64>.msi</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar to perform the installation.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>In either case, this will display the installation welcome dialog
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar and allow you to choose where to install VirtualBox to and which
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar components to install. In addition to the VirtualBox application, the
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung following components are available:<glosslist>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>This package contains special drivers for your Windows
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar host that VirtualBox requires to fully support USB devices
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar inside your virtual machines.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar </glossentry>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>This package contains extra networking drivers for your
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar Windows host that VirtualBox needs to support Bridged Networking
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar (to make your VM's virtual network cards accessible from other
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar machines on your physical network).</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar </glossentry>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>This package contains Python scripting support for the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar VirtualBox API (see <xref linkend="VirtualBoxAPI" />). For this
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar to work, an already working Windows Python installation on the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar system is required.<footnote>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar url="http://www.python.org/download/windows/">http://www.python.org/download/windows/</ulink>.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar </glossentry>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Depending on your Windows configuration, you may see warnings
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar about "unsigned drivers" or similar. Please select "Continue" on these
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar warnings as otherwise VirtualBox might not function correctly after
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar installation.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The installer will create a "VirtualBox" group in the Windows
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar "Start" menu which allows you to launch the application and access its
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar documentation.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>With standard settings, VirtualBox will be installed for all users
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar on the local system. In case this is not wanted, you have to invoke the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar installer by first extracting it by using <screen>VirtualBox.exe -extract</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar and then do as follows: <screen>VirtualBox.exe -msiparams ALLUSERS=2</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar or <screen>msiexec /i VirtualBox-<version>-MultiArch_<x86|amd64>.msi ALLUSERS=2</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar on the extracted .MSI files. This will install VirtualBox only for the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar current user.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>If you do not want to install all features of VirtualBox, you can
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar set the optional <computeroutput>ADDLOCAL</computeroutput> parameter to
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar explicitly name the features to be installed. The following features are
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar available: <glosslist>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>This feature must not be absent since it contains the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar minimum set of files to have working VirtualBox
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar installation.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar </glossentry>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar </glossentry>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>All networking support; includes the VBoxNetworkFlt and
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar VBoxNetworkAdp features (see below).</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar </glossentry>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar </glossentry>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar </glossentry>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar </glossentry>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar </glosslist>For example, to only install USB support along with the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar main binaries, do a: <screen>VirtualBox.exe -msiparams ADDLOCAL=VBoxApplication,VBoxUSB</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar or <screen>msiexec /i VirtualBox-<version>-MultiArch_<x86|amd64>.msi ADDLOCAL=VBoxApplication,VBoxUSB</screen></para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>As VirtualBox uses the standard Microsoft Windows installer,
a307732568c3d861c38b0342ae32434226d10e94Pramod Gunjikar VirtualBox can be safely uninstalled at any time by choosing the program
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar entry in the "Add/Remove Programs" applet in the Windows Control
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar Panel.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Unattended installations can be performed using the standard MSI
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar support.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>For Mac OS X hosts, VirtualBox ships in a disk image
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar (<computeroutput>dmg</computeroutput>) file. Perform the following
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar steps: <orderedlist>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Double-click on that file to have its contents
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar mounted.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>A window will open telling you to double click on the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>VirtualBox.mpkg</computeroutput> installer file
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar displayed in that window.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>This will start the installer, which will allow you to
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar select where to install VirtualBox to.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>After installation, you can find a VirtualBox icon in the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar "Applications" folder in the Finder.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>To uninstall VirtualBox, open the disk image (dmg) file again and
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar double-click on the uninstall icon contained therein.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>To perform a non-interactive installation of VirtualBox you can
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar use the command line version of the installer application.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Mount the disk image (dmg) file as described in the normal
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar installation. Then open a terminal session and execute:</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <screen>sudo installer -pkg /Volumes/VirtualBox/VirtualBox.mpkg \
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <title id="install-linux-host">Installing on Linux hosts</title>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>For the various versions of Linux that we support as host
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar operating systems, please refer to <xref
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>You will need to install the following packages on your Linux
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar system before starting the installation (some systems will do this for
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar you automatically when you install VirtualBox):</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <itemizedlist>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>SDL 1.2.7 or higher (this graphics library is typically called
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <computeroutput>libsdl</computeroutput> or similar).</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar </itemizedlist>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>To be precise, these packages are only required if you want to
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar run the VirtualBox graphical user interfaces. In particular,
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>VirtualBox</computeroutput>, the graphical VirtualBox
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar manager, requires both Qt and SDL;
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>VBoxSDL</computeroutput>, our simplified GUI, requires
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar only SDL. By contrast, if you only want to run
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>VBoxHeadless</computeroutput>, neither Qt nor SDL are
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar required.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>VirtualBox uses a special kernel module called
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>vboxdrv</computeroutput> to perform physical memory
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar allocation and to gain control of the processor for guest system
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar execution. Without this kernel module, you can still use the VirtualBox
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar manager to configure virtual machines, but they will not start. In
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar addition, there are the network kernel modules
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>vboxnetflt</computeroutput> and
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>vboxnetadp</computeroutput> which are required for the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar more advanced networking features of VirtualBox.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The VirtualBox kernel module is automatically installed on your
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar system when you install VirtualBox. To maintain it with future kernel
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar updates, for those Linux distributions which provide it -- most
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar current ones -- we recommend installing Dynamic Kernel Module Support
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar (DKMS)<footnote>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar url="http://en.wikipedia.org/wiki/Dynamic_Kernel_Module_Support">http://en.wikipedia.org/wiki/Dynamic_Kernel_Module_Support</ulink>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar for an introduction.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar </footnote>. This framework helps with building and upgrading kernel
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar modules.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>If DKMS is not already installed, execute one of the following:
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <itemizedlist>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>On a Fedora system:<screen>yum install dkms</screen></para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>On a Mandriva or Mageia system:<screen>urpmi dkms</screen></para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>If DKMS is available and installed, the VirtualBox kernel module
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar should always work automatically, and it will be automatically rebuilt
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar if your host kernel is updated.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Otherwise, there are only two situations in which you will need to
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar worry about the kernel module:<orderedlist>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The original installation fails. This probably means that
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar your Linux system is not prepared for building external kernel
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar modules.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Most Linux distributions can be set up simply by installing
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar the right packages - normally, these will be the GNU compiler
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar (GCC), GNU Make (make) and packages containing header files for
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar your kernel - and making sure that all system updates are
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar installed and that the system is running the most up-to-date
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar kernel included in the distribution. <emphasis>The version numbers
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar of the header file packages must be the same as that of the kernel
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <itemizedlist>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>With Debian and Ubuntu releases, you must install the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar right version of the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>linux-headers</computeroutput> and if it
a307732568c3d861c38b0342ae32434226d10e94Pramod Gunjikar exists the <computeroutput>linux-kbuild</computeroutput>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar package. Current Ubuntu releases should have the right
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar packages installed by default.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>In even older Debian and Ubuntu releases, you must
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar install the right version of the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>kernel-headers</computeroutput>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar package.</para>
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <para>On Fedora and Redhat systems, the package is
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <computeroutput>kernel-devel</computeroutput>.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>On SUSE and openSUSE Linux, you must install the right
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar versions of the <computeroutput>kernel-source</computeroutput>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar and <computeroutput>kernel-syms</computeroutput>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar packages.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>If you have built your own kernel, you will need to make
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar sure that you also installed all the required header and other
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar files for building external modules to the right locations.
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar The details of how to do this will depend on how you built
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar your kernel, and if you are unsure you should consult the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar documentation which you followed to do so.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar </itemizedlist>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The kernel of your Linux host was updated and DKMS is not
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar installed. In that case, the kernel module will need to be
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar reinstalled by executing (as root):</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>VirtualBox is available in a number of package formats native to
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar various common Linux distributions (see <xref linkend="hostossupport" />
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar for details). In addition, there is an alternative generic installer
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar (.run) which should work on most Linux distributions.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <title>Installing VirtualBox from a Debian/Ubuntu package</title>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>First, download the appropriate package for your distribution.
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar The following examples assume that you are installing to a 32-bit
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar Ubuntu Karmic system. Use <computeroutput>dpkg</computeroutput> to
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar install the Debian package:</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <screen>sudo dpkg -i VirtualBox-3.2_$VBOX_VERSION_STRING_Ubuntu_karmic_i386.deb</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>You will be asked to accept the VirtualBox Personal Use and
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar Evaluation License. Unless you answer "yes" here, the installation
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar will be aborted.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The installer will also search for a VirtualBox kernel module
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar suitable for your kernel. The package includes pre-compiled modules
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar for the most common kernel configurations. If no suitable kernel
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar module is found, the installation script tries to build a module
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar itself. If the build process is not successful you will be shown a
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar warning and the package will be left unconfigured. Please have a look
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar at <computeroutput>/var/log/vbox-install.log</computeroutput> to find
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar out why the compilation failed. You may have to install the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar appropriate Linux kernel headers (see <xref
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar linkend="externalkernelmodules" />). After correcting any problems, do
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <screen>sudo /etc/init.d/vboxdrv setup</screen>This will start a
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar second attempt to build the module.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>If a suitable kernel module was found in the package or the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar module was successfully built, the installation script will attempt to
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar load that module. If this fails, please see <xref
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar linkend="linuxkernelmodulefailstoload" /> for further
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar information.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Once VirtualBox has been successfully installed and configured,
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar you can start it by selecting "VirtualBox" in your start menu or from
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar the command line (see <xref linkend="startingvboxonlinux" />).</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <title>Using the alternative installer (VirtualBox.run)</title>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The alternative installer performs the following steps:</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <itemizedlist>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>It unpacks the application files to the target directory,
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <screen>/opt/VirtualBox/</screen> which cannot be changed.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>It builds the VirtualBox kernel modules
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>vboxnetflt</computeroutput> and
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>vboxnetadp</computeroutput>) and installs
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>It creates
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>/etc/init.d/vboxdrv</computeroutput>, an init
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar script to start the VirtualBox kernel module.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>It creates a new system group called
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>vboxusers</computeroutput>.</para>
a307732568c3d861c38b0342ae32434226d10e94Pramod Gunjikar <para>It creates symbolic links in
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>/usr/bin</computeroutput> to the a shell script
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar (<computeroutput>/opt/VirtualBox/VBox</computeroutput>) which does
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar some sanity checks and dispatches to the actual executables,
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>VirtualBox</computeroutput>,
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>VBoxHeadless</computeroutput> and
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>VBoxManage</computeroutput></para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>It creates
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>/etc/udev/rules.d/10-vboxdrv.rules</computeroutput>,
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar a description file for udev, if that is present, which makes the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar USB devices accessible to all users in the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>vboxusers</computeroutput> group.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>It writes the installation directory to
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>/etc/vbox/vbox.cfg</computeroutput>.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar </itemizedlist>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The installer must be executed as root with either
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>uninstall</computeroutput> as the first
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar parameter.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <screen>sudo /VirtualBox.run install</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Or if you do not have the "sudo" command available, run the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar following as root instead:<screen>/VirtualBox.run install</screen></para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>After that you need to put every user which should be able to
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar access USB devices from VirtualBox guests in the group
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>vboxusers</computeroutput>, either through the GUI
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar user management tools or by running the following command as
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <screen>sudo usermod -a -G vboxusers username</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The <computeroutput>usermod</computeroutput> command of some
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar older Linux distributions does not support the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>-a</computeroutput> option (which adds the user to
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar the given group without affecting membership of other groups). In
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar this case, find out the current group memberships with the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>groups</computeroutput> command and add all these
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar groups in a comma-separated list to the command line after the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>-G</computeroutput> option, e.g. like this:
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>usermod -G group1,group2,vboxusers
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <title>Performing a manual installation</title>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>If, for any reason, you cannot use the shell script installer
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar described previously, you can also perform a manual installation.
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar Invoke the installer like this:</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <screen>/VirtualBox.run --keep --noexec</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>This will unpack all the files needed for installation in the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar directory <computeroutput>install</computeroutput> under the current
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar directory. The VirtualBox application files are contained in
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>VirtualBox.tar.bz2</computeroutput> which you can
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar unpack to any directory on your system. For example:</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikarsudo tar jxf /install/VirtualBox.tar.bz2 -C /opt/VirtualBox</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>or as root:<screen>mkdir /opt/VirtualBox
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikartar jxf /install/VirtualBox.tar.bz2 -C /opt/VirtualBox</screen></para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The sources for VirtualBox's kernel module are provided in the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>src</computeroutput> directory. To build the module,
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar change to the directory and issue</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>If everything builds correctly, issue the following command to
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar install the module to the appropriate module directory:</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>In case you do not have sudo, switch the user account to root
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar and perform<screen>make install</screen></para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The VirtualBox kernel module needs a device node to operate. The
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar above make command will tell you how to create the device node,
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar depending on your Linux system. The procedure is slightly different
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar for a classical Linux setup with a
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>/dev</computeroutput> directory, a system with the now
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar deprecated <computeroutput>devfs</computeroutput> and a modern Linux
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar system with <computeroutput>udev</computeroutput>.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>On certain Linux distributions, you might experience
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar difficulties building the module. You will have to analyze the error
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar messages from the build system to diagnose the cause of the problems.
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar In general, make sure that the correct Linux kernel sources are used
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar for the build process.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Note that the <computeroutput>/dev/vboxdrv</computeroutput>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar kernel module device node must be owned by root:root and must be
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Next, you will have to install the system initialization script
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar for the kernel module:<screen>cp /opt/VirtualBox/vboxdrv.sh /etc/init.d/vboxdrv</screen>(assuming
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar you installed VirtualBox to the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>/opt/VirtualBox</computeroutput> directory) and
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar activate the initialization script using the right method for your
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar distribution. You should create VirtualBox's configuration
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikarecho INSTALL_DIR=/opt/VirtualBox > /etc/vbox/vbox.cfg</screen>and, for
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar convenience, create the following symbolic links:</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <screen>ln -sf /opt/VirtualBox/VBox.sh /usr/bin/VirtualBox
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikarln -sf /opt/VirtualBox/VBox.sh /usr/bin/VBoxManage
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikarln -sf /opt/VirtualBox/VBox.sh /usr/bin/VBoxHeadless
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikarln -sf /opt/VirtualBox/VBox.sh /usr/bin/VBoxSDL</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <title>Updating and uninstalling VirtualBox</title>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Before updating or uninstalling VirtualBox, you must terminate
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar any virtual machines which are currently running and exit the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar VirtualBox or VBoxSVC applications. To update VirtualBox, simply run
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar the installer of the updated version. To uninstall VirtualBox, invoke
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar the installer like this: <screen>sudo /VirtualBox.run uninstall</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar or as root<screen>/VirtualBox.run uninstall</screen>. Starting with
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar version 2.2.2, you can uninstall the .run package by invoking <screen>/opt/VirtualBox/uninstall.sh</screen>To
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar manually uninstall VirtualBox, simply undo the steps in the manual
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar installation in reverse order.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <title>Automatic installation of Debian packages</title>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The Debian packages will request some user feedback when
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar installed for the first time. The debconf system is used to perform
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar this task. To prevent any user interaction during installation,
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar default values can be defined. A file
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>vboxconf</computeroutput> can contain the following
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar debconf settings: <screen>virtualbox virtualbox/module-compilation-allowed boolean true
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikarvirtualbox virtualbox/delete-old-modules boolean true</screen>The first line
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar allows compilation of the vboxdrv kernel module if no module was found
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar for the current kernel. The second line allows the package to delete
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar any old vboxdrv kernel modules compiled by previous
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar installations.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>These default settings can be applied with <screen>debconf-set-selections vboxconf</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar prior to the installation of the VirtualBox Debian package.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>In addition there are some common configuration options that can
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar be set prior to the installation, described in <xref
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <title>Automatic installation of .rpm packages</title>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The .rpm format does not provide a configuration system
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar comparable to the debconf system. See <xref
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar linkend="linux_install_opts" /> for how to set some common
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar installation options provided by VirtualBox.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <title id="linux_install_opts">Automatic installation options</title>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>To configure the installation process of our .deb and .rpm
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar packages, you can create a response file named
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>/etc/default/virtualbox</computeroutput>. The
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar automatic generation of the udev rule can be prevented by the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar following setting: <screen>INSTALL_NO_UDEV=1</screen> The creation of
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar the group vboxusers can be prevented by <screen>INSTALL_NO_GROUP=1</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar If the line <screen>INSTALL_NO_VBOXDRV=1</screen> is specified, the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar package installer will not try to build the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>vboxdrv</computeroutput> kernel module if no module
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar fitting the current kernel was found.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The Linux installers create the system user group
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>vboxusers</computeroutput> during installation. Any
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar system user who is going to use USB devices from VirtualBox guests must
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar be a member of that group. A user can be made a member of the group
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>vboxusers</computeroutput> through the GUI user/group
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar management or at the command line with</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <screen>sudo usermod -a -G vboxusers username</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Note that adding an active user to that group will require that
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar user to log out and back in again. This should be done manually after
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar successful installation of the package.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The easiest way to start a VirtualBox program is by running the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar program of your choice (<computeroutput>VirtualBox</computeroutput>,
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>VBoxManage</computeroutput>,
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>VBoxHeadless</computeroutput>) from a terminal. These
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar are symbolic links to <computeroutput>VBox.sh</computeroutput> that
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar start the required program for you.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The following detailed instructions should only be of interest if
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar you wish to execute VirtualBox without installing it first. You should
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar start by compiling the <computeroutput>vboxdrv</computeroutput> kernel
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar module (see above) and inserting it into the Linux kernel. VirtualBox
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar consists of a service daemon (<computeroutput>VBoxSVC</computeroutput>)
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar and several application programs. The daemon is automatically started if
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar necessary. All VirtualBox applications will communicate with the daemon
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar through Unix local domain sockets. There can be multiple daemon
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar instances under different user accounts and applications can only
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar communicate with the daemon running under the user account as the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar application. The local domain socket resides in a subdirectory of your
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar system's directory for temporary files called
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>.vbox-<username>-ipc</computeroutput>. In case of
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar communication problems or server startup problems, you may try to remove
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar this directory.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>All VirtualBox applications
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar (<computeroutput>VirtualBox</computeroutput>,
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>VBoxManage</computeroutput> and
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>VBoxHeadless</computeroutput>) require the VirtualBox
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar directory to be in the library path:</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <screen>LD_LIBRARY_PATH=. /VBoxManage showvminfo "Windows XP"</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <title id="install-solaris-host">Installing on Solaris hosts</title>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>For the specific versions of Solaris that we support as host
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar operating systems, please refer to <xref
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>If you have a previously installed instance of VirtualBox on your
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar Solaris host, please uninstall it first before installing a new instance.
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar Refer to <xref linkend="uninstallsolhost" /> for uninstall
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar instructions.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>VirtualBox is available as a standard Solaris package. Download
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar the VirtualBox SunOS package which includes both the 32-bit and 64-bit
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar versions of VirtualBox. <emphasis>The installation must be performed as
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar root and from the global zone</emphasis> as the VirtualBox installer
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar loads kernel drivers which cannot be done from non-global zones. To
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar verify which zone you are currently in, execute the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>zonename</computeroutput> command. Execute the following
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar commands:</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <screen>gunzip -cd VirtualBox-$VBOX_VERSION_STRING-SunOS.tar.gz | tar xvf -</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Starting with VirtualBox 3.1 the VirtualBox kernel package is no
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar longer a separate package and has been integrated into the main package.
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar Install the VirtualBox package using:</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <screen>pkgadd -d VirtualBox-$VBOX_VERSION_STRING-SunOS.pkg</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>If you are using Solaris Zones, to install VirtualBox only into
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar the current zone and not into any other zone, use
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>pkgadd -G</computeroutput>. For more information refer
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar to the <computeroutput>pkgadd</computeroutput> manual; see also <xref
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The installer will then prompt you to enter the package you wish
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar to install. Choose "1" or "all" and proceed. Next the installer will ask
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar you if you want to allow the postinstall script to be executed. Choose
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar "y" and proceed as it is essential to execute this script which installs
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar the VirtualBox kernel module. Following this confirmation the installer
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar will install VirtualBox and execute the postinstall setup script.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Once the postinstall script has been executed your installation is
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar now complete. You may now safely delete the uncompressed package and
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>autoresponse</computeroutput> files from your system.
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar VirtualBox would be installed in
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>/opt/VirtualBox</computeroutput>.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Starting with VirtualBox 4.1, the installer creates the system
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar user group <computeroutput>vboxuser</computeroutput> during installation
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar for Solaris hosts that support the required USB features for VirtualBox.
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar Any system user who is going to use USB devices from VirtualBox guests
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar must be a member of that group. A user can be made a member of this
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar group through the GUI user/group management or at the command line by
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar executing as root:</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <screen>usermod -G vboxuser username</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Adding an active user to the group will require that user to log
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar out and back in again. This must be done manually after installing
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar VirtualBox.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <title>Starting VirtualBox on Solaris</title>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>The easiest way to start a VirtualBox program is by running the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar program of your choice (<computeroutput>VirtualBox</computeroutput>,
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>VBoxManage</computeroutput>,
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>VBoxHeadless</computeroutput>) from a terminal. These
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar are symbolic links to <computeroutput>VBox.sh</computeroutput> that
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar start the required program for you.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Alternatively, you can directly invoke the required programs from
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <computeroutput>/opt/VirtualBox</computeroutput>. Using the links
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar provided is easier as you do not have to type the full path.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>You can configure some elements of the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>VirtualBox</computeroutput> Qt GUI such as fonts and
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar colours by executing <computeroutput>VBoxQtconfig</computeroutput> from
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung the terminal.</para>
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <title id="uninstallsolhost">Uninstallation</title>
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <para>Uninstallation of VirtualBox on Solaris requires root permissions.
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung To perform the uninstallation, start a root terminal session and
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar execute:</para>
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <para>After confirmation, this will remove VirtualBox from your
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung system.</para>
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <para>If you are uninstalling VirtualBox version 3.0 or lower, you need
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung to remove the VirtualBox kernel interface package, execute:</para>
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <para><screen>pkgrm SUNWvboxkern</screen></para>
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <para>To perform a non-interactive installation of VirtualBox we have
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung provided a response file named
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <computeroutput>autoresponse</computeroutput> that the installer will
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung use for responses to inputs rather than ask them from you.</para>
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <para>Extract the tar.gz package as described in the normal
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung installation. Then open a root terminal session and execute:</para>
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <screen>pkgadd -d VirtualBox-$VBOX_VERSION_STRING-SunOS-x86 -n -a autoresponse SUNWvbox</screen>
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <para>To perform a non-interactive uninstallation, open a root terminal
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar session and execute:</para>
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <screen>pkgrm -n -a /opt/VirtualBox/autoresponse SUNWvbox</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <title id="solariszones">Configuring a zone for running
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung VirtualBox</title>
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <para>Starting with VirtualBox 1.6 it is possible to run VirtualBox from
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung within Solaris zones. For an introduction of Solaris zones, please refer
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung url="http://www.sun.com/bigadmin/features/articles/solaris_zones.jsp">http://www.sun.com/bigadmin/features/articles/solaris_zones.jsp</ulink>.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Assuming that VirtualBox has already been installed into your
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar zone, you need to give the zone access to VirtualBox's device node. This
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar is done by performing the following steps. Start a root terminal and
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung execute:</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Inside the <computeroutput>zonecfg</computeroutput> prompt add the
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>device</computeroutput> resource and
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>match</computeroutput> properties to the zone. Here's
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar how it can be done:</para>
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheung <screen>zonecfg:vboxzone>add device
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikarzonecfg:vboxzone:device>set match=/dev/vboxdrv
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheungzonecfg:vboxzone:device>end
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheungzonecfg:vboxzone>verify
fffafeb2cc01732fd6a28ed530e4424094685eceJohnny Cheungzonecfg:vboxzone>exit</screen>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>If you are running VirtualBox 2.2.0 or above on Solaris 11 or
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar Nevada hosts, you should add a device for
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>/dev/vboxusbmon</computeroutput> too, similar to what
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar was shown above. This does not apply to Solaris 10 hosts due to lack of
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar USB support.</para>
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <para>Replace "vboxzone" with the name of the zone in which you intend
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar to run VirtualBox. Next reboot the zone using
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar <computeroutput>zoneadm</computeroutput> and you should be able to run
c39526b769298791ff5b0b6c5e761f49aabaeb4ePramod Gunjikar VirtualBox from within the configured zone.</para>