VirtualBox

Changeset 56451 in vbox for trunk/doc/manual/en_US


Ignore:
Timestamp:
Jun 16, 2015 1:43:48 PM (10 years ago)
Author:
vboxsync
Message:

doc/manual: fix all docbook XML validity errors in the user_*.xml files. Most were missing/incorrectly placed <para> tags, but there were several severe structural issues, too.

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

Legend:

Unmodified
Added
Removed

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

    r55484 r56451  
    621621      versions <itemizedlist>
    622622          <listitem>
    623             X11R6.8/X11R6.9 and XFree86 version 4.3 (vboxvideo_drv_68.o and vboxmouse_drv_68.o)
     623            <para>X11R6.8/X11R6.9 and XFree86 version 4.3 (vboxvideo_drv_68.o and vboxmouse_drv_68.o)</para>
    624624          </listitem>
    625625
    626626          <listitem>
    627             X11R7.0 (vboxvideo_drv_70.so and vboxmouse_drv_70.so)
     627            <para>X11R7.0 (vboxvideo_drv_70.so and vboxmouse_drv_70.so)</para>
    628628          </listitem>
    629629
    630630          <listitem>
    631             X11R7.1 (vboxvideo_drv_71.so and vboxmouse_drv_71.so)
     631            <para>X11R7.1 (vboxvideo_drv_71.so and vboxmouse_drv_71.so)</para>
    632632          </listitem>
    633633
    634634          <listitem>
    635             X.Org Server versions 1.3 and later (vboxvideo_drv_13.so and vboxmouse_drv_13.so and so on).
     635            <para>X.Org Server versions 1.3 and later (vboxvideo_drv_13.so and vboxmouse_drv_13.so and so on).</para>
    636636          </listitem>
    637637        </itemizedlist> By default these drivers can be found in the
    … …  
    840840    limitations apply: <orderedlist>
    841841        <listitem>
    842            Only PCI cards with non-shared interrupts (such as using MSI on host) are supported at the moment.
     842           <para>Only PCI cards with non-shared interrupts (such as using MSI on host) are supported at the moment.</para>
    843843        </listitem>
    844844
    845845        <listitem>
    846            No guest state can be reliably saved/restored (as the internal state of the PCI card could not be retrieved).
     846           <para>No guest state can be reliably saved/restored (as the internal state of the PCI card could not be retrieved).</para>
    847847        </listitem>
    848848
    849849        <listitem>
    850            Teleportation (live migration) doesn't work (for the same reason).
     850           <para>Teleportation (live migration) doesn't work (for the same reason).</para>
    851851        </listitem>
    852852
    853853        <listitem>
    854            No lazy physical memory allocation. The host will preallocate the whole RAM required for the VM on startup (as we cannot catch physical hardware accesses to the physical memory).
     854           <para>No lazy physical memory allocation. The host will preallocate the whole RAM required for the VM on startup (as we cannot catch physical hardware accesses to the physical memory).</para>
    855855        </listitem>
    856856      </orderedlist></para>
    … …  
    900900            <itemizedlist>
    901901              <listitem>
    902                 <computeroutput>MaxFramerate</computeroutput> The highest rate at which video frames
     902                <para><computeroutput>MaxFramerate</computeroutput> The highest rate at which video frames
    903903                are sent to the guest. A higher frame rate requires more CPU power. Therefore sometimes
    904904                it is useful to set a lower limit. Default is no limit and allow the guest to use all
    905                 frame rates supported by the host webcam.
     905                frame rates supported by the host webcam.</para>
    906906              </listitem>
    907907              <listitem>
    908                 <computeroutput>MaxPayloadTransferSize</computeroutput> How many bytes the emulated
     908                <para><computeroutput>MaxPayloadTransferSize</computeroutput> How many bytes the emulated
    909909                webcam can send to the guest at a time. Default value is 3060 bytes, which is used by
    910910                some webcams. Higher values can slightly reduce CPU load, if the guest is able to use
    911911                larger buffers. However, a high <computeroutput>MaxPayloadTransferSize</computeroutput>
    912                 might be not supported by some guests.
     912                might be not supported by some guests.</para>
    913913              </listitem>
    914914            </itemizedlist>
    … …  
    14781478    replace <code>pcbios</code> by <code>efi</code> in the keys.</para>
    14791479
    1480     <sect2>
    1481       <title>DMI BIOS information (type 0)</title>
    1482       <screen>VBoxManage setextradata "VM name"
     1480    <glosslist>
     1481      <glossentry>
     1482        <glossterm>DMI BIOS information</glossterm>
     1483        <glossdef>
     1484          <para>(type 0)</para>
     1485          <screen>VBoxManage setextradata "VM name"
    14831486      "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSVendor"        "BIOS Vendor"
    14841487VBoxManage setextradata "VM name"
    … …  
    14941497VBoxManage setextradata "VM name"
    14951498      "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSFirmwareMinor" 4</screen>
    1496     </sect2>
    1497     <sect2>
    1498       <title>DMI system information (type 1)</title>
    1499       <screen>VBoxManage setextradata "VM name"
     1499        </glossdef>
     1500      </glossentry>
     1501
     1502      <glossentry>
     1503        <glossterm>DMI system information</glossterm>
     1504        <glossdef>
     1505          <para>(type 1)</para>
     1506          <screen>VBoxManage setextradata "VM name"
    15001507      "VBoxInternal/Devices/pcbios/0/Config/DmiSystemVendor"      "System Vendor"
    15011508VBoxManage setextradata "VM name"
    … …  
    15121519      "VBoxInternal/Devices/pcbios/0/Config/DmiSystemUuid"
    15131520                                               "9852bf98-b83c-49db-a8de-182c42c7226b"</screen>
    1514     </sect2>
    1515     <sect2>
    1516       <title>DMI board information (type 2)</title>
    1517       <screen>VBoxManage setextradata "VM name"
     1521        </glossdef>
     1522      </glossentry>
     1523
     1524      <glossentry>
     1525        <glossterm>DMI board information</glossterm>
     1526        <glossdef>
     1527          <para>(type 2)</para>
     1528          <screen>VBoxManage setextradata "VM name"
    15181529      "VBoxInternal/Devices/pcbios/0/Config/DmiBoardVendor"       "Board Vendor"
    15191530VBoxManage setextradata "VM name"
    … …  
    15291540VBoxManage setextradata "VM name"
    15301541      "VBoxInternal/Devices/pcbios/0/Config/DmiBoardBoardType"    10</screen>
    1531     </sect2>
    1532     <sect2>
    1533       <title>DMI system enclosure or chassis (type 3)</title>
    1534       <screen>VBoxManage setextradata "VM name"
     1542        </glossdef>
     1543      </glossentry>
     1544
     1545      <glossentry>
     1546        <glossterm>DMI system enclosure or chassis</glossterm>
     1547        <glossdef>
     1548          <para>(type 3)</para>
     1549          <screen>VBoxManage setextradata "VM name"
    15351550      "VBoxInternal/Devices/pcbios/0/Config/DmiChassisVendor"     "Chassis Vendor"
    15361551VBoxManage setextradata "VM name"
    … …  
    15421557VBoxManage setextradata "VM name"
    15431558      "VBoxInternal/Devices/pcbios/0/Config/DmiChassisAssetTag"   "Chassis Tag"</screen>
    1544     </sect2>
    1545     <sect2>
    1546       <title>DMI processor informatiion (type 4)</title>
    1547       <screen>VBoxManage setextradata "VM name"
     1559        </glossdef>
     1560      </glossentry>
     1561
     1562      <glossentry>
     1563        <glossterm>DMI processor information</glossterm>
     1564        <glossdef>
     1565          <para>(type 4)</para>
     1566          <screen>VBoxManage setextradata "VM name"
    15481567      "VBoxInternal/Devices/pcbios/0/Config/DmiProcManufacturer"  "GenuineIntel"
    15491568VBoxManage setextradata "VM name"
    15501569      "VBoxInternal/Devices/pcbios/0/Config/DmiProcVersion"       "Pentium(R) III"</screen>
    1551     </sect2>
    1552     <sect2>
    1553       <title>DMI OEM strings (type 11)</title>
    1554       <screen>VBoxManage setextradata "VM name"
     1570        </glossdef>
     1571      </glossentry>
     1572
     1573      <glossentry>
     1574        <glossterm>DMI OEM strings</glossterm>
     1575        <glossdef>
     1576          <para>(type 11)</para>
     1577          <screen>VBoxManage setextradata "VM name"
    15551578      "VBoxInternal/Devices/pcbios/0/Config/DmiOEMVBoxVer"        "vboxVer_1.2.3"
    15561579VBoxManage setextradata "VM name"
    15571580      "VBoxInternal/Devices/pcbios/0/Config/DmiOEMVBoxRev"        "vboxRev_12345"</screen>
    1558     </sect2>
     1581        </glossdef>
     1582      </glossentry>
     1583    </glosslist>
     1584
    15591585    <para>If a DMI string is not set, the default value of VirtualBox is used.
    15601586    To set an empty string use
    … …  
    16641690      following:</para>
    16651691
    1666       <para><glosslist>
    1667           <glossentry>
    1668             <glossterm><computeroutput>--timesync-interval</computeroutput></glossterm>
    1669             <glossdef>
    1670               <para>Specifies the interval at which to synchronize the time
    1671               with the host. The default is 10000 ms (10 seconds).</para>
    1672             </glossdef>
    1673           </glossentry>
    1674 
    1675           <glossentry>
    1676             <glossterm><computeroutput>--timesync-min-adjust</computeroutput></glossterm>
    1677             <glossdef>
    1678               <para>The minimum absolute drift value measured in milliseconds
    1679               to make adjustments for. The default is 1000 ms on OS/2 and 100
    1680               ms elsewhere.</para>
    1681             </glossdef>
    1682           </glossentry>
    1683           <glossentry>
    1684             <glossterm><computeroutput>--timesync-latency-factor</computeroutput></glossterm>
    1685             <glossdef>
    1686               <para>The factor to multiply the time query latency with to
    1687               calculate the dynamic minimum adjust time. The default is 8
    1688               times, that means in detail: Measure the time it takes to
    1689               determine the host time (the guest has to contact the VM host
    1690               service which may take some time), multiply this value by 8 and
    1691               do an adjustment only if the time difference between host and
    1692               guest is bigger than this value. Don't do any time adjustment
    1693               otherwise.</para>
    1694             </glossdef>
    1695           </glossentry>
    1696 
    1697           <glossentry>
    1698             <glossterm><computeroutput>--timesync-max-latency</computeroutput></glossterm>
    1699             <glossdef>
    1700               <para>The max host timer query latency to accept. The default is
    1701               250 ms.</para>
    1702             </glossdef>
    1703           </glossentry>
    1704 
    1705           <glossentry>
    1706             <glossterm><computeroutput>--timesync-set-threshold</computeroutput></glossterm>
    1707             <glossdef>
    1708               <para>The absolute drift threshold, given as milliseconds where
    1709               to start setting the time instead of trying to smoothly adjust
    1710               it. The default is 20 minutes.</para>
    1711             </glossdef>
    1712           </glossentry>
    1713 
    1714           <glossentry>
    1715             <glossterm><computeroutput>--timesync-set-start</computeroutput></glossterm>
    1716             <glossdef>
    1717               <para>Set the time when starting the time sync service.</para>
    1718             </glossdef>
    1719           </glossentry>
    1720 
    1721           <glossentry>
    1722             <glossterm><computeroutput>--timesync-set-on-restore
    1723             0|1</computeroutput></glossterm>
    1724             <glossdef>
    1725               <para>Set the time after the VM was restored from a saved state
    1726               when passing 1 as parameter (default). Disable by passing 0. In
    1727               the latter case, the time will be adjusted smoothly which can
    1728               take a long time.</para>
    1729             </glossdef>
    1730           </glossentry>
    1731         </glosslist></para>
     1692      <glosslist>
     1693        <glossentry>
     1694          <glossterm><computeroutput>--timesync-interval</computeroutput></glossterm>
     1695          <glossdef>
     1696            <para>Specifies the interval at which to synchronize the time
     1697            with the host. The default is 10000 ms (10 seconds).</para>
     1698          </glossdef>
     1699        </glossentry>
     1700
     1701        <glossentry>
     1702          <glossterm><computeroutput>--timesync-min-adjust</computeroutput></glossterm>
     1703          <glossdef>
     1704            <para>The minimum absolute drift value measured in milliseconds
     1705            to make adjustments for. The default is 1000 ms on OS/2 and 100
     1706            ms elsewhere.</para>
     1707          </glossdef>
     1708        </glossentry>
     1709        <glossentry>
     1710          <glossterm><computeroutput>--timesync-latency-factor</computeroutput></glossterm>
     1711          <glossdef>
     1712            <para>The factor to multiply the time query latency with to
     1713            calculate the dynamic minimum adjust time. The default is 8
     1714            times, that means in detail: Measure the time it takes to
     1715            determine the host time (the guest has to contact the VM host
     1716            service which may take some time), multiply this value by 8 and
     1717            do an adjustment only if the time difference between host and
     1718            guest is bigger than this value. Don't do any time adjustment
     1719            otherwise.</para>
     1720          </glossdef>
     1721        </glossentry>
     1722
     1723        <glossentry>
     1724          <glossterm><computeroutput>--timesync-max-latency</computeroutput></glossterm>
     1725          <glossdef>
     1726            <para>The max host timer query latency to accept. The default is
     1727            250 ms.</para>
     1728          </glossdef>
     1729        </glossentry>
     1730
     1731        <glossentry>
     1732          <glossterm><computeroutput>--timesync-set-threshold</computeroutput></glossterm>
     1733          <glossdef>
     1734            <para>The absolute drift threshold, given as milliseconds where
     1735            to start setting the time instead of trying to smoothly adjust
     1736            it. The default is 20 minutes.</para>
     1737          </glossdef>
     1738        </glossentry>
     1739
     1740        <glossentry>
     1741          <glossterm><computeroutput>--timesync-set-start</computeroutput></glossterm>
     1742          <glossdef>
     1743            <para>Set the time when starting the time sync service.</para>
     1744          </glossdef>
     1745        </glossentry>
     1746
     1747        <glossentry>
     1748          <glossterm><computeroutput>--timesync-set-on-restore
     1749          0|1</computeroutput></glossterm>
     1750          <glossdef>
     1751            <para>Set the time after the VM was restored from a saved state
     1752            when passing 1 as parameter (default). Disable by passing 0. In
     1753            the latter case, the time will be adjusted smoothly which can
     1754            take a long time.</para>
     1755          </glossdef>
     1756        </glossentry>
     1757      </glosslist>
    17321758
    17331759      <para>All these parameters can be specified as command line parameters
    … …  
    17901816      </footnote> A VirtualBox VNIC template is a VNIC whose name starts with
    17911817    "vboxvnic_template" (case-sensitive).</para>
    1792  
     1818
    17931819    <para>On Solaris 11 hosts<footnote><para>When Crossbow based bridged
    17941820    networking is used.</para></footnote>, a VNIC template may be used to
    … …  
    18491875
    18501876    <screen>rem_drv vboxnet</screen>
    1851    
     1877
    18521878    <para>Edit the file <computeroutput>/platform/i86pc/kernel/drv/vboxnet.conf</computeroutput>
    18531879    and add a line for the new interface we want to add as shown below:</para>
    … …  
    29622988      </para>
    29632989      <para><screen>VBoxManage setextradata "VM name" GUI/MouseCapturePolicy MODE</screen></para>
    2964      
     2990
    29652991      <para>where <computeroutput>MODE</computeroutput> is one of the
    29662992        following keywords:</para><glosslist>
    … …  
    36853711    <screen>VBoxManage setextradata "VM name" VBoxInternal/Devices/usb-ehci/LUN#0/Config/CaptureFilename "filename"</screen>
    36863712
    3687     The command above enables capturing on the root hub attached to the EHCI controller.
     3713    <para>The command above enables capturing on the root hub attached to the EHCI controller.
    36883714    To enable it for the OHCI or XHCI controller replace <computeroutput>usb-ehci</computeroutput>
    3689     with <computeroutput>usb-ohci</computeroutput> or <computeroutput>usb-xhci</computeroutput> respectively.
     3715    with <computeroutput>usb-ohci</computeroutput> or <computeroutput>usb-xhci</computeroutput> respectively.</para>
    36903716
    36913717  </sect1>

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

    r56175 r56451  
    421421              installed on the guest.</para>
    422422
    423               <note>Drag'n drop is disabled by default. This setting can be
     423              <para><note><para>Drag'n drop is disabled by default. This setting can be
    424424              changed at any time using the "Drag'n'Drop" menu item in the
    425               "Devices" menu of the virtual machine.</note>
    426 
    427               <para>See <xref linkend="guestadd-dnd"/> for more information.</para>
    428 
     425              "Devices" menu of the virtual machine.</para></note></para>
     426
     427              <para>See <xref linkend="guestadd-dnd"/> for more information.
    429428              <footnote><para>Experimental support for drag and drop was added
    430               with VirtualBox 4.2.</para></footnote>
     429              with VirtualBox 4.2.</para></footnote></para>
    431430            </glossdef>
    432431          </glossentry>

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

    r34803 r56451  
    1616<!--$VIRTUALBOX_CHANGELOG_IMPL-->
    1717
    18   <para>With VirtualBox 3.2, changelog information for versions before 2.0 was removed in
    19   order to save space. To access this information, please consult the User Manual of
    20   VirtualBox version 3.1 or earlier.</para>
     18  <sect1>
     19    <title>Older Change log details</title>
     20    <para>With VirtualBox 3.2, changelog information for versions before 2.0
     21    was removed in order to save space. To access this information, please
     22    consult the User Manual of VirtualBox version 3.1 or earlier.</para>
     23  </sect1>
    2124
    2225</chapter>

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

    r56250 r56451  
    582582            generate a server certificate.<orderedlist>
    583583                <listitem>
    584                 Create a CA self signed certificate:
     584                <para>Create a CA self signed certificate:
    585585                <screen>openssl req -new -x509 -days 365 -extensions v3_ca \
    586   -keyout ca_key_private.pem -out ca_cert.pem</screen>
     586  -keyout ca_key_private.pem -out ca_cert.pem</screen></para>
    587587                </listitem>
    588588
    589589                <listitem>
    590                 Generate a server private key and a request for signing:
     590                <para>Generate a server private key and a request for signing:
    591591                <screen>openssl genrsa -out server_key_private.pem
    592 openssl req -new -key server_key_private.pem -out server_req.pem</screen>
     592openssl req -new -key server_key_private.pem -out server_req.pem</screen></para>
    593593                </listitem>
    594594
    595595                <listitem>
    596                 Generate the server certificate:
     596                <para>Generate the server certificate:
    597597                <screen>openssl x509 -req -days 365 -in server_req.pem \
    598   -CA ca_cert.pem -CAkey ca_key_private.pem -set_serial 01 -out server_cert.pem</screen>
     598  -CA ca_cert.pem -CAkey ca_key_private.pem -set_serial 01 -out server_cert.pem</screen></para>
    599599                </listitem>
    600600            </orderedlist>

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

    r55142 r56451  
    362362        will undermine a silent installation.</para>
    363363
    364         <note>On some Windows versions like Windows 2000 and Windows XP the user intervention
    365         popups mentioned above always will be displayed, even after importing the Oracle certificates.</note>
     364        <note><para>On some Windows versions like Windows 2000 and Windows XP the user intervention
     365        popups mentioned above always will be displayed, even after importing the Oracle certificates.</para></note>
    366366
    367367        <para>Since VirtualBox 4.2 installing those CA certificates on a Windows
    … …  
    402402        Windows Guest Additions installer on the CD-ROM:</para>
    403403
    404         <sect4>
    405           <title>VeriSign Code Signing CA</title>
    406           <itemizedlist>
    407             <listitem>
    408               <para>In the Windows Explorer, right click on VBoxWindowsAdditions-&lt;Architecture&gt;.exe,
    409               click on "Properties"</para>
    410             </listitem>
    411             <listitem>
    412               <para>Go to tab "Digital Signatures", choose "Oracle Corporation" and click on "Details"</para>
    413             </listitem>
    414             <listitem>
    415               <para>In tab "General" click on "View Certificate"</para>
    416             </listitem>
    417             <listitem>
    418               <para>In tab "Certification Path" select "VeriSign Class 3 Public Primary CA"</para>
    419             </listitem>
    420             <listitem>
    421               <para>Click on "View Certificate"</para>
    422             </listitem>
    423             <listitem>
    424               <para>In tab "Details" click on "Copy to File ..."</para>
    425             </listitem>
    426             <listitem>
    427               <para>In the upcoming wizard choose "DER encoded binary X.509 (.CER)"
    428               and save the certificate file to a local path, finish the wizard</para>
    429             </listitem>
    430             <listitem>
    431               <para>Close certificate dialog for "Verisign Class 3 Code Signing
    432               2010 CA"</para>
    433             </listitem>
    434           </itemizedlist>
    435         </sect4>
    436 
    437         <sect4>
    438           <title>Oracle Corporation</title>
    439           <itemizedlist>
    440             <listitem>
    441               <para>In the Windows Explorer, right click on VBoxWindowsAdditions-&lt;Architecture&gt;.exe,
    442               click on "Properties"</para>
    443             </listitem>
    444             <listitem>
    445               <para>Go to tab "Digital Signatures", choose "Oracle Corporation" and click on "Details"</para>
    446             </listitem>
    447             <listitem>
    448               <para>In tab "General" click on "View Certificate"</para>
    449             </listitem>
    450             <listitem>
    451               <para>In tab "Details" click on "Copy to File ..."</para>
    452             </listitem>
    453             <listitem>
    454               <para>In the upcoming wizard choose "DER encoded binary X.509 (.CER)"
    455               and save the certificate file to a local path, finish the wizard</para>
    456             </listitem>
    457             <listitem>
    458               <para>Close certificate dialog for "Oracle Corporation"</para>
    459             </listitem>
    460           </itemizedlist>
    461         </sect4>
     404        <glosslist>
     405          <glossentry>
     406            <glossterm>VeriSign Code Signing CA</glossterm>
     407            <glossdef>
     408              <para>Open the Windows Explorer.</para>
     409              <itemizedlist>
     410                <listitem>
     411                  <para>Right click on VBoxWindowsAdditions-&lt;Architecture&gt;.exe,
     412                  click on "Properties"</para>
     413                </listitem>
     414                <listitem>
     415                  <para>Go to tab "Digital Signatures", choose "Oracle Corporation" and click on "Details"</para>
     416                </listitem>
     417                <listitem>
     418                  <para>In tab "General" click on "View Certificate"</para>
     419                </listitem>
     420                <listitem>
     421                  <para>In tab "Certification Path" select "VeriSign Class 3 Public Primary CA"</para>
     422                </listitem>
     423                <listitem>
     424                  <para>Click on "View Certificate"</para>
     425                </listitem>
     426                <listitem>
     427                  <para>In tab "Details" click on "Copy to File ..."</para>
     428                </listitem>
     429                <listitem>
     430                  <para>In the upcoming wizard choose "DER encoded binary X.509 (.CER)"
     431                  and save the certificate file to a local path, finish the wizard</para>
     432                </listitem>
     433                <listitem>
     434                  <para>Close certificate dialog for "Verisign Class 3 Code Signing
     435                  2010 CA"</para>
     436                </listitem>
     437              </itemizedlist>
     438            </glossdef>
     439          </glossentry>
     440
     441          <glossentry>
     442            <glossterm>Oracle Corporation</glossterm>
     443            <glossdef>
     444              <para>Open the Windows Explorer.</para>
     445              <itemizedlist>
     446                <listitem>
     447                  <para>Right click on VBoxWindowsAdditions-&lt;Architecture&gt;.exe,
     448                  click on "Properties"</para>
     449                </listitem>
     450                <listitem>
     451                  <para>Go to tab "Digital Signatures", choose "Oracle Corporation" and click on "Details"</para>
     452                </listitem>
     453                <listitem>
     454                  <para>In tab "General" click on "View Certificate"</para>
     455                </listitem>
     456                <listitem>
     457                  <para>In tab "Details" click on "Copy to File ..."</para>
     458                </listitem>
     459                <listitem>
     460                  <para>In the upcoming wizard choose "DER encoded binary X.509 (.CER)"
     461                  and save the certificate file to a local path, finish the wizard</para>
     462                </listitem>
     463                <listitem>
     464                  <para>Close certificate dialog for "Oracle Corporation"</para>
     465                </listitem>
     466              </itemizedlist>
     467            </glossdef>
     468          </glossentry>
     469        </glosslist>
    462470
    463471        <para>After exporting the two certificates above they can be imported into the
    … …  
    647655              <listitem>
    648656                <para>In order to fully update your guest system, open a
    649                 terminal and run <screen>yum update</screen></para> as root.
     657                terminal and run <screen>yum update</screen> as root.</para>
    650658              </listitem>
    651659
    … …  
    668676              <listitem>
    669677                <para>In order to fully update your guest system, open a
    670                 terminal and run <screen>zypper update</screen></para> as root.
     678                terminal and run <screen>zypper update</screen> as root.</para>
    671679              </listitem>
    672680
    … …  
    706714              <listitem>
    707715                <para>In order to fully update your guest system, open a
    708                 terminal and run <screen>zypper update</screen></para> as root.
     716                terminal and run <screen>zypper update</screen> as root.</para>
    709717              </listitem>
    710718
    … …  
    748756              <listitem>
    749757                <para>In order to fully update your guest system, open a
    750                 terminal and run <screen>urpmi --auto-update</screen></para>
    751                 as root.
     758                terminal and run <screen>urpmi --auto-update</screen>
     759                as root.</para>
    752760              </listitem>
    753761
    … …  
    779787              <listitem>
    780788                <para>In order to fully update your guest system, open a
    781                 terminal and run <screen>yum update</screen></para> as root.
     789                terminal and run <screen>yum update</screen> as root.</para>
    782790              </listitem>
    783791
    … …  
    12751283    implemented.</para></footnote></para>
    12761284
    1277     <para>When transferring data from the host to the guest OS, the host in this
    1278     case is the source, whereas the guest OS is the target. However, when doing
    1279     it the other way around, that is, transferring data from the guest OS to the
    1280     host, the guest OS this time became the source and the host is the target.</para>
    1281 
    1282     <para>For security reasons drag'n drop can be configured at runtime
    1283     on a per-VM basis either using the "Drag'n'Drop" menu item in the "Devices" menu
    1284     of the virtual machine or VBoxManage: The following four modes are available:
     1285    <para>When transferring data from the host to the guest OS, the host in
     1286    this case is the source, whereas the guest OS is the target. However, when
     1287    doing it the other way around, that is, transferring data from the guest OS
     1288    to the host, the guest OS this time became the source and the host is the
     1289    target.</para>
     1290
     1291    <para>For security reasons drag'n drop can be configured at runtime on a
     1292    per-VM basis either using the "Drag'n'Drop" menu item in the "Devices" menu
     1293    of the virtual machine or VBoxManage: The following four modes are
     1294    available:</para>
    12851295
    12861296    <para><mediaobject>
    … …  
    13091319        and vice versa.</para>
    13101320      </listitem>
    1311     </itemizedlist></para>
     1321    </itemizedlist>
    13121322
    13131323    <note><para>Drag'n drop support depends on the frontend being used; at the
    … …  
    14491459      <note><para>Unlike the current basic Direct3D support, the WDDM video
    14501460      driver installation does <emphasis role="bold">not</emphasis> require
    1451       the "Safe Mode".</para></note>
    1452       <para>The Aero theme is not enabled by default. To enable it<itemizedlist>
     1461      the "Safe Mode".</para></note></para>
     1462
     1463      <para>The Aero theme is not enabled by default. To enable it
     1464        <itemizedlist>
    14531465          <listitem>
    14541466            <para>In Windows Vista guest: right-click on the desktop, in the
    14551467            context menu select "Personalize", then select "Windows Color and Appearance"
    14561468            in the "Personalization" window, in the "Appearance Settings" dialog select
    1457             "Windows Aero" and press "OK"</para></listitem>
     1469            "Windows Aero" and press "OK"</para>
     1470          </listitem>
    14581471          <listitem>
    14591472            <para>In Windows 7 guest: right-click on the desktop, in the
    14601473            context menu select "Personalize" and select any Aero theme
    1461             in the "Personalization" window</para></listitem>
    1462           </itemizedlist>
    1463         </para>
     1474            in the "Personalization" window</para>
     1475          </listitem>
     1476        </itemizedlist>
    14641477      </para>
    14651478

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

    r56175 r56451  
    15671567    <para>To experiment with a VM configuration, test different guest OS levels
    15681568    or to simply backup a VM, VirtualBox can create a full or a linked copy of
    1569     an existing VM.<footnote>Cloning support was introduced with VirtualBox
    1570     4.1.</footnote></para>
     1569    an existing VM.<footnote><para>Cloning support was introduced with VirtualBox
     1570    4.1.</para></footnote></para>
    15711571   
    15721572    <para>A wizard will guide you through the clone process:</para>

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

    r54933 r56451  
    1212        <itemizedlist>
    1313            <listitem>
    14                 WDDM Direct3D video driver for Windows guests
    15             </listitem>
    16             <listitem>
    17                 Hardware 3D acceleration support for Windows, Linux, and Solaris
    18                 guests
    19             </listitem>
    20             <listitem>
    21                 Hardware 2D video playback acceleration support for Windows
    22                 guests
    23             </listitem>
    24             <listitem>
    25                 PCI pass-through (Linux hosts only)
    26             </listitem>
    27             <listitem>
    28                 Mac OS X guests (Mac hosts only)
    29             </listitem>
    30             <listitem>
    31                 ICH9 chipset emulation
    32             </listitem>
    33             <listitem>
    34                 EFI firmware
    35             </listitem>
    36             <listitem>
    37                 Host CD/DVD drive pass-through
    38             </listitem>
    39             <listitem>
    40                 Support of iSCSI via internal networking
    41             </listitem>
    42             <listitem>
    43                 Synthetic CPU reporting
     14                <para>WDDM Direct3D video driver for Windows guests</para>
     15            </listitem>
     16            <listitem>
     17                <para>Hardware 3D acceleration support for Windows, Linux, and Solaris
     18                guests</para>
     19            </listitem>
     20            <listitem>
     21                <para>Hardware 2D video playback acceleration support for Windows
     22                guests</para>
     23            </listitem>
     24            <listitem>
     25                <para>PCI pass-through (Linux hosts only)</para>
     26            </listitem>
     27            <listitem>
     28                <para>Mac OS X guests (Mac hosts only)</para>
     29            </listitem>
     30            <listitem>
     31                <para>ICH9 chipset emulation</para>
     32            </listitem>
     33            <listitem>
     34                <para>EFI firmware</para>
     35            </listitem>
     36            <listitem>
     37                <para>Host CD/DVD drive pass-through</para>
     38            </listitem>
     39            <listitem>
     40                <para>Support of iSCSI via internal networking</para>
     41            </listitem>
     42            <listitem>
     43                <para>Synthetic CPU reporting</para>
    4444            </listitem>
    4545        </itemizedlist>

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

    r56223 r56451  
    725725          linkend="vboxmanage-dhcpserver" /> for details.</para>
    726726        </listitem>
    727       </itemizedlist></para>
    728     <para><note>On Linux and Mac OS X hosts the number of host-only interfaces is
    729     limited to 128. There is no such limit for Solaris and Windows hosts.</note></para>
     727      </itemizedlist>
     728    </para>
     729
     730    <para><note><para>On Linux and Mac OS X hosts the number of host-only
     731    interfaces is limited to 128. There is no such limit for Solaris and
     732    Windows hosts.</para></note></para>
    730733  </sect1>
    731734
    … …  
    791794    Internal network case.</para>
    792795
    793     <para><note>
    794         On Unix-based hosts (e.g. Linux, Solaris, Mac OS X) it is not possible
    795         to bind to ports below 1024 from applications that are not run by
    796         <computeroutput>root</computeroutput>. As a result, if you try to
    797         configure such a source UDP port, the VM will refuse to start.
    798       </note></para>
     796    <para><note><para>On Unix-based hosts (e.g. Linux, Solaris, Mac OS X) it is
     797    not possible to bind to ports below 1024 from applications that are not run
     798    by <computeroutput>root</computeroutput>. As a result, if you try to
     799    configure such a source UDP port, the VM will refuse to
     800    start.</para></note></para>
    799801  </sect1>
    800802
    … …  
    937939        <listitem>
    938940          <para>Use <emphasis>bridged</emphasis> attachment instead of
    939             <emphasis>NAT</emphasis></para>;
     941            <emphasis>NAT</emphasis>;</para>
    940942        </listitem>
    941943        <listitem>

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

    r53023 r56451  
    66
    77  <sect1>
    8     <title>Overview</title>
    9     <para>
     8    <title>General Security Principles</title>
     9
     10    <para>The following principles are fundamental to using any application
     11      securely.
     12      <glosslist>
     13        <glossentry>
     14          <glossterm>Keep Software Up To Date</glossterm>
     15          <glossdef>
     16            <para>
     17              One of the principles of good security practise is to keep all
     18              software versions and patches up to date. Activate the VirtualBox
     19              update notification to get notified when a new VirtualBox release
     20              is available. When updating VirtualBox, do not forget to update
     21              the Guest Additions. Keep the host operating system as well as the
     22              guest operating system up to date.
     23            </para>
     24          </glossdef>
     25        </glossentry>
     26
     27        <glossentry>
     28          <glossterm>Restrict Network Access to Critical Services</glossterm>
     29          <glossdef>
     30            <para>
     31              Use proper means, for instance a firewall, to protect your computer
     32              and your guest(s) from accesses from the outside. Choosing the proper
     33              networking mode for VMs helps to separate host networking from the
     34              guest and vice versa.
     35            </para>
     36          </glossdef>
     37        </glossentry>
     38
     39        <glossentry>
     40          <glossterm>Follow the Principle of Least Privilege</glossterm>
     41          <glossdef>
     42            <para>
     43              The principle of least privilege states that users should be given the
     44              least amount of privilege necessary to perform their jobs. Always execute VirtualBox
     45              as a regular user. We strongly discourage anyone from executing
     46              VirtualBox with system privileges.
     47            </para>
     48            <para>
     49              Choose restrictive permissions when creating configuration files,
     50              for instance when creating /etc/default/virtualbox, see
     51              <xref linkend="linux_install_opts"/>. Mode 0600 would be preferred.
     52            </para>
     53          </glossdef>
     54        </glossentry>
     55
     56        <glossentry>
     57          <glossterm>Monitor System Activity</glossterm>
     58          <glossdef>
     59            <para>
     60              System security builds on three pillars: good security protocols, proper
     61              system configuration and system monitoring. Auditing and reviewing audit
     62              records address the third requirement. Each component within a system
     63              has some degree of monitoring capability. Follow audit advice in this
     64              document and regularly monitor audit records.
     65            </para>
     66          </glossdef>
     67        </glossentry>
     68
     69        <glossentry>
     70          <glossterm>Keep Up To Date on Latest Security Information</glossterm>
     71          <glossdef>
     72            <para>
     73              Oracle continually improves its software and documentation. Check this
     74              note note yearly for revisions.
     75            </para>
     76          </glossdef>
     77        </glossentry>
     78
     79      </glosslist>
    1080    </para>
    11 
    12     <sect2>
    13       <title>General Security Principles</title>
    14 
    15       <para>The following principles are fundamental to using any application
    16         securely.
    17         <glosslist>
    18           <glossentry>
    19             <glossterm>Keep Software Up To Date</glossterm>
    20             <glossdef>
    21               <para>
    22                 One of the principles of good security practise is to keep all
    23                 software versions and patches up to date. Activate the VirtualBox
    24                 update notification to get notified when a new VirtualBox release
    25                 is available. When updating VirtualBox, do not forget to update
    26                 the Guest Additions. Keep the host operating system as well as the
    27                 guest operating system up to date.
    28               </para>
    29             </glossdef>
    30           </glossentry>
    31 
    32           <glossentry>
    33             <glossterm>Restrict Network Access to Critical Services</glossterm>
    34             <glossdef>
    35               <para>
    36                 Use proper means, for instance a firewall, to protect your computer
    37                 and your guest(s) from accesses from the outside. Choosing the proper
    38                 networking mode for VMs helps to separate host networking from the
    39                 guest and vice versa.
    40               </para>
    41             </glossdef>
    42           </glossentry>
    43 
    44           <glossentry>
    45             <glossterm>Follow the Principle of Least Privilege</glossterm>
    46             <glossdef>
    47               <para>
    48                 The principle of least privilege states that users should be given the
    49                 least amount of privilege necessary to perform their jobs. Always execute VirtualBox
    50                 as a regular user. We strongly discourage anyone from executing
    51                 VirtualBox with system privileges.
    52               </para>
    53               <para>
    54                 Choose restrictive permissions when creating configuration files,
    55                 for instance when creating /etc/default/virtualbox, see
    56                 <xref linkend="linux_install_opts"/>. Mode 0600 would be preferred.
    57               </para>
    58             </glossdef>
    59           </glossentry>
    60 
    61           <glossentry>
    62             <glossterm>Monitor System Activity</glossterm>
    63             <glossdef>
    64               <para>
    65                 System security builds on three pillars: good security protocols, proper
    66                 system configuration and system monitoring. Auditing and reviewing audit
    67                 records address the third requirement. Each component within a system
    68                 has some degree of monitoring capability. Follow audit advice in this
    69                 document and regularly monitor audit records.
    70               </para>
    71             </glossdef>
    72           </glossentry>
    73 
    74           <glossentry>
    75             <glossterm>Keep Up To Date on Latest Security Information</glossterm>
    76             <glossdef>
    77               <para>
    78                 Oracle continually improves its software and documentation. Check this
    79                 note note yearly for revisions.
    80               </para>
    81             </glossdef>
    82           </glossentry>
    83 
    84         </glosslist>
    85       </para>
    86     </sect2>
    8781  </sect1>
    8882
    8983  <sect1>
    9084    <title>Secure Installation and Configuration</title>
     85
     86    <sect2>
     87      <title>Installation Overview</title>
     88      <para>
     89        The VirtualBox base package should be downloaded only from a trusted source,
     90        for instance the official website
     91        <ulink url="http://www.virtualbox.org">http://www.virtualbox.org</ulink>.
     92        The integrity of the package should be verified with the provided SHA256
     93        checksum which can be found on the official website.
     94      </para>
     95      <para>
     96        General VirtualBox installation instructions for the supported hosts
     97        can be found in <xref linkend="installation"/>.
     98      </para>
     99      <para>
     100        On Windows hosts, the installer allows for disabling USB support, support
     101        for bridged networking, support for host-only networking and the Python
     102        language bindings, see <xref linkend="installation_windows"/>.
     103        All these features are enabled by default but disabling some
     104        of them could be appropriate if the corresponding functionality is not
     105        required by any virtual machine. The Python language bindings are only
     106        required if the VirtualBox API is to be used by external Python
     107        applications. In particular USB support and support
     108        for the two networking modes require the installation of Windows kernel
     109        drivers on the host. Therefore disabling those selected features can
     110        not only be used to restrict the user to certain functionality but
     111        also to minimize the surface provided to a potential attacker.     </para>
     112      <para>
     113        The general case is to install the complete VirtualBox package. The
     114        installation must be done with system privileges. All VirtualBox binaries
     115        should be executed as a regular user and never as a privileged user.
     116      </para>
     117      <para>
     118        The Oracle VM VirtualBox extension pack provides additional features
     119        and must be downloaded and installed separately, see
     120        <xref linkend="intro-installing"/>. As for the base package, the SHA256
     121        checksum of the extension pack should be verified. As the installation
     122        requires system privileges, VirtualBox will ask for the system
     123        password during the installation of the extension pack.
     124      </para>
     125    </sect2>
     126 
     127    <sect2>
     128      <title>Post Installation Configuration</title>
     129      <para>
     130        Normally there is no post installation configuration of VirtualBox components
     131        required. However, on Solaris and Linux hosts it is necessary to configure
     132        the proper permissions for users executing VMs and who should be able to
     133        access certain host resources. For instance, Linux users must be member of
     134        the <emphasis>vboxusers</emphasis> group to be able to pass USB devices to a
     135        guest. If a serial host interface should be accessed from a VM, the proper
     136        permissions must be granted to the user to be able to access that device.
     137        The same applies to other resources like raw partitions, DVD/CD drives
     138        and sound devices.
     139      </para>
     140    </sect2>
    91141  </sect1>
    92 
    93   <sect2>
    94     <title>Installation Overview</title>
    95     <para>
    96       The VirtualBox base package should be downloaded only from a trusted source,
    97       for instance the official website
    98       <ulink url="http://www.virtualbox.org">http://www.virtualbox.org</ulink>.
    99       The integrity of the package should be verified with the provided SHA256
    100       checksum which can be found on the official website.
    101     </para>
    102     <para>
    103       General VirtualBox installation instructions for the supported hosts
    104       can be found in <xref linkend="installation"/>.
    105     </para>
    106     <para>
    107       On Windows hosts, the installer allows for disabling USB support, support
    108       for bridged networking, support for host-only networking and the Python
    109       language bindings, see <xref linkend="installation_windows"/>.
    110       All these features are enabled by default but disabling some
    111       of them could be appropriate if the corresponding functionality is not
    112       required by any virtual machine. The Python language bindings are only
    113       required if the VirtualBox API is to be used by external Python
    114       applications. In particular USB support and support
    115       for the two networking modes require the installation of Windows kernel
    116       drivers on the host. Therefore disabling those selected features can
    117       not only be used to restrict the user to certain functionality but
    118       also to minimize the surface provided to a potential attacker.     </para>
    119     <para>
    120       The general case is to install the complete VirtualBox package. The
    121       installation must be done with system privileges. All VirtualBox binaries
    122       should be executed as a regular user and never as a privileged user.
    123     </para>
    124     <para>
    125       The Oracle VM VirtualBox extension pack provides additional features
    126       and must be downloaded and installed separately, see
    127       <xref linkend="intro-installing"/>. As for the base package, the SHA256
    128       checksum of the extension pack should be verified. As the installation
    129       requires system privileges, VirtualBox will ask for the system
    130       password during the installation of the extension pack.
    131     </para>
    132   </sect2>
    133 
    134   <sect2>
    135     <title>Post Installation Configuration</title>
    136     <para>
    137       Normally there is no post installation configuration of VirtualBox components
    138       required. However, on Solaris and Linux hosts it is necessary to configure
    139       the proper permissions for users executing VMs and who should be able to
    140       access certain host resources. For instance, Linux users must be member of
    141       the <emphasis>vboxusers</emphasis> group to be able to pass USB devices to a
    142       guest. If a serial host interface should be accessed from a VM, the proper
    143       permissions must be granted to the user to be able to access that device.
    144       The same applies to other resources like raw partitions, DVD/CD drives
    145       and sound devices.
    146     </para>
    147   </sect2>
    148 
     142 
    149143  <sect1>
    150144    <title>Security Features</title>

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

    r48627 r56451  
    30363036        Copyright 1996-2002, 2006 by David Turner, Robert Wilhelm, and Werner Lemberg
    30373037      </para>
    3038       <sect4>
     3038      <sect3>
    30393039        <title>Introduction</title>
    3040       </sect4>
    3041       <sect4>
    3042         <title></title>
    30433040        <para>
    30443041          The FreeType  Project is distributed in  several archive packages;
    … …  
    31003097          actually use.
    31013098        </para>
    3102       </sect4>
    3103       <sect4>
     3099      </sect3>
     3100      <sect3>
    31043101        <title>Legal Terms</title>
    31053102        <sect4>
    … …  
    31573154          <itemizedlist>
    31583155            <listitem>
     3156              <para>
    31593157              Redistribution of  source code  must retain this  license file
    31603158              (`FTL.TXT') unaltered; any  additions, deletions or changes to
    … …  
    31633161              original  files must  be  preserved in  all  copies of  source
    31643162              files.
     3163              </para>
    31653164            </listitem>
    31663165            <listitem>
     3166              <para>
    31673167              Redistribution in binary form must provide a  disclaimer  that
    31683168              states  that  the software is based in part of the work of the
    … …  
    31703170              encourage you to put an URL to the FreeType web page  in  your
    31713171              documentation, though this isn't mandatory.
     3172              </para>
    31723173            </listitem>
    31733174          </itemizedlist>
    … …  
    32363237          </para>
    32373238        </sect4>
    3238       </sect4>
     3239      </sect3>
    32393240    </sect2>
    32403241    <sect2 id="licVPX">

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

    r56327 r56451  
    889889          </listitem>
    890890         
    891           This allows you to change the address range occupied by
    892891          <listitem>
    893892            <para><computeroutput>--bridgeadapter&lt;1-N&gt;
    … …  
    43214320          of registers, each having one of the following forms:
    43224321          <itemizedlist>
    4323             <listitem><computeroutput>register-set.register-name.sub-field</computeroutput></listitem>
    4324             <listitem><computeroutput>register-set.register-name</computeroutput></listitem>
    4325             <listitem><computeroutput>cpu-register-name.sub-field</computeroutput></listitem>
    4326             <listitem><computeroutput>cpu-register-name</computeroutput></listitem>
    4327             <listitem><computeroutput>all</computeroutput></listitem>
     4322            <listitem><para><computeroutput>register-set.register-name.sub-field</computeroutput></para></listitem>
     4323            <listitem><para><computeroutput>register-set.register-name</computeroutput></para></listitem>
     4324            <listitem><para><computeroutput>cpu-register-name.sub-field</computeroutput></para></listitem>
     4325            <listitem><para><computeroutput>cpu-register-name</computeroutput></para></listitem>
     4326            <listitem><para><computeroutput>all</computeroutput></para></listitem>
    43284327          </itemizedlist>
    43294328          The <computeroutput>all</computeroutput> form will cause all
    … …  
    43404339          of register assignments, each having one of the following forms:
    43414340          <itemizedlist>
    4342             <listitem><computeroutput>register-set.register-name.sub-field=value</computeroutput></listitem>
    4343             <listitem><computeroutput>register-set.register-name=value</computeroutput></listitem>
    4344             <listitem><computeroutput>cpu-register-name.sub-field=value</computeroutput></listitem>
    4345             <listitem><computeroutput>cpu-register-name=value</computeroutput></listitem>
     4341            <listitem><para><computeroutput>register-set.register-name.sub-field=value</computeroutput></para></listitem>
     4342            <listitem><para><computeroutput>register-set.register-name=value</computeroutput></para></listitem>
     4343            <listitem><para><computeroutput>cpu-register-name.sub-field=value</computeroutput></para></listitem>
     4344            <listitem><para><computeroutput>cpu-register-name=value</computeroutput></para></listitem>
    43464345          </itemizedlist>
    43474346          The value format should be in the same style as what
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