VirtualBox

Changeset 34392 in vbox


Ignore:
Timestamp:
Nov 26, 2010 12:26:27 PM (14 years ago)
Author:
vboxsync
Message:

Manual: fix invalid XML

Location:
trunk/doc/manual/en_US
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • trunk/doc/manual/en_US/SDKRef.xml

    r33539 r34392  
    19251925      xreflabel="IVirtualBox" />), from which all other functionality of the
    19261926      API is derived. With the OOWS for JAX-WS, this is returned from the
    1927       <xref linkend="???" xreflabel="IWebsessionManager::logon()" />
    1928       call.</para>
     1927      <xref linkend="IWebsessionManager__logon"
     1928      xreflabel="IWebsessionManager::logon()" /> call.</para>
    19291929
    19301930      <para>To enumerate virtual machines, one would look at the "machines"
    … …  
    21032103      support callbacks. The new mechanism with events and event listeners
    21042104      works with all of these.</para>
    2105       <para>To simplify developement of application using events,
    2106       concept of event aggregator was introduced. Essentially it's
    2107       mechanism to aggregate multiple event sources into single one,
    2108       and then work with this single aggregated event source instead of
    2109       original sources. As an example, one can evaluate demo recorder
    2110       in VirtualBox Python shell, shipped with SDK - it records mouse
    2111       and keyboard events, represented as separate event sources.
    2112       Code is essentially like this:<screen>
     2105
     2106      <para>To simplify developement of application using events, concept of
     2107      event aggregator was introduced. Essentially it's mechanism to aggregate
     2108      multiple event sources into single one, and then work with this single
     2109      aggregated event source instead of original sources. As an example, one
     2110      can evaluate demo recorder in VirtualBox Python shell, shipped with SDK
     2111      - it records mouse and keyboard events, represented as separate event
     2112      sources. Code is essentially like this:<screen>
    21132113          listener = console.eventSource.createListener()
    21142114          agg = console.eventSource.createAggregator([console.keyboard.eventSource, console.mouse.eventSource])
    … …  
    21192119              ev = agg.getEvent(listener, 1000)
    21202120              processEent(ev)
    2121           agg.unregisterListener(listener)</screen>
    2122          Without using aggregators consumer have to poll on both
    2123          sources, or start multiple threads to block on those sources.
    2124       </para>
     2121          agg.unregisterListener(listener)</screen> Without using aggregators
     2122      consumer have to poll on both sources, or start multiple threads to
     2123      block on those sources.</para>
    21252124    </sect1>
    21262125  </chapter>
    … …  
    30463045
    30473046              <listitem>
    3048                  RDPWebClient.isRDPWebControlById(ElementId)
     3047                <programlisting>RDPWebClient.isRDPWebControlById(ElementId)</programlisting>
    30493048
    30503049                <para>Returns true if the given id refers to a RDPWeb Flash
    30513050                element.</para>
    3052 
    3053                  
    3054               </listitem>
    3055 
    3056               <listitem>
    3057                  RDPWebClient.isRDPWebControlByElement(Element)
     3051              </listitem>
     3052
     3053              <listitem>
     3054                <programlisting>RDPWebClient.isRDPWebControlByElement(Element)</programlisting>
    30583055
    30593056                <para>Returns true if the given element is a RDPWeb Flash
    30603057                element.</para>
    3061 
    3062                  
    3063               </listitem>
    3064 
    3065               <listitem>
    3066                  RDPWebClient.getFlashById(ElementId)
     3058              </listitem>
     3059
     3060              <listitem>
     3061                <programlisting>RDPWebClient.getFlashById(ElementId)</programlisting>
    30673062
    30683063                <para>Returns an element, which is referenced by the given id.
    30693064                This function will try to resolve any element, event if it is
    30703065                not a Flash movie.</para>
    3071 
    3072                  
    30733066              </listitem>
    30743067            </itemizedlist></para>

  • trunk/doc/manual/en_US/user_AdvancedTopics.xml

    r33386 r34392  
    298298      with a value of <computeroutput>VBoxGINA.dll</computeroutput>.</para>
    299299
    300       <para><note>
    301           The VirtualBox GINA is implemented as a wrapper around the standard Windows
    302           GINA (<computeroutput>MSGINA.DLL</computeroutput>),
    303           therefore it will most likely not work correctly with 3rd party GINA modules.
    304         </note></para>
     300      <note>
     301        <para>The VirtualBox GINA module is implemented as a wrapper around
     302        the standard Windows GINA module
     303        (<computeroutput>MSGINA.DLL</computeroutput>). As a result, it will
     304        most likely not work correctly with 3rd party GINA modules.</para>
     305      </note>
    305306
    306307      <para>To manually install the VirtualBox credential module, extract the
    … …  
    622623      <para>As described in <xref linkend="vbox-auth" />, VirtualBox supports
    623624      arbitrary external modules to perform authentication. When the
    624       authentication method is set to "external" for a
    625       particular VM, VirtualBox calls the library that was specified with
     625      authentication method is set to "external" for a particular VM,
     626      VirtualBox calls the library that was specified with
    626627      <computeroutput>VBoxManage setproperty vrdeauthlibrary</computeroutput>.
    627628      This library will be loaded by the VM process on demand, i.e. when the
    … …  
    952953
    953954    <para>The old sequence of configuring a serial port used the following 6
    954       commands:</para><screen>VBoxManage setextradata "VM name"
     955    commands:</para>
     956
     957    <screen>VBoxManage setextradata "VM name"
    955958      "VBoxInternal/Devices/serial/0/Config/IRQ" 4
    956959VBoxManage setextradata "VM name"
    … …  
    964967VBoxManage setextradata "VM name"
    965968      "VBoxInternal/Devices/serial/0/LUN#0/AttachedDriver/Config/IsServer" 1</screen>
    966     <para>This sets up a serial port in the guest with the default
    967     settings for COM1 (IRQ 4, I/O address 0x3f8) and the
     969
     970    <para>This sets up a serial port in the guest with the default settings
     971    for COM1 (IRQ 4, I/O address 0x3f8) and the
    968972    <computeroutput>Location</computeroutput> setting assumes that this
    969973    configuration is used on a Windows host, because the Windows named pipe
    … …  
    12881292
    12891293          <glossentry>
    1290             <glossterm><computeroutput>--timesync-set-on-restore 0|1</computeroutput></glossterm>
     1294            <glossterm><computeroutput>--timesync-set-on-restore
     1295            0|1</computeroutput></glossterm>
    12911296
    12921297            <glossdef>
    12931298              <para>Set the time after the VM was restored from a saved state
    1294                 when passing 1 as parameter (default). Disable by passing 0.
    1295                 In the latter case, the time will be adjusted smoothly which
    1296                 can take a long time.</para>
     1299              when passing 1 as parameter (default). Disable by passing 0. In
     1300              the latter case, the time will be adjusted smoothly which can
     1301              take a long time.</para>
    12971302            </glossdef>
    12981303          </glossentry>

  • trunk/doc/manual/en_US/user_GuestAdditions.xml

    r33768 r34392  
    11<?xml version="1.0" encoding="UTF-8"?>
    22<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
    3   "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
     3"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
    44<chapter>
    55  <title id="guestadditions">Guest Additions</title>
    … …  
    207207        <para>In the "Devices" menu in the virtual machine's menu bar,
    208208        VirtualBox has a handy menu item named "Install Guest Additions",
    209         which either allows to upgrade already installed Guest Additions
    210         (only Windows Guest Additions 4.0 and later) automatically or
    211         mounts the Guest Additions ISO file inside your virtual machine
    212         to perform a manual update.</para>
     209        which either allows to upgrade already installed Guest Additions (only
     210        Windows Guest Additions 4.0 and later) automatically or mounts the
     211        Guest Additions ISO file inside your virtual machine to perform a
     212        manual update.</para>
    213213
    214214        <para>In case of a manual update, a Windows guest should then
    … …  
    442442      <para>Note that some Linux distributions already come with VirtualBox
    443443      Guest Additions or a part thereof. You may keep the distribution's
    444       version of the Guest Additions but often, these are not up to date
    445       and limited in functionality. Therefore, you can choose the install
    446       the Guest Additions that come with VirtualBox, overriding the already
     444      version of the Guest Additions but often, these are not up to date and
     445      limited in functionality. Therefore, you can choose the install the
     446      Guest Additions that come with VirtualBox, overriding the already
    447447      installed version. The VirtualBox Linux Guest Additions installer tries
    448448      to detect existing installation and replace them but depending on how
    … …  
    472472
    473473            <para>Again, as with Linux hosts, we recommend using DKMS for
    474             Linux guests as well. If it is not installed, use this
    475             command for Ubuntu/Debian systems:<screen>sudo apt-get install dkms</screen>
     474            Linux guests as well. If it is not installed, use this command for
     475            Ubuntu/Debian systems:<screen>sudo apt-get install dkms</screen>
    476476            or for Fedora systems: <screen>yum install dkms</screen></para>
    477477
    478             <para>Make sure to nstall DKMS <emphasis>before</emphasis> installing the
    479             Linux Guest Additions.</para>
     478            <para>Make sure to nstall DKMS <emphasis>before</emphasis>
     479            installing the Linux Guest Additions.</para>
    480480          </listitem>
    481481
    … …  
    502502        <para>For your convenience, the following step-by-step instructions
    503503        have been verified to work for freshly installed copies of the most
    504         popular Linux distributions. After these preparational steps, you
    505         can execute the VirtualBox Guest Additions installer as described
     504        popular Linux distributions. After these preparational steps, you can
     505        execute the VirtualBox Guest Additions installer as described
    506506        above.</para>
    507507
    508         <sect4><title>Ubuntu 10.04 ("Lucid Lynx")</title><para>
    509         <orderedlist>
    510           <listitem>
    511             <para>In order to update your system to the latest version
    512             of the packets, open a terminal and as root, execute
    513             <screen>apt-get update</screen>
    514             followed by
    515             <screen>apt-get upgrade</screen></para>
    516           </listitem>
    517           <listitem>
    518             <para>Install DKMS using
    519             <screen>apt-get install dkms</screen></para>
    520           </listitem>
    521           <listitem>
    522             <para>Reboot your guest system in order to activate the
    523             updates and then proceed as described above.</para>
    524           </listitem>
    525         </orderedlist></para></sect4>
    526 
    527         <sect4><title>Fedora 13 ("Goddard")</title><para>
    528         <orderedlist>
    529           <listitem>
    530             <para>In order to update your system to the latest version
    531             of the packets, open a terminal and as root, execute
    532             <screen>yum update</screen></para>
    533           </listitem>
    534           <listitem>
    535             <para>Install DKMS and the GNU C compiler using
    536             <screen>yum install dkms</screen>
    537             followed by
    538             <screen>yum install gcc</screen></para>
    539           </listitem>
    540           <listitem>
    541             <para>Reboot your guest system in order to activate the
    542             updates and then proceed as described above.</para>
    543           </listitem>
    544         </orderedlist></para></sect4>
    545 
    546         <sect4><title>openSUSE 11.2</title><para>
    547         <orderedlist>
    548           <listitem>
    549             <para>In order to update your system to the latest version
    550             of the packets, open a terminal and as root, execute
    551             <screen>zypper update</screen></para>
    552           </listitem>
    553           <listitem>
    554             <para>Install the make tool and the GNU C compiler using
    555             <screen>zypper install make gcc</screen></para>
    556           </listitem>
    557           <listitem>
    558             <para>Reboot your guest system in order to activate the
    559             updates.</para>
    560           </listitem>
    561           <listitem>
    562             <para>Find out which kernel you are running using
    563             <screen>uname -a</screen>
    564             An example would be <computeroutput>2.6.31.12-0.2-default</computeroutput>
    565             which refers to the "default" kernel. Then install the correct kernel
    566             development package. In the above example this would be
    567             <screen>zypper install kernel-default-devel</screen></para>
    568           </listitem>
    569           <listitem>
    570             <para>Make sure that your running kernel
    571             (<computeroutput>uname -a</computeroutput>) and the kernel packages
    572             you have installed (<computeroutput>rpm -qa kernel\*</computeroutput>)
    573             have the exact same version number. Proceed with the installation as described
    574             above.</para>
    575           </listitem>
    576         </orderedlist></para></sect4>
    577 
    578         <sect4><title>SuSE Linux Enterprise Desktop (SLED) 11</title><para>
    579         <orderedlist>
    580           <listitem>
    581             <para>In order to update your system to the latest version
    582             of the packets, open a terminal and as root, execute
    583             <screen>zypper update</screen></para>
    584           </listitem>
    585           <listitem>
    586             <para>Install the GNU C compiler using
    587             <screen>zypper install gcc</screen></para>
    588           </listitem>
    589           <listitem>
    590             <para>Reboot your guest system in order to activate the
    591             updates.</para>
    592           </listitem>
    593           <listitem>
    594             <para>Find out which kernel you are running using
    595             <screen>uname -a</screen>
    596             An example would be <computeroutput>2.6.27.19-5.1-default</computeroutput>
    597             which refers to the "default" kernel. Then install the correct kernel
    598             development package. In the above example this would be
    599             <screen>zypper install kernel-syms kernel-source</screen></para>
    600           </listitem>
    601           <listitem>
    602             <para>Make sure that your running kernel
    603             (<computeroutput>uname -a</computeroutput>) and the kernel packages
    604             you have installed (<computeroutput>rpm -qa kernel\*</computeroutput>)
    605             have the exact same version number. Proceed with the installation as described
    606             above.</para>
    607           </listitem>
    608         </orderedlist></para></sect4>
    609 
    610         <sect4><title>Mandrake 2010</title><para>
    611         <orderedlist>
    612           <listitem>
    613             <para>Mandrake ships with the VirtualBox Guest Additions which
    614             will be replaced if you follow these steps.</para>
    615           </listitem>
    616           <listitem>
    617             <para>In order to update your system to the latest version
    618             of the packets, open a terminal and as root and execute
    619             <screen>urpmi --auto-update</screen></para>
    620           </listitem>
    621           <listitem><para>Reboot your system in order to activate the updates.</para>
    622           </listitem>
    623           <listitem><para>Install DKMS using
    624             <screen>urpmi dkms</screen>
    625             and make sure the choose the correct kernel-devel package when asked
    626             by the installer (use <computeroutput>uname -a</computeroutput> to compare).</para>
    627           </listitem>
    628         </orderedlist></para></sect4>
    629 
    630         <sect4><title>CentOS 5.5, Red Hat Enterprise Linux 5.5 and Oracle Enterprise
    631             Linux 5.5</title><para>
    632         <orderedlist>
    633           <listitem>
    634             <para>Add <computeroutput>divider=10</computeroutput> to the kernel boot options
    635             in <computeroutput>/etc/grub.conf</computeroutput> to reduce the idle CPU load.</para>
    636           </listitem>
    637           <listitem>
    638             <para>To update your system to the latest version
    639             of the packets, open a terminal and as root, execute
    640             <screen>yum update</screen></para>
    641           </listitem>
    642           <listitem>
    643             <para>Install the GNU C compiler and the kernel development packages using
    644             <screen>yum install gcc</screen>
    645             followed by
    646             <screen>yum install kernel-devel</screen></para>
    647           </listitem>
    648           <listitem>
    649             <para>Reboot your guest system in order to activate the
    650             updates and then proceed as described above.</para>
    651           </listitem>
    652           <listitem>
    653             <para>Note that OpenGL support is not available unless you update to a later Linux kernel.</para>
    654             <para>In case Oracle Enterprise Linux does not find the required packages, you either have to
    655             install them from a different source (e.g. DVD) or use Oracle's public Yum server located at
    656             <ulink url="http://public-yum.oracle.com/">http://public-yum.oracle.com</ulink>.</para>
    657           </listitem>
    658         </orderedlist></para></sect4>
    659 
    660         <sect4><title>Debian 5 ("Lenny")</title><para>
    661         <orderedlist>
    662           <listitem>
    663             <para>In order to update your system to the latest version
    664             of the packets, open a terminal and as root, execute
    665             <screen>apt-get update</screen>
    666             followed by
    667             <screen>apt-get upgrade</screen></para>
    668           </listitem>
    669           <listitem>
    670             <para>Install the make tool and the GNU C compiler using
    671             <screen>apt-get install make gcc</screen></para>
    672           </listitem>
    673           <listitem>
    674             <para>Reboot your guest system in order to activate the
    675             updates.</para>
    676           </listitem>
    677           <listitem>
    678             <para>Determine the exact version of your kernel using
    679             <computeroutput>uname -a</computeroutput> and install the correct version
    680             of the linux-headers package, e.g. using
    681             <screen>apt-get install linux-headers-2.6.26-2-686</screen></para>
    682 
    683           <listitem>
    684             <para>Note that OpenGL support is not available unless you update to a later Linux kernel.</para>
    685           </listitem>
    686           </listitem>
    687         </orderedlist></para></sect4>
    688         </sect3>
    689 
    690         <sect3><title>Manual setup of selected guest services</title>
     508        <sect4>
     509          <title>Ubuntu 10.04 ("Lucid Lynx")</title>
     510
     511          <para><orderedlist>
     512              <listitem>
     513                <para>In order to update your system to the latest version of
     514                the packets, open a terminal and as root, execute <screen>apt-get update</screen>
     515                followed by <screen>apt-get upgrade</screen></para>
     516              </listitem>
     517
     518              <listitem>
     519                <para>Install DKMS using <screen>apt-get install dkms</screen></para>
     520              </listitem>
     521
     522              <listitem>
     523                <para>Reboot your guest system in order to activate the
     524                updates and then proceed as described above.</para>
     525              </listitem>
     526            </orderedlist></para>
     527        </sect4>
     528
     529        <sect4>
     530          <title>Fedora 13 ("Goddard")</title>
     531
     532          <para><orderedlist>
     533              <listitem>
     534                <para>In order to update your system to the latest version of
     535                the packets, open a terminal and as root, execute <screen>yum update</screen></para>
     536              </listitem>
     537
     538              <listitem>
     539                <para>Install DKMS and the GNU C compiler using <screen>yum install dkms</screen>
     540                followed by <screen>yum install gcc</screen></para>
     541              </listitem>
     542
     543              <listitem>
     544                <para>Reboot your guest system in order to activate the
     545                updates and then proceed as described above.</para>
     546              </listitem>
     547            </orderedlist></para>
     548        </sect4>
     549
     550        <sect4>
     551          <title>openSUSE 11.2</title>
     552
     553          <para><orderedlist>
     554              <listitem>
     555                <para>In order to update your system to the latest version of
     556                the packets, open a terminal and as root, execute <screen>zypper update</screen></para>
     557              </listitem>
     558
     559              <listitem>
     560                <para>Install the make tool and the GNU C compiler using
     561                <screen>zypper install make gcc</screen></para>
     562              </listitem>
     563
     564              <listitem>
     565                <para>Reboot your guest system in order to activate the
     566                updates.</para>
     567              </listitem>
     568
     569              <listitem>
     570                <para>Find out which kernel you are running using <screen>uname -a</screen>
     571                An example would be
     572                <computeroutput>2.6.31.12-0.2-default</computeroutput> which
     573                refers to the "default" kernel. Then install the correct
     574                kernel development package. In the above example this would be
     575                <screen>zypper install kernel-default-devel</screen></para>
     576              </listitem>
     577
     578              <listitem>
     579                <para>Make sure that your running kernel
     580                (<computeroutput>uname -a</computeroutput>) and the kernel
     581                packages you have installed (<computeroutput>rpm -qa
     582                kernel\*</computeroutput>) have the exact same version number.
     583                Proceed with the installation as described above.</para>
     584              </listitem>
     585            </orderedlist></para>
     586        </sect4>
     587
     588        <sect4>
     589          <title>SuSE Linux Enterprise Desktop (SLED) 11</title>
     590
     591          <para><orderedlist>
     592              <listitem>
     593                <para>In order to update your system to the latest version of
     594                the packets, open a terminal and as root, execute <screen>zypper update</screen></para>
     595              </listitem>
     596
     597              <listitem>
     598                <para>Install the GNU C compiler using <screen>zypper install gcc</screen></para>
     599              </listitem>
     600
     601              <listitem>
     602                <para>Reboot your guest system in order to activate the
     603                updates.</para>
     604              </listitem>
     605
     606              <listitem>
     607                <para>Find out which kernel you are running using <screen>uname -a</screen>
     608                An example would be
     609                <computeroutput>2.6.27.19-5.1-default</computeroutput> which
     610                refers to the "default" kernel. Then install the correct
     611                kernel development package. In the above example this would be
     612                <screen>zypper install kernel-syms kernel-source</screen></para>
     613              </listitem>
     614
     615              <listitem>
     616                <para>Make sure that your running kernel
     617                (<computeroutput>uname -a</computeroutput>) and the kernel
     618                packages you have installed (<computeroutput>rpm -qa
     619                kernel\*</computeroutput>) have the exact same version number.
     620                Proceed with the installation as described above.</para>
     621              </listitem>
     622            </orderedlist></para>
     623        </sect4>
     624
     625        <sect4>
     626          <title>Mandrake 2010</title>
     627
     628          <para><orderedlist>
     629              <listitem>
     630                <para>Mandrake ships with the VirtualBox Guest Additions which
     631                will be replaced if you follow these steps.</para>
     632              </listitem>
     633
     634              <listitem>
     635                <para>In order to update your system to the latest version of
     636                the packets, open a terminal and as root and execute <screen>urpmi --auto-update</screen></para>
     637              </listitem>
     638
     639              <listitem>
     640                <para>Reboot your system in order to activate the
     641                updates.</para>
     642              </listitem>
     643
     644              <listitem>
     645                <para>Install DKMS using <screen>urpmi dkms</screen> and make
     646                sure the choose the correct kernel-devel package when asked by
     647                the installer (use <computeroutput>uname -a</computeroutput>
     648                to compare).</para>
     649              </listitem>
     650            </orderedlist></para>
     651        </sect4>
     652
     653        <sect4>
     654          <title>CentOS 5.5, Red Hat Enterprise Linux 5.5 and Oracle
     655          Enterprise Linux 5.5</title>
     656
     657          <para><orderedlist>
     658              <listitem>
     659                <para>Add <computeroutput>divider=10</computeroutput> to the
     660                kernel boot options in
     661                <computeroutput>/etc/grub.conf</computeroutput> to reduce the
     662                idle CPU load.</para>
     663              </listitem>
     664
     665              <listitem>
     666                <para>To update your system to the latest version of the
     667                packets, open a terminal and as root, execute <screen>yum update</screen></para>
     668              </listitem>
     669
     670              <listitem>
     671                <para>Install the GNU C compiler and the kernel development
     672                packages using <screen>yum install gcc</screen> followed by
     673                <screen>yum install kernel-devel</screen></para>
     674              </listitem>
     675
     676              <listitem>
     677                <para>Reboot your guest system in order to activate the
     678                updates and then proceed as described above.</para>
     679              </listitem>
     680
     681              <listitem>
     682                <para>Note that OpenGL support is not available unless you
     683                update to a later Linux kernel.</para>
     684
     685                <para>In case Oracle Enterprise Linux does not find the
     686                required packages, you either have to install them from a
     687                different source (e.g. DVD) or use Oracle's public Yum server
     688                located at <ulink
     689                url="http://public-yum.oracle.com/">http://public-yum.oracle.com</ulink>.</para>
     690              </listitem>
     691            </orderedlist></para>
     692        </sect4>
     693
     694        <sect4>
     695          <title>Debian 5 ("Lenny")</title>
     696
     697          <para><orderedlist>
     698              <listitem>
     699                <para>In order to update your system to the latest version of
     700                the packets, open a terminal and as root, execute <screen>apt-get update</screen>
     701                followed by <screen>apt-get upgrade</screen></para>
     702              </listitem>
     703
     704              <listitem>
     705                <para>Install the make tool and the GNU C compiler using
     706                <screen>apt-get install make gcc</screen></para>
     707              </listitem>
     708
     709              <listitem>
     710                <para>Reboot your guest system in order to activate the
     711                updates.</para>
     712              </listitem>
     713
     714              <listitem>
     715                <para>Determine the exact version of your kernel using
     716                <computeroutput>uname -a</computeroutput> and install the
     717                correct version of the linux-headers package, e.g. using
     718                <screen>apt-get install linux-headers-2.6.26-2-686</screen></para>
     719
     720                <para>Note that OpenGL support is not available unless you
     721                update to a later Linux kernel.</para>
     722              </listitem>
     723            </orderedlist></para>
     724        </sect4>
     725      </sect3>
     726
     727      <sect3>
     728        <title>Manual setup of selected guest services</title>
     729
    691730        <para>The VirtualBox Guest Additions contain several different
    692731        drivers. If for any reason you do not wish to set them all up, you can
    … …  
    701740        by running the command <screen>  /usr/lib/VBoxGuestAdditions/vboxadd setup</screen>
    702741        as root (you will need to replace <emphasis>lib</emphasis> by
    703         <emphasis>lib64</emphasis>
    704         on some 64bit guests), and on older guests without the udev service
    705         you will need to add the <emphasis>vboxadd</emphasis> service to the
    706         default runlevel to ensure that the modules get loaded.</para>
     742        <emphasis>lib64</emphasis> on some 64bit guests), and on older guests
     743        without the udev service you will need to add the
     744        <emphasis>vboxadd</emphasis> service to the default runlevel to ensure
     745        that the modules get loaded.</para>
    707746
    708747        <para>To setup the time synchronization service, run the command
    … …  
    777816
    778817        <para>If you have a version of the Guest Additions installed on your
    779         virtual machine and wish to remove it without installing new ones,
    780         you can do so by inserting the Guest Additions CD image into the
    781         virtual CD-ROM drive as described above and running the installer for
    782         the current Guest Additions with the "uninstall" parameter from the
    783         path that the CD image is mounted on in the guest:
    784         <screen>sh ./VBoxLinuxAdditions-x86.run uninstall</screen>
    785         <para>(substituting <computeroutput>VBoxLinuxAdditions-amd64</computeroutput>
    786           on a 64-bit guest).  While this will normally work
    787         without issues, you may need to do some manual clean up of the guest
    788         (particularly of the XFree86Config or xorg.conf file) in some cases,
    789         particularly if the Additions version installed or the guest
    790         operating system were very old, or if you made your own changes to
    791         the Guest Additions setup after you installed them.</para>
    792        </para>
    793        <para>
    794          Starting with version 3.1.0, you can uninstall the Additions
    795          by invoking
    796          <screen>/opt/VBoxGuestAdditions-$VBOX_VERSION_STRING/uninstall.sh</screen>
    797          substituting <computeroutput>/opt/VBoxGuestAdditions-$VBOX_VERSION_STRING</computeroutput>
    798          with the Guest Additions installation directory.
    799        </para>
     818        virtual machine and wish to remove it without installing new ones, you
     819        can do so by inserting the Guest Additions CD image into the virtual
     820        CD-ROM drive as described above and running the installer for the
     821        current Guest Additions with the "uninstall" parameter from the path
     822        that the CD image is mounted on in the guest: <screen>sh ./VBoxLinuxAdditions-x86.run uninstall</screen></para>
     823
     824        <para>With a 64-bit guest, use
     825        <computeroutput>VBoxLinuxAdditions-amd64</computeroutput> instead.
     826        While this will normally work without issues, you may need to do some
     827        manual cleanup of the guest (particularly of the XFree86Config or
     828        xorg.conf file) in some cases, particularly if the Additions version
     829        installed or the guest operating system were very old, or if you made
     830        your own changes to the Guest Additions setup after you installed
     831        them.</para>
     832
     833        <para>Starting with version 3.1.0, you can uninstall the Additions by
     834        invoking <screen>/opt/VBoxGuestAdditions-$VBOX_VERSION_STRING/uninstall.sh</screen>Please
     835        replace
     836        <computeroutput>/opt/VBoxGuestAdditions-$VBOX_VERSION_STRING</computeroutput>
     837        with the correct Guest Additions installation directory.</para>
    800838      </sect3>
    801839    </sect2>
    … …  
    9791017      <title>Manual mounting</title>
    9801018
    981         <para>You can mount the shared folder from inside a VM the same way
    982         as you would mount an ordinary network share:</para>
    983 
    984         <para><itemizedlist>
    985         <listitem>
    986           <para>In a Windows guest, starting with VirtualBox 1.5.0, shared
    987           folders are browseable and are therefore visible in Windows
    988           Explorer. So, to attach the host's shared folder to your Windows
    989           guest, open Windows Explorer and look for it under "My Networking
    990           Places" -&gt; "Entire Network" -&gt; "VirtualBox Shared Folders". By
    991           right-clicking on a shared folder and selecting "Map network drive"
    992           from the menu that pops up, you can assign a drive letter to that
    993           shared folder.</para>
    994 
    995           <para>Alternatively, on the Windows command line, use the
    996           following:</para>
    997 
    998           <screen>net use x: \\vboxsvr\sharename</screen>
    999 
    1000           <para>While <computeroutput>vboxsvr</computeroutput> is a fixed name
    1001           (note that <computeroutput>vboxsrv</computeroutput> would also
    1002           work), replace "x:" with the drive letter that you want to use for
    1003           the share, and <computeroutput>sharename</computeroutput> with the
    1004           share name specified with
    1005           <computeroutput>VBoxManage</computeroutput>.</para>
    1006         </listitem>
    1007 
    1008         <listitem>
    1009           <para>In a Linux guest, use the following command:</para>
    1010 
    1011           <screen>mount -t vboxsf [-o OPTIONS] sharename mountpoint</screen>
    1012 
    1013           <para>To mount a shared folder during boot, add the following entry
    1014           to /etc/fstab:</para>
    1015 
    1016           <screen>sharename   mountpoint   vboxsf   defaults  0   0</screen>
    1017         </listitem>
    1018 
    1019         <listitem>
    1020           <para>In a Solaris guest, use the following command:</para>
    1021 
    1022           <screen>mount -F vboxfs [-o OPTIONS] sharename mountpoint</screen>
    1023 
    1024           <para>Replace <computeroutput>sharename</computeroutput> (use
    1025           lowercase) with the share name specified with
    1026           <computeroutput>VBoxManage</computeroutput> or the GUI, and
    1027           <computeroutput>mountpoint</computeroutput> with the path where you
    1028           want the share to be mounted on the guest (e.g.
    1029           <computeroutput>/mnt/share</computeroutput>). The usual mount rules
    1030           apply, that is, create this directory first if it does not exist
    1031           yet.</para>
    1032 
    1033           <para>Here is an example of mounting the shared folder for the user
    1034           "jack" on OpenSolaris:</para>
    1035 
    1036           <screen>$ id
     1019      <para>You can mount the shared folder from inside a VM the same way as
     1020      you would mount an ordinary network share:</para>
     1021
     1022      <para><itemizedlist>
     1023          <listitem>
     1024            <para>In a Windows guest, starting with VirtualBox 1.5.0, shared
     1025            folders are browseable and are therefore visible in Windows
     1026            Explorer. So, to attach the host's shared folder to your Windows
     1027            guest, open Windows Explorer and look for it under "My Networking
     1028            Places" -&gt; "Entire Network" -&gt; "VirtualBox Shared Folders".
     1029            By right-clicking on a shared folder and selecting "Map network
     1030            drive" from the menu that pops up, you can assign a drive letter
     1031            to that shared folder.</para>
     1032
     1033            <para>Alternatively, on the Windows command line, use the
     1034            following:</para>
     1035
     1036            <screen>net use x: \\vboxsvr\sharename</screen>
     1037
     1038            <para>While <computeroutput>vboxsvr</computeroutput> is a fixed
     1039            name (note that <computeroutput>vboxsrv</computeroutput> would
     1040            also work), replace "x:" with the drive letter that you want to
     1041            use for the share, and <computeroutput>sharename</computeroutput>
     1042            with the share name specified with
     1043            <computeroutput>VBoxManage</computeroutput>.</para>
     1044          </listitem>
     1045
     1046          <listitem>
     1047            <para>In a Linux guest, use the following command:</para>
     1048
     1049            <screen>mount -t vboxsf [-o OPTIONS] sharename mountpoint</screen>
     1050
     1051            <para>To mount a shared folder during boot, add the following
     1052            entry to /etc/fstab:</para>
     1053
     1054            <screen>sharename   mountpoint   vboxsf   defaults  0   0</screen>
     1055          </listitem>
     1056
     1057          <listitem>
     1058            <para>In a Solaris guest, use the following command:</para>
     1059
     1060            <screen>mount -F vboxfs [-o OPTIONS] sharename mountpoint</screen>
     1061
     1062            <para>Replace <computeroutput>sharename</computeroutput> (use
     1063            lowercase) with the share name specified with
     1064            <computeroutput>VBoxManage</computeroutput> or the GUI, and
     1065            <computeroutput>mountpoint</computeroutput> with the path where
     1066            you want the share to be mounted on the guest (e.g.
     1067            <computeroutput>/mnt/share</computeroutput>). The usual mount
     1068            rules apply, that is, create this directory first if it does not
     1069            exist yet.</para>
     1070
     1071            <para>Here is an example of mounting the shared folder for the
     1072            user "jack" on OpenSolaris:</para>
     1073
     1074            <screen>$ id
    10371075uid=5000(jack) gid=1(other)
    10381076$ mkdir /export/home/jack/mount
    … …  
    10421080sharedfile1.mp3 sharedfile2.txt
    10431081$</screen>
    1044           <para>Beyond the standard options supplied by the
    1045           <computeroutput>mount</computeroutput> command, the following are
    1046           available:</para>
    1047 
    1048           <screen>iocharset CHARSET</screen>
    1049 
    1050           <para>to set the character set used for I/O operations (utf8 by
    1051           default) and</para>
    1052 
    1053           <screen>convertcp CHARSET</screen>
    1054 
    1055           <para>to specify the character set used for the shared folder name
    1056           (utf8 by default).</para>
    1057 
    1058           <para>The generic mount options (documented in the mount manual
    1059           page) apply also. Especially useful are the options
    1060           <computeroutput>uid</computeroutput>,
    1061           <computeroutput>gid</computeroutput> and
    1062           <computeroutput>mode</computeroutput>, as they allow access by
    1063           normal users (in read/write mode, depending on the settings) even if
    1064           root has mounted the filesystem.</para>
    1065         </listitem>
    1066       </itemizedlist></para>
     1082
     1083            <para>Beyond the standard options supplied by the
     1084            <computeroutput>mount</computeroutput> command, the following are
     1085            available:</para>
     1086
     1087            <screen>iocharset CHARSET</screen>
     1088
     1089            <para>to set the character set used for I/O operations (utf8 by
     1090            default) and</para>
     1091
     1092            <screen>convertcp CHARSET</screen>
     1093
     1094            <para>to specify the character set used for the shared folder name
     1095            (utf8 by default).</para>
     1096
     1097            <para>The generic mount options (documented in the mount manual
     1098            page) apply also. Especially useful are the options
     1099            <computeroutput>uid</computeroutput>,
     1100            <computeroutput>gid</computeroutput> and
     1101            <computeroutput>mode</computeroutput>, as they allow access by
     1102            normal users (in read/write mode, depending on the settings) even
     1103            if root has mounted the filesystem.</para>
     1104          </listitem>
     1105        </itemizedlist></para>
    10671106    </sect2>
    10681107
    … …  
    10701109      <title>Automatic mounting</title>
    10711110
    1072       <para>Starting with version 3.3.0, VirtualBox supports automatic mounting
    1073       support for shared folders. The installed Guest Additions will then take
    1074       care of all shared folders which are marked as being auto-mounted as soon
    1075       as a user is logged in to the guest OS. This makes it more convenient
    1076       instead of mounting shared folders manually described in <xref
    1077       linkend="sf_mount_manual" />.</para>
     1111      <para>Starting with version 3.3.0, VirtualBox supports automatic
     1112      mounting support for shared folders. The installed Guest Additions will
     1113      then take care of all shared folders which are marked as being
     1114      auto-mounted as soon as a user is logged in to the guest OS. This makes
     1115      it more convenient instead of mounting shared folders manually described
     1116      in <xref linkend="sf_mount_manual" />.</para>
     1117
    10781118      <note>
    10791119        <para>Auto-mounting currently is only supported on Windows, Linux and
    … …  
    10811121      </note>
    10821122
    1083       <para>On Windows guests an auto-mounted shared folder will be represented by an own
    1084       drive letter (e.g. <computeroutput>E:</computeroutput>), depending on the
    1085       remaining free drive letters of the system.</para>
    1086 
    1087       <para>On Linux and Solaris guests auto-mounted shared folders get mounted into
    1088       the <computeroutput>/media</computeroutput> directory, along with the prefix
    1089       <computeroutput>sf_</computeroutput>, so the shared folder <computeroutput>myfiles</computeroutput>
    1090       would be mounted to <computeroutput>/media/sf_myfiles</computeroutput> on Linux
    1091       and <computeroutput>/mnt/sf_myfiles</computeroutput> on Solaris.</para>
    1092 
    1093       <para>To change the prefix <computeroutput>sf_</computeroutput> of a given
    1094       virtual machine, set the value of its <computeroutput>/VirtualBox/GuestAdd/SharedFolders/MountPrefix</computeroutput>
    1095       guest property to another value; see <xref linkend="guestadd-guestprops" /> for details.</para>
    1096 
    1097       <para>To get a user full access to the auto-mounted shared folders on the guest
    1098       this user needs to be part of the newly create group "vboxsf", which is created by the
    1099       VirtualBox Guest Additions installer. Without being in that group read-only access
    1100       is provided.</para>
    1101 
    1102       <para>To get changes applied, for example by adding new or deleting auto-mounted
    1103       shared folders while a VM is running, the guest OS needs to be rebooted. However,
    1104       this does not affect <xref linkend="sf_mount_manual" />.</para>
     1123      <para>On Windows guests an auto-mounted shared folder will be
     1124      represented by an own drive letter (e.g.
     1125      <computeroutput>E:</computeroutput>), depending on the remaining free
     1126      drive letters of the system.</para>
     1127
     1128      <para>On Linux and Solaris guests auto-mounted shared folders get
     1129      mounted into the <computeroutput>/media</computeroutput> directory,
     1130      along with the prefix <computeroutput>sf_</computeroutput>, so the
     1131      shared folder <computeroutput>myfiles</computeroutput> would be mounted
     1132      to <computeroutput>/media/sf_myfiles</computeroutput> on Linux and
     1133      <computeroutput>/mnt/sf_myfiles</computeroutput> on Solaris.</para>
     1134
     1135      <para>To change the prefix <computeroutput>sf_</computeroutput> of a
     1136      given virtual machine, set the value of its
     1137      <computeroutput>/VirtualBox/GuestAdd/SharedFolders/MountPrefix</computeroutput>
     1138      guest property to another value; see <xref
     1139      linkend="guestadd-guestprops" /> for details.</para>
     1140
     1141      <para>To get a user full access to the auto-mounted shared folders on
     1142      the guest this user needs to be part of the newly create group "vboxsf",
     1143      which is created by the VirtualBox Guest Additions installer. Without
     1144      being in that group read-only access is provided.</para>
     1145
     1146      <para>To get changes applied, for example by adding new or deleting
     1147      auto-mounted shared folders while a VM is running, the guest OS needs to
     1148      be rebooted. However, this does not affect <xref
     1149      linkend="sf_mount_manual" />.</para>
    11051150    </sect2>
    11061151  </sect1>
    … …  
    14101455    guest; no additional software needs to be installed on the host.
    14111456    Additionally, text mode output (to stdout and stderr) can be shown on the
    1412     host for further processing along with options to specify user
    1413     credentials and a timeout value (in milliseconds) to limit time the
    1414     application is able to run.</para>
     1457    host for further processing along with options to specify user credentials
     1458    and a timeout value (in milliseconds) to limit time the application is
     1459    able to run.</para>
    14151460
    14161461    <para>This feature can be used to automate deployment of software within
    14171462    the guest.</para>
    14181463
    1419     <para>Starting with version 4.0, the Guest Additions for Windows
    1420     allow for automatic updating (only already installed Guest Additions 4.0
    1421     or later).</para>
    1422 
    1423     <para>To use these feature, use the VirtualBox command line or the GUI. See
    1424     <xref linkend="mountingadditionsiso" /> or <xref linkend="vboxmanage-guestcontrol" />
    1425     for details.</para>
     1464    <para>Starting with version 4.0, the Guest Additions for Windows allow for
     1465    automatic updating (only already installed Guest Additions 4.0 or
     1466    later).</para>
     1467
     1468    <para>To use these feature, use the VirtualBox command line or the GUI.
     1469    See <xref linkend="mountingadditionsiso" /> or <xref
     1470    linkend="vboxmanage-guestcontrol" /> for details.</para>
    14261471  </sect1>
    14271472
    … …  
    14891534    <title>Page Fusion</title>
    14901535
    1491     <para>Page Fusion is a novel technique to further improve VM density on the host,
    1492     i.e. a way of overcommitting resources. It was first introduced with VirtualBox 3.2
    1493     and is currently limited to VMs running Windows 2000 and later. In a typical scenario,
    1494     dozens, up to hundreds of very similar VMs are consolidated on a powerful host
    1495     computer and the level of consolidation is most often limited by the amount of RAM
    1496     that can be installed in a system at reasonable cost. Often, due to RAM exhaustion,
    1497     additional VMs cannot be started even though the host's CPUs still provide capacity.
    1498     To circumvent this restriction, hypervisors can benefit from the fact that often, VMs
    1499     are very similar (e.g. multiple VMs running Windows XP Service Pack 2) and therefore
    1500     contain a number of identical RAM cells. The hypervisor can look for such duplicate
    1501     data in memory, eliminate the redundancy (deduplication) and thereby free additional
    1502     memory.</para>
    1503 
    1504     <para>Traditional hypervisors use a technique often called "page sharing" or
    1505     "same page merging" where they go through all memory and compute checksums (hashes)
    1506     for each memory page. Then, they look for pages with identical hashes and compare
    1507     the content of the pages (if two pages produce the same hash, it is very likely that
    1508     the pages are identical in content). Identical pages get eliminated so that all VMs
    1509     point to the same page as long as none of the VMs tries to modify the page. If such
    1510     a page gets modified, the previously eliminated duplicates get allocated again. All
    1511     this is fully transparent to the virtual machine. However, the classical algorithm
    1512     has several drawbacks. First of all, it takes rather long to scan the complete
    1513     memory (esp. when the system is not idling) so the additional memory only becomes
    1514     available after some time (this can be hours or even days!). Also, the whole page
    1515     sharing algorithm generally consumes significant CPU resources and increases the
    1516     virtualization overhead by 10-20%.</para>
    1517 
    1518     <para>Page Fusion in VirtualBox uses the VirtualBox Guest Additions to identify
    1519     memory cells that are most likely identical across VMs and therefore achieves
    1520     most of the possible savings of page sharing almost immediately and with almost no
    1521     overhead. Page Fusion is also much less likely to be tricked by identical memory
    1522     that it will eliminate just to learn seconds later that the memory will now change
    1523     and having to perform a highly expensive and often service disrupting reallocation.
    1524     </para>
    1525 
    1526     <para>Page Fusion can be enabled for a VM using:
    1527     <screen>VBoxManage modifyvm "VM name" --pagefusion on</screen>
    1528     </para>
     1536    <para>Page Fusion is a novel technique to further improve VM density on
     1537    the host, i.e. a way of overcommitting resources. It was first introduced
     1538    with VirtualBox 3.2 and is currently limited to VMs running Windows 2000
     1539    and later. In a typical scenario, dozens, up to hundreds of very similar
     1540    VMs are consolidated on a powerful host computer and the level of
     1541    consolidation is most often limited by the amount of RAM that can be
     1542    installed in a system at reasonable cost. Often, due to RAM exhaustion,
     1543    additional VMs cannot be started even though the host's CPUs still provide
     1544    capacity. To circumvent this restriction, hypervisors can benefit from the
     1545    fact that often, VMs are very similar (e.g. multiple VMs running Windows
     1546    XP Service Pack 2) and therefore contain a number of identical RAM cells.
     1547    The hypervisor can look for such duplicate data in memory, eliminate the
     1548    redundancy (deduplication) and thereby free additional memory.</para>
     1549
     1550    <para>Traditional hypervisors use a technique often called "page sharing"
     1551    or "same page merging" where they go through all memory and compute
     1552    checksums (hashes) for each memory page. Then, they look for pages with
     1553    identical hashes and compare the content of the pages (if two pages
     1554    produce the same hash, it is very likely that the pages are identical in
     1555    content). Identical pages get eliminated so that all VMs point to the same
     1556    page as long as none of the VMs tries to modify the page. If such a page
     1557    gets modified, the previously eliminated duplicates get allocated again.
     1558    All this is fully transparent to the virtual machine. However, the
     1559    classical algorithm has several drawbacks. First of all, it takes rather
     1560    long to scan the complete memory (esp. when the system is not idling) so
     1561    the additional memory only becomes available after some time (this can be
     1562    hours or even days!). Also, the whole page sharing algorithm generally
     1563    consumes significant CPU resources and increases the virtualization
     1564    overhead by 10-20%.</para>
     1565
     1566    <para>Page Fusion in VirtualBox uses the VirtualBox Guest Additions to
     1567    identify memory cells that are most likely identical across VMs and
     1568    therefore achieves most of the possible savings of page sharing almost
     1569    immediately and with almost no overhead. Page Fusion is also much less
     1570    likely to be tricked by identical memory that it will eliminate just to
     1571    learn seconds later that the memory will now change and having to perform
     1572    a highly expensive and often service disrupting reallocation.</para>
     1573
     1574    <para>Page Fusion can be enabled for a VM using: <screen>VBoxManage modifyvm "VM name" --pagefusion on</screen></para>
    15291575
    15301576    <para>You can observe Page Fusion operation using some metrics.
    1531     <computeroutput>RAM/VMM/Shared</computeroutput> shows the total amount of fused
    1532     pages whereas the per VM metric <computeroutput>Guest/RAM/Usage/Shared</computeroutput>
    1533     will return the amount of fused memory for a given VM. Please refer to
    1534     <xref linkend="metrics" /> for information on how to query metrics.</para>
     1577    <computeroutput>RAM/VMM/Shared</computeroutput> shows the total amount of
     1578    fused pages whereas the per VM metric
     1579    <computeroutput>Guest/RAM/Usage/Shared</computeroutput> will return the
     1580    amount of fused memory for a given VM. Please refer to <xref
     1581    linkend="metrics" /> for information on how to query metrics.</para>
    15351582
    15361583    <para><note>
    1537       <para>VirtualBox supports Page Fusion only on 64-bit host operating systems.
    1538       Mac OS X hosts are currently not supported. Page Fusion is only available for
    1539       Windows 2000 and later guests with current Guest Additions.</para>
    1540     </note></para>
     1584        <para>VirtualBox supports Page Fusion only on 64-bit host operating
     1585        systems. Mac OS X hosts are currently not supported. Page Fusion is
     1586        only available for Windows 2000 and later guests with current Guest
     1587        Additions.</para>
     1588      </note></para>
    15411589  </sect1>
    15421590</chapter>

  • trunk/doc/manual/en_US/user_Installation.xml

    r31735 r34392  
    11<?xml version="1.0" encoding="UTF-8"?>
    22<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
    3   "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
     3"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
    44<chapter id="installation">
    55  <title>Installation details</title>
    … …  
    7373            <glossdef>
    7474              <para>This package contains Python scripting support for the
    75               VirtualBox API (see <xref linkend="VirtualBoxAPI" />). To get this
    76               feature installed an already working Python installation on the
    77               system is required.</para>
     75              VirtualBox API (see <xref linkend="VirtualBoxAPI" />). To get
     76              this feature installed an already working Python installation on
     77              the system is required.</para>
    7878            </glossdef>
    7979          </glossentry>
    … …  
    9797      current user.</para>
    9898
    99       <para>To not install certain features of VirtualBox there is an <computeroutput>ADDLOCAL</computeroutput>
    100       parameter that can be specified additionally to explicitly name the features
    101       to be installed. The following features are available:
    102 
    103         <glosslist>
     99      <para>To not install certain features of VirtualBox there is an
     100      <computeroutput>ADDLOCAL</computeroutput> parameter that can be
     101      specified additionally to explicitly name the features to be installed.
     102      The following features are available: <glosslist>
    104103          <glossentry>
    105104            <glossterm>VBoxApplication</glossterm>
    106105
    107106            <glossdef>
    108               <para>Main binaries of VirtualBox.
    109                 <note>This feature never can be absent,
    110                 since it contains the minimum set of files to have working VirtualBox installation!</note>
    111               </para>
     107              <para>Main binaries of VirtualBox.<note>
     108                  <para>This feature never can be absent, since it contains
     109                  the minimum set of files to have working VirtualBox
     110                  installation!</para>
     111                </note></para>
    112112            </glossdef>
    113113          </glossentry>
    … …  
    125125
    126126            <glossdef>
    127               <para>All networking support; includes the VBoxNetworkFlt and VBoxNetworkAdp features (see below).</para>
     127              <para>All networking support; includes the VBoxNetworkFlt and
     128              VBoxNetworkAdp features (see below).</para>
    128129            </glossdef>
    129130          </glossentry>
    … …  
    152153            </glossdef>
    153154          </glossentry>
    154         </glosslist>
    155 
    156       To only install USB support along with the main binaries, do a:
    157       <screen>VirtualBox.exe -msiparams ADDLOCAL=VBoxApplication,VBoxUSB</screen>
     155        </glosslist> To only install USB support along with the main binaries,
     156      do a: <screen>VirtualBox.exe -msiparams ADDLOCAL=VBoxApplication,VBoxUSB</screen>
    158157      or <screen>msiexec /i VirtualBox-&lt;version&gt;-MultiArch_&lt;x86|amd64&gt;.msi ADDLOCAL=VBoxApplication,VBoxUSB</screen></para>
    159 
    160158    </sect2>
    161159
    … …  
    402400
    403401        <para>First, download the appropriate package for your distribution.
    404         The following examples assume that you are installing to a 32-bit Ubuntu
    405         Karmic system. Use <computeroutput>dpkg</computeroutput> to install the
    406         Debian package:</para>
     402        The following examples assume that you are installing to a 32-bit
     403        Ubuntu Karmic system. Use <computeroutput>dpkg</computeroutput> to
     404        install the Debian package:</para>
    407405
    408406        <screen>sudo dpkg -i VirtualBox-3.2_$VBOX_VERSION_STRING_Ubuntu_karmic_i386.deb</screen>
    … …  
    653651        prior to the installation of the VirtualBox Debian package.</para>
    654652
    655         <para>In addition there are some common configuration options that can be set prior to
    656         the installation, described in <xref linkend="linux_install_opts" />.</para>
     653        <para>In addition there are some common configuration options that can
     654        be set prior to the installation, described in <xref
     655        linkend="linux_install_opts" />.</para>
    657656      </sect3>
    658657
    … …  
    661660
    662661        <para>The .rpm format does not provide a configuration system
    663         comparable to the debconf system. See <xref linkend="linux_install_opts" />
    664         for how to set some common installation options provided by VirtualBox.</para>
     662        comparable to the debconf system. See <xref
     663        linkend="linux_install_opts" /> for how to set some common
     664        installation options provided by VirtualBox.</para>
    665665      </sect3>
    666666
    667667      <sect3>
    668668        <title id="linux_install_opts">Automatic installation options</title>
    669         <para>To configure the installation process of our .deb and .rpm packages, a file
    670         <computeroutput>/etc/default/virtualbox</computeroutput> is interpreted.
    671         The automatic generation of the udev rule can be prevented by the following setting:
    672         <screen>INSTALL_NO_UDEV=1</screen> The creation of the group vboxusers can be prevented
    673         by <screen>INSTALL_NO_GROUP=1</screen> If the line <screen>INSTALL_NO_VBOXDRV=1</screen>
    674         is specified, the package installer will not try to build the
    675         <computeroutput>vboxdrv</computeroutput> kernel module if no module according to the
    676         current kernel was found.</para>
     669
     670        <para>To configure the installation process of our .deb and .rpm
     671        packages, a file
     672        <computeroutput>/etc/default/virtualbox</computeroutput> is
     673        interpreted. The automatic generation of the udev rule can be
     674        prevented by the following setting: <screen>INSTALL_NO_UDEV=1</screen>
     675        The creation of the group vboxusers can be prevented by <screen>INSTALL_NO_GROUP=1</screen>
     676        If the line <screen>INSTALL_NO_VBOXDRV=1</screen> is specified, the
     677        package installer will not try to build the
     678        <computeroutput>vboxdrv</computeroutput> kernel module if no module
     679        according to the current kernel was found.</para>
    677680      </sect3>
    678 
    679681    </sect2>
    680682
Note: See TracChangeset for help on using the changeset viewer.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette