VirtualBox

Changeset 99797 in vbox for trunk/doc/manual


Ignore:
Timestamp:
May 15, 2023 5:27:56 PM (21 months ago)
Author:
vboxsync
Message:

Docs: bugref:10302. Merging changes from the docs team. Almost exclusively conkeyref related stuff.

Location:
trunk/doc/manual/en_US/dita
Files:
302 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/manual/en_US/dita/UserManual.ditamap

    r99514 r99797  
    6868  -->
    6969    <frontmatter>
     70       <mapref href="conkeyrefs.ditamap" format="ditamap" toc="no" processing-role="resource-only"/>
    7071       <booklists>
    7172          <toc/>
  • trunk/doc/manual/en_US/dita/ohc.ditaval

    r99111 r99797  
    1 <?xml version="1.0" encoding="UTF-8"?>
     1<?xml version='1.0' encoding='UTF-8'?>
    22<val>
    33  <prop action="exclude" att="platform" val="htmlhelp"/>
  • trunk/doc/manual/en_US/dita/topics/BasicConcepts.dita

    r98549 r99797  
    77    <p>
    88    This chapter provides detailed steps for configuring an
    9     Oracle VM VirtualBox virtual machine (VM). For an introduction to
    10     Oracle VM VirtualBox and steps to get your first virtual machine running,
     9    <ph conkeyref="vbox-conkeyref-phrases/product-name"/> virtual machine (VM). For an introduction to
     10    <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and steps to get your first virtual machine running,
    1111    see <xref href="Introduction.dita#Introduction"/>.
    1212  </p>
     
    2020      <li>
    2121        <p>
    22         Have Oracle VM VirtualBox present an ISO CD-ROM image to a guest
     22        Have <ph conkeyref="vbox-conkeyref-phrases/product-name"/> present an ISO CD-ROM image to a guest
    2323        system as if it were a physical CD-ROM.
    2424      </p>
  • trunk/doc/manual/en_US/dita/topics/ExperimentalFeatures.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       Some Oracle VM VirtualBox features are labeled as experimental. Such
     8      Some <ph conkeyref="vbox-conkeyref-phrases/product-name"/> features are labeled as experimental. Such
    99      features are provided on an "as-is" basis and are not formally
    1010      supported. However, feedback and suggestions about such features
     
    5252      <li>
    5353        <p>
    54           Using Oracle VM VirtualBox and Hyper-V on the same host
     54          Using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and Hyper-V on the same host
    5555        </p>
    5656      </li>
  • trunk/doc/manual/en_US/dita/topics/Introduction.dita

    r99182 r99797  
    66  <body>
    77    <p>
    8     Welcome to Oracle VM VirtualBox.
     8    Welcome to <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    99  </p>
    1010    <p>
    11     Oracle VM VirtualBox is a cross-platform virtualization application. What
     11    <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is a cross-platform virtualization application. What
    1212    does that mean? For one thing, it installs on your existing Intel or
    1313    AMD-based computers, whether they are running Windows, macOS, Linux,
     
    2222  </p>
    2323    <p>
    24     Oracle VM VirtualBox is deceptively simple yet also very powerful. It can
     24    <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is deceptively simple yet also very powerful. It can
    2525    run everywhere from small embedded systems or desktop class machines
    2626    all the way up to datacenter deployments and even Cloud
     
    2828  </p>
    2929    <p>
    30     The following screenshot shows how Oracle VM VirtualBox, installed on an
     30    The following screenshot shows how <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, installed on an
    3131    Apple Mac computer, is running Windows Server 2016 in a virtual
    3232    machine window.
     
    4646    In this User Manual, we will begin simply with a quick introduction
    4747    to virtualization and how to get your first virtual machine running
    48     with the easy-to-use Oracle VM VirtualBox graphical user interface.
     48    with the easy-to-use <ph conkeyref="vbox-conkeyref-phrases/product-name"/> graphical user interface.
    4949    Subsequent chapters will go into much more detail covering more
    5050    powerful tools and features, but fortunately, it is not necessary to
    51     read the entire User Manual before you can use Oracle VM VirtualBox.
     51    read the entire User Manual before you can use <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    5252  </p>
    5353    <p>
    54     You can find a summary of Oracle VM VirtualBox's capabilities in
    55     <xref href="features-overview.dita#features-overview"/>. For existing Oracle VM VirtualBox
     54    You can find a summary of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s capabilities in
     55    <xref href="features-overview.dita#features-overview"/>. For existing <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    5656    users who just want to find out what is new in this release, see the
    57     <xref href="https://docs.oracle.com/en/virtualization/virtualbox/7.0/relnotes/ChangeLog.html" format="html" scope="external">Change Log</xref>.
     57    <xref href="https://docs.oracle.com/en/virtualization/virtualbox/7.0/relnotes/relnotes-ChangeLog.html" format="html" scope="external">Change Log</xref>.
    5858  </p>
    5959  </body>
  • trunk/doc/manual/en_US/dita/topics/KnownProblems.dita

    r98549 r99797  
    77    <p>
    88      The following section describes known problems with this release
    9       of Oracle VM VirtualBox. Unless marked otherwise, these issues are
     9      of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. Unless marked otherwise, these issues are
    1010      planned to be fixed in later releases.
    1111    </p>
     
    1313      <li>
    1414        <p>
    15           The macOS installer packages for Oracle VM VirtualBox 7 currently do
     15          The macOS installer packages for <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 7 currently do
    1616          not include the Internal Networking feature, which is
    1717          available on all other platforms. This will be addressed with
    18           an update of Oracle VM VirtualBox 7. For setups which depend on this
    19           functionality it is best to keep using Oracle VM VirtualBox 6.1.
    20         </p>
    21       </li>
    22       <li>
    23         <p>
    24           Poor performance when using Oracle VM VirtualBox and
     18          an update of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 7. For setups which depend on this
     19          functionality it is best to keep using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 6.1.
     20        </p>
     21      </li>
     22      <li>
     23        <p>
     24          Poor performance when using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and
    2525          <b outputclass="bold">Hyper-V</b> on the same host. To
    2626          fix this, certain Windows features like "Hyper-V Platform",
     
    146146      <li>
    147147        <p>
    148           The RDP server in the Oracle VM VirtualBox extension pack supports
     148          The RDP server in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> extension pack supports
    149149          only audio streams in format 22.05kHz stereo 16-bit. If the
    150150          RDP client requests any other audio format there will be no
     
    202202          <li>
    203203            <p>
    204               Oracle VM VirtualBox does not provide Guest Additions for Mac OS
     204              <ph conkeyref="vbox-conkeyref-phrases/product-name"/> does not provide Guest Additions for Mac OS
    205205              X at this time.
    206206            </p>
     
    230230          <li>
    231231            <p>
    232               By default, the Oracle VM VirtualBox EFI enables debug output of
     232              By default, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> EFI enables debug output of
    233233              the Mac OS X kernel to help you diagnose boot problems.
    234234              Note that there is a lot of output and not all errors are
  • trunk/doc/manual/en_US/dita/topics/TechnicalBackground.dita

    r99016 r99797  
    88    This chapter provides additional information for readers who are
    99    familiar with computer architecture and technology and wish to find
    10     out more about how Oracle VM VirtualBox works <i>under the
     10    out more about how <ph conkeyref="vbox-conkeyref-phrases/product-name"/> works <i>under the
    1111    hood</i>. The contents of this chapter are not required
    12     reading in order to use Oracle VM VirtualBox successfully.
     12    reading in order to use <ph conkeyref="vbox-conkeyref-phrases/product-name"/> successfully.
    1313  </p>
    1414  </body>
  • trunk/doc/manual/en_US/dita/topics/Troubleshooting.dita

    r99016 r99797  
    77    <p>
    88    This chapter provides answers to commonly asked questions. In order
    9     to improve your user experience with Oracle VM VirtualBox, it is
     9    to improve your user experience with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, it is
    1010    recommended to read this section to learn more about common pitfalls
    1111    and get recommendations on how to use the product.
  • trunk/doc/manual/en_US/dita/topics/VirtualBoxAPI.dita

    r99016 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="VirtualBoxAPI">
    4   <title>Oracle VM VirtualBox Programming Interfaces</title>
     4  <title><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Programming Interfaces</title>
    55 
    66  <body>
    77    <p>
    8     Oracle VM VirtualBox comes with comprehensive support for third-party
     8    <ph conkeyref="vbox-conkeyref-phrases/product-name"/> comes with comprehensive support for third-party
    99    developers. The so-called <i>Main API</i> of
    10     Oracle VM VirtualBox exposes the entire feature set of the virtualization
     10    <ph conkeyref="vbox-conkeyref-phrases/product-name"/> exposes the entire feature set of the virtualization
    1111    engine. It is completely documented and available to anyone who
    12     wishes to control Oracle VM VirtualBox programmatically.
     12    wishes to control <ph conkeyref="vbox-conkeyref-phrases/product-name"/> programmatically.
    1313  </p>
    1414    <p>
  • trunk/doc/manual/en_US/dita/topics/addhostonlysolaris.dita

    r98549 r99797  
    77  <body>
    88    <p>
    9       By default Oracle VM VirtualBox provides you with one host-only network
     9      By default <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides you with one host-only network
    1010      interface. Adding more host-only network interfaces on Oracle
    1111      Solaris hosts requires manual configuration. Here is how to add
     
    6969      <filepath>/etc/nwam/llp</filepath> and add the appropriate entries
    7070      to set the netmask and static IP for each of those interfaces. The
    71       Oracle VM VirtualBox installer only updates these configuration files
     71      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> installer only updates these configuration files
    7272      for the one "vboxnet0" interface it creates by default.
    7373    </p>
  • trunk/doc/manual/en_US/dita/topics/additions-linux-graphics-mouse.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8           In Linux and Oracle Solaris guests, Oracle VM VirtualBox graphics
     8          In Linux and Oracle Solaris guests, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> graphics
    99          and mouse integration goes through the X Window System.
    10           Oracle VM VirtualBox can use the X.Org variant of the system, or
     10          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can use the X.Org variant of the system, or
    1111          XFree86 version 4.3 which is identical to the first X.Org
    1212          release. During the installation process, the X.Org display
     
    1919          many unsupported systems will work correctly too, the guest's
    2020          graphics mode will change to fit the size of the
    21           Oracle VM VirtualBox window on the host when it is resized. You can
     21          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> window on the host when it is resized. You can
    2222          also ask the guest system to switch to a particular resolution
    2323          by sending a video mode hint using the
     
    3838        </p>
    3939    <p>
    40           Starting from Oracle VM VirtualBox 7, Linux guest screen resize
     40          Starting from <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 7, Linux guest screen resize
    4141          functionality for guests running VMSVGA graphics configuration
    4242          has been changed. Since then, this functionality consists of a
  • trunk/doc/manual/en_US/dita/topics/additions-linux-install-unattended.dita

    r98549 r99797  
    77    <p>
    88          You can configure unattended installation of the
    9           Oracle VM VirtualBox Guest Additions when you create a new VM using
     9          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions when you create a new VM using
    1010          the <b outputclass="bold">Create Virtual Machine</b>
    1111          wizard. Select the <b outputclass="bold">Guest
  • trunk/doc/manual/en_US/dita/topics/additions-linux-install.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8           The Oracle VM VirtualBox Guest Additions for Linux are provided on
     8          The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions for Linux are provided on
    99          the same virtual CD-ROM file as the Guest Additions for
    1010          Windows. See <xref href="mountingadditionsiso.dita#mountingadditionsiso"/>. They also
  • trunk/doc/manual/en_US/dita/topics/additions-linux.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         Like the Windows Guest Additions, the Oracle VM VirtualBox Guest
     8        Like the Windows Guest Additions, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest
    99        Additions for Linux are a set of device drivers and system
    1010        applications which may be installed in the guest operating
     
    5454    <p>
    5555        Note that some Linux distributions already come with all or part
    56         of the Oracle VM VirtualBox Guest Additions. You may choose to keep
     56        of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions. You may choose to keep
    5757        the distribution's version of the Guest Additions but these are
    5858        often not up to date and limited in functionality, so we
    5959        recommend replacing them with the Guest Additions that come with
    60         Oracle VM VirtualBox. The Oracle VM VirtualBox Linux Guest Additions
     60        <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Linux Guest Additions
    6161        installer tries to detect an existing installation and replace
    6262        them but depending on how the distribution integrates the Guest
  • trunk/doc/manual/en_US/dita/topics/additions-os2.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         Oracle VM VirtualBox also ships with a set of drivers that improve
     8        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also ships with a set of drivers that improve
    99        running OS/2 in a virtual machine. Due to restrictions of OS/2
    1010        itself, this variant of the Guest Additions has a limited
  • trunk/doc/manual/en_US/dita/topics/additions-solaris-install-unattended.dita

    r98549 r99797  
    77    <p>
    88          You can configure unattended installation of the
    9           Oracle VM VirtualBox Guest Additions when you create a new VM using
     9          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions when you create a new VM using
    1010          the <b outputclass="bold">Create Virtual Machine</b>
    1111          wizard. Select the <b outputclass="bold">Guest
  • trunk/doc/manual/en_US/dita/topics/additions-solaris-install.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8           The Oracle VM VirtualBox Guest Additions for Oracle Solaris are
     8          The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions for Oracle Solaris are
    99          provided on the same ISO CD-ROM as the Additions for Windows
    1010          and Linux. They come with an installation program that guides
  • trunk/doc/manual/en_US/dita/topics/additions-solaris.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         Like the Windows Guest Additions, the Oracle VM VirtualBox Guest
     8        Like the Windows Guest Additions, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest
    99        Additions for Oracle Solaris take the form of a set of device
    1010        drivers and system applications which may be installed in the
  • trunk/doc/manual/en_US/dita/topics/additions-windows-install-unattended-certs.dita

    r98549 r99797  
    77    <p>
    88            To avoid popups when performing an unattended installation
    9             of the Oracle VM VirtualBox Guest Additions, the code signing
     9            of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions, the code signing
    1010            certificates used to sign the drivers needs to be installed
    1111            in the correct certificate stores on the guest operating
     
    4040      <li>
    4141        <p>
    42                 Mount the Oracle VM VirtualBox Guest Additions .ISO.
     42                Mount the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions .ISO.
    4343              </p>
    4444      </li>
     
    4747                Open a command line window on the guest and change to
    4848                the <filepath>cert</filepath> folder on the
    49                 Oracle VM VirtualBox Guest Additions CD.
     49                <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions CD.
    5050              </p>
    5151      </li>
  • trunk/doc/manual/en_US/dita/topics/additions-windows-install-unattended.dita

    r98549 r99797  
    77    <p>
    88          You can configure unattended installation of the
    9           Oracle VM VirtualBox Guest Additions when you create a new VM using
     9          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions when you create a new VM using
    1010          the <b outputclass="bold">Create Virtual Machine</b>
    1111          wizard. Select the <b outputclass="bold">Guest
  • trunk/doc/manual/en_US/dita/topics/additions-windows-updating.dita

    r98549 r99797  
    1818      <li>
    1919        <p>
    20               Oracle VM VirtualBox Graphics Adapter
     20              <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Graphics Adapter
    2121            </p>
    2222      </li>
    2323      <li>
    2424        <p>
    25               Oracle VM VirtualBox System Device
     25              <ph conkeyref="vbox-conkeyref-phrases/product-name"/> System Device
    2626            </p>
    2727      </li>
  • trunk/doc/manual/en_US/dita/topics/additions-windows.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         The Oracle VM VirtualBox Windows Guest Additions are designed to be
     8        The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Windows Guest Additions are designed to be
    99        installed in a virtual machine running a Windows operating
    1010        system. The following versions of Windows guests are supported:
  • trunk/doc/manual/en_US/dita/topics/auth-config-using.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="auth-config-using">
    44  <title>Configuring and Using Authentication</title>
    5  
     5
    66  <body>
    77    <p>
    8         The following components of Oracle VM VirtualBox can use passwords for
     8        The following components of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can use passwords for
    99        authentication:
    1010      </p>
     
    1212      <li>
    1313        <p>
    14             When using remote iSCSI storage and the storage server
    15             requires authentication, an initiator secret can optionally
    16             be supplied with the <userinput>VBoxManage
    17             storageattach</userinput> command. As long as no settings
    18             password is provided, by using the command line option
    19            <codeph>--settingspwfile</codeph>, then this secret is
    20             stored <i>unencrypted</i> in the machine
    21             configuration and is therefore potentially readable on the
    22             host. See <xref href="storage-iscsi.dita">iSCSI Servers</xref> and
    23             <xref href="vboxmanage-storageattach.dita">VBoxManage storageattach</xref>.
    24           </p>
     14          When using remote iSCSI storage and the storage server requires authentication, an
     15          initiator secret can optionally be supplied with the <userinput>VBoxManage
     16          storageattach</userinput> command. As long as no settings password is provided, by using
     17          the command line option <codeph>--settingspwfile</codeph>, then this secret is stored
     18          <i>unencrypted</i> in the machine configuration and is therefore potentially readable on
     19          the host. See <xref href="storage-iscsi.dita">iSCSI Servers</xref> and <xref
     20          href="vboxmanage-storageattach.dita">VBoxManage storageattach</xref>.
     21        </p>
    2522      </li>
    2623      <li>
    2724        <p>
    28             When using the Oracle VM VirtualBox web service to control an
    29             Oracle VM VirtualBox host remotely, connections to the web service
     25            When using the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> web service to control an
     26            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> host remotely, connections to the web service
    3027            are authenticated in various ways. This is described in
    31             detail in the Oracle VM VirtualBox Software Development Kit (SDK)
     28            detail in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Software Development Kit (SDK)
    3229            reference. See <xref href="VirtualBoxAPI.dita#VirtualBoxAPI"/>.
    3330          </p>
     
    3532    </ul>
    3633  </body>
    37  
     34
    3835</topic>
  • trunk/doc/manual/en_US/dita/topics/autologon.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox provides Guest Addition modules for Windows, Linux,
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides Guest Addition modules for Windows, Linux,
    99      and Oracle Solaris to enable automated logins on the guest.
    1010    </p>
  • trunk/doc/manual/en_US/dita/topics/autologon_unix.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         Oracle VM VirtualBox provides a custom PAM module (Pluggable
     8        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides a custom PAM module (Pluggable
    99        Authentication Module) which can be used to perform automated
    1010        guest logins on platforms which support this framework.
     
    8282            <codeph>use_first_pass</codeph> for
    8383            <filepath>pam_unix2.so</filepath> is needed in order to pass
    84             the credentials from the Oracle VM VirtualBox module to the shadow
     84            the credentials from the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> module to the shadow
    8585            database authentication module. For Ubuntu, this needs to be
    8686            added to <filepath>/etc/pam.d/common-auth</filepath>, to the
     
    8888            <filepath>pam_unix.so</filepath>. This argument tells the
    8989            PAM module to use credentials already present in the stack,
    90             such as the ones provided by the Oracle VM VirtualBox PAM module.
     90            such as the ones provided by the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> PAM module.
    9191          </p>
    9292      </li>
  • trunk/doc/manual/en_US/dita/topics/autologon_unix_lightdm.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="autologon_unix_lightdm">
    4   <title>Oracle VM VirtualBox Greeter for Ubuntu/LightDM</title>
     4  <title><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Greeter for Ubuntu/LightDM</title>
    55 
    66  <body>
    77    <p>
    8           Oracle VM VirtualBox comes with a greeter module, named
     8          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> comes with a greeter module, named
    99          <userinput>vbox-greeter</userinput>, that can be used with
    1010          LightDM. LightDM is the default display manager for Ubuntu
     
    4141    <p>
    4242          The <userinput>vbox-greeter</userinput> module is installed by the
    43           Oracle VM VirtualBox Guest Additions installer and is located in
     43          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions installer and is located in
    4444          <filepath>/usr/sbin/</filepath>. To enable
    4545          <userinput>vbox-greeter</userinput> as the standard greeter
  • trunk/doc/manual/en_US/dita/topics/autologon_win.dita

    r98549 r99797  
    1111        modules. In Windows Vista and later releases, the GINA modules
    1212        were replaced with a new mechanism called credential providers.
    13         The Oracle VM VirtualBox Guest Additions for Windows come with both, a
     13        The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions for Windows come with both, a
    1414        GINA and a credential provider module, and therefore enable any
    1515        Windows guest to perform automated logins.
    1616      </p>
    1717    <p>
    18         To activate the Oracle VM VirtualBox GINA or credential provider
     18        To activate the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> GINA or credential provider
    1919        module, install the Guest Additions using the command line
    2020        switch <codeph>/with_autologon</codeph>. All the following
     
    2323      </p>
    2424    <p>
    25         To manually install the Oracle VM VirtualBox GINA module, extract the
     25        To manually install the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> GINA module, extract the
    2626        Guest Additions as shown in
    2727        <xref href="windows-guest-file-extraction.dita">Manual File Extraction</xref>, and copy the
     
    3434    <note>
    3535      <p>
    36           The Oracle VM VirtualBox GINA module is implemented as a wrapper
     36          The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> GINA module is implemented as a wrapper
    3737          around the <filepath>MSGINA.DLL</filepath> standard Windows
    3838          GINA module. As a result, it might not work correctly with
     
    4141    </note>
    4242    <p>
    43         To manually install the Oracle VM VirtualBox credential provider
     43        To manually install the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> credential provider
    4444        module, extract the Guest Additions as shown in
    4545        <xref href="windows-guest-file-extraction.dita">Manual File Extraction</xref> and copy the
     
    7070    <p>
    7171        While the VM is running, the credentials can be queried by the
    72         Oracle VM VirtualBox login modules, GINA or credential provider, using
    73         the Oracle VM VirtualBox Guest Additions device driver. When Windows
     72        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> login modules, GINA or credential provider, using
     73        the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions device driver. When Windows
    7474        is in <i>logged out</i> mode, the login modules
    7575        will constantly poll for credentials and if they are present, a
     
    9494            For <b outputclass="bold">Windows XP guests.</b> The
    9595            login subsystem needs to be configured to use the classic
    96             login dialog, as the Oracle VM VirtualBox GINA module does not
     96            login dialog, as the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> GINA module does not
    9797            support the Windows XP-style welcome dialog.
    9898          </p>
     
    124124    </ul>
    125125    <p>
    126         The following command forces Oracle VM VirtualBox to keep the
     126        The following command forces <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to keep the
    127127        credentials after they were read by the guest and on VM reset:
    128128      </p>
  • trunk/doc/manual/en_US/dita/topics/autostart-osx.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         On macOS, launchd is used to start the Oracle VM VirtualBox autostart
     8        On macOS, launchd is used to start the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> autostart
    99        service. An example configuration file can be found in
    1010        <filepath>/Applications/VirtualBox.app/Contents/MacOS/org.virtualbox.vboxautostart.plist</filepath>.
  • trunk/doc/manual/en_US/dita/topics/autostart-solaris.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         On Oracle Solaris hosts, the Oracle VM VirtualBox autostart daemon is
     8        On Oracle Solaris hosts, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> autostart daemon is
    99        integrated into the SMF framework. To enable it you must point
    1010        the service to an existing configuration file which has the same
     
    1616    <p>
    1717        When everything is configured correctly you can start the
    18         Oracle VM VirtualBox autostart service with the following command:
     18        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> autostart service with the following command:
    1919      </p>
    2020    <pre xml:space="preserve"># svcadm enable svc:/application/virtualbox/autostart:default</pre>
  • trunk/doc/manual/en_US/dita/topics/basic-unattended.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox can install a guest OS automatically. You only need
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can install a guest OS automatically. You only need
    99      to provide the installation medium and a few other parameters,
    1010      such as the name of the default user.
     
    2424        </p>
    2525        <p>
    26           During this step, Oracle VM VirtualBox scans the installation medium
     26          During this step, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> scans the installation medium
    2727          and changes certain parameters to ensure a seamless
    28           installation as a guest running on Oracle VM VirtualBox.
     28          installation as a guest running on <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    2929        </p>
    3030      </li>
  • trunk/doc/manual/en_US/dita/topics/buffer-overwriting-mitigation.dita

    r98549 r99797  
    3030        </p>
    3131    <p>
    32           The default action taken by Oracle VM VirtualBox is to clear the
     32          The default action taken by <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is to clear the
    3333          affected buffers when a thread is scheduled to execute guest
    3434          code, rather than on each VM entry. This reduces the
  • trunk/doc/manual/en_US/dita/topics/changeacpicust.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       You can configure Oracle VM VirtualBox to present up to four custom ACPI
     8      You can configure <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to present up to four custom ACPI
    99      tables to the guest. Use a command such as the following to
    1010      configure custom ACPI tables. Note that
  • trunk/doc/manual/en_US/dita/topics/changedmi.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       The DMI data that Oracle VM VirtualBox provides to guests can be changed
     8      The DMI data that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides to guests can be changed
    99      for a specific VM. Use the following commands to configure the DMI
    1010      BIOS information. In case your VM is configured to use EFI
     
    106106    </ul>
    107107    <p>
    108       If a DMI string is not set, the default value of Oracle VM VirtualBox is
     108      If a DMI string is not set, the default value of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is
    109109      used. To set an empty string use
    110110      <codeph>"&lt;EMPTY&gt;"</codeph>.
  • trunk/doc/manual/en_US/dita/topics/changenat.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="changenat">
    4   <title>Fine Tuning the Oracle VM VirtualBox NAT Engine</title>
     4  <title>Fine Tuning the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> NAT Engine</title>
    55 
    66  <body/>
  • trunk/doc/manual/en_US/dita/topics/changetimesync.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         The Oracle VM VirtualBox Guest Additions ensure that the guest's
     8        The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions ensure that the guest's
    99        system time is synchronized with the host time. There are
    1010        several parameters which can be tuned. The parameters can be set
  • trunk/doc/manual/en_US/dita/topics/changetscmode.dita

    r98549 r99797  
    77  <body>
    88    <p>
    9         By default, Oracle VM VirtualBox keeps all sources of time visible to
     9        By default, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> keeps all sources of time visible to
    1010        the guest synchronized to a single time source, the monotonic
    1111        host time. This reflects the assumptions of many guest operating
  • trunk/doc/manual/en_US/dita/topics/changevpd.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         Oracle VM VirtualBox reports vendor product data for its virtual hard
     8        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> reports vendor product data for its virtual hard
    99        disks which consist of hard disk serial number, firmware
    1010        revision and model number. These can be changed using the
  • trunk/doc/manual/en_US/dita/topics/clone.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="clone">
    44  <title>Cloning Virtual Machines</title>
    5  
     5
    66  <body>
    77    <p>
     
    6767      <li>
    6868        <p><b outputclass="bold">Path:</b> Choose a location for
    69           the cloned virtual machine, otherwise Oracle VM VirtualBox uses the
     69          the cloned virtual machine, otherwise <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses the
    7070          default machines folder.
    7171        </p>
     
    129129          differencing disk images based on the source VM disk images.
    130130          If you select the current state of the source VM as the clone
    131           point, Oracle VM VirtualBox creates a new snapshot.
     131          point, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates a new snapshot.
    132132        </p>
    133133      </li>
     
    181181    </p>
    182182    <p>
    183       You can also use the <userinput>VBoxManage clonevm</userinput> command
    184       to clone a VM. See <xref href="vboxmanage-clonevm.dita"/>.
     183      You can also use the <userinput>VBoxManage clonevm</userinput> command to clone a VM. See
     184      <xref href="vboxmanage-clonevm.dita"/>.
    185185    </p>
    186186  </body>
    187  
     187
    188188</topic>
  • trunk/doc/manual/en_US/dita/topics/cloningvdis.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="cloningvdis">
    44  <title>Cloning Disk Images</title>
    5  
     5
    66  <body>
    77    <p>
    8       You can duplicate hard disk image files on the same host to
    9       quickly produce a second virtual machine with the same OS setup.
    10       However, you should <i>only</i> make copies of
    11       virtual disk images using the utility supplied with
    12       Oracle VM VirtualBox. See <xref href="vboxmanage-clonemedium.dita"/>.
    13       This is because Oracle VM VirtualBox assigns a UUID to each disk image,
    14       which is also stored inside the image, and Oracle VM VirtualBox will
    15       refuse to work with two images that use the same number. If you do
    16       accidentally try to reimport a disk image which you copied
    17       normally, you can make a second copy using the <userinput>VBoxManage
    18       clonevm</userinput> command and import that instead.
     8      You can duplicate hard disk image files on the same host to quickly produce a second virtual
     9      machine with the same OS setup. However, you should <i>only</i> make copies of virtual disk
     10      images using the utility supplied with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. See
     11      <xref href="vboxmanage-clonemedium.dita"/>. This is because <ph conkeyref="vbox-conkeyref-phrases/product-name"/> assigns a UUID to
     12      each disk image, which is also stored inside the image, and <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will refuse
     13      to work with two images that use the same number. If you do accidentally try to reimport a
     14      disk image which you copied normally, you can make a second copy using the
     15      <userinput>VBoxManage clonevm</userinput> command and import that instead.
    1916    </p>
    2017    <p>
    2118      Note that Linux distributions identify the boot hard disk from the
    22       ID of the drive. The ID Oracle VM VirtualBox reports for a drive is
     19      ID of the drive. The ID <ph conkeyref="vbox-conkeyref-phrases/product-name"/> reports for a drive is
    2320      determined from the UUID of the virtual disk image. So if you
    2421      clone a disk image and try to boot the copied image the guest
     
    3532    <pre xml:space="preserve">hdparm -i /dev/sda</pre>
    3633  </body>
    37  
     34
    3835</topic>
  • trunk/doc/manual/en_US/dita/topics/cloud-create-api-keypair.dita

    r98549 r99797  
    77    <p/>
    88    <p>
    9         To use the cloud integration features of Oracle VM VirtualBox, you
     9        To use the cloud integration features of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, you
    1010        must generate an API signing key pair that is used for API
    11         requests to Oracle Cloud Infrastructure.
     11        requests to <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
    1212      </p>
    1313    <p>
    14         Your API requests are signed with your private key, and Oracle Cloud Infrastructure
     14        Your API requests are signed with your private key, and <ph conkeyref="vbox-conkeyref-phrases/oci"/>
    1515        uses the public key to verify the authenticity of the request.
    16         You must upload the public key to the Oracle Cloud Infrastructure Console.
     16        You must upload the public key to the <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console.
    1717      </p>
    1818    <note>
    1919      <p>
    2020          This key pair is not the same SSH key that you use to access
    21           compute instances on Oracle Cloud Infrastructure.
     21          compute instances on <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
    2222        </p>
    2323    </note>
  • trunk/doc/manual/en_US/dita/topics/cloud-create-cloud-profile.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="cloud-create-cloud-profile">
    44  <title>Creating a Cloud Profile</title>
    5  
     5
    66  <body>
    77    <p>
    8         Oracle VM VirtualBox uses a <i>cloud profile</i> to
    9         connect to Oracle Cloud Infrastructure. A cloud profile is a text file that contains
     8        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses a <i>cloud profile</i> to
     9        connect to <ph conkeyref="vbox-conkeyref-phrases/oci"/>. A cloud profile is a text file that contains
    1010        details of your key files and Oracle Cloud Identifier (OCID)
    1111        resource identifiers for your cloud account, such as the
     
    3333      </li>
    3434      <li>
    35         <p><b outputclass="bold">Region</b>. Shown on the Oracle Cloud Infrastructure
     35        <p><b outputclass="bold">Region</b>. Shown on the <ph conkeyref="vbox-conkeyref-phrases/oci"/>
    3636            Console. Click
    3737            <b outputclass="bold">Administration</b>,
     
    4141      <li>
    4242        <p><b outputclass="bold">Tenancy OCID.</b> Shown on the
    43             Oracle Cloud Infrastructure Console. Click
     43            <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console. Click
    4444            <b outputclass="bold">Administration</b>,
    4545            <b outputclass="bold">Tenancy Details</b>.
     
    5151      <li>
    5252        <p><b outputclass="bold">Compartment OCID.</b> Shown on
    53             the Oracle Cloud Infrastructure Console. Click
     53            the <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console. Click
    5454            <b outputclass="bold">Identity</b>,
    5555            <b outputclass="bold">Compartments</b>.
     
    6161      <li>
    6262        <p><b outputclass="bold">User OCID.</b> Shown on the
    63             Oracle Cloud Infrastructure Console. Click
     63            <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console. Click
    6464            <b outputclass="bold">Profile</b>,
    6565            <b outputclass="bold">User Settings</b>.
     
    8181          </p>
    8282        <p>
    83             The Cloud Profile Manager is a VirtualBox Manager tool that enables
     83            The Cloud Profile Manager is a <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> tool that enables
    8484            you to create, edit, and manage cloud profiles for your
    8585            cloud service accounts.
     
    8888      <li>
    8989        <p>
    90             Automatically, by using the <userinput>VBoxManage
    91             cloudprofile</userinput> command. See
    92             <xref href="vboxmanage-cloudprofile.dita"/>.
    93           </p>
     90          Automatically, by using the <userinput>VBoxManage cloudprofile</userinput> command. See
     91          <xref href="vboxmanage-cloudprofile.dita"/>.
     92        </p>
    9493      </li>
    9594      <li>
    9695        <p>
    9796            Manually, by creating an <filepath>oci_config</filepath>
    98             file in your Oracle VM VirtualBox global configuration directory.
     97            file in your <ph conkeyref="vbox-conkeyref-phrases/product-name"/> global configuration directory.
    9998            For example, this is
    10099            <filepath>$HOME/.config/VirtualBox/oci_config</filepath> on
     
    105104        <p>
    106105            Manually, by creating a <filepath>config</filepath> file in
    107             your Oracle Cloud Infrastructure configuration directory. For example, this is
     106            your <ph conkeyref="vbox-conkeyref-phrases/oci"/> configuration directory. For example, this is
    108107            <filepath>$HOME/.oci/config</filepath> on a Linux host.
    109108          </p>
    110109        <p>
    111             This is the same file that is used by the Oracle Cloud Infrastructure command line
     110            This is the same file that is used by the <ph conkeyref="vbox-conkeyref-phrases/oci"/> command line
    112111            interface.
    113112          </p>
    114113        <p>
    115             Oracle VM VirtualBox automatically uses the
     114            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> automatically uses the
    116115            <filepath>config</filepath> file if no cloud profile file is
    117116            present in your global configuration directory.
     
    122121    </ul>
    123122  </body>
    124  
     123
    125124</topic>
  • trunk/doc/manual/en_US/dita/topics/cloud-export-oci-prepare-vm.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="cloud-export-oci-prepare-vm">
    4   <title>Preparing a VM for Export to Oracle Cloud Infrastructure</title>
     4  <title>Preparing a VM for Export to <ph conkeyref="vbox-conkeyref-phrases/oci"/></title>
    55 
    66  <body>
    77    <p>
    8           Oracle Cloud Infrastructure provides the option to import a custom Linux image.
    9           Before an Oracle VM VirtualBox image can be exported to Oracle Cloud Infrastructure, the
     8          <ph conkeyref="vbox-conkeyref-phrases/oci"/> provides the option to import a custom Linux image.
     9          Before an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> image can be exported to <ph conkeyref="vbox-conkeyref-phrases/oci"/>, the
    1010          custom image needs to be prepared to ensure that instances
    1111          launched from the custom image can boot correctly and that
    1212          network connections will work. This section provides advice on
    13           how to prepare a Linux image for export from Oracle VM VirtualBox.
     13          how to prepare a Linux image for export from <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    1414        </p>
    1515    <p>
     
    2222              addresses.</b> Configure the VM to use a DHCP
    2323              server to allocate network addresses, rather than using a
    24               static IP address. The Oracle Cloud Infrastructure instance will then be
     24              static IP address. The <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance will then be
    2525              allocated an IP address automatically.
    2626            </p>
     
    3939      <li>
    4040        <p><b outputclass="bold">Disable persistent network device
    41               naming rules.</b> This means that the Oracle Cloud Infrastructure
     41              naming rules.</b> This means that the <ph conkeyref="vbox-conkeyref-phrases/oci"/>
    4242              instance will use the same network device names as the VM.
    4343            </p>
     
    7878        <p><b outputclass="bold">Enable the serial
    7979              console.</b> This enables you to troubleshoot the
    80               instance when it is running on Oracle Cloud Infrastructure.
     80              instance when it is running on <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
    8181            </p>
    8282        <ol>
     
    171171    <p>
    172172          For more information about importing a custom Linux image into
    173           Oracle Cloud Infrastructure, see also:
     173          <ph conkeyref="vbox-conkeyref-phrases/oci"/>, see also:
    174174        </p>
    175175    <p>
  • trunk/doc/manual/en_US/dita/topics/cloud-export-oci.dita

    r99497 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="cloud-export-oci">
    4   <title>Exporting an Appliance to Oracle Cloud Infrastructure</title>
    5  
     4  <title>Exporting an Appliance to <ph conkeyref="vbox-conkeyref-phrases/oci"/></title>
     5
    66  <body>
    77    <p>
    8         Oracle VM VirtualBox supports the export of VMs to an Oracle Cloud Infrastructure service.
    9         The exported VM is stored on Oracle Cloud Infrastructure as a custom Linux image. You
     8        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports the export of VMs to an <ph conkeyref="vbox-conkeyref-phrases/oci"/> service.
     9        The exported VM is stored on <ph conkeyref="vbox-conkeyref-phrases/oci"/> as a custom Linux image. You
    1010        can configure whether a cloud instance is created and started
    1111        after the export process has completed.
     
    1313    <note>
    1414      <p>
    15           Before you export a VM to Oracle Cloud Infrastructure, you must prepare the VM as
     15          Before you export a VM to <ph conkeyref="vbox-conkeyref-phrases/oci"/>, you must prepare the VM as
    1616          described in <xref href="cloud-export-oci-prepare-vm.dita#cloud-export-oci-prepare-vm"/>.
    1717        </p>
    1818    </note>
    1919    <p>
    20         Use the following steps to export a VM to Oracle Cloud Infrastructure:
     20        Use the following steps to export a VM to <ph conkeyref="vbox-conkeyref-phrases/oci"/>:
    2121      </p>
    2222    <ol>
     
    3737        <p>
    3838            From the <b outputclass="bold">Format</b> drop-down
    39             list, select <b outputclass="bold">Oracle Cloud Infrastructure</b>.
     39            list, select <b outputclass="bold"><ph conkeyref="vbox-conkeyref-phrases/oci"/></b>.
    4040          </p>
    4141        <p>
    4242            In the <b outputclass="bold">Profile</b> drop-down
    43             list, select the cloud profile used for your Oracle Cloud Infrastructure account.
     43            list, select the cloud profile used for your <ph conkeyref="vbox-conkeyref-phrases/oci"/> account.
    4444          </p>
    4545        <fig id="fig-export-appliance-oci">
     
    5757            In the <b outputclass="bold">Machine Creation</b>
    5858            field, select an option to configure settings for the cloud
    59             instance created when you export to Oracle Cloud Infrastructure. The options
     59            instance created when you export to <ph conkeyref="vbox-conkeyref-phrases/oci"/>. The options
    6060            enable you to do one of the following:
    6161          </p>
     
    8282        <p>
    8383            Click <b outputclass="bold">Next</b> to make an API
    84             request to the Oracle Cloud Infrastructure service and open the
     84            request to the <ph conkeyref="vbox-conkeyref-phrases/oci"/> service and open the
    8585            <b outputclass="bold">Appliance Settings</b> page.
    8686          </p>
     
    8989        <p>
    9090            (Optional) Edit storage settings used for the exported
    91             virtual machine in Oracle Cloud Infrastructure. You can change the following
     91            virtual machine in <ph conkeyref="vbox-conkeyref-phrases/oci"/>. You can change the following
    9292            settings:
    9393          </p>
     
    100100          <li>
    101101            <p>
    102                 Whether to store the custom image in Oracle Cloud Infrastructure.
     102                Whether to store the custom image in <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
    103103              </p>
    104104          </li>
    105105          <li>
    106106            <p>
    107                 The display name for the custom image in Oracle Cloud Infrastructure.
     107                The display name for the custom image in <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
    108108              </p>
    109109          </li>
     
    114114            <p><b outputclass="bold">Paravirtualized</b> mode
    115115                gives improved performance and should be suitable for
    116                 most Oracle VM VirtualBox VMs.
     116                most <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VMs.
    117117              </p>
    118118            <p><b outputclass="bold">Emulated</b> mode is
     
    136136        <p>
    137137            Click <b outputclass="bold">Finish</b>. The VM is
    138             exported to Oracle Cloud Infrastructure.
     138            exported to <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
    139139          </p>
    140140        <p>
    141141            Depending on the <b outputclass="bold">Machine
    142142            Creation</b> setting, a cloud instance may be started
    143             after upload to Oracle Cloud Infrastructure is completed.
     143            after upload to <ph conkeyref="vbox-conkeyref-phrases/oci"/> is completed.
    144144          </p>
    145145      </li>
    146146      <li>
    147147        <p>
    148             Monitor the export process by using the Oracle Cloud Infrastructure Console.
     148            Monitor the export process by using the <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console.
    149149          </p>
    150150      </li>
    151151    </ol>
    152152    <p>
    153         You can also use the <userinput>VBoxManage export</userinput>
    154         command to export a VM to Oracle Cloud Infrastructure. See
    155         <xref href="vboxmanage-export.dita"/>.
    156       </p>
     153        You can also use the <userinput>VBoxManage export</userinput> command to export a VM to
     154        <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="vboxmanage-export.dita"/>.
     155    </p>
    157156  </body>
    158157</topic>
  • trunk/doc/manual/en_US/dita/topics/cloud-import-oci.dita

    r99497 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="cloud-import-oci">
    4   <title>Importing an Instance from Oracle Cloud Infrastructure</title>
    5  
     4  <title>Importing an Instance from <ph conkeyref="vbox-conkeyref-phrases/oci"/></title>
     5
    66  <body>
    77    <p>
    88        Perform the following steps to import a cloud instance from
    9         Oracle Cloud Infrastructure into Oracle VM VirtualBox:
     9        <ph conkeyref="vbox-conkeyref-phrases/oci"/> into <ph conkeyref="vbox-conkeyref-phrases/product-name"/>:
    1010      </p>
    1111    <ol>
     
    1919        <p>
    2020            In the <b outputclass="bold">Source</b> drop-down
    21             list, select <b outputclass="bold">Oracle Cloud Infrastructure</b>.
     21            list, select <b outputclass="bold"><ph conkeyref="vbox-conkeyref-phrases/oci"/></b>.
    2222          </p>
    2323        <p>
    2424            In the <b outputclass="bold">Profile</b> drop-down
    25             list, select the cloud profile for your Oracle Cloud Infrastructure account.
     25            list, select the cloud profile for your <ph conkeyref="vbox-conkeyref-phrases/oci"/> account.
    2626          </p>
    2727        <p>
     
    3131        <p>
    3232            Click <b outputclass="bold">Next</b> to make an API
    33             request to the Oracle Cloud Infrastructure service and display the
     33            request to the <ph conkeyref="vbox-conkeyref-phrases/oci"/> service and display the
    3434            <b outputclass="bold">Appliance Settings</b> page.
    3535          </p>
     
    5555        <p>
    5656            Click <b outputclass="bold">Finish</b> to import the
    57             instance from Oracle Cloud Infrastructure.
     57            instance from <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
    5858          </p>
    5959      </li>
    6060      <li>
    6161        <p>
    62             Monitor the import process by using the Oracle Cloud Infrastructure Console.
     62            Monitor the import process by using the <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console.
    6363          </p>
    6464      </li>
    6565    </ol>
    6666    <p>
    67         You can also use the <userinput>VBoxManage import</userinput>
    68         command to import an instance from Oracle Cloud Infrastructure. See
    69         <xref href="vboxmanage-import.dita"/>.
    70       </p>
     67        You can also use the <userinput>VBoxManage import</userinput> command to import an instance
     68        from <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="vboxmanage-import.dita"/>.
     69    </p>
    7170  </body>
    7271</topic>
  • trunk/doc/manual/en_US/dita/topics/cloud-integration-steps.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="cloud-integration-steps">
    4   <title>Preparing for Oracle Cloud Infrastructure Integration</title>
     4  <title>Preparing for <ph conkeyref="vbox-conkeyref-phrases/oci"/> Integration</title>
    55 
    66  <body>
    77    <p>
    88        Perform the following configuration steps before using
    9         Oracle VM VirtualBox to integrate with your Oracle Cloud Infrastructure account.
     9        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to integrate with your <ph conkeyref="vbox-conkeyref-phrases/oci"/> account.
    1010      </p>
    1111    <ol>
     
    1313        <p><b outputclass="bold">Install the Extension Pack.</b>
    1414            Cloud integration features are only available when you
    15             install the Oracle VM VirtualBox Extension Pack. See
     15            install the <ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/>. See
    1616            <xref href="intro-installing.dita#intro-installing"/>.
    1717          </p>
     
    2020        <p><b outputclass="bold">Create a key pair.</b> Generate
    2121            an API signing key pair that is used for API requests to
    22             Oracle Cloud Infrastructure. See <xref href="cloud-create-api-keypair.dita#cloud-create-api-keypair"/>.
     22            <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="cloud-create-api-keypair.dita#cloud-create-api-keypair"/>.
    2323          </p>
    2424        <p>
  • trunk/doc/manual/en_US/dita/topics/cloud-integration.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="cloud-integration">
    4   <title>Integrating with Oracle Cloud Infrastructure</title>
     4  <title>Integrating with <ph conkeyref="vbox-conkeyref-phrases/oci"/></title>
    55 
    66  <body>
    77    <p>
    8       This section describes how to use the features of Oracle VM VirtualBox
    9       to integrate with Oracle Cloud Infrastructure.
     8      This section describes how to use the features of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
     9      to integrate with <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
    1010    </p>
    1111    <p>
    12       Integrating with Oracle Cloud Infrastructure involves the following steps:
     12      Integrating with <ph conkeyref="vbox-conkeyref-phrases/oci"/> involves the following steps:
    1313    </p>
    1414    <ul>
    1515      <li>
    16         <p><b outputclass="bold">Prepare for Oracle Cloud Infrastructure
    17           Integration.</b> Before using Oracle VM VirtualBox with Oracle Cloud Infrastructure
     16        <p><b outputclass="bold">Prepare for <ph conkeyref="vbox-conkeyref-phrases/oci"/>
     17          Integration.</b> Before using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with <ph conkeyref="vbox-conkeyref-phrases/oci"/>
    1818          there are some initial configuration steps you may need to do.
    1919          See <xref href="cloud-integration-steps.dita#cloud-integration-steps"/>.
     
    2121      </li>
    2222      <li>
    23         <p><b outputclass="bold">Use Oracle VM VirtualBox with
    24           Oracle Cloud Infrastructure.</b><xref href="cloud-vbox-oci-tasks.dita#cloud-vbox-oci-tasks"/>
    25           describes how you can use Oracle VM VirtualBox with Oracle Cloud Infrastructure.
     23        <p><b outputclass="bold">Use <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with
     24          <ph conkeyref="vbox-conkeyref-phrases/oci"/>.</b><xref href="cloud-vbox-oci-tasks.dita#cloud-vbox-oci-tasks"/>
     25          describes how you can use <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
    2626        </p>
    2727      </li>
  • trunk/doc/manual/en_US/dita/topics/cloud-upload-public-key.dita

    r99182 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="cloud-upload-public-key">
    4   <title>Uploading the Public Key to Oracle Cloud Infrastructure</title>
     4  <title>Uploading the Public Key to <ph conkeyref="vbox-conkeyref-phrases/oci"/></title>
    55 
    66  <body>
    77    <p>
    8         Use the following steps to upload your public key to Oracle Cloud Infrastructure.
     8        Use the following steps to upload your public key to <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
    99      </p>
    1010    <ol>
    1111      <li>
    1212        <p>
    13             Log in to the Oracle Cloud Infrastructure Console.
     13            Log in to the <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console.
    1414          </p>
    1515      </li>
     
    4545          </p>
    4646        <fig id="fig-upload-key-oci">
    47           <title>Upload Public Key Dialog in Oracle Cloud Infrastructure Console</title>
     47          <title>Upload Public Key Dialog in <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console</title>
    4848          <xref href="images/upload-key.png" format="png" platform="htmlhelp">
    4949            <image href="images/upload-key.png" width="12cm" placement="break">
    50               <alt>Upload Public Key Dialog in Oracle Cloud Infrastructure Console</alt>
     50              <alt>Upload Public Key Dialog in <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console</alt>
    5151            </image>
    5252          </xref>
    5353          <image href="images/upload-key.png" width="12cm" placement="break" platform="ohc">
    54             <alt>Upload Public Key Dialog in Oracle Cloud Infrastructure Console</alt>
     54            <alt>Upload Public Key Dialog in <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console</alt>
    5555          </image>
    5656        </fig>
  • trunk/doc/manual/en_US/dita/topics/cloud-using-cli.dita

    r99497 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="cloud-using-cli">
    4   <title>Using VBoxManage Commands With Oracle Cloud Infrastructure</title>
    5  
     4  <title>Using VBoxManage Commands With <ph conkeyref="vbox-conkeyref-phrases/oci"/></title>
     5
    66  <body>
    77    <p>
    88        This section includes some examples of how
    99        <userinput>VBoxManage</userinput> commands can be used to integrate
    10         with Oracle Cloud Infrastructure and perform common cloud operations.
     10        with <ph conkeyref="vbox-conkeyref-phrases/oci"/> and perform common cloud operations.
    1111      </p>
    1212    <p>
     
    2222    <p>
    2323        The new cloud profile is added to the
    24         <filepath>oci_config</filepath> file in your Oracle VM VirtualBox
     24        <filepath>oci_config</filepath> file in your <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    2525        global configuration directory. For example, this is
    2626        <filepath>$HOME/.VirtualBox/oci_config</filepath> on a Windows
     
    3131    </p>
    3232    <p>
    33         To list the instances in your Oracle Cloud Infrastructure compartment:
     33        To list the instances in your <ph conkeyref="vbox-conkeyref-phrases/oci"/> compartment:
    3434      </p>
    3535    <pre xml:space="preserve">VBoxManage cloud --provider="OCI" --profile="vbox-oci" list instances
    3636</pre>
    3737    <p>
    38       <b outputclass="bold">Exporting an Oracle VM VirtualBox VM to the
     38      <b outputclass="bold">Exporting an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VM to the
    3939        Cloud</b>
    4040    </p>
     
    5151    <p>
    5252      <b outputclass="bold">Importing a Cloud Instance Into
    53         Oracle VM VirtualBox</b>
     53        <ph conkeyref="vbox-conkeyref-phrases/product-name"/></b>
    5454    </p>
    5555    <p>
    56         To import a cloud instance and create an Oracle VM VirtualBox VM
     56        To import a cloud instance and create an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VM
    5757        called <codeph>oci_Import</codeph>:
    5858      </p>
     
    6666    </p>
    6767    <p>
    68         To create a new cloud instance from a custom image on Oracle Cloud Infrastructure:
     68        To create a new cloud instance from a custom image on <ph conkeyref="vbox-conkeyref-phrases/oci"/>:
    6969      </p>
    7070    <pre xml:space="preserve">VBoxManage cloud --provider="OCI" --profile="vbox-oci" instance create \
     
    7575    </p>
    7676    <p>
    77         To terminate an instance in your compartment on Oracle Cloud Infrastructure:
     77        To terminate an instance in your compartment on <ph conkeyref="vbox-conkeyref-phrases/oci"/>:
    7878      </p>
    7979    <pre xml:space="preserve">VBoxManage cloud --provider="OCI" --profile="vbox-oci" instance terminate \
    8080--id="ocid1.instance.oc1..." </pre>
    8181    <p>
    82         For more details about the available commands for cloud
    83         operations, see <xref href="vboxmanage-cloud.dita"/>.
    84       </p>
     82        For more details about the available commands for cloud operations, see <xref
     83        href="vboxmanage-cloud.dita"/>.
     84    </p>
    8585  </body>
    86  
     86
    8787</topic>
  • trunk/doc/manual/en_US/dita/topics/cloud-using-cloud-networks.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="cloud-using-cloud-networks">
    44  <title>Using a Cloud Network</title>
    5  
     5
    66  <body>
    77    <p>
    88        A cloud network is a type of network that can be used for
    9         connections from a local VM to a remote Oracle Cloud Infrastructure cloud instance.
     9        connections from a local VM to a remote <ph conkeyref="vbox-conkeyref-phrases/oci"/> cloud instance.
    1010      </p>
    1111    <p>
     
    1515      <li>
    1616        <p>
    17             Set up a virtual cloud network on Oracle Cloud Infrastructure.
     17            Set up a virtual cloud network on <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
    1818          </p>
    1919        <p>
    2020            The following steps create and configure a virtual cloud
    21             network (VCN) on Oracle Cloud Infrastructure. The VCN is used to tunnel network
     21            network (VCN) on <ph conkeyref="vbox-conkeyref-phrases/oci"/>. The VCN is used to tunnel network
    2222            traffic across the cloud.
    2323          </p>
     
    2626            <p>
    2727                Ensure that you have a cloud profile for connecting to
    28                 Oracle Cloud Infrastructure. See <xref href="cloud-create-cloud-profile.dita#cloud-create-cloud-profile"/>.
     28                <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="cloud-create-cloud-profile.dita#cloud-create-cloud-profile"/>.
    2929              </p>
    3030          </li>
     
    4040              </p>
    4141            <p>
    42                 Other options are available for the <userinput>VBoxManage
    43                 cloud network setup</userinput> command, to enable you to
    44                 configure details for the VCN. For example, you can
    45                 configure the operating system used for the cloud
    46                 gateway instance and the IP address range used by the
    47                 tunneling network. See
    48                 <xref href="vboxmanage-cloud.dita"/>.
    49               </p>
     42                Other options are available for the <userinput>VBoxManage cloud network
     43                setup</userinput> command, to enable you to configure details for the VCN. For
     44                example, you can configure the operating system used for the cloud gateway instance
     45                and the IP address range used by the tunneling network. See <xref href="vboxmanage-cloud.dita"/>.
     46            </p>
    5047            <p>
    5148                For best results, use an Oracle Linux 7 instance for the
     
    5754      <li>
    5855        <p>
    59             Register the new cloud network with Oracle VM VirtualBox.
     56            Register the new cloud network with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    6057          </p>
    6158        <p>
     
    7471    </ol>
    7572  </body>
    76  
     73
    7774</topic>
  • trunk/doc/manual/en_US/dita/topics/cloud-using-cloud-profile-manager.dita

    r99182 r99797  
    1313        <b outputclass="bold">File</b>,
    1414        <b outputclass="bold">Cloud Profile Manager</b> in
    15         VirtualBox Manager.
     15        <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.
    1616      </p>
    1717    <fig id="fig-cloud-profile-manager">
     
    3838        <p>
    3939            To create a cloud profile by importing settings from your
    40             Oracle Cloud Infrastructure configuration file.
     40            <ph conkeyref="vbox-conkeyref-phrases/oci"/> configuration file.
    4141          </p>
    4242      </li>
     
    9292        </ul>
    9393        <p>
    94             Some of these are settings for your Oracle Cloud Infrastructure account, which you
    95             can view from the Oracle Cloud Infrastructure Console.
     94            Some of these are settings for your <ph conkeyref="vbox-conkeyref-phrases/oci"/> account, which you
     95            can view from the <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console.
    9696          </p>
    9797      </li>
     
    104104        <p>
    105105            This creates a new subgroup of the
    106             <b outputclass="bold">OCI</b> group in VirtualBox Manager.
     106            <b outputclass="bold">OCI</b> group in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.
    107107            See <xref href="cloud-vm-oci-group.dita#cloud-vm-oci-group"/>.
    108108          </p>
     
    115115        <p>
    116116            The cloud profile settings are saved to the
    117             <filepath>oci_config</filepath> file in your Oracle VM VirtualBox
     117            <filepath>oci_config</filepath> file in your <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    118118            global settings directory.
    119119          </p>
     
    121121    </ol>
    122122    <p>
    123         Perform the following steps to import an existing Oracle Cloud Infrastructure
     123        Perform the following steps to import an existing <ph conkeyref="vbox-conkeyref-phrases/oci"/>
    124124        configuration file into the Cloud Profile Manager:
    125125      </p>
     
    128128        <p>
    129129            Ensure that a <filepath>config</filepath> file is present in
    130             your Oracle Cloud Infrastructure configuration directory. For example, this is
     130            your <ph conkeyref="vbox-conkeyref-phrases/oci"/> configuration directory. For example, this is
    131131            <filepath>$HOME/.oci/config</filepath> on a Linux host.
    132132          </p>
     
    141141          <p>
    142142              This action overwrites any cloud profiles that are in your
    143               Oracle VM VirtualBox global settings directory.
     143              <ph conkeyref="vbox-conkeyref-phrases/product-name"/> global settings directory.
    144144            </p>
    145145        </note>
     
    151151        <p>
    152152            Your cloud profile settings are saved to the
    153             <filepath>oci_config</filepath> file in your Oracle VM VirtualBox
     153            <filepath>oci_config</filepath> file in your <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    154154            global settings directory.
    155155          </p>
  • trunk/doc/manual/en_US/dita/topics/cloud-vbox-oci-tasks.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="cloud-vbox-oci-tasks">
    4   <title>Using Oracle VM VirtualBox With Oracle Cloud Infrastructure</title>
     4  <title>Using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> With <ph conkeyref="vbox-conkeyref-phrases/oci"/></title>
    55 
    66  <body>
    77    <p>
    8         This section describes how you can use Oracle VM VirtualBox with Oracle Cloud Infrastructure
     8        This section describes how you can use <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with <ph conkeyref="vbox-conkeyref-phrases/oci"/>
    99        to do the following tasks:
    1010      </p>
     
    1212      <li>
    1313        <p>
    14             Create, add, and manage Oracle Cloud Infrastructure cloud instances using
    15             VirtualBox Manager. See <xref href="cloud-vm.dita#cloud-vm"/>.
     14            Create, add, and manage <ph conkeyref="vbox-conkeyref-phrases/oci"/> cloud instances using
     15            <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. See <xref href="cloud-vm.dita#cloud-vm"/>.
    1616          </p>
    1717      </li>
    1818      <li>
    1919        <p>
    20             Export an Oracle VM VirtualBox VM to Oracle Cloud Infrastructure. See
     20            Export an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VM to <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See
    2121            <xref href="cloud-export-oci.dita#cloud-export-oci"/>.
    2222          </p>
     
    2424      <li>
    2525        <p>
    26             Import a cloud instance into Oracle VM VirtualBox. See
     26            Import a cloud instance into <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. See
    2727            <xref href="cloud-import-oci.dita#cloud-import-oci"/>.
    2828          </p>
     
    3030      <li>
    3131        <p>
    32             Connect from a local VM to an Oracle Cloud Infrastructure cloud subnet. See
     32            Connect from a local VM to an <ph conkeyref="vbox-conkeyref-phrases/oci"/> cloud subnet. See
    3333            <xref href="cloud-using-cloud-networks.dita#cloud-using-cloud-networks"/>.
    3434          </p>
     
    3737        <p>
    3838            Use the <userinput>VBoxManage</userinput> commands to integrate
    39             with Oracle Cloud Infrastructure and perform cloud operations. See
     39            with <ph conkeyref="vbox-conkeyref-phrases/oci"/> and perform cloud operations. See
    4040            <xref href="cloud-using-cli.dita#cloud-using-cli"/>.
    4141          </p>
  • trunk/doc/manual/en_US/dita/topics/cloud-vm-add.dita

    r99182 r99797  
    77    <p>
    88          When you add a cloud VM, an <i>existing</i>
    9           Oracle Cloud Infrastructure instance is associated with the cloud VM. You can only
     9          <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance is associated with the cloud VM. You can only
    1010          add one cloud VM for each instance.
    1111        </p>
     
    5454                  service provider that hosts the instance used for the
    5555                  cloud VM. Select
    56                   <b outputclass="bold">Oracle Cloud Infrastructure</b>.
     56                  <b outputclass="bold"><ph conkeyref="vbox-conkeyref-phrases/oci"/></b>.
    5757                </p>
    5858          </li>
     
    7979              A cloud VM with the same name as the instance is added to
    8080              the <b outputclass="bold">OCI</b> group in
    81               VirtualBox Manager.
     81              <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.
    8282            </p>
    8383      </li>
     
    8989            </p>
    9090        <p>
    91               The cloud VM name in VirtualBox Manager is updated automatically.
     91              The cloud VM name in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> is updated automatically.
    9292            </p>
    9393      </li>
  • trunk/doc/manual/en_US/dita/topics/cloud-vm-control.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8           You can use VirtualBox Manager to control a cloud VM as follows:
     8          You can use <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> to control a cloud VM as follows:
    99        </p>
    1010    <ul>
     
    1212        <p><b outputclass="bold">Start.</b> Use the
    1313              <b outputclass="bold">Start</b> button in the
    14               VirtualBox Manager toolbar.
     14              <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> toolbar.
    1515            </p>
    1616      </li>
     
    2525        <p><b outputclass="bold">Terminate.</b> Use the
    2626              <b outputclass="bold">Terminate</b> button in the
    27               VirtualBox Manager toolbar.
     27              <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> toolbar.
    2828            </p>
    2929        <note type="caution">
    3030          <p>
    31                 This action deletes the instance from Oracle Cloud Infrastructure.
     31                This action deletes the instance from <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
    3232              </p>
    3333        </note>
     
    3535    </ul>
    3636    <p>
    37           When you control a cloud VM in VirtualBox Manager the machine list is
     37          When you control a cloud VM in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> the machine list is
    3838          updated automatically with the current instance state, such as
    3939          <b outputclass="bold">Stopped</b> or
     
    4141        </p>
    4242    <p>
    43           When you control an instance using the Oracle Cloud Infrastructure console,
    44           VirtualBox Manager updates the status for the corresponding cloud VM
     43          When you control an instance using the <ph conkeyref="vbox-conkeyref-phrases/oci"/> console,
     44          <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> updates the status for the corresponding cloud VM
    4545          automatically.
    4646        </p>
  • trunk/doc/manual/en_US/dita/topics/cloud-vm-instance-console.dita

    r98549 r99797  
    4646    </ol>
    4747    <p>
    48           See the Oracle Cloud Infrastructure documentation for details about how you can use
     48          See the <ph conkeyref="vbox-conkeyref-phrases/oci"/> documentation for details about how you can use
    4949          an instance console connection to troubleshoot instance
    5050          problems.
  • trunk/doc/manual/en_US/dita/topics/cloud-vm-new.dita

    r99182 r99797  
    77    <p>
    88          When you create a new cloud VM, a <i>new</i>
    9           Oracle Cloud Infrastructure instance is created and associated with the cloud VM.
     9          <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance is created and associated with the cloud VM.
    1010        </p>
    1111    <p>
     
    5353            <p><b outputclass="bold">Location:</b> The cloud
    5454                  service provider that will host the new instance.
    55                   Select <b outputclass="bold">Oracle Cloud Infrastructure</b>.
     55                  Select <b outputclass="bold"><ph conkeyref="vbox-conkeyref-phrases/oci"/></b>.
    5656                </p>
    5757          </li>
     
    7878        <p>
    7979              You can use this page to change the default settings for
    80               the new Oracle Cloud Infrastructure instance, such as the display name, shape,
     80              the new <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance, such as the display name, shape,
    8181              and networking configuration.
    8282            </p>
     
    9090        <p>
    9191              Click <b outputclass="bold">Finish</b> to create a
    92               new Oracle Cloud Infrastructure instance using the selected image or boot
     92              new <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance using the selected image or boot
    9393              volume. The new instance is started automatically.
    9494            </p>
    9595        <p>
    9696              The new cloud VM is shown in the
    97               <b outputclass="bold">OCI</b> group in VirtualBox Manager.
     97              <b outputclass="bold">OCI</b> group in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.
    9898            </p>
    9999      </li>
  • trunk/doc/manual/en_US/dita/topics/cloud-vm-oci-group.dita

    r99182 r99797  
    66  <body>
    77    <p>
    8           All cloud VMs are shown in the machine list in VirtualBox Manager, in
     8          All cloud VMs are shown in the machine list in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, in
    99          a special VM group called
    1010          <b outputclass="bold">OCI</b>.
     
    2929    </fig>
    3030    <p>
    31           All cloud profiles registered with Oracle VM VirtualBox are listed
     31          All cloud profiles registered with <ph conkeyref="vbox-conkeyref-phrases/product-name"/> are listed
    3232          automatically in the OCI group.
    3333        </p>
    3434    <p>
    35           To enable or disable listing of cloud VMs in VirtualBox Manager for a
     35          To enable or disable listing of cloud VMs in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> for a
    3636          specific cloud profile, do the following:
    3737        </p>
  • trunk/doc/manual/en_US/dita/topics/cloud-vm-remove.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8           You can use VirtualBox Manager to remove a cloud VM as follows:
     8          You can use <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> to remove a cloud VM as follows:
    99        </p>
    1010    <p>
     
    2323        <p>
    2424              Click <b outputclass="bold">Delete Everything</b>
    25               to remove the cloud VM from VirtualBox Manager and also to delete
    26               the Oracle Cloud Infrastructure instance and any associated boot volumes.
     25              to remove the cloud VM from <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> and also to delete
     26              the <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance and any associated boot volumes.
    2727            </p>
    2828      </li>
  • trunk/doc/manual/en_US/dita/topics/cloud-vm-settings.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8           Select the cloud VM in VirtualBox Manager and click
     8          Select the cloud VM in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> and click
    99          <b outputclass="bold">Settings</b>.
    1010        </p>
     
    1313        <p>
    1414              For a <i>new</i> cloud VM, you can change
    15               many settings for the Oracle Cloud Infrastructure instance, such as the display
     15              many settings for the <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance, such as the display
    1616              name, shape, and disk size.
    1717            </p>
     
    2020        <p>
    2121              When you <i>add</i> a cloud VM based on an
    22               existing Oracle Cloud Infrastructure instance you can only change the display
     22              existing <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance you can only change the display
    2323              name.
    2424            </p>
  • trunk/doc/manual/en_US/dita/topics/cloud-vm.dita

    r99182 r99797  
    88        A cloud virtual machine (<i>cloud VM</i>) is a
    99        type of VM that represents an instance on a cloud service. Cloud
    10         VMs are shown in the machine list in VirtualBox Manager, in the same way
     10        VMs are shown in the machine list in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, in the same way
    1111        as local VMs are.
    1212      </p>
    1313    <p>
    1414        By using cloud VMs you can create, manage, and control your
    15         Oracle Cloud Infrastructure instances from VirtualBox Manager.
     15        <ph conkeyref="vbox-conkeyref-phrases/oci"/> instances from <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.
    1616      </p>
    1717    <note>
    1818      <p>
    1919          Cloud VMs do not install, export, or import instances to the
    20           Oracle VM VirtualBox host. All operations are done remotely on the
     20          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> host. All operations are done remotely on the
    2121          cloud service.
    2222        </p>
    2323    </note>
    2424    <fig id="fig-cloud-vm-overview">
    25       <title>Cloud VMs, Shown in VirtualBox Manager</title>
     25      <title>Cloud VMs, Shown in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/></title>
    2626      <xref href="images/cloudvm-overview.png" format="png" platform="htmlhelp">
    2727        <image href="images/cloudvm-overview.png" width="12cm" placement="break">
    28           <alt>Cloud VMs, Shown in VirtualBox Manager</alt>
     28          <alt>Cloud VMs, Shown in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/></alt>
    2929        </image>
    3030      </xref>
    3131      <image platform="ohc" href="images/cloudvm-overview.png" width="12cm" placement="break">
    32         <alt>Cloud VMs, Shown in VirtualBox Manager</alt>
     32        <alt>Cloud VMs, Shown in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/></alt>
    3333      </image>
    3434    </fig>
    3535    <p>
    36         Cloud VMs can be used to do the following tasks in Oracle Cloud Infrastructure:
     36        Cloud VMs can be used to do the following tasks in <ph conkeyref="vbox-conkeyref-phrases/oci"/>:
    3737      </p>
    3838    <ul>
    3939      <li>
    40         <p><b outputclass="bold">Create a new Oracle Cloud Infrastructure
     40        <p><b outputclass="bold">Create a new <ph conkeyref="vbox-conkeyref-phrases/oci"/>
    4141            instance.</b> See <xref href="cloud-vm-new.dita#cloud-vm-new"/>.
    4242          </p>
    4343      </li>
    4444      <li>
    45         <p><b outputclass="bold"> Use an existing Oracle Cloud Infrastructure
     45        <p><b outputclass="bold"> Use an existing <ph conkeyref="vbox-conkeyref-phrases/oci"/>
    4646            instance.</b> See <xref href="cloud-vm-add.dita#cloud-vm-add"/>.
    4747          </p>
    4848      </li>
    4949      <li>
    50         <p><b outputclass="bold">Configure an Oracle Cloud Infrastructure
     50        <p><b outputclass="bold">Configure an <ph conkeyref="vbox-conkeyref-phrases/oci"/>
    5151            instance.</b> You can change settings for the
    5252            instance, such as display name and shape. See
     
    5555      </li>
    5656      <li>
    57         <p><b outputclass="bold">Control an Oracle Cloud Infrastructure instance.</b>
     57        <p><b outputclass="bold">Control an <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance.</b>
    5858            Stop, start, and terminate the instance. See
    5959            <xref href="cloud-vm-control.dita#cloud-vm-control"/>
     
    6262      <li>
    6363        <p><b outputclass="bold">Create a console connection to an
    64             Oracle Cloud Infrastructure instance</b>. See
     64            <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance</b>. See
    6565            <xref href="cloud-vm-instance-console.dita#cloud-vm-instance-console"/>.
    6666          </p>
  • trunk/doc/manual/en_US/dita/topics/collect-debug-info.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="collect-debug-info">
    44  <title>Collecting Debugging Information</title>
    5  
     5
    66  <body>
    77    <p>
    88        For problem determination, it is often important to collect
    9         debugging information which can be analyzed by Oracle VM VirtualBox
     9        debugging information which can be analyzed by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    1010        support. This section contains information about what kind of
    1111        information can be obtained.
    1212      </p>
    1313    <p>
    14         Every time Oracle VM VirtualBox starts up a VM, a so-called
     14        Every time <ph conkeyref="vbox-conkeyref-phrases/product-name"/> starts up a VM, a so-called
    1515        <i>release log file</i> is created, containing
    1616        lots of information about the VM configuration and runtime
     
    2626        <filepath>.3</filepath>. Sometimes when there is a problem, it
    2727        is useful to have a look at the logs. Also when requesting
    28         support for Oracle VM VirtualBox, supplying the corresponding log file
     28        support for <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, supplying the corresponding log file
    2929        is mandatory.
    3030      </p>
    3131    <p>
    32         For convenience, for each virtual machine, VirtualBox Manager can show
     32        For convenience, for each virtual machine, <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> can show
    3333        these logs in a window. Select a virtual machine from the
    3434        machine list on the left and click
     
    3838        The release log file, <filepath>VBox.log</filepath>, contains a
    3939        wealth of diagnostic information, such as Host OS type and
    40         version, Oracle VM VirtualBox version and build. It also includes a
     40        version, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> version and build. It also includes a
    4141        complete dump of the guest's configuration (CFGM), detailed
    4242        information about the host CPU type and supported features,
     
    5252        guest crashes. For information about enabling core dumps on
    5353        Linux, Oracle Solaris, and macOS systems, refer to the following
    54         core dump article on the Oracle VM VirtualBox website:
     54        core dump article on the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> website:
    5555      </p>
    5656    <p><ph>http://www.virtualbox.org/wiki/Core_dump</ph>.
    5757      </p>
    5858    <p>
    59         You can also use <userinput>VBoxManage debugvm</userinput> to create
    60         a dump of a complete virtual machine. See
    61         <xref href="vboxmanage-debugvm.dita">VBoxManage debugvm</xref>.
    62       </p>
     59        You can also use <userinput>VBoxManage debugvm</userinput> to create a dump of a complete
     60        virtual machine. See <xref href="vboxmanage-debugvm.dita">VBoxManage debugvm</xref>.
     61    </p>
    6362    <p>
    6463        For network related problems, it is often helpful to capture a
     
    6968      </p>
    7069    <p>
    71         Oracle VM VirtualBox provides an ability to capture network traffic
     70        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides an ability to capture network traffic
    7271        only on a specific VM's network adapter. Refer to the following
    73         network tracing article on the Oracle VM VirtualBox website for
     72        network tracing article on the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> website for
    7473        information on enabling this capture:
    7574      </p>
     
    7776      </p>
    7877    <p>
    79         The trace files created by Oracle VM VirtualBox are in
     78        The trace files created by <ph conkeyref="vbox-conkeyref-phrases/product-name"/> are in
    8079        <filepath>.pcap</filepath> format and can be easily analyzed
    8180        with Wireshark.
    8281      </p>
    8382  </body>
    84  
     83
    8584</topic>
  • trunk/doc/manual/en_US/dita/topics/configbasics.dita

    r98549 r99797  
    3232    </note>
    3333    <p>
    34       Oracle VM VirtualBox provides a wide range of parameters that can be
     34      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides a wide range of parameters that can be
    3535      changed for a virtual machine. The various settings that can be
    3636      changed in the <b outputclass="bold">Settings</b> window
  • trunk/doc/manual/en_US/dita/topics/cpuhotplug.dita

    r99497 r99797  
    77    <p>
    88      With virtual machines running modern server operating systems,
    9       Oracle VM VirtualBox supports CPU hot-plugging.
     9      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports CPU hot-plugging.
    1010    </p>
    1111    <p>
    1212      On a physical computer CPU hot-plugging would mean that a CPU can
    13       be added or removed while the machine is running. Oracle VM VirtualBox
     13      be added or removed while the machine is running. <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    1414      supports adding and removing of virtual CPUs while a virtual
    1515      machine is running.
  • trunk/doc/manual/en_US/dita/topics/create-vm-wizard-hardware.dita

    r99182 r99797  
    2626      <li>
    2727        <p><b outputclass="bold">Base Memory.</b> Select the
    28             amount of RAM that Oracle VM VirtualBox should allocate every time
     28            amount of RAM that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> should allocate every time
    2929            the virtual machine is started. The amount of memory
    3030            selected here will be taken away from your host machine and
  • trunk/doc/manual/en_US/dita/topics/create-vm-wizard-name-os.dita

    r99182 r99797  
    3333        <p><b outputclass="bold">Name.</b> A name for the new
    3434            VM. The name you enter is shown in the machine list of
    35             VirtualBox Manager and is also used for the virtual machine's files
     35            <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> and is also used for the virtual machine's files
    3636            on disk.
    3737          </p>
     
    7070            install something very unusual that is not listed, select
    7171            the <b outputclass="bold">Other</b> type. Depending
    72             on your selection, Oracle VM VirtualBox will enable or disable
     72            on your selection, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will enable or disable
    7373            certain VM settings that your guest OS may require. This is
    7474            particularly important for 64-bit guests. See
     
    7777          </p>
    7878        <p>
    79             If an ISO image is selected and Oracle VM VirtualBox detects the
     79            If an ISO image is selected and <ph conkeyref="vbox-conkeyref-phrases/product-name"/> detects the
    8080            operating system for the ISO, the
    8181            <b outputclass="bold">Type</b> and
  • trunk/doc/manual/en_US/dita/topics/create-vm-wizard-summary.dita

    r98549 r99797  
    1717        Click <b outputclass="bold">Finish</b> to create your new
    1818        virtual machine. The virtual machine is displayed in the machine
    19         list on the left side of the VirtualBox Manager window, with the name
     19        list on the left side of the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> window, with the name
    2020        that you entered on the first page of the wizard.
    2121      </p>
  • trunk/doc/manual/en_US/dita/topics/create-vm-wizard-unattended-examples.dita

    r98549 r99797  
    88        To configure unattended installation, you typically just need to
    99        specify an ISO image in the <b outputclass="bold">Create Virtual
    10         Machine</b> wizard. Oracle VM VirtualBox then detects the OS
     10        Machine</b> wizard. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> then detects the OS
    1111        type and the unattended installation process is done
    1212        automatically when the wizard is completed. However, in some
  • trunk/doc/manual/en_US/dita/topics/create-vm-wizard-unattended-install.dita

    r99182 r99797  
    1919        Use this page to set up the required parameters for unattended
    2020        guest OS installation and to configure automatic installation of
    21         the Oracle VM VirtualBox Guest Additions. See also
     21        the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions. See also
    2222        <xref href="create-vm-wizard-unattended-examples.dita#create-vm-wizard-unattended-examples"/> for some
    2323        typical scenarios when using automated installation.
  • trunk/doc/manual/en_US/dita/topics/create-vm-wizard-virtual-hard-disk.dita

    r99497 r99797  
    1010      </p>
    1111    <p>
    12         There are many ways in which Oracle VM VirtualBox can provide hard
     12        There are many ways in which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can provide hard
    1313        disk space to a VM, see <xref href="storage.dita#storage"/>. The most
    1414        common way is to use a large image file on your physical hard
    15         disk, whose contents Oracle VM VirtualBox presents to your VM as if it
     15        disk, whose contents <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents to your VM as if it
    1616        were a complete hard disk. This file then represents an entire
    1717        hard disk, so you can even copy it to another host and use it
    18         with another Oracle VM VirtualBox installation.
     18        with another <ph conkeyref="vbox-conkeyref-phrases/product-name"/> installation.
    1919      </p>
    2020    <fig id="fig-create-vm-hard-disk">
     
    9595        <p>
    9696            The drop-down list presented in the window lists all disk
    97             images which are known by Oracle VM VirtualBox. These disk images
     97            images which are known by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. These disk images
    9898            are currently attached to a virtual machine, or have been
    9999            attached to a virtual machine.
     
    115115    <p>
    116116        To prevent your physical hard disk on the host OS from filling
    117         up, Oracle VM VirtualBox limits the size of the image file. But the
     117        up, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> limits the size of the image file. But the
    118118        image file must be large enough to hold the contents of the
    119119        guest OS and the applications you want to install. For a Windows
  • trunk/doc/manual/en_US/dita/topics/customize-vm-manager.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="customize-vm-manager">
    4   <title>Customizing VirtualBox Manager</title>
     4  <title>Customizing <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/></title>
    55 
    66  <body>
    77    <p>
    88        There are several advanced customization settings for locking
    9         down VirtualBox Manager. Locking down means removing some features that
     9        down <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. Locking down means removing some features that
    1010        the user should not see.
    1111      </p>
     
    2121        <dd>
    2222          <p>
    23               Do not allow users to start VirtualBox Manager. Trying to do so
     23              Do not allow users to start <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. Trying to do so
    2424              will show a window containing a proper error message.
    2525            </p>
     
    4848    </dl>
    4949    <p>
    50         To disable any of these VirtualBox Manager customizations use the
     50        To disable any of these <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> customizations use the
    5151        following command:
    5252      </p>
  • trunk/doc/manual/en_US/dita/topics/customvesa.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         Apart from the standard VESA resolutions, the Oracle VM VirtualBox
     8        Apart from the standard VESA resolutions, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    99        VESA BIOS enables you to add up to 16 custom video modes which
    1010        will be reported to the guest operating system. When using
    11         Windows guests with the Oracle VM VirtualBox Guest Additions, a custom
     11        Windows guests with the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions, a custom
    1212        graphics driver will be used instead of the fallback VESA
    1313        solution so this information does not apply.
     
    3434vga = 864</pre>
    3535    <p>
    36         For guest operating systems with Oracle VM VirtualBox Guest Additions,
     36        For guest operating systems with <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions,
    3737        a custom video mode can be set using the video mode hint
    3838        feature.
  • trunk/doc/manual/en_US/dita/topics/diffimages.dita

    r99182 r99797  
    2626      When the machine reads a sector from such a virtual hard disk, it
    2727      looks into the differencing image first. If the sector is present,
    28       it is returned from there. If not, Oracle VM VirtualBox looks into the
     28      it is returned from there. If not, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> looks into the
    2929      parent. In other words, the parent becomes
    3030      <i>read-only</i>. It is never written to again, but
     
    3838      read-only as well, and write operations only go to the
    3939      second-level differencing image. When reading from the virtual
    40       disk, Oracle VM VirtualBox needs to look into the second differencing
     40      disk, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> needs to look into the second differencing
    4141      image first, then into the first if the sector was not found, and
    4242      then into the original image.
     
    4949      Write operations always go to the one <i>active</i>
    5050      differencing image that is attached to the machine, and for read
    51       operations, Oracle VM VirtualBox may need to look up all the parents in
     51      operations, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> may need to look up all the parents in
    5252      the chain until the sector in question is found. You can view such
    5353      a tree in the Virtual Media Manager.
     
    6868      machine, the virtual hard disk behaves like any other disk. While
    6969      the virtual machine is running, there is a slight run-time I/O
    70       overhead because Oracle VM VirtualBox might need to look up sectors
     70      overhead because <ph conkeyref="vbox-conkeyref-phrases/product-name"/> might need to look up sectors
    7171      several times. This is not noticeable however since the tables
    7272      with sector information are always kept in memory and can be
     
    7979      <li>
    8080        <p><b outputclass="bold">Snapshots.</b> When you create a
    81           snapshot, as explained in the previous section, Oracle VM VirtualBox
     81          snapshot, as explained in the previous section, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    8282          <i>freezes</i> the images attached to the
    8383          virtual machine and creates differencing images for each image
     
    102102          <li>
    103103            <p>
    104               Oracle VM VirtualBox copies the virtual machine settings that
     104              <ph conkeyref="vbox-conkeyref-phrases/product-name"/> copies the virtual machine settings that
    105105              were copied into the snapshot back to the virtual machine.
    106106              As a result, if you have made changes to the machine
     
    136136          differencing images becomes obsolete. In this case, the
    137137          differencing image of the disk attachment cannot simply be
    138           deleted. Instead, Oracle VM VirtualBox needs to look at each sector
     138          deleted. Instead, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> needs to look at each sector
    139139          of the differencing image and needs to copy it back into its
    140140          parent. This is called "merging" images and can be a
  • trunk/doc/manual/en_US/dita/topics/disabletimesync.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         Once installed and started, the Oracle VM VirtualBox Guest Additions
     8        Once installed and started, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions
    99        will try to synchronize the guest time with the host time. This
    1010        can be prevented by forbidding the guest service from reading
  • trunk/doc/manual/en_US/dita/topics/diskencryption-decryption.dita

    r98549 r99797  
    77    <p>
    88        In some circumstances it might be required to decrypt previously
    9         encrypted images. This can be done in VirtualBox Manager for a complete
     9        encrypted images. This can be done in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> for a complete
    1010        VM or using <userinput>VBoxManage</userinput> with the following
    1111        command:
  • trunk/doc/manual/en_US/dita/topics/diskencryption-encryption.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         Encrypting disk images can be done either using VirtualBox Manager or
    9         the <userinput>VBoxManage</userinput>. While VirtualBox Manager is easier to
     8        Encrypting disk images can be done either using <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> or
     9        the <userinput>VBoxManage</userinput>. While <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> is easier to
    1010        use, it works on a per VM basis and encrypts all disk images
    1111        attached to the specific VM. With <userinput>VBoxManage</userinput>
  • trunk/doc/manual/en_US/dita/topics/diskencryption-limitations.dita

    r98549 r99797  
    1212      <li>
    1313        <p>
    14             This feature is part of the Oracle VM VirtualBox Extension Pack,
     14            This feature is part of the <ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/>,
    1515            which needs to be installed. Otherwise disk encryption is
    1616            unavailable.
     
    4545        <p>
    4646            When encrypting or decrypting the images, the password is
    47             passed in clear text using the Oracle VM VirtualBox API. This
     47            passed in clear text using the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> API. This
    4848            needs to be kept in mind, especially when using third party
    4949            API clients which make use of the webservice where the
     
    5656            Encrypting images with differencing images is only possible
    5757            if there are no snapshots or a linear chain of snapshots.
    58             This limitation may be addressed in a future Oracle VM VirtualBox
     58            This limitation may be addressed in a future <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    5959            version.
    6060          </p>
  • trunk/doc/manual/en_US/dita/topics/diskencryption-startvm.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         When a VM is started using VirtualBox Manager, a dialog will open where
     8        When a VM is started using <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, a dialog will open where
    99        the user needs to enter all passwords for all encrypted images
    1010        attached to the VM. If another frontend like VBoxHeadless is
  • trunk/doc/manual/en_US/dita/topics/diskencryption.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox enables you to transparently encrypt the data
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to transparently encrypt the data
    99      stored in hard disk images for the guest. It does not depend on a
    1010      specific image format to be used. Images which have the data
    11       encrypted are not portable between Oracle VM VirtualBox and other
     11      encrypted are not portable between <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and other
    1212      virtualization software.
    1313    </p>
    1414    <p>
    15       Oracle VM VirtualBox uses the AES algorithm in XTS mode and supports
     15      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses the AES algorithm in XTS mode and supports
    1616      128-bit or 256-bit data encryption keys (DEK). The DEK is stored
    1717      encrypted in the medium properties and is decrypted during VM
  • trunk/doc/manual/en_US/dita/topics/efi.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox includes experimental support for the Extensible
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> includes experimental support for the Extensible
    99      Firmware Interface (EFI), which is an industry standard intended
    1010      to replace the legacy BIOS as the primary interface for
     
    1212    </p>
    1313    <p>
    14       By default, Oracle VM VirtualBox uses the BIOS firmware for virtual
     14      By default, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses the BIOS firmware for virtual
    1515      machines. To use EFI for a given virtual machine, you can enable
    1616      EFI in the machine's <b outputclass="bold">Settings</b>
     
    3030    </p>
    3131    <p>
    32       Another possible use of EFI in Oracle VM VirtualBox is development and
     32      Another possible use of EFI in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is development and
    3333      testing of EFI applications, without booting any OS.
    3434    </p>
    3535    <p>
    36       Note that the Oracle VM VirtualBox EFI support is experimental and will
     36      Note that the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> EFI support is experimental and will
    3737      be enhanced as EFI matures and becomes more widespread. Mac OS X,
    3838      Linux, and newer Windows guests are known to work fine. Windows 7
    39       guests are unable to boot with the Oracle VM VirtualBox EFI
     39      guests are unable to boot with the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> EFI
    4040      implementation.
    4141    </p>
  • trunk/doc/manual/en_US/dita/topics/efividmode.dita

    r98549 r99797  
    99        Protocol) and UGA (Universal Graphics Adapter). Modern OSes,
    1010        such as Mac OS X, generally use GOP, while some older ones still
    11         use UGA. Oracle VM VirtualBox provides a configuration option to
     11        use UGA. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides a configuration option to
    1212        control the graphics resolution for both interfaces, making the
    1313        difference mostly irrelevant for users.
  • trunk/doc/manual/en_US/dita/topics/emul-hardware.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox virtualizes nearly all hardware of the host.
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> virtualizes nearly all hardware of the host.
    99      Depending on a VM's configuration, the guest will see the
    1010      following virtual hardware:
     
    1212    <ul>
    1313      <li>
    14         <p><b outputclass="bold">Input devices.</b> Oracle VM VirtualBox
     14        <p><b outputclass="bold">Input devices.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    1515          can emulate a standard PS/2 keyboard and mouse. These devices
    1616          are supported by most guest OSes.
    1717        </p>
    1818        <p>
    19           In addition, Oracle VM VirtualBox can provide virtual USB input
     19          In addition, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can provide virtual USB input
    2020          devices to avoid having to capture mouse and keyboard, as
    2121          described in <xref href="keyb_mouse_normal.dita#keyb_mouse_normal"/>.
     
    2424      <li>
    2525        <p><b outputclass="bold">Graphics.</b> The default
    26           Oracle VM VirtualBox graphics device for Windows guests is an SVGA
     26          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> graphics device for Windows guests is an SVGA
    2727          device. For Linux guests, the default graphics device emulates
    2828          a VMware SVGA graphics device. See
     
    3535      </li>
    3636      <li>
    37         <p><b outputclass="bold">Storage.</b> Oracle VM VirtualBox
     37        <p><b outputclass="bold">Storage.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    3838          emulates the most common types of hard disk controllers. See
    3939          <xref href="harddiskcontrollers.dita#harddiskcontrollers"/>. Whereas supporting
    4040          only one of these controllers would be enough for
    41           Oracle VM VirtualBox by itself, this multitude of storage adapters
     41          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> by itself, this multitude of storage adapters
    4242          is required for compatibility with other hypervisors. Windows
    4343          is very selective about its boot devices, and migrating VMs
     
    5252      </li>
    5353      <li>
    54         <p><b outputclass="bold">USB.</b> Oracle VM VirtualBox emulates
     54        <p><b outputclass="bold">USB.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> emulates
    5555          these types of USB host controllers: xHCI, EHCI, and OHCI.
    5656          While xHCI handles all USB transfer speeds, some legacy guest
  • trunk/doc/manual/en_US/dita/topics/externalkernelmodules.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="externalkernelmodules">
    4   <title>The Oracle VM VirtualBox Kernel Modules</title>
     4  <title>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Kernel Modules</title>
    55 
    66  <body>
    77    <p>
    88        In order to run other operating systems in virtual machines
    9         alongside your main operating system, Oracle VM VirtualBox needs to
     9        alongside your main operating system, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> needs to
    1010        integrate very tightly with your system. To do this it installs
    1111        a driver module called <userinput>vboxdrv</userinput> into the
    1212        system kernel. The kernel is the part of the operating system
    1313        which controls your processor and physical hardware. Without
    14         this kernel module, you can still use VirtualBox Manager to configure
     14        this kernel module, you can still use <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> to configure
    1515        virtual machines, but they will not start.
    1616      </p>
     
    2424    <p>
    2525        Since distributing driver modules separately from the kernel is
    26         not something which Linux supports well, the Oracle VM VirtualBox
     26        not something which Linux supports well, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    2727        install process creates the modules on the system where they
    2828        will be used. This means that you may need to install some
  • trunk/doc/manual/en_US/dita/topics/features-overview.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       The following is a brief outline of Oracle VM VirtualBox's main
     8      The following is a brief outline of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s main
    99      features:
    1010    </p>
    1111    <ul>
    1212      <li>
    13         <p><b outputclass="bold">Portability.</b> Oracle VM VirtualBox
     13        <p><b outputclass="bold">Portability.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    1414          runs on a large number of 64-bit host operating systems. See
    1515          <xref href="hostossupport.dita#hostossupport"/>.
    1616        </p>
    1717        <p>
    18           Oracle VM VirtualBox is a so-called <i>hosted</i>
     18          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is a so-called <i>hosted</i>
    1919          hypervisor, sometimes referred to as a <i>type
    2020          2</i> hypervisor. Whereas a
    2121          <i>bare-metal</i> or <i>type 1</i>
    22           hypervisor runs directly on the hardware, Oracle VM VirtualBox
     22          hypervisor runs directly on the hardware, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    2323          requires an existing OS to be installed. It can thus run
    2424          alongside existing applications on that host.
    2525        </p>
    2626        <p>
    27           To a very large degree, Oracle VM VirtualBox is functionally
     27          To a very large degree, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is functionally
    2828          identical on all of the host platforms, and the same file and
    2929          image formats are used. This enables you to run virtual
     
    4040        </p>
    4141        <p>
    42           For users of Oracle Cloud Infrastructure the functionality extends to exporting and
     42          For users of <ph conkeyref="vbox-conkeyref-phrases/oci"/> the functionality extends to exporting and
    4343          importing virtual machines to and from the cloud. This
    4444          simplifies development of applications and deployment to the
     
    5050        <p><b outputclass="bold">Guest Additions: shared folders,
    5151          seamless windows, 3D virtualization.</b> The
    52           Oracle VM VirtualBox Guest Additions are software packages which can
     52          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions are software packages which can
    5353          be installed <i>inside</i> of supported guest
    5454          systems to improve their performance and to provide additional
     
    6868      <li>
    6969        <p><b outputclass="bold">Comprehensive hardware
    70           support.</b> Among other features, Oracle VM VirtualBox
     70          support.</b> Among other features, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    7171          supports the following:
    7272        </p>
     
    7474          <li>
    7575            <p><b outputclass="bold">Guest multiprocessing
    76               (SMP).</b> Oracle VM VirtualBox can present up to 32
     76              (SMP).</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can present up to 32
    7777              virtual CPUs to each virtual machine, irrespective of how
    7878              many CPU cores are physically present on your host.
     
    8181          <li>
    8282            <p><b outputclass="bold">USB device support.</b>
    83               Oracle VM VirtualBox implements a virtual USB controller and
     83              <ph conkeyref="vbox-conkeyref-phrases/product-name"/> implements a virtual USB controller and
    8484              enables you to connect arbitrary USB devices to your
    8585              virtual machines without having to install device-specific
     
    9090          <li>
    9191            <p><b outputclass="bold">Hardware compatibility.</b>
    92               Oracle VM VirtualBox virtualizes a vast array of virtual
     92              <ph conkeyref="vbox-conkeyref-phrases/product-name"/> virtualizes a vast array of virtual
    9393              devices, among them many devices that are typically
    9494              provided by other virtualization platforms. That includes
     
    9999              systems. This enables easy cloning of disk images from
    100100              real machines and importing of third-party virtual
    101               machines into Oracle VM VirtualBox.
     101              machines into <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    102102            </p>
    103103          </li>
     
    105105            <p><b outputclass="bold">Full ACPI support.</b> The
    106106              Advanced Configuration and Power Interface (ACPI) is fully
    107               supported by Oracle VM VirtualBox. This enables easy cloning of
     107              supported by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. This enables easy cloning of
    108108              disk images from real machines or third-party virtual
    109               machines into Oracle VM VirtualBox. With its unique
     109              machines into <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. With its unique
    110110              <i>ACPI power status support</i>,
    111               Oracle VM VirtualBox can even report to ACPI-aware guest OSes
     111              <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can even report to ACPI-aware guest OSes
    112112              the power status of the host. For mobile systems running
    113113              on battery, the guest can thus enable energy saving and
     
    118118          <li>
    119119            <p><b outputclass="bold">Multiscreen resolutions.</b>
    120               Oracle VM VirtualBox virtual machines support screen resolutions
     120              <ph conkeyref="vbox-conkeyref-phrases/product-name"/> virtual machines support screen resolutions
    121121              many times that of a physical screen, allowing them to be
    122122              spread over a large number of screens attached to the host
     
    136136          <li>
    137137            <p><b outputclass="bold">PXE Network boot.</b> The
    138               integrated virtual network cards of Oracle VM VirtualBox fully
     138              integrated virtual network cards of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> fully
    139139              support remote booting using the Preboot Execution
    140140              Environment (PXE).
     
    145145      <li>
    146146        <p><b outputclass="bold">Multigeneration branched
    147           snapshots.</b> Oracle VM VirtualBox can save arbitrary
     147          snapshots.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can save arbitrary
    148148          snapshots of the state of the virtual machine. You can go back
    149149          in time and revert the virtual machine to any such snapshot
     
    155155      </li>
    156156      <li>
    157         <p><b outputclass="bold">VM groups.</b> Oracle VM VirtualBox
     157        <p><b outputclass="bold">VM groups.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    158158          provides a groups feature that enables the user to organize
    159159          and control virtual machines collectively, as well as
     
    169169      <li>
    170170        <p><b outputclass="bold">Clean architecture and unprecedented
    171           modularity.</b> Oracle VM VirtualBox has an extremely modular
     171          modularity.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has an extremely modular
    172172          design with well-defined internal programming interfaces and a
    173173          clean separation of client and server code. This makes it easy
    174174          to control it from several interfaces at once. For example,
    175175          you can start a VM simply by clicking on a button in the
    176           Oracle VM VirtualBox graphical user interface and then control that
     176          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> graphical user interface and then control that
    177177          machine from the command line, or even remotely. See
    178178          <xref href="frontends.dita#frontends"/>.
    179179        </p>
    180180        <p>
    181           Due to its modular architecture, Oracle VM VirtualBox can also
     181          Due to its modular architecture, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can also
    182182          expose its full functionality and configurability through a
    183183          comprehensive <b outputclass="bold">software development kit
    184           (SDK),</b> which enables integration of Oracle VM VirtualBox
     184          (SDK),</b> which enables integration of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    185185          with other software systems. See
    186           <xref href="VirtualBoxAPI.dita">Oracle VM VirtualBox Programming Interfaces</xref>.
     186          <xref href="VirtualBoxAPI.dita"><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Programming Interfaces</xref>.
    187187        </p>
    188188      </li>
     
    204204        </p>
    205205        <p>
    206           On top of this special capacity, Oracle VM VirtualBox offers you
     206          On top of this special capacity, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> offers you
    207207          more unique features:
    208208        </p>
     
    210210          <li>
    211211            <p><b outputclass="bold">Extensible RDP
    212               authentication.</b> Oracle VM VirtualBox already supports
     212              authentication.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> already supports
    213213              Winlogon on Windows and PAM on Linux for RDP
    214214              authentication. In addition, it includes an easy-to-use
     
    220220          <li>
    221221            <p><b outputclass="bold">USB over RDP.</b> Using RDP
    222               virtual channel support, Oracle VM VirtualBox also enables you
     222              virtual channel support, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also enables you
    223223              to connect arbitrary USB devices locally to a virtual
    224               machine which is running remotely on an Oracle VM VirtualBox RDP
     224              machine which is running remotely on an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> RDP
    225225              server. See <xref href="usb-over-rdp.dita">Remote USB</xref>.
    226226            </p>
  • trunk/doc/manual/en_US/dita/topics/frontends.dita

    r98549 r99797  
    77    <p>
    88      As briefly mentioned in <xref href="features-overview.dita#features-overview"/>,
    9       Oracle VM VirtualBox has a very flexible internal design that enables
     9      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has a very flexible internal design that enables
    1010      you to use multiple interfaces to control the same virtual
    1111      machines. For example, you can start a virtual machine with the
    12       VirtualBox Manager window and then stop it from the command line. With
    13       Oracle VM VirtualBox's support for the Remote Desktop Protocol (RDP),
     12      <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> window and then stop it from the command line. With
     13      <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s support for the Remote Desktop Protocol (RDP),
    1414      you can even run virtual machines remotely on a headless server
    1515      and have all the graphical output redirected over the network.
     
    1717    <p>
    1818      The following front-ends are shipped in the standard
    19       Oracle VM VirtualBox package:
     19      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> package:
    2020    </p>
    2121    <ul>
    2222      <li>
    2323        <p><b outputclass="bold">VirtualBox.</b> This is the
    24           VirtualBox Manager, a graphical user interface that uses the Qt
     24          <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, a graphical user interface that uses the Qt
    2525          toolkit. This interface is described throughout this manual.
    2626          While this is the simplest and easiest front-end to use, some
    27           of the more advanced Oracle VM VirtualBox features are not included.
     27          of the more advanced <ph conkeyref="vbox-conkeyref-phrases/product-name"/> features are not included.
    2828        </p>
    2929      </li>
     
    3131        <p><b outputclass="bold">VBoxManage.</b> A command-line
    3232          interface for automated and detailed control of every aspect
    33           of Oracle VM VirtualBox. See
     33          of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. See
    3434          <xref href="vboxmanage.dita#vboxmanage"/>.
    3535        </p>
     
    5151      If the above front-ends still do not satisfy your particular
    5252      needs, it is possible to create yet another front-end to the
    53       complex virtualization engine that is the core of Oracle VM VirtualBox,
    54       as the Oracle VM VirtualBox core neatly exposes all of its features in a
    55       clean API. See <xref href="VirtualBoxAPI.dita">Oracle VM VirtualBox Programming Interfaces</xref>.
     53      complex virtualization engine that is the core of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>,
     54      as the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> core neatly exposes all of its features in a
     55      clean API. See <xref href="VirtualBoxAPI.dita"><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Programming Interfaces</xref>.
    5656    </p>
    5757  </body>
  • trunk/doc/manual/en_US/dita/topics/gimproviders.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox enables the exposure of a paravirtualization
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables the exposure of a paravirtualization
    99      interface, to facilitate accurate and efficient execution of
    1010      software within a virtual machine. These interfaces require the
    1111      guest operating system to recognize their presence and make use of
    1212      them in order to leverage the benefits of communicating with the
    13       Oracle VM VirtualBox hypervisor.
     13      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> hypervisor.
    1414    </p>
    1515    <p>
     
    2525      the <i>Hyper-V</i> paravirtualization provider can
    2626      be used for VMs to run on any host platform supported by
    27       Oracle VM VirtualBox and not just Windows.
     27      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and not just Windows.
    2828    </p>
    2929    <p>
    30       Oracle VM VirtualBox provides the following interfaces:
     30      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides the following interfaces:
    3131    </p>
    3232    <ul>
     
    4141        <p><b outputclass="bold">KVM</b>: Presents a Linux KVM
    4242          hypervisor interface which is recognized by Linux kernels
    43           version 2.6.25 or later. Oracle VM VirtualBox's implementation
     43          version 2.6.25 or later. <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s implementation
    4444          currently supports paravirtualized clocks and SMP spinlocks.
    4545          This provider is recommended for Linux guests.
     
    4949        <p><b outputclass="bold">Hyper-V</b>: Presents a Microsoft
    5050          Hyper-V hypervisor interface which is recognized by Windows 7
    51           and newer operating systems. Oracle VM VirtualBox's implementation
     51          and newer operating systems. <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s implementation
    5252          currently supports paravirtualized clocks, APIC frequency
    5353          reporting, guest debugging, guest crash reporting and relaxed
  • trunk/doc/manual/en_US/dita/topics/guestadd-2d.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         The Oracle VM VirtualBox Guest Additions contain experimental hardware
     8        The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions contain experimental hardware
    99        2D video acceleration support for Windows guests.
    1010      </p>
     
    1212        With this feature, if an application such as a video player
    1313        inside your Windows VM uses 2D video overlays to play a movie
    14         clip, then Oracle VM VirtualBox will attempt to use your host's video
     14        clip, then <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will attempt to use your host's video
    1515        acceleration hardware instead of performing overlay stretching
    1616        and color conversion in software, which would be slow. This
     
    4545    </ul>
    4646    <p>
    47         Technically, Oracle VM VirtualBox implements this by exposing video
     47        Technically, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> implements this by exposing video
    4848        overlay DirectDraw capabilities in the Guest Additions video
    4949        driver. The driver sends all overlay commands to the host
    5050        through a special communication tunnel implemented by
    51         Oracle VM VirtualBox. On the host side, OpenGL is then used to
     51        <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. On the host side, OpenGL is then used to
    5252        implement color space transformation and scaling.
    5353      </p>
  • trunk/doc/manual/en_US/dita/topics/guestadd-3d.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         The Oracle VM VirtualBox Guest Additions contain experimental hardware
     8        The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions contain experimental hardware
    99        3D support for Windows, Linux, and Oracle Solaris guests.
    1010      </p>
     
    1313        uses 3D features through the OpenGL or Direct3D 8/9 programming
    1414        interfaces, instead of emulating them in software, which would
    15         be slow, Oracle VM VirtualBox will attempt to use your host's 3D
     15        be slow, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will attempt to use your host's 3D
    1616        hardware. This works for all supported host platforms, provided
    1717        that your host operating system can make use of your accelerated
     
    5959          <p>
    6060              For the basic Direct3D acceleration to work in a Windows
    61               Guest, Oracle VM VirtualBox needs to replace Windows system
     61              Guest, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> needs to replace Windows system
    6262              files in the virtual machine. As a result, the Guest
    6363              Additions installation program offers Direct3D
     
    8080          <p>
    8181              Untrusted guest systems should not be allowed to use the
    82               3D acceleration features of Oracle VM VirtualBox, just as
     82              3D acceleration features of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, just as
    8383              untrusted host software should not be allowed to use 3D
    8484              acceleration. Drivers for 3D hardware are generally too
     
    8787              operating system running them. In addition, enabling 3D
    8888              acceleration gives the guest direct access to a large body
    89               of additional program code in the Oracle VM VirtualBox host
     89              of additional program code in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> host
    9090              process which it might conceivably be able to use to crash
    9191              the virtual machine.
     
    9595    </ul>
    9696    <p>
    97         To enable Aero theme support, the Oracle VM VirtualBox WDDM video
     97        To enable Aero theme support, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> WDDM video
    9898        driver must be installed, which is available with the Guest
    9999        Additions installation. The WDDM driver is not installed by
     
    111111      </p>
    112112    <p>
    113         Technically, Oracle VM VirtualBox implements 3D acceleration by
     113        Technically, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> implements 3D acceleration by
    114114        installing an additional hardware 3D driver inside the guest
    115115        when the Guest Additions are installed. This driver acts as a
     
    119119        hardware acceleration through the OpenGL or Direct3D programming
    120120        interfaces, these are sent to the host through a special
    121         communication tunnel implemented by Oracle VM VirtualBox. The
     121        communication tunnel implemented by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. The
    122122        <i>host</i> then performs the requested 3D
    123123        operation using the host's programming interfaces.
  • trunk/doc/manual/en_US/dita/topics/guestadd-balloon.dita

    r99497 r99797  
    1515        <li>
    1616          <p>
    17               Oracle VM VirtualBox supports memory ballooning only on 64-bit
     17              <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports memory ballooning only on 64-bit
    1818              hosts. It is not supported on macOS hosts.
    1919            </p>
     
    3737      </p>
    3838    <p>
    39         When memory ballooning is requested, the Oracle VM VirtualBox Guest
     39        When memory ballooning is requested, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest
    4040        Additions, which run inside the guest, allocate physical memory
    4141        from the guest operating system on the kernel level and lock
     
    4343        not use that memory any longer. No guest applications can
    4444        allocate it, and the guest kernel will not use it either.
    45         Oracle VM VirtualBox can then reuse this memory and give it to another
     45        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can then reuse this memory and give it to another
    4646        virtual machine.
    4747      </p>
    4848    <p>
    4949        The memory made available through the ballooning mechanism is
    50         only available for reuse by Oracle VM VirtualBox. It is
     50        only available for reuse by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. It is
    5151        <i>not</i> returned as free memory to the host.
    5252        Requesting balloon memory from a running guest will therefore
  • trunk/doc/manual/en_US/dita/topics/guestadd-dnd-formats.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         As Oracle VM VirtualBox can run on a variety of host operating systems
     8        As <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can run on a variety of host operating systems
    99        and also supports a wide range of guests, certain data formats
    1010        must be translated after transfer. This is so that the
     
    2121    </note>
    2222    <p>
    23         The following formats are handled by the Oracle VM VirtualBox drag and
     23        The following formats are handled by the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> drag and
    2424        drop service:
    2525      </p>
  • trunk/doc/manual/en_US/dita/topics/guestadd-dnd-limitations.dita

    r98549 r99797  
    1212        UAC-elevated (User Account Control) programs and
    1313        non-UAC-elevated programs is not allowed. If you start
    14         Oracle VM VirtualBox with Administrator privileges then drag and drop
     14        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with Administrator privileges then drag and drop
    1515        will not work with Windows Explorer, which runs with regular
    1616        user privileges by default.
  • trunk/doc/manual/en_US/dita/topics/guestadd-dnd.dita

    r99182 r99797  
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox enables you to drag and drop content from the host
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to drag and drop content from the host
    99      to the guest, and vice versa. For this to work the latest version
    1010      of the Guest Additions must be installed on the guest.
     
    2424      most common one, XDND, is supported for now. Applications using
    2525      other protocols, such as Motif or OffiX, will not be recognized by
    26       Oracle VM VirtualBox.
     26      <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    2727    </p>
    2828    <p>
     
    9797      <p>
    9898        Drag and drop support depends on the frontend being used. At the
    99         moment, only the VirtualBox Manager frontend provides this
     99        moment, only the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> frontend provides this
    100100        functionality.
    101101      </p>
  • trunk/doc/manual/en_US/dita/topics/guestadd-gc-file-manager-using.dita

    r98549 r99797  
    2525          <li>
    2626            <p>
    27                 In VirtualBox Manager, click on the machine name. Click
     27                In <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, click on the machine name. Click
    2828                <b outputclass="bold">File Manager</b> in the
    2929                machine tools menu for the VM.
  • trunk/doc/manual/en_US/dita/topics/guestadd-guestcontrol.dita

    r99497 r99797  
    2525    </p>
    2626    <p>
    27       To use these features, use the Oracle VM VirtualBox command line. See
     27      To use these features, use the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> command line. See
    2828      <xref href="vboxmanage-guestcontrol.dita"/>.
    2929    </p>
  • trunk/doc/manual/en_US/dita/topics/guestadd-guestprops.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="guestadd-guestprops">
    44  <title>Guest Properties</title>
    5  
     5
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox enables requests of some properties from a running
    9       guest, provided that the Oracle VM VirtualBox Guest Additions are
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables requests of some properties from a running
     9      guest, provided that the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions are
    1010      installed and the VM is running. This provides the following
    1111      advantages:
     
    1515        <p>
    1616          A number of predefined VM characteristics are automatically
    17           maintained by Oracle VM VirtualBox and can be retrieved on the host.
     17          maintained by <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and can be retrieved on the host.
    1818          For example, to monitor VM performance and statistics.
    1919        </p>
     
    2727    </ul>
    2828    <p>
    29       To accomplish this, Oracle VM VirtualBox establishes a private
    30       communication channel between the Oracle VM VirtualBox Guest Additions
     29      To accomplish this, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> establishes a private
     30      communication channel between the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions
    3131      and the host, and software on both sides can use this channel to
    3232      exchange string data for arbitrary purposes. Guest properties are
     
    3838      In addition to establishing the general mechanism of reading and
    3939      writing values, a set of predefined guest properties is
    40       automatically maintained by the Oracle VM VirtualBox Guest Additions to
     40      automatically maintained by the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions to
    4141      allow for retrieving interesting guest data such as the guest's
    4242      exact operating system and service pack level, the installed
     
    5252    </p>
    5353    <p>
    54       A more flexible way to use this channel is with the
    55       <userinput>VBoxManage guestproperty</userinput> command. See
    56       <xref href="vboxmanage-guestproperty.dita"/>. For example, to have
    57       <i>all</i> the available guest properties for a
    58       given running VM listed with their respective values, use this
    59       command:
     54      A more flexible way to use this channel is with the <userinput>VBoxManage
     55      guestproperty</userinput> command. See <xref href="vboxmanage-guestproperty.dita"/>.
     56      For example, to have <i>all</i> the available guest properties for a given running VM
     57      listed with their respective values, use this command:
    6058    </p>
    6159    <pre xml:space="preserve">$ VBoxManage guestproperty enumerate "Windows Vista III"
     
    139137      ...</pre>
    140138    <p>
    141       For more complex needs, you can use the Oracle VM VirtualBox programming
    142       interfaces. See <xref href="VirtualBoxAPI.dita">Oracle VM VirtualBox Programming Interfaces</xref>.
     139      For more complex needs, you can use the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> programming
     140      interfaces. See <xref href="VirtualBoxAPI.dita"><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Programming Interfaces</xref>.
    143141    </p>
    144142  </body>
  • trunk/doc/manual/en_US/dita/topics/guestadd-intro.dita

    r98549 r99797  
    1313      See <xref href="guestossupport.dita#guestossupport"/> for details on what guest
    1414      operating systems are fully supported with Guest Additions by
    15       Oracle VM VirtualBox.
     15      <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    1616    </p>
    1717    <p>
    18       The Oracle VM VirtualBox Guest Additions for all supported guest
     18      The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions for all supported guest
    1919      operating systems are provided as a single CD-ROM image file which
    2020      is called <filepath>VBoxGuestAdditions.iso</filepath>. This image
    21       file is located in the installation directory of Oracle VM VirtualBox.
     21      file is located in the installation directory of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    2222      To install the Guest Additions for a particular VM, you mount this
    2323      ISO file in your VM as a virtual CD-ROM and install from there.
     
    4444          an easy way to exchange files between the host and the guest.
    4545          Much like ordinary Windows network shares, you can tell
    46           Oracle VM VirtualBox to treat a certain host directory as a shared
    47           folder, and Oracle VM VirtualBox will make it available to the guest
     46          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to treat a certain host directory as a shared
     47          folder, and <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will make it available to the guest
    4848          operating system as a network share, irrespective of whether
    4949          the guest actually has a network. See
     
    5353      <li>
    5454        <p><b outputclass="bold">Better video support.</b> While
    55           the virtual graphics card which Oracle VM VirtualBox emulates for
     55          the virtual graphics card which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> emulates for
    5656          any guest operating system provides all the basic features,
    5757          the custom video drivers that are installed with the Guest
     
    9898      <li>
    9999        <p><b outputclass="bold">Time synchronization.</b> With
    100           the Guest Additions installed, Oracle VM VirtualBox can ensure that
     100          the Guest Additions installed, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can ensure that
    101101          the guest's system time is better synchronized with that of
    102102          the host.
     
    136136    </ul>
    137137    <p>
    138       Each version of Oracle VM VirtualBox, even minor releases, ship with
     138      Each version of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, even minor releases, ship with
    139139      their own version of the Guest Additions. While the interfaces
    140       through which the Oracle VM VirtualBox core communicates with the Guest
     140      through which the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> core communicates with the Guest
    141141      Additions are kept stable so that Guest Additions already
    142       installed in a VM should continue to work when Oracle VM VirtualBox is
     142      installed in a VM should continue to work when <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is
    143143      upgraded on the host, for best results, it is recommended to keep
    144144      the Guest Additions at the same version.
     
    147147      The Windows and Linux Guest Additions therefore check
    148148      automatically whether they have to be updated. If the host is
    149       running a newer Oracle VM VirtualBox version than the Guest Additions, a
     149      running a newer <ph conkeyref="vbox-conkeyref-phrases/product-name"/> version than the Guest Additions, a
    150150      notification with further instructions is displayed in the guest.
    151151    </p>
  • trunk/doc/manual/en_US/dita/topics/guestadd-pagefusion.dita

    r99497 r99797  
    1313        In a server environment running several similar VMs on the same
    1414        host, lots of memory pages are identical. For example, if the
    15         VMs are using identical operating systems. Oracle VM VirtualBox's Page
     15        VMs are using identical operating systems. <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s Page
    1616        Fusion technology can efficiently identify these identical
    1717        memory pages and share them between multiple VMs.
     
    1919    <note>
    2020      <p>
    21           Oracle VM VirtualBox supports Page Fusion only on 64-bit hosts, and
     21          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports Page Fusion only on 64-bit hosts, and
    2222          it is not supported on macOS hosts. Page Fusion currently
    2323          works only with Windows 2000 and later guests.
     
    6363          </p>
    6464        <p>
    65             Page Fusion in Oracle VM VirtualBox uses logic in the
    66             Oracle VM VirtualBox Guest Additions to quickly identify memory
     65            Page Fusion in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses logic in the
     66            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions to quickly identify memory
    6767            cells that are most likely identical across VMs. It can
    6868            therefore achieve most of the possible savings of page
     
    8686      </p>
    8787    <pre xml:space="preserve">VBoxManage modifyvm "VM name" --page-fusion on</pre>
    88     <p>
    89         You can observe Page Fusion operation using some metrics.
    90         <codeph>RAM/VMM/Shared</codeph> shows the total amount of
    91         fused pages, whereas the per-VM metric
    92         <codeph>Guest/RAM/Usage/Shared</codeph> will return the amount
    93         of fused memory for a given VM. See
    94         <xref href="vboxmanage-metrics.dita"/> for information on how to
    95         query metrics.
    96       </p>
     88    <p> You can observe Page Fusion operation using some metrics. <codeph>RAM/VMM/Shared</codeph>
     89      shows the total amount of fused pages, whereas the per-VM metric
     90        <codeph>Guest/RAM/Usage/Shared</codeph> will return the amount of fused memory for a given
     91      VM. See <xref href="vboxmanage-metrics.dita"/> for information on how to query metrics. </p>
    9792    <note>
    9893      <p>
  • trunk/doc/manual/en_US/dita/topics/guestadditions.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8     The previous chapter covered getting started with Oracle VM VirtualBox and
     8    The previous chapter covered getting started with <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and
    99    installing operating systems in a virtual machine. For any serious
    10     and interactive use, the Oracle VM VirtualBox Guest Additions will make
     10    and interactive use, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions will make
    1111    your life much easier by providing closer integration between host
    1212    and guest and improving the interactive performance of guest
  • trunk/doc/manual/en_US/dita/topics/guestossupport.dita

    r99182 r99797  
    66  <body>
    77    <p>
    8       Because Oracle VM VirtualBox is designed to provide a generic
     8      Because <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is designed to provide a generic
    99      virtualization environment for x86 systems, it can run guest
    1010      operating systems (OSes) of any kind.
     
    2323        <p><b outputclass="bold">Platforms With Limited
    2424          Support.</b> These legacy guest OS platforms can be
    25           used with Oracle VM VirtualBox, but only qualify for <i>best
     25          used with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, but only qualify for <i>best
    2626          effort</i> support. Therefore, resolution of customer
    2727          issues is not guaranteed. See
  • trunk/doc/manual/en_US/dita/topics/guestxorgsetup.dita

    r98549 r99797  
    1212      </p>
    1313    <p>
    14         The Oracle VM VirtualBox Guest Additions includes drivers for X.Org.
     14        The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions includes drivers for X.Org.
    1515        By default these drivers are in the following directory:
    1616      </p>
     
    2626        load the <codeph>vboxvideo</codeph> driver. Many recent X
    2727        server versions look for it automatically if they see that they
    28         are running in Oracle VM VirtualBox. For an optimal user experience,
     28        are running in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. For an optimal user experience,
    2929        the guest kernel drivers must be loaded and the Guest Additions
    3030        tool <userinput>VBoxClient</userinput> must be running as a client
     
    4141      </p>
    4242    <p>
    43         The Oracle VM VirtualBox guest graphics driver can use any graphics
     43        The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> guest graphics driver can use any graphics
    4444        configuration for which the virtual resolution fits into the
    4545        virtual video memory allocated to the virtual machine, minus a
  • trunk/doc/manual/en_US/dita/topics/gui-details-settings.dita

    r98549 r99797  
    2222          Virtual machine settings can also be changed using the
    2323          <b outputclass="bold">Settings</b> button on the
    24           VirtualBox Manager toolbar.
     24          <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> toolbar.
    2525        </p>
    2626    <p>
  • trunk/doc/manual/en_US/dita/topics/gui-details-toolbar.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="gui-details-toolbar">
    4   <title>VirtualBox Manager Toolbar</title>
     4  <title><ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> Toolbar</title>
    55 
    66  <body>
  • trunk/doc/manual/en_US/dita/topics/gui-details.dita

    r99182 r99797  
    1111      </p>
    1212    <fig id="fig-vbox-details-pane">
    13       <title>VirtualBox Manager Details Pane, Including Toolbar</title>
     13      <title><ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> Details Pane, Including Toolbar</title>
    1414      <xref href="images/details-pane.png" format="png" platform="htmlhelp">
    1515        <image href="images/details-pane.png" width="12cm" placement="break">
    16           <alt>VirtualBox Manager Details Pane, Including Toolbar</alt>
     16          <alt><ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> Details Pane, Including Toolbar</alt>
    1717        </image>
    1818      </xref>
    1919      <image platform="ohc" href="images/details-pane.png" width="12cm" placement="break">
    20         <alt>VirtualBox Manager Details Pane, Including Toolbar</alt>
     20        <alt><ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> Details Pane, Including Toolbar</alt>
    2121      </image>
    2222    </fig>
  • trunk/doc/manual/en_US/dita/topics/gui-tools-global.dita

    r99182 r99797  
    66  <body>
    77    <p>
    8           In the left pane of the VirtualBox Manager window, click the
     8          In the left pane of the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> window, click the
    99          <b outputclass="bold">Menu</b> icon in the
    1010          <b outputclass="bold">Tools</b> banner located above
     
    3030      <li>
    3131        <p><b outputclass="bold">Welcome.</b> Displays the
    32               VirtualBox Manager welcome message. The VirtualBox Manager toolbar is also
     32              <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> welcome message. The <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> toolbar is also
    3333              included, to enable you to get started with using
    34               Oracle VM VirtualBox. See
     34              <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. See
    3535              <xref href="gui-virtualboxmanager.dita#gui-virtualboxmanager/fig-vbox-manager-initial"/>.
    3636            </p>
     
    4040              <b outputclass="bold">Extension Pack Manager</b>
    4141              tool. This tool is used to install and uninstall
    42               Oracle VM VirtualBox Extension Packs. See
     42              <ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/>s. See
    4343              <xref href="install-ext-pack-manager.dita#install-ext-pack-manager"/>.
    4444            </p>
     
    4848              <b outputclass="bold">Virtual Media Manager</b>
    4949              tool. This tool is used to manage the disk images used by
    50               Oracle VM VirtualBox. See
     50              <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. See
    5151              <xref href="virtual-media-manager.dita#virtual-media-manager"/>.
    5252            </p>
     
    5656              <b outputclass="bold">Network Manager</b> tool.
    5757              This tool is used to create and configure some types of
    58               networks used by Oracle VM VirtualBox. See
     58              networks used by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. See
    5959              <xref href="network-manager.dita#network-manager"/>.
    6060            </p>
     
    6464              <b outputclass="bold">Cloud Profile Editor</b>
    6565              tool. This tool is used to configure connections to a
    66               cloud service, such as Oracle Cloud Infrastructure. See
     66              cloud service, such as <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See
    6767              <xref href="cloud-using-cloud-profile-manager.dita#cloud-using-cloud-profile-manager"/>.
    6868            </p>
  • trunk/doc/manual/en_US/dita/topics/gui-tools-machine.dita

    r99182 r99797  
    66  <body>
    77    <p>
    8           In the machine list in the left pane of the VirtualBox Manager window,
     8          In the machine list in the left pane of the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> window,
    99          select a virtual machine.
    1010        </p>
  • trunk/doc/manual/en_US/dita/topics/gui-tools.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="gui-tools">
    4   <title>VirtualBox Manager Tools</title>
     4  <title><ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> Tools</title>
    55 
    66  <body>
    77    <p>
    8         VirtualBox Manager provides two types of user tools, to enable you to
     8        <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> provides two types of user tools, to enable you to
    99        perform common tasks easily.
    1010      </p>
  • trunk/doc/manual/en_US/dita/topics/gui-virtualboxmanager.dita

    r99182 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="gui-virtualboxmanager">
    4   <title>VirtualBox Manager</title>
     4  <title><ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/></title>
    55 
    66  <body>
    77    <p>
    8       VirtualBox Manager is the user interface for Oracle VM VirtualBox. You can use
    9       VirtualBox Manager to create, configure, and manage your virtual machines.
     8      <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> is the user interface for <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. You can use
     9      <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> to create, configure, and manage your virtual machines.
    1010    </p>
    1111    <p>
    12       This section describes the main features of the VirtualBox Manager user
     12      This section describes the main features of the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> user
    1313      interface. Subsequent sections and chapters describe how to use
    14       VirtualBox Manager to perform tasks in Oracle VM VirtualBox.
     14      <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> to perform tasks in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    1515    </p>
    1616    <p>
    17       When you start Oracle VM VirtualBox, the
    18       <b outputclass="bold">VirtualBox Manager</b> window is displayed.
     17      When you start <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, the
     18      <b outputclass="bold"><ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/></b> window is displayed.
    1919    </p>
    20     <p><xref href="#gui-virtualboxmanager/fig-vbox-manager-initial"/> shows VirtualBox Manager the
    21       first time you start Oracle VM VirtualBox, before you have created any
     20    <p><xref href="#gui-virtualboxmanager/fig-vbox-manager-initial"/> shows <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> the
     21      first time you start <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, before you have created any
    2222      virtual machines.
    2323    </p>
    2424    <fig id="fig-vbox-manager-initial">
    25       <title>VirtualBox Manager, Showing Welcome Screen After Initial Startup</title>
     25      <title><ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, Showing Welcome Screen After Initial Startup</title>
    2626      <xref href="images/virtualbox-main-empty.png" format="png" platform="htmlhelp">
    2727        <image href="images/virtualbox-main-empty.png" width="12cm" placement="break">
    28           <alt>VirtualBox Manager, Showing Welcome Screen After Initial Startup</alt>
     28          <alt><ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, Showing Welcome Screen After Initial Startup</alt>
    2929        </image>
    3030      </xref>
    3131      <image platform="ohc" href="images/virtualbox-main-empty.png" width="12cm" placement="break">
    32         <alt>VirtualBox Manager, Showing Welcome Screen After Initial Startup</alt>
     32        <alt><ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, Showing Welcome Screen After Initial Startup</alt>
    3333      </image>
    3434    </fig>
    35     <p><xref href="#gui-virtualboxmanager/fig-vbox-manager-populated"/> shows how VirtualBox Manager
     35    <p><xref href="#gui-virtualboxmanager/fig-vbox-manager-populated"/> shows how <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>
    3636      might look after you have created some virtual machines.
    3737    </p>
    3838    <fig id="fig-vbox-manager-populated">
    39       <title>VirtualBox Manager Window, After Creating Virtual Machines</title>
     39      <title><ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> Window, After Creating Virtual Machines</title>
    4040      <xref href="images/virtualbox-main.png" format="png" platform="htmlhelp">
    4141        <image href="images/virtualbox-main.png" width="12cm" placement="break">
    42           <alt>VirtualBox Manager Window, After Creating Virtual Machines</alt>
     42          <alt><ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> Window, After Creating Virtual Machines</alt>
    4343        </image>
    4444      </xref>
    4545      <image platform="ohc" href="images/virtualbox-main.png" width="12cm" placement="break">
    46         <alt>VirtualBox Manager Window, After Creating Virtual Machines</alt>
     46        <alt><ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> Window, After Creating Virtual Machines</alt>
    4747      </image>
    4848    </fig>
    4949    <p>
    50       The main components of the VirtualBox Manager window are as follows:
     50      The main components of the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> window are as follows:
    5151    </p>
    5252    <ul>
     
    7373      <li>
    7474        <p><b outputclass="bold">Help Viewer.</b> A window that
    75           displays context-sensitive help topics for VirtualBox Manager tasks.
     75          displays context-sensitive help topics for <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> tasks.
    7676          See <xref href="help-viewer.dita#help-viewer"/>.
    7777        </p>
  • trunk/doc/manual/en_US/dita/topics/gui-vmgroups.dita

    r99182 r99797  
    3131      <li>
    3232        <p>
    33           Create a group using VirtualBox Manager. Do one of the following:
     33          Create a group using <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. Do one of the following:
    3434        </p>
    3535        <ul>
     
    101101      <li>
    102102        <p>
    103           Use VirtualBox Manager menu options to control and manage all the VMs
     103          Use <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> menu options to control and manage all the VMs
    104104          in a group. For example:
    105105          <b outputclass="bold">Start</b>,
  • trunk/doc/manual/en_US/dita/topics/guitweaks.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="guitweaks">
    4   <title>Locking Down VirtualBox Manager</title>
     4  <title>Locking Down <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/></title>
    55 
    66  <body/>
  • trunk/doc/manual/en_US/dita/topics/harddiskcontrollers.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="harddiskcontrollers">
    44  <title>Hard Disk Controllers</title>
    5  
     5
    66  <body>
    77    <p>
    88      In a computing device, hard disks and CD/DVD drives are connected
    99      to a device called a hard disk controller, which drives hard disk
    10       operation and data transfers. Oracle VM VirtualBox can emulate the most
     10      operation and data transfers. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can emulate the most
    1111      common types of hard disk controllers typically found in computing
    1212      devices: IDE, SATA (AHCI), SCSI, SAS, USB-based, NVMe and
     
    2828        </p>
    2929        <p>
    30           In Oracle VM VirtualBox, each virtual machine may have one IDE
     30          In <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, each virtual machine may have one IDE
    3131          controller enabled, which gives you up to four virtual storage
    3232          devices that you can attach to the machine. By default, one of
     
    4141        <p>
    4242          You can also select which exact type of IDE controller
    43           hardware Oracle VM VirtualBox should present to the virtual machine:
     43          hardware <ph conkeyref="vbox-conkeyref-phrases/product-name"/> should present to the virtual machine:
    4444          PIIX3, PIIX4, or ICH6. This makes no difference in terms of
    4545          performance, but if you import a virtual machine from another
     
    5050          After you have created a new virtual machine with the
    5151          <b outputclass="bold">New Virtual Machine</b> wizard in
    52           VirtualBox Manager, you will typically see one IDE controller in the
     52          <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, you will typically see one IDE controller in the
    5353          machine's <b outputclass="bold">Storage</b> settings.
    5454          The virtual CD/DVD drive will be attached to one of the four
     
    6565        </p>
    6666        <p>
    67           Like a real SATA controller, Oracle VM VirtualBox's virtual SATA
     67          Like a real SATA controller, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s virtual SATA
    6868          controller operates faster and also consumes fewer CPU
    6969          resources than the virtual IDE controller. Also, this enables
    7070          you to connect up to 30 virtual hard disks to one machine
    71           instead of just three, when compared to the Oracle VM VirtualBox IDE
     71          instead of just three, when compared to the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> IDE
    7272          controller with a DVD drive attached.
    7373        </p>
    7474        <p>
    7575          For this reason, depending on the selected guest OS,
    76           Oracle VM VirtualBox uses SATA as the default for newly created
     76          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses SATA as the default for newly created
    7777          virtual machines. One virtual SATA controller is created by
    7878          default, and the default disk that is created with a new VM is
     
    9494          </p>
    9595          <p>
    96             Oracle VM VirtualBox recommends the Intel Matrix Storage drivers,
     96            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> recommends the Intel Matrix Storage drivers,
    9797            which can be downloaded from
    9898            <ph>http://downloadcenter.intel.com/Product_Filter.aspx?ProductID=2101</ph>.
     
    102102          To add a SATA controller to a machine for which it has not
    103103          been enabled by default, either because it was created by an
    104           earlier version of Oracle VM VirtualBox, or because SATA is not
     104          earlier version of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, or because SATA is not
    105105          supported by default by the selected guest OS, do the
    106106          following. Go to the <b outputclass="bold">Storage</b>
     
    114114        </p>
    115115        <p>
    116           To change the IDE compatibility mode settings for the SATA
    117           controller, see <xref href="vboxmanage-storagectl.dita"/>.
     116            To change the IDE compatibility mode settings for the SATA controller, see <xref
     117            href="vboxmanage-storagectl.dita"/>.
    118118        </p>
    119119      </li>
     
    130130        <p>
    131131          Primarily for compatibility with other virtualization
    132           software, Oracle VM VirtualBox optionally supports LSI Logic and
     132          software, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> optionally supports LSI Logic and
    133133          BusLogic SCSI controllers, to each of which up to fifteen
    134134          virtual hard disks can be attached.
     
    164164        <p>
    165165          To support high-end guests which require SAS controllers,
    166           Oracle VM VirtualBox emulates a LSI Logic SAS controller, which can
     166          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> emulates a LSI Logic SAS controller, which can
    167167          be enabled much the same way as a SCSI controller. At this
    168168          time, up to 255 devices can be connected to the SAS
     
    190190        </p>
    191191        <p>
    192           The virtual USB storage controller offered by Oracle VM VirtualBox
     192          The virtual USB storage controller offered by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    193193          works differently to the other storage controller types. While
    194194          most storage controllers appear as a single PCI device to the
     
    245245    </ul>
    246246    <p>
    247       In summary, Oracle VM VirtualBox gives you the following categories of
     247      In summary, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> gives you the following categories of
    248248      virtual storage slots:
    249249    </p>
     
    298298      the only controller supported by your guest. Whether you use SATA,
    299299      SCSI, or SAS does not make any real difference. The variety of
    300       controllers is only supplied by Oracle VM VirtualBox for compatibility
     300      controllers is only supplied by <ph conkeyref="vbox-conkeyref-phrases/product-name"/> for compatibility
    301301      with existing hardware and other hypervisors.
    302302    </p>
    303303  </body>
    304  
     304
    305305</topic>
  • trunk/doc/manual/en_US/dita/topics/hdimagewrites.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="hdimagewrites">
    44  <title>Special Image Write Modes</title>
    5  
     5
    66  <body>
    77    <p>
    8       For each virtual disk image supported by Oracle VM VirtualBox, you can
     8      For each virtual disk image supported by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, you can
    99      determine separately how it should be affected by write operations
    1010      from a virtual machine and snapshot operations. This applies to
     
    1414    </p>
    1515    <p>
    16       By default, images are in <i>normal</i> mode. To
    17       mark an existing image with one of the non-standard modes listed
    18       below, use <userinput>VBoxManage modifymedium</userinput>. See
    19       <xref href="vboxmanage-modifymedium.dita"/>. Alternatively, use
    20       <userinput>VBoxManage storageattach</userinput> to attach the image to
    21       a VM and specify the <codeph>--mtype</codeph> argument. See
    22       <xref href="vboxmanage-storageattach.dita"/>.
     16      By default, images are in <i>normal</i> mode. To mark an existing image with one of the
     17      non-standard modes listed below, use <userinput>VBoxManage modifymedium</userinput>. See
     18      <xref href="vboxmanage-modifymedium.dita"/>. Alternatively, use <userinput>VBoxManage
     19      storageattach</userinput> to attach the image to a VM and specify the
     20      <codeph>--mtype</codeph> argument. See <xref href="vboxmanage-storageattach.dita"/>.
    2321    </p>
    2422    <p>
     
    3937        <p>
    4038          The image file itself is not reset. Instead, when a snapshot
    41           is taken, Oracle VM VirtualBox <i>freezes</i> the
     39          is taken, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> <i>freezes</i> the
    4240          image file and no longer writes to it. For the write
    4341          operations from the VM, a second,
     
    118116        </note>
    119117        <p>
    120           Oracle VM VirtualBox never writes to an immutable image directly at
     118          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> never writes to an immutable image directly at
    121119          all. All write operations from the machine are directed to a
    122120          differencing image. The next time the VM is powered on, the
     
    126124        <p>
    127125          The differencing image is only reset when the machine is
    128           powered on from within Oracle VM VirtualBox, not when you reboot by
     126          powered on from within <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, not when you reboot by
    129127          requesting a reboot from within the machine. This is also why
    130128          immutable images behave as described above when snapshots are
    131129          also present, which use differencing images as well.
    132130        </p>
    133         <p>
    134           If the automatic discarding of the differencing image on VM
    135           startup does not fit your needs, you can turn it off using the
    136           <codeph>autoreset</codeph> parameter of <userinput>VBoxManage
    137           modifymedium</userinput>. See
    138           <xref href="vboxmanage-modifymedium.dita"/>.
    139         </p>
     131        <p> If the automatic discarding of the differencing image on VM startup does not fit your
     132          needs, you can turn it off using the <codeph>autoreset</codeph> parameter of
     133            <userinput>VBoxManage modifymedium</userinput>. See <xref
     134            href="vboxmanage-modifymedium.dita"/>. </p>
    140135      </li>
    141136      <li>
     
    195190    </p>
    196191  </body>
    197  
     192
    198193</topic>
  • trunk/doc/manual/en_US/dita/topics/headless-vm-steps.dita

    r98549 r99797  
    1616      <li>
    1717        <p>
    18             Oracle VM VirtualBox on a server machine with a supported host
    19             operating system. The Oracle VM VirtualBox Extension Pack for the
     18            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> on a server machine with a supported host
     19            operating system. The <ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/> for the
    2020            VRDP server must be installed, see <xref href="vrde.dita#vrde"/>.
    2121            The procedures assume a Linux server is used.
  • trunk/doc/manual/en_US/dita/topics/heartbeatservice.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox ships a simple heartbeat service. Once the Guest
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> ships a simple heartbeat service. Once the Guest
    99      Additions are active, the guest sends frequent heartbeat pings to
    1010      the host. If the guest stops sending the heartbeat pings without
     
    1818      interval</i> defines the time between two heartbeat pings.
    1919      The default value is 2 seconds, that is, the heartbeat service of
    20       the Oracle VM VirtualBox Guest Additions will send a heartbeat ping
     20      the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions will send a heartbeat ping
    2121      every two seconds. The value in nanoseconds can be configured like
    2222      this:
  • trunk/doc/manual/en_US/dita/topics/help-viewer.dita

    r98549 r99797  
    77    <p>
    88        The Help Viewer is a window that displays context-sensitive help
    9         to assist you in completing common VirtualBox Manager tasks. You can
     9        to assist you in completing common <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> tasks. You can
    1010        display the Help Viewer in the following ways:
    1111      </p>
     
    1313      <li>
    1414        <p>
    15             In a VirtualBox Manager wizard or dialog, click
     15            In a <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> wizard or dialog, click
    1616            <b outputclass="bold">Help</b> to display the
    1717            relevant help topic.
     
    2020      <li>
    2121        <p>
    22             In VirtualBox Manager or from a guest VM, do either of the
     22            In <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> or from a guest VM, do either of the
    2323            following:
    2424          </p>
     
    5454          <li>
    5555            <p><b outputclass="bold">Contents.</b> Displays the
    56                 help topic location in the Oracle VM VirtualBox documentation.
     56                help topic location in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> documentation.
    5757              </p>
    5858          </li>
  • trunk/doc/manual/en_US/dita/topics/host-key-customize.dita

    r99182 r99797  
    88        To disable all Host key combinations, open the preferences and
    99        change the Host key to None. This might be useful when using
    10         Oracle VM VirtualBox in a kiosk mode.
     10        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> in a kiosk mode.
    1111      </p>
    1212    <p>
  • trunk/doc/manual/en_US/dita/topics/hostossupport.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       Currently, Oracle VM VirtualBox runs on the following host OSes:
     8      Currently, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> runs on the following host OSes:
    99    </p>
    1010    <ul>
     
    148148        </ul>
    149149        <p>
    150           It should be possible to use Oracle VM VirtualBox on most systems
     150          It should be possible to use <ph conkeyref="vbox-conkeyref-phrases/product-name"/> on most systems
    151151          based on Linux kernel 2.6, 3.x, 4.x or 5.x using either the
    152           Oracle VM VirtualBox installer or by doing a manual installation.
     152          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> installer or by doing a manual installation.
    153153          See <xref href="install-linux-host.dita#install-linux-host"/>. However, the
    154154          formally tested and supported Linux distributions are those
  • trunk/doc/manual/en_US/dita/topics/hostpowertweaks.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       Some host power management events are handled by Oracle VM VirtualBox.
     8      Some host power management events are handled by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    99      The actual behavior depends on the platform:
    1010    </p>
     
    1717        <p>
    1818          This event is currently only handled on Windows hosts and Mac
    19           OS X hosts. When this event is generated, Oracle VM VirtualBox will
     19          OS X hosts. When this event is generated, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will
    2020          pause all running VMs.
    2121        </p>
     
    2727        <p>
    2828          This event is currently only handled on Windows hosts and Mac
    29           OS X hosts. When this event is generated, Oracle VM VirtualBox will
     29          OS X hosts. When this event is generated, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will
    3030          resume all VMs which are where paused before.
    3131        </p>
     
    3838        <p>
    3939          This event is currently only handled on Windows hosts and Mac
    40           OS X hosts. When this event is generated, Oracle VM VirtualBox will
     40          OS X hosts. When this event is generated, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will
    4141          save the state and terminate all VMs in preparation of a
    4242          potential host powerdown.
  • trunk/doc/manual/en_US/dita/topics/hwvirt.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox enables software in the virtual machine to run
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables software in the virtual machine to run
    99      directly on the processor of the host, but an array of complex
    1010      techniques is employed to intercept operations that would
    1111      interfere with your host. Whenever the guest attempts to do
    1212      something that could be harmful to your computer and its data,
    13       Oracle VM VirtualBox steps in and takes action. In particular, for lots
     13      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> steps in and takes action. In particular, for lots
    1414      of hardware that the guest believes to be accessing,
    15       Oracle VM VirtualBox simulates a certain <i>virtual</i>
     15      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> simulates a certain <i>virtual</i>
    1616      environment according to how you have configured a virtual
    1717      machine. For example, when the guest attempts to access a hard
    18       disk, Oracle VM VirtualBox redirects these requests to whatever you have
     18      disk, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> redirects these requests to whatever you have
    1919      configured to be the virtual machine's virtual hard disk. This is
    2020      normally an image file on your host.
     
    2222    <p>
    2323      Unfortunately, the x86 platform was never designed to be
    24       virtualized. Detecting situations in which Oracle VM VirtualBox needs to
     24      virtualized. Detecting situations in which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> needs to
    2525      take control over the guest code that is executing, as described
    26       above, is difficult. To achieve this, Oracle VM VirtualBox uses
     26      above, is difficult. To achieve this, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses
    2727      <i>hardware virtualization</i>.
    2828    </p>
    2929    <p>
    3030      Intel and AMD processors have support for hardware virtualization.
    31       This means that these processors can help Oracle VM VirtualBox to
     31      This means that these processors can help <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to
    3232      intercept potentially dangerous operations that a guest operating
    3333      system may be attempting and also makes it easier to present
     
    4343      <p>
    4444        On many systems, the hardware virtualization features first need
    45         to be enabled in the BIOS before Oracle VM VirtualBox can use them.
     45        to be enabled in the BIOS before <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can use them.
    4646      </p>
    4747    </note>
     
    6161      <li>
    6262        <p>
    63           Oracle VM VirtualBox's 64-bit guest and multiprocessing (SMP)
     63          <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s 64-bit guest and multiprocessing (SMP)
    6464          support both require hardware virtualization to be enabled.
    6565          This is not much of a limitation since the vast majority of
     
    7373      <p>
    7474        Do not run other hypervisors, either open source or commercial
    75         virtualization products, together with Oracle VM VirtualBox. While
     75        virtualization products, together with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. While
    7676        several hypervisors can normally be
    7777        <i>installed</i> in parallel, do not attempt to
    7878        <i>run</i> several virtual machines from competing
    79         hypervisors at the same time. Oracle VM VirtualBox cannot track what
     79        hypervisors at the same time. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> cannot track what
    8080        another hypervisor is currently attempting to do on the same
    8181        host, and especially if several products attempt to use hardware
  • trunk/doc/manual/en_US/dita/topics/hyperv-support.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="hyperv-support">
    4   <title>Using Hyper-V with Oracle VM VirtualBox</title>
     4  <title>Using Hyper-V with <ph conkeyref="vbox-conkeyref-phrases/product-name"/></title>
    55 
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox can be used on a Windows host where Hyper-V is
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can be used on a Windows host where Hyper-V is
    99      running. This is an experimental feature.
    1010    </p>
    1111    <p>
    12       No configuration is required. Oracle VM VirtualBox detects Hyper-V
     12      No configuration is required. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> detects Hyper-V
    1313      automatically and uses Hyper-V as the virtualization engine for
    1414      the host system. The CPU icon in the VM window status bar
     
    1818      <p>
    1919        When using this feature, some host systems might experience
    20         significant Oracle VM VirtualBox performance degradation.
     20        significant <ph conkeyref="vbox-conkeyref-phrases/product-name"/> performance degradation.
    2121      </p>
    2222    </note>
  • trunk/doc/manual/en_US/dita/topics/import-instance-sequence.dita

    r98549 r99797  
    77    <p>
    88          The following describes the sequence of events when you import
    9           an instance from Oracle Cloud Infrastructure.
     9          an instance from <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
    1010        </p>
    1111    <ul>
     
    1818      <li>
    1919        <p>
    20               The custom image is exported to an Oracle Cloud Infrastructure object and is
     20              The custom image is exported to an <ph conkeyref="vbox-conkeyref-phrases/oci"/> object and is
    2121              stored using Object Storage in the bucket specified by the
    2222              user.
     
    2525      <li>
    2626        <p>
    27               The Oracle Cloud Infrastructure object is downloaded to the local host. The
     27              The <ph conkeyref="vbox-conkeyref-phrases/oci"/> object is downloaded to the local host. The
    2828              object is a TAR archive which contains a boot volume of
    2929              the instance in QCOW2 format and a JSON file containing
     
    3636              archive and a new VMDK image is created by converting the
    3737              boot volume into the VMDK format. The VMDK image is
    38               registered with Oracle VM VirtualBox.
     38              registered with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    3939            </p>
    4040      </li>
     
    4646        <p>
    4747              By default, the new VM is not started after import from
    48               Oracle Cloud Infrastructure.
     48              <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
    4949            </p>
    5050      </li>
  • trunk/doc/manual/en_US/dita/topics/install-ext-pack-manager.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="install-ext-pack-manager">
    44  <title>The Extension Pack Manager</title>
    5  
     5
    66  <body>
    77    <p>
    88        Extension packs can be installed and managed using the
    99        <b outputclass="bold">Extension Pack Manager</b> tool in
    10         VirtualBox Manager.
     10        <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.
    1111      </p>
    1212    <p>
     
    5050    </ol>
    5151    <p>
    52         Alternatively, you can use the <userinput>VBoxManage</userinput>
    53         command line to install and manage Oracle VM VirtualBox extension
    54         packs. See <xref href="vboxmanage-extpack.dita"/>.
    55       </p>
     52        Alternatively, you can use the <userinput>VBoxManage</userinput> command line to install and
     53        manage an <ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/>. See <xref href="vboxmanage-extpack.dita"/>.
     54    </p>
    5655  </body>
    57  
     56
    5857</topic>
  • trunk/doc/manual/en_US/dita/topics/install-ext-pack.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       Extension packs provide extra functionality to the Oracle VM VirtualBox
     8      Extension packs provide extra functionality to the <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    99      base package, such as extended USB device support and cloud
    1010      integration features. See <xref href="intro-installing.dita#intro-installing"/>.
    1111    </p>
    1212    <p>
    13       To install an Oracle VM VirtualBox extension pack, do the following:
     13      To install an <ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/>, do the following:
    1414    </p>
    1515    <ol>
     
    1919        </p>
    2020        <p>
    21           Oracle VM VirtualBox extension packs have a
     21          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> extension packs have a
    2222          <filepath>.vbox-extpack</filepath> file name extension.
    2323        </p>
  • trunk/doc/manual/en_US/dita/topics/install-linux-alt-installer.dita

    r98549 r99797  
    1919      <li>
    2020        <p>
    21               Builds and installs the Oracle VM VirtualBox kernel modules:
     21              Builds and installs the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> kernel modules:
    2222              <userinput>vboxdrv</userinput>, <userinput>vboxnetflt</userinput>,
    2323              and <userinput>vboxnetadp</userinput>.
     
    2727        <p>
    2828              Creates <filepath>/sbin/rcvboxdrv</filepath>, an init
    29               script to start the Oracle VM VirtualBox kernel module.
     29              script to start the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> kernel module.
    3030            </p>
    3131      </li>
  • trunk/doc/manual/en_US/dita/topics/install-linux-debian-automatic.dita

    r98549 r99797  
    2323    <p>
    2424          These default settings can be applied prior to the
    25           installation of the Oracle VM VirtualBox Debian package, as follows:
     25          installation of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Debian package, as follows:
    2626        </p>
    2727    <pre xml:space="preserve">debconf-set-selections vboxconf</pre>
  • trunk/doc/manual/en_US/dita/topics/install-linux-debian-ubuntu.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="install-linux-debian-ubuntu">
    4   <title>Installing Oracle VM VirtualBox from a Debian or Ubuntu Package</title>
     4  <title>Installing <ph conkeyref="vbox-conkeyref-phrases/product-name"/> from a Debian or Ubuntu Package</title>
    55 
    66  <body>
     
    3535        </p>
    3636    <p>
    37           Once Oracle VM VirtualBox has been successfully installed and
     37          Once <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has been successfully installed and
    3838          configured, you can start it by clicking
    3939          <b outputclass="bold">VirtualBox</b> in your
  • trunk/doc/manual/en_US/dita/topics/install-linux-manual.dita

    r98549 r99797  
    1414          This will unpack all the files needed for installation in the
    1515          directory <codeph>install</codeph> under the current
    16           directory. The Oracle VM VirtualBox application files are contained
     16          directory. The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> application files are contained
    1717          in <filepath>VirtualBox.tar.bz2</filepath> which you can
    1818          unpack to any directory on your system. For example:
     
    2626tar jxf ./install/VirtualBox.tar.bz2 -C /opt/VirtualBox</pre>
    2727    <p>
    28           The sources for Oracle VM VirtualBox's kernel module are provided in
     28          The sources for <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s kernel module are provided in
    2929          the <filepath>src</filepath> directory. To build the module,
    3030          change to the directory and use the following command:
     
    4242    <pre xml:space="preserve">make install</pre>
    4343    <p>
    44           The Oracle VM VirtualBox kernel module needs a device node to
     44          The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> kernel module needs a device node to
    4545          operate. The above <userinput>make</userinput> command will tell
    4646          you how to create the device node, depending on your Linux
     
    6969    <pre xml:space="preserve">cp /opt/VirtualBox/vboxdrv.sh /sbin/rcvboxdrv</pre>
    7070    <p>
    71           This example assumes you installed Oracle VM VirtualBox to the
     71          This example assumes you installed <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to the
    7272          <filepath>/opt/VirtualBox</filepath> directory.
    7373        </p>
    7474    <p>
    75           Create a configuration file for Oracle VM VirtualBox, as follows:
     75          Create a configuration file for <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, as follows:
    7676        </p>
    7777    <pre xml:space="preserve">mkdir /etc/vbox
  • trunk/doc/manual/en_US/dita/topics/install-linux-performing.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         Oracle VM VirtualBox is available in a number of package formats
     8        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is available in a number of package formats
    99        native to various common Linux distributions. See
    1010        <xref href="hostossupport.dita#hostossupport"/>. In addition, there is an
  • trunk/doc/manual/en_US/dita/topics/install-linux-prereq.dita

    r98549 r99797  
    1212        You may need to install the following packages on your Linux
    1313        system before starting the installation. Some systems will do
    14         this for you automatically when you install Oracle VM VirtualBox.
     14        this for you automatically when you install <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    1515      </p>
    1616    <ul>
     
    3030      <p>
    3131          These packages are only required if you want to run the
    32           Oracle VM VirtualBox graphical user interfaces. In particular,
     32          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> graphical user interfaces. In particular,
    3333          <userinput>VirtualBox</userinput>, the graphical VirtualBox
    3434          Manager, requires both Qt and SDL. If you only want to run
  • trunk/doc/manual/en_US/dita/topics/install-linux-rpm-automatic.dita

    r98549 r99797  
    99          comparable to the debconf system. See
    1010          <xref href="linux_install_opts.dita#linux_install_opts"/> for how to set some
    11           common installation options provided by Oracle VM VirtualBox.
     11          common installation options provided by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    1212        </p>
    1313  </body>
  • trunk/doc/manual/en_US/dita/topics/install-linux-update-uninstall.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="install-linux-update-uninstall">
    4   <title>Updating and Uninstalling Oracle VM VirtualBox</title>
     4  <title>Updating and Uninstalling <ph conkeyref="vbox-conkeyref-phrases/product-name"/></title>
    55 
    66  <body>
    77    <p>
    8           Before updating or uninstalling Oracle VM VirtualBox, you must
     8          Before updating or uninstalling <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, you must
    99          terminate any virtual machines which are currently running and
    10           exit the Oracle VM VirtualBox or VBoxSVC applications. To update
    11           Oracle VM VirtualBox, simply run the installer of the updated
    12           version. To uninstall Oracle VM VirtualBox, run the installer as
     10          exit the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> or VBoxSVC applications. To update
     11          <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, simply run the installer of the updated
     12          version. To uninstall <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, run the installer as
    1313          follows:
    1414        </p>
     
    2323    <pre xml:space="preserve">/opt/VirtualBox/uninstall.sh</pre>
    2424    <p>
    25           To manually uninstall Oracle VM VirtualBox, perform the manual
     25          To manually uninstall <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, perform the manual
    2626          installation steps in reverse order.
    2727        </p>
  • trunk/doc/manual/en_US/dita/topics/install-linux-vboxusers.dita

    r98549 r99797  
    88        The Linux installers create the system user group
    99        <codeph>vboxusers</codeph> during installation. Any system
    10         user who is going to use USB devices from Oracle VM VirtualBox guests
     10        user who is going to use USB devices from <ph conkeyref="vbox-conkeyref-phrases/product-name"/> guests
    1111        must be a member of that group. A user can be made a member of
    1212        the group <codeph>vboxusers</codeph> either by using the
  • trunk/doc/manual/en_US/dita/topics/install-mac-performing.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         For macOS hosts, Oracle VM VirtualBox ships in a
     8        For macOS hosts, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> ships in a
    99        <filepath>dmg</filepath> disk image file. Perform the following
    1010        steps to install on a macOS host:
     
    2727        <p>
    2828            This starts the installer, which enables you to select where
    29             to install Oracle VM VirtualBox.
     29            to install <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    3030          </p>
    3131      </li>
    3232      <li>
    3333        <p>
    34             An Oracle VM VirtualBox icon is added to the
     34            An <ph conkeyref="vbox-conkeyref-phrases/product-name"/> icon is added to the
    3535            <filepath>Applications</filepath> folder in the Finder.
    3636          </p>
  • trunk/doc/manual/en_US/dita/topics/install-mac-unattended.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         To perform a non-interactive installation of Oracle VM VirtualBox you
     8        To perform a non-interactive installation of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> you
    99        can use the command line version of the installer application.
    1010      </p>
  • trunk/doc/manual/en_US/dita/topics/install-mac-uninstall.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         To uninstall Oracle VM VirtualBox, open the disk image
     8        To uninstall <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, open the disk image
    99        <filepath>dmg</filepath> file and double-click on the uninstall
    1010        icon shown.
  • trunk/doc/manual/en_US/dita/topics/install-solaris-host.dita

    r98549 r99797  
    1010    </p>
    1111    <p>
    12       If you have a previously installed instance of Oracle VM VirtualBox on
     12      If you have a previously installed instance of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> on
    1313      your Oracle Solaris host, please uninstall it first before
    1414      installing a new instance. See
  • trunk/doc/manual/en_US/dita/topics/install-solaris-performing.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         Oracle VM VirtualBox is available as a standard Oracle Solaris
    9         package. Download the Oracle VM VirtualBox SunOS package, which
    10         includes the 64-bit version of Oracle VM VirtualBox. <i>The
     8        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is available as a standard Oracle Solaris
     9        package. Download the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> SunOS package, which
     10        includes the 64-bit version of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. <i>The
    1111        installation must be performed as root and from the global
    12         zone</i>. This is because the Oracle VM VirtualBox installer
     12        zone</i>. This is because the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> installer
    1313        loads kernel drivers, which cannot be done from non-global
    1414        zones. To verify which zone you are currently in, execute the
     
    2020    <pre xml:space="preserve">gunzip -cd VirtualBox-<varname>version-number</varname>-SunOS.tar.gz | tar xvf -</pre>
    2121    <p>
    22         The Oracle VM VirtualBox kernel package is integrated into the main
    23         package. Install the Oracle VM VirtualBox package as follows:
     22        The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> kernel package is integrated into the main
     23        package. Install the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> package as follows:
    2424      </p>
    2525    <pre xml:space="preserve">pkgadd -d VirtualBox-<varname>version-number</varname>-SunOS.pkg</pre>
     
    3131        script to be executed. Choose <b outputclass="bold">y</b>
    3232        and proceed, as it is essential to execute this script which
    33         installs the Oracle VM VirtualBox kernel module. Following this
    34         confirmation the installer will install Oracle VM VirtualBox and
     33        installs the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> kernel module. Following this
     34        confirmation the installer will install <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and
    3535        execute the postinstall setup script.
    3636      </p>
     
    3939        is now complete. You may now safely delete the uncompressed
    4040        package and <filepath>autoresponse</filepath> files from your
    41         system. Oracle VM VirtualBox is installed in
     41        system. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is installed in
    4242        <filepath>/opt/VirtualBox</filepath>.
    4343      </p>
    4444    <note>
    4545      <p>
    46           If you need to use Oracle VM VirtualBox from non-global zones, see
     46          If you need to use <ph conkeyref="vbox-conkeyref-phrases/product-name"/> from non-global zones, see
    4747          <xref href="solaris-zones.dita#solaris-zones"/>.
    4848        </p>
  • trunk/doc/manual/en_US/dita/topics/install-solaris-starting.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="install-solaris-starting">
    4   <title>Starting Oracle VM VirtualBox on Oracle Solaris</title>
     4  <title>Starting <ph conkeyref="vbox-conkeyref-phrases/product-name"/> on Oracle Solaris</title>
    55 
    66  <body>
    77    <p>
    8         The easiest way to start an Oracle VM VirtualBox program is by running
     8        The easiest way to start an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> program is by running
    99        the program of your choice (<userinput>VirtualBox</userinput>,
    1010        <userinput>VBoxManage</userinput>, or
  • trunk/doc/manual/en_US/dita/topics/install-solaris-unattended.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         To perform a non-interactive installation of Oracle VM VirtualBox
     8        To perform a non-interactive installation of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    99        there is a response file named
    1010        <filepath>autoresponse</filepath>. The installer uses this for
  • trunk/doc/manual/en_US/dita/topics/install-solaris-vboxuser.dita

    r98549 r99797  
    99        <codeph>vboxuser</codeph> during installation for Oracle
    1010        Solaris hosts that support the USB features required by
    11         Oracle VM VirtualBox. Any system user who is going to use USB devices
    12         from Oracle VM VirtualBox guests must be a member of this group. A
     11        <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. Any system user who is going to use USB devices
     12        from <ph conkeyref="vbox-conkeyref-phrases/product-name"/> guests must be a member of this group. A
    1313        user can be made a member of this group either by using the
    1414        desktop user and group tools or by running the following command
  • trunk/doc/manual/en_US/dita/topics/install-win-performing.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         The Oracle VM VirtualBox installation can be started in either of the
     8        The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> installation can be started in either of the
    99        following ways:
    1010      </p>
     
    3131        Using either way displays the installation
    3232        <b outputclass="bold">Welcome</b> dialog and enables you
    33         to choose where to install Oracle VM VirtualBox, and which components
    34         to install. In addition to the Oracle VM VirtualBox application, the
     33        to choose where to install <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, and which components
     34        to install. In addition to the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> application, the
    3535        following components are available:
    3636      </p>
     
    3939        <p><b outputclass="bold">USB support.</b> This package
    4040            contains special drivers for your Windows host that
    41             Oracle VM VirtualBox requires to fully support USB devices inside
     41            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> requires to fully support USB devices inside
    4242            your virtual machines.
    4343          </p>
     
    4646        <p><b outputclass="bold">Networking.</b> This package
    4747            contains extra networking drivers for your Windows host that
    48             Oracle VM VirtualBox needs to support Bridged Networking. This
     48            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> needs to support Bridged Networking. This
    4949            enables your VM's virtual network cards to be accessed from
    5050            other machines on your physical network.
     
    5454        <p><b outputclass="bold">Python support.</b> This
    5555            package contains Python scripting support for the
    56             Oracle VM VirtualBox API, see <xref href="VirtualBoxAPI.dita">Oracle VM VirtualBox Programming Interfaces</xref>.
     56            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> API, see <xref href="VirtualBoxAPI.dita"><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Programming Interfaces</xref>.
    5757            For this to work, an already working Windows Python
    5858            installation on the system is required.
     
    7474        about unsigned drivers, or similar. Click
    7575        <b outputclass="bold">Continue</b> for these warnings, as
    76         otherwise Oracle VM VirtualBox might not function correctly after
     76        otherwise <ph conkeyref="vbox-conkeyref-phrases/product-name"/> might not function correctly after
    7777        installation.
    7878      </p>
    7979    <p>
    80         The installer will create an Oracle VM VirtualBox group in the Windows
     80        The installer will create an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> group in the Windows
    8181        <b outputclass="bold">Start</b> menu, which enables you
    8282        to launch the application and access its documentation.
    8383      </p>
    8484    <p>
    85         With standard settings, Oracle VM VirtualBox will be installed for all
     85        With standard settings, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will be installed for all
    8686        users on the local system. If this is not wanted, you must
    8787        invoke the installer by first extracting as follows:
     
    9090    <p>
    9191        Then, run either of the following commands on the extracted .MSI
    92         file. This will install Oracle VM VirtualBox only for the current
     92        file. This will install <ph conkeyref="vbox-conkeyref-phrases/product-name"/> only for the current
    9393        user.
    9494      </p>
     
    9696    <pre xml:space="preserve">msiexec /i VirtualBox-&lt;version&gt;-Win.msi ALLUSERS=2</pre>
    9797    <p>
    98         If you do not want to install all features of Oracle VM VirtualBox,
     98        If you do not want to install all features of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>,
    9999        you can set the optional <codeph>ADDLOCAL</codeph> parameter
    100100        to explicitly name the features to be installed. The following
     
    108108        <dd>
    109109          <p>
    110               Main binaries of Oracle VM VirtualBox.
     110              Main binaries of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    111111            </p>
    112112          <note>
    113113            <p>
    114114                This feature must not be absent, since it contains the
    115                 minimum set of files to have working Oracle VM VirtualBox
     115                minimum set of files to have working <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    116116                installation.
    117117              </p>
  • trunk/doc/manual/en_US/dita/topics/install-win-public-props.dita

    r98549 r99797  
    2121          </p>
    2222        <p>
    23             Specifies whether or not an Oracle VM VirtualBox icon on the
     23            Specifies whether or not an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> icon on the
    2424            desktop should be created.
    2525          </p>
     
    3434          </p>
    3535        <p>
    36             Specifies whether or not an Oracle VM VirtualBox icon in the Quick
     36            Specifies whether or not an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> icon in the Quick
    3737            Launch Bar should be created.
    3838          </p>
     
    4949            Specifies whether or not the file extensions .vbox,
    5050            .vbox-extpack, .ovf, .ova, .vdi, .vmdk, .vhd and .vdd should
    51             be associated with Oracle VM VirtualBox. Files of these types then
    52             will be opened with Oracle VM VirtualBox.
     51            be associated with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. Files of these types then
     52            will be opened with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    5353          </p>
    5454        <p>
     
    6262          </p>
    6363        <p>
    64             Specifies whether to start Oracle VM VirtualBox right after
     64            Specifies whether to start <ph conkeyref="vbox-conkeyref-phrases/product-name"/> right after
    6565            successful installation.
    6666          </p>
  • trunk/doc/manual/en_US/dita/topics/install-win-uninstall.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         As Oracle VM VirtualBox uses the standard Microsoft Windows installer,
    9         Oracle VM VirtualBox can be safely uninstalled at any time. Click the
     8        As <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses the standard Microsoft Windows installer,
     9        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can be safely uninstalled at any time. Click the
    1010        program entry in the <b outputclass="bold">Add/Remove
    1111        Programs</b> list in the Windows Control Panel.
  • trunk/doc/manual/en_US/dita/topics/installation.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8     As installation of Oracle VM VirtualBox varies depending on your host
     8    As installation of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> varies depending on your host
    99    operating system, the following sections provide installation
    1010    instructions for Windows, macOS, Linux, and Oracle Solaris.
  • trunk/doc/manual/en_US/dita/topics/intro-64bitguests.dita

    r98549 r99797  
    1919    <p>
    2020        If you use the <b outputclass="bold">Create VM</b> wizard
    21         of VirtualBox Manager, Oracle VM VirtualBox automatically uses the correct
     21        of <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> automatically uses the correct
    2222        settings for each selected 64-bit OS type. See
    2323        <xref href="create-vm-wizard.dita#create-vm-wizard"/>.
  • trunk/doc/manual/en_US/dita/topics/intro-installing.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="intro-installing">
    4   <title>Installing Oracle VM VirtualBox and Extension Packs</title>
     4  <title>Installing <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and Extension Packs</title>
    55 
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox comes in many different packages, and installation
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> comes in many different packages, and installation
    99      depends on your host OS. If you have installed software before,
    1010      installation should be straightforward. On each host platform,
    11       Oracle VM VirtualBox uses the installation method that is most common
     11      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses the installation method that is most common
    1212      and easy to use. If you run into trouble or have special
    1313      requirements, see <xref href="installation.dita#installation"/> for details
     
    1515    </p>
    1616    <p>
    17       Oracle VM VirtualBox is split into the following components:
     17      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is split into the following components:
    1818    </p>
    1919    <ul>
     
    2727        <p><b outputclass="bold">Extension packs.</b> Additional
    2828          extension packs can be downloaded which extend the
    29           functionality of the Oracle VM VirtualBox base package. Currently,
     29          functionality of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> base package. Currently,
    3030          Oracle provides a single extension pack, available from:
    3131          <ph>http://www.virtualbox.org</ph>. The extension pack
  • trunk/doc/manual/en_US/dita/topics/intro-macosxguests.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         Oracle VM VirtualBox enables you to install and execute unmodified
     8        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to install and execute unmodified
    99        versions of Mac OS X guests on supported host hardware. Note
    1010        that this feature is experimental and thus unsupported.
    1111      </p>
    1212    <p>
    13         Oracle VM VirtualBox is the first product to provide the modern PC
     13        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is the first product to provide the modern PC
    1414        architecture expected by OS X without requiring any of the
    1515        modifications used by competing virtualization solutions. For
     
    4040            hardware. Most DVDs that accompany Apple hardware check for
    4141            the exact model. These restrictions are
    42             <i>not</i> circumvented by Oracle VM VirtualBox and
     42            <i>not</i> circumvented by <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and
    4343            continue to apply.
    4444          </p>
     
    6969      <li>
    7070        <p>
    71             In addition, Mac OS X support in Oracle VM VirtualBox is an
     71            In addition, Mac OS X support in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is an
    7272            experimental feature. See <xref href="KnownIssues.dita">Known Limitations</xref>.
    7373          </p>
  • trunk/doc/manual/en_US/dita/topics/intro-removable-media-changing.dita

    r98549 r99797  
    99        media in the <b outputclass="bold">Devices</b> menu of
    1010        the VM's window. Here you can select in detail what
    11         Oracle VM VirtualBox presents to your VM as a CD, DVD, or floppy
     11        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents to your VM as a CD, DVD, or floppy
    1212        drive.
    1313      </p>
    1414    <p>
    1515        The settings are the same as those available for the VM in the
    16         <b outputclass="bold">Settings</b> window of VirtualBox Manager.
     16        <b outputclass="bold">Settings</b> window of <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.
    1717        But as the <b outputclass="bold">Settings</b> window is
    1818        disabled while the VM is in the Running or Saved state, the
  • trunk/doc/manual/en_US/dita/topics/intro-removing.dita

    r99497 r99797  
    66  <body>
    77    <p>
    8       You can remove a VM from Oracle VM VirtualBox or move the VM and its
     8      You can remove a VM from <ph conkeyref="vbox-conkeyref-phrases/product-name"/> or move the VM and its
    99      associated files, such as disk images, to another location on the
    1010      host.
     
    1313      <li>
    1414        <p><b outputclass="bold">Removing a VM.</b> To remove a
    15           VM, right-click on the VM in the VirtualBox Manager machine list and
     15          VM, right-click on the VM in the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> machine list and
    1616          select <b outputclass="bold">Remove</b>.
    1717        </p>
     
    2929        <p><b outputclass="bold">Moving a VM.</b> To move a VM to
    3030          a new location on the host, right-click on the VM in the
    31           VirtualBox Manager's machine list and select
     31          <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>'s machine list and select
    3232          <b outputclass="bold">Move</b>.
    3333        </p>
     
    3737        </p>
    3838        <p>
    39           When you move a VM, Oracle VM VirtualBox configuration files are
     39          When you move a VM, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> configuration files are
    4040          updated automatically to use the new location on the host.
    4141        </p>
     
    4444          is disabled while a VM is running.
    4545        </p>
    46         <p>
    47           You can also use the <userinput>VBoxManage movevm</userinput>
    48           command to move a VM. See <xref href="vboxmanage-movevm.dita"/>.
    49         </p>
     46        <p> You can also use the <userinput>VBoxManage movevm</userinput> command to move a VM. See
     47            <xref href="vboxmanage-movevm.dita"/>. </p>
    5048      </li>
    5149    </ul>
    5250    <p>
    5351      For information about removing or moving a disk image file from
    54       Oracle VM VirtualBox, see <xref href="virtual-media-manager.dita#virtual-media-manager"/>.
     52      <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, see <xref href="virtual-media-manager.dita#virtual-media-manager"/>.
    5553    </p>
    5654  </body>
  • trunk/doc/manual/en_US/dita/topics/intro-running.dita

    r98549 r99797  
    1212        <p>
    1313          Double-click on the VM's entry in the machine list in
    14           VirtualBox Manager.
     14          <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.
    1515        </p>
    1616      </li>
    1717      <li>
    1818        <p>
    19           Select the VM's entry in the machine list in VirtualBox Manager, and
     19          Select the VM's entry in the machine list in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, and
    2020          click <b outputclass="bold">Start</b> in the toolbar
    2121          the top of the window.
  • trunk/doc/manual/en_US/dita/topics/intro-save-machine-state.dita

    r99182 r99797  
    99        button of your virtual machine window, at the top right of the
    1010        window, just like you would close any other window on your
    11         system, Oracle VM VirtualBox asks you whether you want to save or
     11        system, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> asks you whether you want to save or
    1212        power off the VM. As a shortcut, you can also press
    1313        <b outputclass="bold">Host key + Q</b>.
     
    3131      <li>
    3232        <p><b outputclass="bold">Save the machine state:</b>
    33             With this option, Oracle VM VirtualBox
     33            With this option, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    3434            <i>freezes</i> the virtual machine by
    3535            completely saving its state to your local disk.
     
    5353      <li>
    5454        <p><b outputclass="bold">Power off the machine:</b> With
    55             this option, Oracle VM VirtualBox also stops running the virtual
     55            this option, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also stops running the virtual
    5656            machine, but <i>without</i> saving its state.
    5757          </p>
     
    8080    <p>
    8181        The <b outputclass="bold">Discard</b> button in the
    82         VirtualBox Manager window discards a virtual machine's saved state. This
     82        <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> window discards a virtual machine's saved state. This
    8383        has the same effect as powering it off, and the same warnings
    8484        apply.
  • trunk/doc/manual/en_US/dita/topics/intro-starting.dita

    r98549 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="intro-starting">
    4   <title>Starting Oracle VM VirtualBox</title>
     4  <title>Starting <ph conkeyref="vbox-conkeyref-phrases/product-name"/></title>
    55 
    66  <body>
    77    <p>
    8       After installation, you can start Oracle VM VirtualBox as follows:
     8      After installation, you can start <ph conkeyref="vbox-conkeyref-phrases/product-name"/> as follows:
    99    </p>
    1010    <ul>
     
    2929        <p><b outputclass="bold">Linux or Oracle Solaris
    3030          hosts</b>. Depending on your desktop environment, an
    31           Oracle VM VirtualBox item may have been placed in either the System
     31          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> item may have been placed in either the System
    3232          or System Tools group of your
    3333          <b outputclass="bold">Applications</b> menu.
     
    3838    </ul>
    3939    <p>
    40       When you start Oracle VM VirtualBox, the VirtualBox Manager interface is shown.
     40      When you start <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> interface is shown.
    4141      See <xref href="gui-virtualboxmanager.dita#gui-virtualboxmanager"/>.
    4242    </p>
  • trunk/doc/manual/en_US/dita/topics/iocaching.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="iocaching">
    44  <title>Host Input/Output Caching</title>
    5  
     5
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox can optionally disable the I/O caching that the
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can optionally disable the I/O caching that the
    99      host OS would otherwise perform on disk image files.
    1010    </p>
    1111    <p>
    12       Traditionally, Oracle VM VirtualBox has opened disk image files as
     12      Traditionally, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has opened disk image files as
    1313      normal files, which results in them being cached by the host OS
    1414      like any other file. The main advantage of this is speed: when the
     
    6666    <p>
    6767      If you decide to disable host I/O caching for the above reasons,
    68       Oracle VM VirtualBox uses its own small cache to buffer writes, but no
     68      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses its own small cache to buffer writes, but no
    6969      read caching since this is typically already performed by the
    70       guest OS. In addition, Oracle VM VirtualBox fully supports asynchronous
     70      guest OS. In addition, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> fully supports asynchronous
    7171      I/O for its virtual SATA, SCSI, and SAS controllers through
    7272      multiple I/O threads.
     
    7878    </p>
    7979    <p>
    80       For this reason, Oracle VM VirtualBox enables you to configure whether
     80      For this reason, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to configure whether
    8181      the host I/O cache is used for each I/O controller separately.
    8282      Either select the <b outputclass="bold">Use Host I/O
     
    9292    </p>
    9393    <p>
    94       For the above reasons, Oracle VM VirtualBox uses SATA controllers by
     94      For the above reasons, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses SATA controllers by
    9595      default for new virtual machines.
    9696    </p>
    9797  </body>
    98  
     98
    9999</topic>
  • trunk/doc/manual/en_US/dita/topics/iscsi-intnet.dita

    r99497 r99797  
    66  <body>
    77    <p>
    8         As an experimental feature, Oracle VM VirtualBox enables access to an
     8        As an experimental feature, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables access to an
    99        iSCSI target running in a virtual machine which is configured to
    1010        use Internal Networking mode. See
  • trunk/doc/manual/en_US/dita/topics/keyb_mouse_normal.dita

    r99182 r99797  
    66  <body>
    77    <p>
    8         Oracle VM VirtualBox provides a virtual USB tablet device to new
     8        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides a virtual USB tablet device to new
    99        virtual machines through which mouse events are communicated to
    1010        the guest OS. If you are running a modern guest OS that can
     
    3434    <p>
    3535        To return ownership of keyboard and mouse to your host OS,
    36         Oracle VM VirtualBox reserves a special key on your keyboard: the
     36        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> reserves a special key on your keyboard: the
    3737        <i>Host key</i>. By default, this is the
    3838        <i>right Ctrl key</i> on your keyboard. On a Mac
     
    104104    </ul>
    105105    <p>
    106         As this behavior is inconvenient, Oracle VM VirtualBox provides a set
     106        As this behavior is inconvenient, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides a set
    107107        of tools and device drivers for guest systems called the
    108         Oracle VM VirtualBox Guest Additions. These tools make VM keyboard and
     108        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions. These tools make VM keyboard and
    109109        mouse operations much more seamless. Most importantly, the Guest
    110110        Additions suppress the second "guest" mouse pointer and make
  • trunk/doc/manual/en_US/dita/topics/legacy-fullscreen-mode.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         Oracle VM VirtualBox uses special window manager facilities to switch
     8        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses special window manager facilities to switch
    99        a multi-screen machine to full-screen on a multi-monitor host
    1010        system. However, not all window managers provide these
    11         facilities correctly. Oracle VM VirtualBox can be configured to use a
     11        facilities correctly. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can be configured to use a
    1212        legacy method of switching to full-screen mode instead, by using
    1313        the command:
  • trunk/doc/manual/en_US/dita/topics/linux-guest-manual-setup.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         The Oracle VM VirtualBox Guest Additions contain several different
     8        The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions contain several different
    99        drivers. If you do not want to configure them all, use the
    1010        following command to install the Guest Additions:
  • trunk/doc/manual/en_US/dita/topics/log-viewer.dita

    r99182 r99797  
    66  <body>
    77    <p>
    8       Every time you start up a VM, Oracle VM VirtualBox creates a log file
     8      Every time you start up a VM, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates a log file
    99      that records system configuration and events. The
    10       <b outputclass="bold">Log Viewer</b> is a VirtualBox Manager tool
     10      <b outputclass="bold">Log Viewer</b> is a <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> tool
    1111      that enables you to view and analyze system logs.
    1212    </p>
     
    4444      Log messages for the VM are displayed in tabs in the Log Viewer
    4545      window. See <xref href="collect-debug-info.dita">Collecting Debugging Information</xref> for details of
    46       the various log files generated by Oracle VM VirtualBox.
     46      the various log files generated by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    4747    </p>
    4848    <p>
     
    6868        <p><b outputclass="bold">Filter:</b> Uses filter terms to
    6969          display specific types of log messages. Common log message
    70           terms used by Oracle VM VirtualBox, such as Audio and NAT, are
     70          terms used by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, such as Audio and NAT, are
    7171          included by default. Select one or more terms from the
    7272          drop-down list. To add your own filter term, enter the text
  • trunk/doc/manual/en_US/dita/topics/max-resolution-guests.dita

    r98549 r99797  
    88    <p>
    99        When guest systems with the Guest Additions installed are
    10         started using the graphical frontend, the normal Oracle VM VirtualBox
     10        started using the graphical frontend, the normal <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    1111        application, they will not be allowed to use screen resolutions
    1212        greater than the host's screen size unless the user manually
  • trunk/doc/manual/en_US/dita/topics/mountingadditionsiso.dita

    r98549 r99797  
    77    <p>
    88          In the <b outputclass="bold">Devices</b> menu in the
    9           virtual machine's menu bar, Oracle VM VirtualBox has a menu item
     9          virtual machine's menu bar, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has a menu item
    1010          <b outputclass="bold">Insert Guest Additions CD
    1111          Image</b>, which mounts the Guest Additions ISO file
     
    6464          <li>
    6565            <p>
    66                   On a Windows host, this file is in the Oracle VM VirtualBox
     66                  On a Windows host, this file is in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    6767                  installation directory, usually in
    6868                  <filepath>C:\Program
     
    7373            <p>
    7474                  On macOS hosts, this file is in the application bundle
    75                   of Oracle VM VirtualBox. Right-click on the Oracle VM VirtualBox
     75                  of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. Right-click on the <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    7676                  icon in Finder and choose <b outputclass="bold">Show
    7777                  Package Contents</b>. The file is located in
     
    8383                  On a Linux host, this file is in the
    8484                  <filepath>additions</filepath> folder where you
    85                   installed Oracle VM VirtualBox, usually
     85                  installed <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, usually
    8686                  <filepath>/opt/VirtualBox/</filepath>.
    8787                </p>
     
    9191                  On Oracle Solaris hosts, this file is in the
    9292                  <filepath>additions</filepath> folder where you
    93                   installed Oracle VM VirtualBox, usually
     93                  installed <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, usually
    9494                  <filepath>/opt/VirtualBox</filepath>.
    9595                </p>
     
    108108    <p>
    109109          Unless you have the Autostart feature disabled in your Windows
    110           guest, Windows will now autostart the Oracle VM VirtualBox Guest
     110          guest, Windows will now autostart the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest
    111111          Additions installation program from the Additions ISO. If the
    112112          Autostart feature has been turned off, choose
  • trunk/doc/manual/en_US/dita/topics/mouse-capture.dita

    r98549 r99797  
    99        guest window and the guest expects relative mouse coordinates at
    1010        this time. This happens if the pointing device is configured as
    11         PS/2 mouse and the guest has not yet started the Oracle VM VirtualBox
     11        PS/2 mouse and the guest has not yet started the <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    1212        Guest Additions. For instance, the guest is booting or the Guest
    1313        Additions are not installed, or if the pointing device is
  • trunk/doc/manual/en_US/dita/topics/nat-adv-settings.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         The Oracle VM VirtualBox NAT stack performance is often determined by
     8        The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> NAT stack performance is often determined by
    99        its interaction with the host's TCP/IP stack and the size of
    1010        several buffers, <codeph>SO_RCVBUF</codeph> and
  • trunk/doc/manual/en_US/dita/topics/nat-adv-tftp.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         For network booting in NAT mode, by default Oracle VM VirtualBox uses
     8        For network booting in NAT mode, by default <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses
    99        a built-in TFTP server at the IP address 10.0.2.4. This default
    1010        behavior should work fine for typical remote-booting scenarios.
  • trunk/doc/manual/en_US/dita/topics/nat-bind-sockets.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         By default, Oracle VM VirtualBox's NAT engine will route TCP/IP
     8        By default, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s NAT engine will route TCP/IP
    99        packets through the default interface assigned by the host's
    1010        TCP/IP stack. The technical reason for this is that the NAT
  • trunk/doc/manual/en_US/dita/topics/nat-limitations.dita

    r98549 r99797  
    1515            <userinput>ping</userinput> or <userinput>traceroute</userinput>,
    1616            rely on the ICMP protocol for sending and receiving
    17             messages. Oracle VM VirtualBox ICMP support has some limitations,
     17            messages. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> ICMP support has some limitations,
    1818            meaning <userinput>ping</userinput> should work but some other
    1919            tools may not work reliably.
  • trunk/doc/manual/en_US/dita/topics/nat_host_resolver_proxy.dita

    r98549 r99797  
    99        offers a list of registered DNS servers of the host. If for some
    1010        reason you need to hide this DNS server list and use the host's
    11         resolver settings, thereby forcing the Oracle VM VirtualBox NAT engine
     11        resolver settings, thereby forcing the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> NAT engine
    1212        to intercept DNS requests and forward them to host's resolver,
    1313        use the following command:
  • trunk/doc/manual/en_US/dita/topics/natforward.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="natforward">
    44  <title>Configuring Port Forwarding with NAT</title>
    5  
     5
    66  <body>
    77    <p>
    88        As the virtual machine is connected to a private network
    9         internal to Oracle VM VirtualBox and invisible to the host, network
     9        internal to <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and invisible to the host, network
    1010        services on the guest are not accessible to the host machine or
    1111        to other computers on the same network. However, like a physical
    12         router, Oracle VM VirtualBox can make selected services available to
     12        router, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can make selected services available to
    1313        the world outside the guest through <i>port
    14         forwarding</i>. This means that Oracle VM VirtualBox listens to
     14        forwarding</i>. This means that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> listens to
    1515        certain ports on the host and resends all packets which arrive
    1616        there to the guest, on the same or a different port.
     
    3636      </p>
    3737    <p>
    38         Alternatively, the command line tool
    39         <userinput>VBoxManage</userinput> can be used. See
     38        Alternatively, the command line tool <userinput>VBoxManage</userinput> can be used. See
    4039        <xref href="vboxmanage-modifyvm.dita"/>.
    41       </p>
     40    </p>
    4241    <p>
    4342        You will need to know which ports on the guest the service uses
     
    8988      </p>
    9089    <p>
    91         It is possible to configure incoming NAT connections while the
    92         VM is running, see <xref href="vboxmanage-controlvm.dita"/>.
    93       </p>
     90        It is possible to configure incoming NAT connections while the VM is running, see <xref
     91        href="vboxmanage-controlvm.dita"/>.
     92    </p>
    9493  </body>
    95  
     94
    9695</topic>
  • trunk/doc/manual/en_US/dita/topics/nested-virt.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="nested-virt">
    44  <title>Nested Virtualization</title>
    5  
     5
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox supports <i>nested
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports <i>nested
    99      virtualization</i>. This feature enables the passthrough of
    1010      hardware virtualization functions to the guest VM. That means that
    11       you can install a hypervisor, such as Oracle VM VirtualBox, Oracle VM
    12       Server or KVM, on an Oracle VM VirtualBox guest. You can then create and
     11      you can install a hypervisor, such as <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, Oracle VM
     12      Server or KVM, on an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> guest. You can then create and
    1313      run VMs within the guest VM.
    1414    </p>
     
    2525      <li>
    2626        <p>
    27           From VirtualBox Manager, select the <b outputclass="bold">Enable
     27          From <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, select the <b outputclass="bold">Enable
    2828          Nested VT-x/AMD-V</b> check box on the
    2929          <b outputclass="bold">Processor</b> tab. To disable the
     
    3333      <li>
    3434        <p>
    35           Use the <codeph>--nested-hw-virt</codeph> option of the
    36           <userinput>VBoxManage modifyvm</userinput> command to enable or
    37           disable nested virtualization. See
     35          Use the <codeph>--nested-hw-virt</codeph> option of the <userinput>VBoxManage
     36          modifyvm</userinput> command to enable or disable nested virtualization. See
    3837          <xref href="vboxmanage-modifyvm.dita">VBoxManage modifyvm</xref>.
    3938        </p>
     
    4140    </ul>
    4241  </body>
    43  
     42
    4443</topic>
  • trunk/doc/manual/en_US/dita/topics/nestedpaging.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="nestedpaging">
    44  <title>Nested Paging and VPIDs</title>
    5  
     5
    66  <body>
    77    <p>
     
    4242        </p>
    4343        <p>
    44           If nested paging is enabled, the Oracle VM VirtualBox hypervisor can
    45           also use <i>large pages</i> to reduce TLB usage
    46           and overhead. This can yield a performance improvement of up
    47           to 5%. To enable this feature for a VM, you use the
    48           <userinput>VBoxManage modifyvm --large-pages</userinput> command.
    49           See <xref href="vboxmanage-modifyvm.dita">VBoxManage modifyvm</xref>.
     44          If nested paging is enabled, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> hypervisor can also use <i>large
     45          pages</i> to reduce TLB usage and overhead. This can yield a performance improvement of
     46          up to 5%. To enable this feature for a VM, you use the <userinput>VBoxManage modifyvm --large-pages</userinput>
     47          command. See <xref href="vboxmanage-modifyvm.dita">VBoxManage
     48          modifyvm</xref>.
    5049        </p>
    5150        <p>
     
    6261          Translation Lookaside Buffers (TLBs).
    6362        </p>
    64         <p>
    65           To enable these features for a VM, you use the
    66           <userinput>VBoxManage modifyvm --vtx-vpid</userinput> and
    67           <userinput>VBoxManage modifyvm --large-pages</userinput> commands.
    68           See <xref href="vboxmanage-modifyvm.dita">VBoxManage modifyvm</xref>.
    69         </p>
     63        <p> To enable these features for a VM, you use the <userinput>VBoxManage modifyvm
     64            --vtx-vpid</userinput> and <userinput>VBoxManage modifyvm --large-pages</userinput>
     65          commands. See <xref href="vboxmanage-modifyvm.dita">VBoxManage modifyvm</xref>. </p>
    7066      </li>
    7167    </ul>
    7268  </body>
    73  
     69
    7470</topic>
  • trunk/doc/manual/en_US/dita/topics/network-manager-cloud-network-tab.dita

    r98549 r99797  
    4242      <li>
    4343        <p><b outputclass="bold">Provider:</b> The cloud service
    44             provider, such as Oracle Cloud Infrastructure.
     44            provider, such as <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
    4545          </p>
    4646      </li>
     
    5454            tunneling network. Click the
    5555            <b outputclass="bold">Network</b> icon to view the
    56             subnets on Oracle Cloud Infrastructure that are available for tunneling traffic.
     56            subnets on <ph conkeyref="vbox-conkeyref-phrases/oci"/> that are available for tunneling traffic.
    5757          </p>
    5858        <p>
     
    6060            of how you can use the <userinput>VBoxManage cloud</userinput>
    6161            command to create and configure a virtual cloud network
    62             (VCN) on Oracle Cloud Infrastructure.
     62            (VCN) on <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
    6363          </p>
    6464      </li>
  • trunk/doc/manual/en_US/dita/topics/network-manager-host-only-tab.dita

    r98549 r99797  
    4545            Use the <b outputclass="bold">DHCP Server</b> tab to
    4646            configure settings for the DHCP server used by the host-only
    47             network. The DHCP server is built into Oracle VM VirtualBox and
     47            network. The DHCP server is built into <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and
    4848            manages IP addresses for the network automatically.
    4949          </p>
  • trunk/doc/manual/en_US/dita/topics/network-manager.dita

    r98549 r99797  
    77    <p>
    88      The <b outputclass="bold">Network Manager</b> tool in
    9       VirtualBox Manager enables you to create, delete, and configure the
    10       following types of networks used by Oracle VM VirtualBox:
     9      <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> enables you to create, delete, and configure the
     10      following types of networks used by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>:
    1111    </p>
    1212    <ul>
  • trunk/doc/manual/en_US/dita/topics/network_bandwidth_limit.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox supports limiting of the maximum bandwidth used for
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports limiting of the maximum bandwidth used for
    99      network transmission. Several network adapters of one VM may share
    1010      limits through bandwidth groups. It is possible to have more than
     
    1313    <note>
    1414      <p>
    15         Oracle VM VirtualBox shapes VM traffic only in the transmit direction,
     15        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> shapes VM traffic only in the transmit direction,
    1616        delaying the packets being sent by virtual machines. It does not
    1717        limit the traffic being received by virtual machines.
  • trunk/doc/manual/en_US/dita/topics/network_bridged.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       With bridged networking, Oracle VM VirtualBox uses a device driver on
     8      With bridged networking, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses a device driver on
    99      your <i>host</i> system that filters data from your
    1010      physical network adapter. This driver is therefore called a
    1111      <i>net filter</i> driver. This enables
    12       Oracle VM VirtualBox to intercept data from the physical network and
     12      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to intercept data from the physical network and
    1313      inject data into it, effectively creating a new network interface
    1414      in software. When a guest is using such a new software interface,
     
    4646        not support promiscuous mode. All traffic has to use the MAC
    4747        address of the host's wireless adapter, and therefore
    48         Oracle VM VirtualBox needs to replace the source MAC address in the
     48        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> needs to replace the source MAC address in the
    4949        Ethernet header of an outgoing packet to make sure the reply
    50         will be sent to the host interface. When Oracle VM VirtualBox sees an
     50        will be sent to the host interface. When <ph conkeyref="vbox-conkeyref-phrases/product-name"/> sees an
    5151        incoming packet with a destination IP address that belongs to
    5252        one of the virtual machine adapters it replaces the destination
    5353        MAC address in the Ethernet header with the VM adapter's MAC
    54         address and passes it on. Oracle VM VirtualBox examines ARP and DHCP
     54        address and passes it on. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> examines ARP and DHCP
    5555        packets in order to learn the IP addresses of virtual machines.
    5656      </p>
     
    6464        <p><b outputclass="bold">macOS hosts.</b> Functionality is
    6565          limited when using AirPort, the Mac's wireless networking
    66           system, for bridged networking. Currently, Oracle VM VirtualBox
     66          system, for bridged networking. Currently, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    6767          supports only IPv4 and IPv6 over AirPort. For other protocols,
    6868          such as IPX, you must choose a wired interface.
     
    7272        <p><b outputclass="bold">Linux hosts.</b> Functionality is
    7373          limited when using wireless interfaces for bridged networking.
    74           Currently, Oracle VM VirtualBox supports only IPv4 and IPv6 over
     74          Currently, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports only IPv4 and IPv6 over
    7575          wireless. For other protocols, such as IPX, you must choose a
    7676          wired interface.
     
    100100          On Oracle Solaris 11 hosts build 159 and above, it is possible
    101101          to use Oracle Solaris Crossbow Virtual Network Interfaces
    102           (VNICs) directly with Oracle VM VirtualBox without any additional
     102          (VNICs) directly with <ph conkeyref="vbox-conkeyref-phrases/product-name"/> without any additional
    103103          configuration other than each VNIC must be exclusive for every
    104104          guest network interface.
    105105        </p>
    106106        <p>
    107           When using VLAN interfaces with Oracle VM VirtualBox, they must be
     107          When using VLAN interfaces with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, they must be
    108108          named according to the PPA-hack naming scheme, such as
    109109          e1000g513001. Otherwise, the guest may receive packets in an
  • trunk/doc/manual/en_US/dita/topics/network_cloud.dita

    r99497 r99797  
    77    <p>
    88      Cloud networks can be used for connections from a local VM to a
    9       subnet on a remote Oracle Cloud Infrastructure instance. See
     9      subnet on a remote <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance. See
    1010      <xref href="network-manager-cloud-network-tab.dita#network-manager-cloud-network-tab"/> for details of
    1111      how to create and configure a cloud network using the Network
    12       Manager tool in VirtualBox Manager.
     12      Manager tool in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.
    1313    </p>
    1414    <p>
     
    2929      </li>
    3030      <li>
    31         <p>
    32           On the command line, use <userinput>VBoxManage modifyvm
    33           vmname --nic <varname>x</varname> cloud</userinput>. See
    34           <xref href="vboxmanage-modifyvm.dita"/>.
    35         </p>
     31        <p> On the command line, use <userinput>VBoxManage modifyvm vmname --nic
     32              <varname>x</varname> cloud</userinput>. See <xref href="vboxmanage-modifyvm.dita"/>. </p>
    3633      </li>
    3734    </ul>
  • trunk/doc/manual/en_US/dita/topics/network_hostonly.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="network_hostonly">
    44  <title>Host-Only Networking</title>
    5  
     5
    66  <body>
    77    <p>
     
    1616    </p>
    1717    <p>
    18       When host-only networking is used, Oracle VM VirtualBox creates a new
     18      When host-only networking is used, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates a new
    1919      software interface on the host which then appears next to your
    2020      existing network interfaces. In other words, whereas with bridged
     
    5151      machine may contain a web server and a second one a database, and
    5252      since they are intended to talk to each other, the appliance can
    53       instruct Oracle VM VirtualBox to set up a host-only network for the two.
     53      instruct <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to set up a host-only network for the two.
    5454      A second, bridged, network would then connect the web server to
    5555      the outside world to serve data to, but the outside world cannot
     
    7474      <li>
    7575        <p>
    76           On the command line, use <userinput>VBoxManage modifyvm
    77          vmname --nic <varname>x</varname> hostonly</userinput>. See
    78           <xref href="vboxmanage-modifyvm.dita"/>.
     76          On the command line, use <userinput>VBoxManage modifyvm vmname --nic
     77          <varname>x</varname> hostonly</userinput>. See <xref href="vboxmanage-modifyvm.dita"/>.
    7978        </p>
    8079      </li>
     
    8281    <p>
    8382      For host-only networking, as with internal networking, you may
    84       find the DHCP server useful that is built into Oracle VM VirtualBox.
     83      find the DHCP server useful that is built into <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    8584      This is enabled by default and manages the IP addresses in the
    8685      host-only network. Without the DHCP server you would need to
     
    9089      <li>
    9190        <p>
    92           In VirtualBox Manager you can configure the DHCP server by choosing
     91          In <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> you can configure the DHCP server by choosing
    9392          <b outputclass="bold">File</b>,
    9493          <b outputclass="bold">Tools</b>,
     
    101100      </li>
    102101      <li>
    103         <p>
    104           Alternatively, you can use the <userinput>VBoxManage
    105           dhcpserver</userinput> command. See
    106           <xref href="vboxmanage-dhcpserver.dita"/>.
    107         </p>
     102        <p> Alternatively, you can use the <userinput>VBoxManage dhcpserver</userinput> command. See
     103            <xref href="vboxmanage-dhcpserver.dita"/>. </p>
    108104      </li>
    109105    </ul>
     
    116112    </note>
    117113    <p>
    118       On Linux, macOS and Solaris Oracle VM VirtualBox will only allow IP
     114      On Linux, macOS and Solaris <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will only allow IP
    119115      addresses in 192.168.56.0/21 range to be assigned to host-only
    120116      adapters. For IPv6 only link-local addresses are allowed. If other
     
    143139      </pre>
    144140  </body>
    145  
     141
    146142</topic>
  • trunk/doc/manual/en_US/dita/topics/network_internal.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="network_internal">
    44  <title>Internal Networking</title>
    5  
     5
    66  <body>
    77    <p>
     
    2727      central configuration. Every internal network is identified simply
    2828      by its name. Once there is more than one active virtual network
    29       card with the same internal network ID, the Oracle VM VirtualBox support
     29      card with the same internal network ID, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> support
    3030      driver will automatically <i>wire</i> the cards and
    31       act as a network switch. The Oracle VM VirtualBox support driver
     31      act as a network switch. The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> support driver
    3232      implements a complete Ethernet switch and supports both
    3333      broadcast/multicast frames and promiscuous mode.
     
    4242        <p>
    4343          Use the VM's <b outputclass="bold">Settings</b> window
    44           in VirtualBox Manager. In the <b outputclass="bold">Network</b>
     44          in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. In the <b outputclass="bold">Network</b>
    4545          category of the Settings window, select
    4646          <b outputclass="bold">Internal Network</b> from the
     
    6767    </ul>
    6868    <p>
    69       Unless you configure the virtual network cards in the guest
    70       operating systems that are participating in the internal network
    71       to use static IP addresses, you may want to use the DHCP server
    72       that is built into Oracle VM VirtualBox to manage IP addresses for the
    73       internal network. See <xref href="vboxmanage-dhcpserver.dita"/>.
     69      Unless you configure the virtual network cards in the guest operating systems that are
     70      participating in the internal network to use static IP addresses, you may want to use the DHCP
     71      server that is built into <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to manage IP addresses for the internal
     72      network. See <xref href="vboxmanage-dhcpserver.dita"/>.
    7473    </p>
    7574    <p>
     
    8180    </p>
    8281  </body>
    83  
     82
    8483</topic>
  • trunk/doc/manual/en_US/dita/topics/network_nat.dita

    r98549 r99797  
    1010      require any configuration on the host network and guest system.
    1111      For this reason, it is the default networking mode in
    12       Oracle VM VirtualBox.
     12      <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    1313    </p>
    1414    <p>
    1515      A virtual machine with NAT enabled acts much like a real computer
    1616      that connects to the Internet through a router. The router, in
    17       this case, is the Oracle VM VirtualBox networking engine, which maps
     17      this case, is the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> networking engine, which maps
    1818      traffic from and to the virtual machine transparently. In
    19       Oracle VM VirtualBox this router is placed between each virtual machine
     19      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> this router is placed between each virtual machine
    2020      and the host. This separation maximizes security since by default
    2121      virtual machines cannot talk to each other.
     
    2929    <p>
    3030      The network frames sent out by the guest operating system are
    31       received by Oracle VM VirtualBox's NAT engine, which extracts the TCP/IP
     31      received by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s NAT engine, which extracts the TCP/IP
    3232      data and resends it using the host operating system. To an
    3333      application on the host, or to another computer on the same
    3434      network as the host, it looks like the data was sent by the
    35       Oracle VM VirtualBox application on the host, using an IP address
    36       belonging to the host. Oracle VM VirtualBox listens for replies to the
     35      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> application on the host, using an IP address
     36      belonging to the host. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> listens for replies to the
    3737      packages sent, and repacks and resends them to the guest machine
    3838      on its private network.
     
    5353      The virtual machine receives its network address and configuration
    5454      on the private network from a DHCP server integrated into
    55       Oracle VM VirtualBox. The IP address thus assigned to the virtual
     55      <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. The IP address thus assigned to the virtual
    5656      machine is usually on a completely different network than the
    5757      host. As more than one card of a virtual machine can be set up to
     
    5959      10.0.2.0, the second card to the network 10.0.3.0 and so on. If
    6060      you need to change the guest-assigned IP range, see
    61       <xref href="changenat.dita">Fine Tuning the Oracle VM VirtualBox NAT Engine</xref>.
     61      <xref href="changenat.dita">Fine Tuning the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> NAT Engine</xref>.
    6262    </p>
    6363  </body>
  • trunk/doc/manual/en_US/dita/topics/network_nat_service.dita

    r98549 r99797  
    9191    <p>
    9292      NAT networks can also be created, deleted, and configured using
    93       the Network Manager tool in VirtualBox Manager. Click
     93      the Network Manager tool in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. Click
    9494      <b outputclass="bold">File</b>, <b outputclass="bold">
    9595      Tools</b>, <b outputclass="bold">Network
  • trunk/doc/manual/en_US/dita/topics/network_performance.dita

    r99497 r99797  
    77            <body>
    88               <p>
    9       Oracle VM VirtualBox provides a variety of virtual network adapters that
     9      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides a variety of virtual network adapters that
    1010      can be attached to the host's network in a number of ways.
    1111      Depending on which types of adapters and attachments are used the
     
    7474          Adapter, Internal Network, and Host-Only Adapter.
    7575        </p>
    76                      <p>
    77           To setup a promiscuous mode policy, either select from the
    78           drop down list located in the <b outputclass="bold">Network
    79           Settings</b> dialog for the network adaptor or use the
    80           command line tool <userinput>VBoxManage</userinput>. See
    81           <xref href="vboxmanage-modifyvm.dita"/>.
    82         </p>
     76                     <p> To setup a promiscuous mode policy, either select from the drop down list
     77          located in the <b outputclass="bold">Network Settings</b> dialog for the network adaptor
     78          or use the command line tool <userinput>VBoxManage</userinput>. See <xref
     79            href="vboxmanage-modifyvm.dita"/>. </p>
    8380                     <p>
    8481          Promiscuous mode policies are as follows:
  • trunk/doc/manual/en_US/dita/topics/network_vde.dita

    r98549 r99797  
    99      infrastructure system, spanning across multiple hosts in a secure
    1010      way. It enables L2/L3 switching, including spanning-tree protocol,
    11       VLANs, and WAN emulation. It is an optional part of Oracle VM VirtualBox
     11      VLANs, and WAN emulation. It is an optional part of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    1212      which is only included in the source code.
    1313    </p>
     
    2121    </p>
    2222    <p>
    23       The Oracle VM VirtualBox VDE driver has a single parameter: VDE network.
     23      The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VDE driver has a single parameter: VDE network.
    2424      This is the name of the VDE network switch socket to which the VM
    2525      will be connected.
  • trunk/doc/manual/en_US/dita/topics/networkingdetails.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="networkingdetails">
    44  <title>Virtual Networking</title>
    5  
     5
    66  <body>
    77    <p>
    8     As mentioned in <xref href="settings-network.dita#settings-network"/>, Oracle VM VirtualBox
     8    As mentioned in <xref href="settings-network.dita#settings-network"/>, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    99    provides up to eight virtual PCI Ethernet cards for each virtual
    1010    machine. For each such card, you can individually select the
     
    2525    </ul>
    2626    <p>
    27     Four of the network cards can be configured in the
    28     <b outputclass="bold">Network</b> section of the
    29     <b outputclass="bold">Settings</b> window in VirtualBox Manager. You
    30     can configure all eight network cards on the command line using
    31     <userinput>VBoxManage modifyvm</userinput>. See
    32     <xref href="vboxmanage-modifyvm.dita"/>.
    33   </p>
     27      Four of the network cards can be configured in the <b outputclass="bold">Network</b> section
     28      of the <b outputclass="bold">Settings</b> window in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. You can configure all
     29      eight network cards on the command line using <userinput>VBoxManage modifyvm</userinput>. See
     30      <xref href="vboxmanage-modifyvm.dita"/>.
     31    </p>
    3432    <p>
    3533    This chapter explains the various networking settings in more
  • trunk/doc/manual/en_US/dita/topics/networkingmodes.dita

    r99182 r99797  
    1212      <li>
    1313        <p><b outputclass="bold">Not attached.</b> In this mode,
    14           Oracle VM VirtualBox reports to the guest that a network card is
     14          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> reports to the guest that a network card is
    1515          present, but that there is no connection. This is as if no
    1616          Ethernet cable was plugged into the card. Using this mode, it
     
    4141          for more advanced networking needs, such as network
    4242          simulations and running servers in a guest. When enabled,
    43           Oracle VM VirtualBox connects to one of your installed network cards
     43          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> connects to one of your installed network cards
    4444          and exchanges network packets directly, circumventing your
    4545          host operating system's network stack.
     
    7272          used modes which share the same generic network interface, by
    7373          allowing the user to select a driver which can be included
    74           with Oracle VM VirtualBox or be distributed in an extension pack.
     74          with <ph conkeyref="vbox-conkeyref-phrases/product-name"/> or be distributed in an extension pack.
    7575        </p>
    7676        <p>
     
    9090              Distributed Ethernet switch on a Linux or a FreeBSD host.
    9191              At the moment this option requires compilation of
    92               Oracle VM VirtualBox from sources, as the Oracle packages do not
     92              <ph conkeyref="vbox-conkeyref-phrases/product-name"/> from sources, as the Oracle packages do not
    9393              include it.
    9494            </p>
  • trunk/doc/manual/en_US/dita/topics/nichardware.dita

    r98549 r99797  
    88      For each card, you can individually select what kind of
    99      <i>hardware</i> will be presented to the virtual
    10       machine. Oracle VM VirtualBox can virtualize the following types of
     10      machine. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can virtualize the following types of
    1111      networking hardware:
    1212    </p>
     
    5959    <p>
    6060      The Paravirtualized network adapter (virtio-net) is special. If
    61       you select this adapter, then Oracle VM VirtualBox does
     61      you select this adapter, then <ph conkeyref="vbox-conkeyref-phrases/product-name"/> does
    6262      <i>not</i> virtualize common networking hardware
    6363      that is supported by common guest operating systems. Instead,
    64       Oracle VM VirtualBox expects a special software interface for
     64      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> expects a special software interface for
    6565      virtualized environments to be provided by the guest, thus
    6666      avoiding the complexity of emulating networking hardware and
    67       improving network performance. Oracle VM VirtualBox provides support for
     67      improving network performance. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides support for
    6868      the industry-standard <i>virtio</i> networking
    6969      drivers, which are part of the open source KVM project.
     
    9191    </ul>
    9292    <p>
    93       Oracle VM VirtualBox also has limited support for <i>jumbo
     93      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also has limited support for <i>jumbo
    9494      frames</i>. These are networking packets with more than
    9595      1500 bytes of data, provided that you use the Intel card
  • trunk/doc/manual/en_US/dita/topics/otherextpacks.dita

    r98549 r99797  
    99      pack is open source and replaces the previous integration of the
    1010      VNC remote access protocol. This is experimental code, and is
    11       initially available in the Oracle VM VirtualBox source code package
     11      initially available in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> source code package
    1212      only. It is to a large portion code contributed by users, and is
    1313      not supported in any way by Oracle.
     
    2121    </p>
    2222    <p>
    23       It is possible to install both the Oracle VM VirtualBox Extension Pack
     23      It is possible to install both the <ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/>
    2424      and VNC, but only one VRDE module can be active at any time. The
    2525      following command switches to the VNC VRDE module in VNC:
     
    4747      The following command switches back to VRDP, if installed:
    4848    </p>
    49     <pre xml:space="preserve">VBoxManage setproperty vrdeextpack "Oracle VM VirtualBox Extension Pack"</pre>
     49    <pre xml:space="preserve">VBoxManage setproperty vrdeextpack "<ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/>"</pre>
    5050  </body>
    5151 
  • trunk/doc/manual/en_US/dita/topics/ovf-about.dita

    r98549 r99797  
    99        virtualization products which enables the creation of ready-made
    1010        virtual machines that can then be imported into a hypervisor
    11         such as Oracle VM VirtualBox. Oracle VM VirtualBox makes OVF import and
    12         export easy to do, using VirtualBox Manager or the command-line
     11        such as <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> makes OVF import and
     12        export easy to do, using <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> or the command-line
    1313        interface.
    1414      </p>
     
    1919        one can offer complete ready-to-use software packages, including
    2020        OSes with applications, that need no configuration or
    21         installation except for importing into Oracle VM VirtualBox.
     21        installation except for importing into <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    2222      </p>
    2323    <note>
    2424      <p>
    25           The OVF standard is complex, and support in Oracle VM VirtualBox is
     25          The OVF standard is complex, and support in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is
    2626          an ongoing process. In particular, no guarantee is made that
    27           Oracle VM VirtualBox supports all appliances created by other
     27          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports all appliances created by other
    2828          virtualization software. For a list of known limitations, see
    2929          <xref href="KnownIssues.dita">Known Limitations</xref>.
     
    4141            description file in an XML dialect with an
    4242            <filepath>.ovf</filepath> extension. These files must then
    43             reside in the same directory for Oracle VM VirtualBox to be able
     43            reside in the same directory for <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to be able
    4444            to import them.
    4545          </p>
     
    5151            <filepath>.ova</filepath> extension. Such archive files use
    5252            a variant of the TAR archive format and can therefore be
    53             unpacked outside of Oracle VM VirtualBox with any utility that can
     53            unpacked outside of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with any utility that can
    5454            unpack standard TAR files.
    5555          </p>
  • trunk/doc/manual/en_US/dita/topics/ovf-export-appliance.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="ovf-export-appliance">
    44  <title>Exporting an Appliance in OVF Format</title>
    5  
     5
    66  <body>
    77    <p>
     
    3939              </p>
    4040            <p>
    41                 The <b outputclass="bold">Oracle Cloud Infrastructure</b> value exports
    42                 the appliance to Oracle Cloud Infrastructure. See
     41                The <b outputclass="bold"><ph conkeyref="vbox-conkeyref-phrases/oci"/></b> value exports
     42                the appliance to <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See
    4343                <xref href="cloud-export-oci.dita#cloud-export-oci"/>.
    4444              </p>
     
    9393    </ol>
    9494    <p>
    95         You can use the <userinput>VBoxManage export</userinput> command to
    96         export an appliance. See <xref href="vboxmanage-export.dita"/>.
    97       </p>
     95      You can use the <userinput>VBoxManage export</userinput> command to export an appliance. See
     96      <xref href="vboxmanage-export.dita"/>.
     97    </p>
    9898  </body>
    99  
     99
    100100</topic>
  • trunk/doc/manual/en_US/dita/topics/ovf-import-appliance.dita

    r99497 r99797  
    1515          </p>
    1616        <p>
    17             Oracle VM VirtualBox creates file type associations automatically
     17            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates file type associations automatically
    1818            for any OVF and OVA files on your host OS.
    1919          </p>
     
    4343        <p>
    4444            By default, membership of VM groups is preserved on import
    45             for VMs that were initially exported from Oracle VM VirtualBox.
     45            for VMs that were initially exported from <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    4646            You can change this behavior by using the
    4747            <b outputclass="bold">Primary Group</b> setting for
     
    8787          </p>
    8888        <p>
    89             Oracle VM VirtualBox copies the disk images and creates local VMs
     89            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> copies the disk images and creates local VMs
    9090            with the settings described on the
    9191            <b outputclass="bold">Appliance Settings</b> page.
     
    102102      </li>
    103103    </ol>
    104     <p>
    105         You can use the <userinput>VBoxManage import</userinput> command to
    106         import an appliance. See <xref href="vboxmanage-import.dita"/>.
    107       </p>
     104    <p> You can use the <userinput>VBoxManage import</userinput> command to import an appliance. See
     105        <xref href="vboxmanage-import.dita"/>. </p>
    108106  </body>
    109107 
  • trunk/doc/manual/en_US/dita/topics/ovf.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox can import and export virtual machines in the
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can import and export virtual machines in the
    99      following formats:
    1010    </p>
     
    1818      <li>
    1919        <p><b outputclass="bold">Cloud service formats.</b> Export
    20           to and import from cloud services such as Oracle Cloud Infrastructure is supported.
     20          to and import from cloud services such as <ph conkeyref="vbox-conkeyref-phrases/oci"/> is supported.
    2121          See <xref href="cloud-integration.dita#cloud-integration"/>.
    2222        </p>
  • trunk/doc/manual/en_US/dita/topics/pcspeaker_passthrough.dita

    r99182 r99797  
    88      As an experimental feature, primarily due to being limited to
    99      Linux host only and unknown Linux distribution coverage,
    10       Oracle VM VirtualBox supports passing through the PC speaker to the
     10      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports passing through the PC speaker to the
    1111      host. The PC speaker, sometimes called the system speaker, is a
    1212      way to produce audible feedback such as beeps without the need for
     
    1414    </p>
    1515    <p>
    16       The PC speaker passthrough feature in Oracle VM VirtualBox handles beeps
     16      The PC speaker passthrough feature in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> handles beeps
    1717      only. Advanced PC speaker use by the VM, such as PCM audio, will
    1818      not work, resulting in undefined host behavior.
    1919    </p>
    2020    <p>
    21       Producing beeps on Linux is a very complex topic. Oracle VM VirtualBox
     21      Producing beeps on Linux is a very complex topic. <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    2222      offers a collection of options, in an attempt to make this work
    2323      deterministically and reliably on as many Linux distributions and
     
    192192    <p>
    193193      Enabling PC speaker passthrough for the VM is usually the simple
    194       part. The real difficulty is making sure that Oracle VM VirtualBox can
     194      part. The real difficulty is making sure that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can
    195195      access the necessary device, because in a typical Linux install
    196196      most of them can only be accessed by user <codeph>root</codeph>.
     
    209209      controlling terminal as the device configured to be used for
    210210      beeping, something which is often very difficult to achieve for
    211       GUI applications such as Oracle VM VirtualBox. The table above contains
     211      GUI applications such as <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. The table above contains
    212212      some hints, but in general refer to the Linux documentation.
    213213    </p>
  • trunk/doc/manual/en_US/dita/topics/pot-insecure.dita

    r98549 r99797  
    66  <body>
    77    <p>
    8         The following features of Oracle VM VirtualBox can present security
     8        The following features of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can present security
    99        problems:
    1010      </p>
     
    5151      <li>
    5252        <p>
    53             When using the Oracle VM VirtualBox web service to control an
    54             Oracle VM VirtualBox host remotely, connections to the web
     53            When using the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> web service to control an
     54            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> host remotely, connections to the web
    5555            service, over which the API calls are transferred using SOAP
    5656            XML, are not encrypted. They use plain HTTP by default. This
     
    7979        <p>
    8080            Because of shortcomings in older Windows versions, using
    81             Oracle VM VirtualBox on Windows versions older than Vista with
     81            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> on Windows versions older than Vista with
    8282            Service Pack 1 is not recommended.
    8383          </p>
  • trunk/doc/manual/en_US/dita/topics/preface-audience.dita

    r99016 r99797  
    77    <p>
    88      This document is intended for administrators with previous
    9       experience of using Oracle VM VirtualBox. It is assumed that readers are
     9      experience of using <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. It is assumed that readers are
    1010      familiar with Web technologies and have a general understanding of
    1111      Windows and UNIX platforms.
  • trunk/doc/manual/en_US/dita/topics/preface.dita

    r99016 r99797  
    77    <p>
    88      This document provides information on the advanced features
    9       of Oracle VM VirtualBox.
     9      of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    1010  </p>
    1111  </body>
  • trunk/doc/manual/en_US/dita/topics/preferences.dita

    r99016 r99797  
    2222        <p>
    2323          Click <b outputclass="bold">Preferences</b> on the
    24           Welcome screen in VirtualBox Manager.
     24          Welcome screen in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.
    2525        </p>
    2626      </li>
     
    5454        <p><b outputclass="bold">Language.</b> Enables you to
    5555          specify the language used for menus, labels, and text in
    56           VirtualBox Manager.
     56          <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.
    5757        </p>
    5858      </li>
     
    7070      <li>
    7171        <p><b outputclass="bold">Interface.</b> Enables you to
    72           select a color theme for the VirtualBox Manager user interface.
     72          select a color theme for the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> user interface.
    7373        </p>
    7474        <note>
  • trunk/doc/manual/en_US/dita/topics/privacy.dita

    r99016 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="privacy">
    4   <title>Oracle VM VirtualBox Privacy Information</title>
     4  <title><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Privacy Information</title>
    55 
    66  <body>
     
    1313    apply to your personal data collected and used by Oracle. The
    1414    following privacy information describes in more detail which
    15     information is exchanged between the Oracle VM VirtualBox application and
     15    information is exchanged between the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> application and
    1616    Oracle, and which information is collected by the virtualbox.org
    1717    website.
     
    3434    will most likely not work without them.
    3535  </p>
    36     <p><b outputclass="bold">§ 3 Oracle VM VirtualBox registration
    37     process.</b> The Oracle VM VirtualBox application may ask that the
     36    <p><b outputclass="bold">§ 3 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> registration
     37    process.</b> The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> application may ask that the
    3838    user optionally register with Oracle. If you choose to register,
    3939    your name, e-mail address, country and company will be submitted to
     
    4242  </p>
    4343    <p><b outputclass="bold">§ 4 Update notifications.</b> The
    44     Oracle VM VirtualBox application may contact Oracle to find out whether a
    45     new version of Oracle VM VirtualBox has been released and notify the user
     44    <ph conkeyref="vbox-conkeyref-phrases/product-name"/> application may contact Oracle to find out whether a
     45    new version of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has been released and notify the user
    4646    if that is the case. In the process, anonymous data such as your IP
    4747    address and a non-identifying counter, together with the product
     
    4949    find out whether an update is available. By default, this check is
    5050    performed once a day. You change this interval or disable these
    51     checks altogether in the Oracle VM VirtualBox preferences.
     51    checks altogether in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> preferences.
    5252  </p>
    5353    <p><b outputclass="bold">§ 5 Usage of personal information.</b>
     
    5757    forum services, to administer the website and to contact you due to
    5858    technical issues. Oracle may also inform you about new product
    59     releases related to Oracle VM VirtualBox.
     59    releases related to <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    6060  </p>
    6161    <p>
     
    6868    <ph>https://www.oracle.com/legal/privacy/privacy-policy.html</ph>
    6969    and the privacy information will be kept up to date in the
    70     documentation which comes with the Oracle VM VirtualBox application. You
     70    documentation which comes with the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> application. You
    7171    should check these places occasionally to ensure you are happy with
    7272    any changes.
  • trunk/doc/manual/en_US/dita/topics/rawdisk-access-disk-partitions.dita

    r99016 r99797  
    3636        </p>
    3737    <p>
    38           Oracle VM VirtualBox uses the same partition numbering as your Linux
     38          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses the same partition numbering as your Linux
    3939          host. As a result, the numbers given in the above example
    4040          would refer to the first primary partition and the first
  • trunk/doc/manual/en_US/dita/topics/rawdisk.dita

    r99016 r99797  
    77    <p>
    88        As an alternative to using virtual disk images as described in
    9         <xref href="storage.dita">Virtual Storage</xref>, Oracle VM VirtualBox can also present
     9        <xref href="storage.dita">Virtual Storage</xref>, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can also present
    1010        either entire physical hard disks or selected partitions as
    1111        virtual disks to virtual machines.
    1212      </p>
    1313    <p>
    14         With Oracle VM VirtualBox, this type of access is called <i>raw
     14        With <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, this type of access is called <i>raw
    1515        hard disk access</i>. It enables a guest operating system
    1616        to access its virtual hard disk without going through the host
  • trunk/doc/manual/en_US/dita/topics/restrict-network-attachments.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8         It is possible to remove networking modes from Oracle VM VirtualBox
     8        It is possible to remove networking modes from <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    99        GUI. To do this, use the following command:
    1010      </p>
  • trunk/doc/manual/en_US/dita/topics/seamlesswindows.dita

    r99182 r99797  
    77    <p>
    88      With the <i>seamless windows</i> feature of
    9       Oracle VM VirtualBox, you can have the windows that are displayed within
     9      <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, you can have the windows that are displayed within
    1010      a virtual machine appear side by side next to the windows of your
    1111      host. This feature is supported for the following guest operating
     
    2626    </ul>
    2727    <p>
    28       After seamless windows are enabled, Oracle VM VirtualBox suppresses the
     28      After seamless windows are enabled, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> suppresses the
    2929      display of the desktop background of your guest, allowing you to
    3030      run the windows of your guest operating system seamlessly next to
  • trunk/doc/manual/en_US/dita/topics/sec-rec-cve-2018-12126-et-al.dita

    r99016 r99797  
    99        Nehalem. The CVE-2018-12130 also affects some Atom Silvermont,
    1010        Atom Airmont, and Knights family CPUs, however the scope is so
    11         limited that the host OS should deal with it and Oracle VM VirtualBox
     11        limited that the host OS should deal with it and <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    1212        is therefore not affected. Leaks only happens when entering and
    1313        leaving C states.
  • trunk/doc/manual/en_US/dita/topics/security-encryption.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8         The following components of Oracle VM VirtualBox use encryption to
     8        The following components of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> use encryption to
    99        protect sensitive data:
    1010      </p>
     
    1212      <li>
    1313        <p>
    14             When using the Oracle VM VirtualBox Extension Pack provided by
     14            When using the <ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/> provided by
    1515            Oracle for VRDP remote desktop support, RDP data can
    1616            optionally be encrypted. See <xref href="vrde-crypt.dita#vrde-crypt"/>.
     
    2323      <li>
    2424        <p>
    25             When using the Oracle VM VirtualBox Extension Pack provided by
     25            When using the <ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/> provided by
    2626            Oracle for disk encryption, the data stored in disk images
    2727            can optionally be encrypted. See
  • trunk/doc/manual/en_US/dita/topics/security-features.dita

    r99016 r99797  
    77    <p>
    88      This section outlines the specific security mechanisms offered by
    9       Oracle VM VirtualBox.
     9      <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    1010    </p>
    1111  </body>
  • trunk/doc/manual/en_US/dita/topics/security-general.dita

    r99016 r99797  
    1414          of the principles of good security practise is to keep all
    1515          software versions and patches up to date. Activate the
    16           Oracle VM VirtualBox update notification to get notified when a new
    17           Oracle VM VirtualBox release is available. When updating
    18           Oracle VM VirtualBox, do not forget to update the Guest Additions.
     16          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> update notification to get notified when a new
     17          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> release is available. When updating
     18          <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, do not forget to update the Guest Additions.
    1919          Keep the host operating system as well as the guest operating
    2020          system up to date.
     
    3434          privilege.</b> The principle of least privilege states
    3535          that users should be given the least amount of privilege
    36           necessary to perform their jobs. Always execute Oracle VM VirtualBox
     36          necessary to perform their jobs. Always execute <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    3737          as a regular user. We strongly discourage anyone from
    38           executing Oracle VM VirtualBox with system privileges.
     38          executing <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with system privileges.
    3939        </p>
    4040        <p>
  • trunk/doc/manual/en_US/dita/topics/security-model.dita

    r99016 r99797  
    77    <p>
    88        One property of virtual machine monitors (VMMs) like
    9         Oracle VM VirtualBox is to encapsulate a guest by executing it in a
     9        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is to encapsulate a guest by executing it in a
    1010        protected environment, a virtual machine, running as a user
    1111        process on the host operating system. The guest cannot
  • trunk/doc/manual/en_US/dita/topics/security-secure-install-overview.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8         The Oracle VM VirtualBox base package should be downloaded only from a
     8        The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> base package should be downloaded only from a
    99        trusted source, for instance the official website
    1010        <ph>http://www.virtualbox.org</ph>. The integrity of the
     
    1313      </p>
    1414    <p>
    15         General Oracle VM VirtualBox installation instructions for the
     15        General <ph conkeyref="vbox-conkeyref-phrases/product-name"/> installation instructions for the
    1616        supported hosts can be found in <xref href="installation.dita">Installation Details</xref>.
    1717      </p>
     
    2424        appropriate if the corresponding functionality is not required
    2525        by any virtual machine. The Python language bindings are only
    26         required if the Oracle VM VirtualBox API is to be used by external
     26        required if the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> API is to be used by external
    2727        Python applications. In particular USB support and support for
    2828        the two networking modes require the installation of Windows
     
    3333      </p>
    3434    <p>
    35         The general case is to install the complete Oracle VM VirtualBox
     35        The general case is to install the complete <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    3636        package. The installation must be done with system privileges.
    37         All Oracle VM VirtualBox binaries should be executed as a regular user
     37        All <ph conkeyref="vbox-conkeyref-phrases/product-name"/> binaries should be executed as a regular user
    3838        and never as a privileged user.
    3939      </p>
    4040    <p>
    41         The Oracle VM VirtualBox Extension Pack provides additional features
     41        The <ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/> provides additional features
    4242        and must be downloaded and installed separately, see
    43         <xref href="intro-installing.dita">Installing Oracle VM VirtualBox and Extension Packs</xref>. As for the base package, the
     43        <xref href="intro-installing.dita">Installing <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and Extension Packs</xref>. As for the base package, the
    4444        SHA256 checksum of the extension pack should be verified. As the
    45         installation requires system privileges, Oracle VM VirtualBox will ask
     45        installation requires system privileges, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will ask
    4646        for the system password during the installation of the extension
    4747        pack.
  • trunk/doc/manual/en_US/dita/topics/security-secure-install-postinstall.dita

    r99016 r99797  
    77    <p>
    88        Normally there is no post installation configuration of
    9         Oracle VM VirtualBox components required. However, on Oracle Solaris
     9        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> components required. However, on Oracle Solaris
    1010        and Linux hosts it is necessary to configure the proper
    1111        permissions for users executing VMs and who should be able to
  • trunk/doc/manual/en_US/dita/topics/security-vrdp-auth.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8           When using the Oracle VM VirtualBox Extension Pack provided by
     8          When using the <ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/> provided by
    99          Oracle for VRDP remote desktop support, you can optionally use
    1010          various methods to configure RDP authentication. The "null"
  • trunk/doc/manual/en_US/dita/topics/serialports.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="serialports">
    44  <title>Serial Ports</title>
    5  
     5
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox supports the use of virtual serial ports in a
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports the use of virtual serial ports in a
    99      virtual machine.
    1010    </p>
     
    3636    </p>
    3737    <p>
    38       You can use either the Settings tabs or the
    39       <userinput>VBoxManage</userinput> command to set up virtual serial
    40       ports. For the latter, see <xref href="vboxmanage-modifyvm.dita"/>
    41       for information on the <codeph>--uart</codeph>,
    42       <codeph>--uart-mode</codeph> and <codeph>--uart-type</codeph>
    43       options.
     38      You can use either the Settings tabs or the <userinput>VBoxManage</userinput> command to set
     39      up virtual serial ports. For the latter, see <xref href="vboxmanage-modifyvm.dita"/> for
     40      information on the <codeph>--uart</codeph>, <codeph>--uart-mode</codeph> and
     41      <codeph>--uart-type</codeph> options.
    4442    </p>
    4543    <p>
     
    9896              <codeph>COM1</codeph>. On Linux or Oracle Solaris hosts,
    9997              it will be a device node like
    100               <filepath>/dev/ttyS0</filepath>. Oracle VM VirtualBox will then
     98              <filepath>/dev/ttyS0</filepath>. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will then
    10199              simply redirect all data received from and sent to the
    102100              virtual serial port to the physical device.
     
    105103          <li>
    106104            <p><b outputclass="bold">Host Pipe:</b> Configure
    107               Oracle VM VirtualBox to connect the virtual serial port to a
     105              <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to connect the virtual serial port to a
    108106              software pipe on the host. This depends on your host OS,
    109107              as follows:
     
    126124                  domain socket is used instead. The socket filename
    127125                  must be chosen such that the user running
    128                   Oracle VM VirtualBox has sufficient privileges to create and
     126                  <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has sufficient privileges to create and
    129127                  write to it. The <filepath>/tmp</filepath> directory
    130128                  is often a good candidate.
     
    139137            </ul>
    140138            <p>
    141               In this case, you can configure whether Oracle VM VirtualBox
     139              In this case, you can configure whether <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    142140              should create the named pipe, or the local domain socket
    143               non-Windows hosts, itself or whether Oracle VM VirtualBox should
     141              non-Windows hosts, itself or whether <ph conkeyref="vbox-conkeyref-phrases/product-name"/> should
    144142              assume that the pipe or socket exists already. With the
    145143              <userinput>VBoxManage</userinput> command-line options, this
     
    158156              useful for capturing diagnostic output from a guest. Any
    159157              file may be used for this purpose, as long as the user
    160               running Oracle VM VirtualBox has sufficient privileges to create
     158              running <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has sufficient privileges to create
    161159              and write to the file.
    162160            </p>
     
    211209    </p>
    212210  </body>
    213  
     211
    214212</topic>
  • trunk/doc/manual/en_US/dita/topics/settings-acceleration.dita

    r99497 r99797  
    66  <body>
    77    <p>
    8         On this tab, you can configure Oracle VM VirtualBox to use hardware
     8        On this tab, you can configure <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to use hardware
    99        virtualization extensions that your host CPU supports.
    1010      </p>
    1111    <ul>
    1212      <li>
    13         <p><b outputclass="bold">Paravirtualization
    14             Interface:</b> Oracle VM VirtualBox provides
    15             paravirtualization interfaces to improve time-keeping
    16             accuracy and performance of guest OSes. The options
    17             available are documented under the
    18            <codeph>--paravirt-provider</codeph> option in
    19             <xref href="vboxmanage-modifyvm.dita"/>. For further details
    20             on the paravirtualization providers, see
    21             <xref href="gimproviders.dita">Paravirtualization Providers</xref>.
    22           </p>
     13        <p><b outputclass="bold">Paravirtualization Interface:</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides
     14          paravirtualization interfaces to improve time-keeping accuracy and performance of guest
     15          OSes. The options available are documented under the <codeph>--paravirt-provider</codeph>
     16          option in <xref href="vboxmanage-modifyvm.dita"/>. For further details on the
     17          paravirtualization providers, see <xref href="gimproviders.dita">Paravirtualization
     18            Providers</xref>. </p>
    2319      </li>
    2420      <li>
     
    4945        In most cases, the default settings on the
    5046        <b outputclass="bold">Acceleration</b> tab will work
    51         well. Oracle VM VirtualBox selects sensible defaults, depending on the
     47        well. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> selects sensible defaults, depending on the
    5248        OS that you selected when you created the virtual machine. In
    5349        certain situations, however, you may want to change the
  • trunk/doc/manual/en_US/dita/topics/settings-audio.dita

    r99016 r99797  
    1919      <li>
    2020        <p><b outputclass="bold">Host Audio Driver:</b> The audio
    21           driver that Oracle VM VirtualBox uses on the host.
     21          driver that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses on the host.
    2222        </p>
    2323        <p>
  • trunk/doc/manual/en_US/dita/topics/settings-basic.dita

    r99016 r99797  
    1414        <p><b outputclass="bold">Name:</b> The name of the the
    1515            VM, as shown in the list of VMs in the main VirtualBox
    16             Manager window. Using this name, Oracle VM VirtualBox also saves
     16            Manager window. Using this name, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also saves
    1717            the VM's configuration files. If you change the name,
    18             Oracle VM VirtualBox renames these files as well. As a result, you
     18            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> renames these files as well. As a result, you
    1919            can only use characters which are allowed for file names on
    2020            your host OS.
    2121          </p>
    2222        <p>
    23             Note that internally, Oracle VM VirtualBox uses unique identifiers
     23            Note that internally, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses unique identifiers
    2424            (UUIDs) to identify virtual machines. You can display these
    2525            using the <userinput>VBoxManage</userinput> commands.
  • trunk/doc/manual/en_US/dita/topics/settings-general-advanced.dita

    r99016 r99797  
    1212      <li>
    1313        <p><b outputclass="bold">Snapshot Folder:</b> By
    14             default, Oracle VM VirtualBox saves snapshot data together with
    15             your other Oracle VM VirtualBox configuration data. See
    16             <xref href="vboxconfigdata.dita">Where Oracle VM VirtualBox Stores its Files</xref>. With this setting, you
     14            default, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> saves snapshot data together with
     15            your other <ph conkeyref="vbox-conkeyref-phrases/product-name"/> configuration data. See
     16            <xref href="vboxconfigdata.dita">Where <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Stores its Files</xref>. With this setting, you
    1717            can specify any other folder for each VM.
    1818          </p>
     
    2323            shared with that of your host. If you select
    2424            <b outputclass="bold">Bidirectional</b>, then
    25             Oracle VM VirtualBox will always make sure that both clipboards
     25            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will always make sure that both clipboards
    2626            contain the same data. If you select
    2727            <b outputclass="bold">Host to Guest</b> or
    2828            <b outputclass="bold">Guest to Host</b>, then
    29             Oracle VM VirtualBox will only ever copy clipboard data in one
     29            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will only ever copy clipboard data in one
    3030            direction.
    3131          </p>
    3232        <p>
    33             Clipboard sharing requires that the Oracle VM VirtualBox Guest
     33            Clipboard sharing requires that the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest
    3434            Additions be installed. In such a case, this setting has no
    3535            effect. See <xref href="guestadditions.dita#guestadditions"/>.
  • trunk/doc/manual/en_US/dita/topics/settings-motherboard.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="settings-motherboard">
    44  <title>Motherboard Tab</title>
    5  
     5
    66  <body>
    77    <p>
     
    3232            order in which the guest OS will attempt to boot from the
    3333            various virtual boot devices. Analogous to a real PC's BIOS
    34             setting, Oracle VM VirtualBox can tell a guest OS to start from
     34            setting, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can tell a guest OS to start from
    3535            the virtual floppy, the virtual CD/DVD drive, the virtual
    3636            hard drive (each of these as defined by the other VM
     
    3838          </p>
    3939        <p>
    40             If you select <b outputclass="bold">Network</b>, the
    41             VM will attempt to boot from a network using the PXE
    42             mechanism. This needs to be configured in detail on the
    43             command line. See <xref href="vboxmanage-modifyvm.dita"/>.
    44           </p>
     40            If you select <b outputclass="bold">Network</b>, the VM will attempt to boot from a
     41            network using the PXE mechanism. This needs to be configured in detail on the command
     42            line. See <xref href="vboxmanage-modifyvm.dita"/>.
     43        </p>
    4544      </li>
    4645      <li>
     
    4948            PIIX3 is the default chipset for most guests. For some guest
    5049            OSes such as Mac OS X, the PIIX3 chipset is not well
    51             supported. As a result, Oracle VM VirtualBox supports an emulation
     50            supported. As a result, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports an emulation
    5251            of the ICH9 chipset, which supports PCI express, three PCI
    5352            buses, PCI-to-PCI bridges and Message Signaled Interrupts
     
    7069            default virtual pointing device for some guest OSes is the
    7170            traditional PS/2 mouse. If set to <b outputclass="bold">USB
    72             Tablet</b>, Oracle VM VirtualBox reports to the virtual
     71            Tablet</b>, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> reports to the virtual
    7372            machine that a USB tablet device is present and communicates
    7473            mouse events to the virtual machine through this device.
     
    8079            Using the virtual USB tablet has the advantage that
    8180            movements are reported in absolute coordinates, instead of
    82             as relative position changes. This enables Oracle VM VirtualBox to
     81            as relative position changes. This enables <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to
    8382            translate mouse events over the VM window into tablet events
    8483            without having to "capture" the mouse in the guest as
     
    122121      <li>
    123122        <p><b outputclass="bold">Hardware Clock in UTC Time:</b>
    124             If selected, Oracle VM VirtualBox will report the system time in
     123            If selected, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will report the system time in
    125124            UTC format to the guest instead of the local (host) time.
    126125            This affects how the virtual real-time clock (RTC) operates
     
    146145        In addition, you can turn off the <b outputclass="bold">Advanced
    147146        Configuration and Power Interface (ACPI)</b> which
    148         Oracle VM VirtualBox presents to the guest OS by default.
     147        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents to the guest OS by default.
    149148      </p>
    150149    <p>
    151         ACPI is the current industry standard to allow OSes to recognize
    152         hardware, configure motherboards and other devices and manage
    153         power. As most computers contain this feature and Windows and
    154         Linux support ACPI, it is also enabled by default in
    155         Oracle VM VirtualBox. ACPI can only be turned off using the command
    156         line. See <xref href="vboxmanage-modifyvm.dita"/>.
    157       </p>
     150        ACPI is the current industry standard to allow OSes to recognize hardware, configure
     151        motherboards and other devices and manage power. As most computers contain this feature and
     152        Windows and Linux support ACPI, it is also enabled by default in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. ACPI
     153        can only be turned off using the command line. See <xref href="vboxmanage-modifyvm.dita"/>.
     154    </p>
    158155    <note type="attention">
    159156      <p>
     
    166163    </note>
    167164  </body>
    168  
     165
    169166</topic>
  • trunk/doc/manual/en_US/dita/topics/settings-network.dita

    r99016 r99797  
    88      The <b outputclass="bold">Network</b> section in a virtual
    99      machine's <b outputclass="bold">Settings</b> window enables
    10       you to configure how Oracle VM VirtualBox presents virtual network cards
     10      you to configure how <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents virtual network cards
    1111      to your VM, and how they operate.
    1212    </p>
    1313    <p>
    14       When you first create a virtual machine, Oracle VM VirtualBox by default
     14      When you first create a virtual machine, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> by default
    1515      enables one virtual network card and selects the Network Address
    1616      Translation (NAT) mode for it. This way the guest can connect to
     
    2020    </p>
    2121    <p>
    22       This default setup is good for the majority of Oracle VM VirtualBox
    23       users. However, Oracle VM VirtualBox is extremely flexible in how it can
     22      This default setup is good for the majority of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
     23      users. However, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is extremely flexible in how it can
    2424      virtualize networking. It supports many virtual network cards per
    2525      virtual machine. The first four virtual network cards can be
    26       configured in detail in VirtualBox Manager. Additional network cards can
     26      configured in detail in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. Additional network cards can
    2727      be configured using the <userinput>VBoxManage</userinput> command.
    2828    </p>
  • trunk/doc/manual/en_US/dita/topics/settings-processor.dita

    r99016 r99797  
    1313        <p><b outputclass="bold">Processor(s):</b> Sets the
    1414            number of virtual CPU cores the guest OSes can see.
    15             Oracle VM VirtualBox supports symmetrical multiprocessing (SMP)
     15            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports symmetrical multiprocessing (SMP)
    1616            and can present up to 32 virtual CPU cores to each virtual
    1717            machine.
     
    6161    </ul>
    6262    <p>
    63         With virtual machines running modern server OSes, Oracle VM VirtualBox
     63        With virtual machines running modern server OSes, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    6464        also supports CPU hot-plugging. For details, see
    6565        <xref href="cpuhotplug.dita">CPU Hot-Plugging</xref>.
  • trunk/doc/manual/en_US/dita/topics/settings-remote-display.dita

    r99016 r99797  
    88        On the <b outputclass="bold">Remote Display</b> tab, if
    99        the VirtualBox Remote Display Extension (VRDE) is installed, you
    10         can enable the VRDP server that is built into Oracle VM VirtualBox.
     10        can enable the VRDP server that is built into <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    1111        This enables you to connect to the console of the virtual
    1212        machine remotely with any standard RDP viewer, such as
  • trunk/doc/manual/en_US/dita/topics/settings-screen.dita

    r99016 r99797  
    1515          </p>
    1616        <p>
    17             VirtualBox Manager will show a warning if the amount of video memory
     17            <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> will show a warning if the amount of video memory
    1818            is too small to be able to switch the VM into full screen
    1919            mode. The minimum value depends on the number of virtual
     
    3131      <li>
    3232        <p><b outputclass="bold">Monitor Count:</b> With this
    33             setting, Oracle VM VirtualBox can provide more than one virtual
     33            setting, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can provide more than one virtual
    3434            monitor to a virtual machine. If a guest OS supports
    35             multiple attached monitors, Oracle VM VirtualBox can pretend that
     35            multiple attached monitors, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can pretend that
    3636            multiple virtual monitors are present. Up to eight such
    3737            virtual monitors are supported.
     
    4545            multiple monitors, you will need at least as many physical
    4646            monitors as you have virtual monitors configured, or
    47             Oracle VM VirtualBox will report an error.
     47            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will report an error.
    4848          </p>
    4949        <p>
  • trunk/doc/manual/en_US/dita/topics/settings-storage.dita

    r99182 r99797  
    1313      In a real computer, so-called <i>storage
    1414      controllers</i> connect physical disk drives to the rest of
    15       the computer. Similarly, Oracle VM VirtualBox presents virtual storage
     15      the computer. Similarly, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents virtual storage
    1616      controllers to a virtual machine. Under each controller, the
    1717      virtual devices, such as hard disks, CD/DVD or floppy drives,
     
    2020    <note>
    2121      <p>
    22         This section gives a quick introduction to the Oracle VM VirtualBox
     22        This section gives a quick introduction to the <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    2323        storage settings. See <xref href="storage.dita#storage"/> for a full
    24         description of the available storage settings in Oracle VM VirtualBox.
     24        description of the available storage settings in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    2525      </p>
    2626    </note>
     
    6464    </ul>
    6565    <p>
    66       If you created your VM with an older version of Oracle VM VirtualBox,
     66      If you created your VM with an older version of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>,
    6767      the default storage layout may differ. You might then only have an
    6868      IDE controller to which both the CD/DVD drive and the hard disks
    6969      have been attached. This might also apply if you selected an older
    7070      OS type when you created the VM. Since older OSes do not support
    71       SATA without additional drivers, Oracle VM VirtualBox will make sure
     71      SATA without additional drivers, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will make sure
    7272      that no such devices are present initially. See
    7373      <xref href="harddiskcontrollers.dita#harddiskcontrollers"/>.
    7474    </p>
    7575    <p>
    76       Oracle VM VirtualBox also provides a <i>floppy
     76      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also provides a <i>floppy
    7777      controller</i>. You cannot add devices other than floppy
    7878      drives to this controller. Virtual floppy drives, like virtual
     
    113113        <p>
    114114          See <xref href="vdidetails.dita#vdidetails"/> for information on the image
    115           file types that are supported by Oracle VM VirtualBox.
     115          file types that are supported by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    116116        </p>
    117117        <p>
  • trunk/doc/manual/en_US/dita/topics/settings-usb.dita

    r99016 r99797  
    99        The <b outputclass="bold">USB</b> section in a virtual
    1010        machine's <b outputclass="bold">Settings</b> window
    11         enables you to configure Oracle VM VirtualBox's sophisticated USB
     11        enables you to configure <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s sophisticated USB
    1212        support.
    1313      </p>
    1414                  <p>
    15         Oracle VM VirtualBox can enable virtual machines to access the USB
    16         devices on your host directly. To achieve this, Oracle VM VirtualBox
     15        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can enable virtual machines to access the USB
     16        devices on your host directly. To achieve this, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    1717        presents the guest OS with a virtual USB controller. As soon as
    1818        the guest system starts using a USB device, it will appear as
     
    4141                  <p>
    4242        In addition to allowing a guest access to your local USB
    43         devices, Oracle VM VirtualBox even enables your guests to connect to
     43        devices, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> even enables your guests to connect to
    4444        remote USB devices by use of the VirtualBox Remote Desktop
    4545        Extension (VRDE). See <xref href="usb-over-rdp.dita">Remote USB</xref>.
  • trunk/doc/manual/en_US/dita/topics/sf_mount_auto.dita

    r99016 r99797  
    77               <body>
    88                  <p>
    9         Oracle VM VirtualBox provides the option to mount shared folders
     9        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides the option to mount shared folders
    1010        automatically. When automatic mounting is enabled for a shared
    1111        folder, the Guest Additions service will mount it for you
  • trunk/doc/manual/en_US/dita/topics/sf_mount_manual.dita

    r99016 r99797  
    1818            and look for the folder in <b outputclass="bold">My
    1919            Networking Places</b>, <b outputclass="bold">Entire
    20             Network</b>, <b outputclass="bold">Oracle VM VirtualBox
     20            Network</b>, <b outputclass="bold"><ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    2121            Shared Folders</b>. By right-clicking on a shared
    2222            folder and selecting <b outputclass="bold">Map Network
     
    5757            Replace <varname>sharename</varname>, use a
    5858            lowercase string, with the share name specified with
    59             <userinput>VBoxManage</userinput> or VirtualBox Manager. Replace
     59            <userinput>VBoxManage</userinput> or <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. Replace
    6060            <varname>mountpoint</varname> with the path where
    6161            you want the share to be mounted on the guest, such as
  • trunk/doc/manual/en_US/dita/topics/shared-folders.dita

    r99016 r99797  
    99      Shared folders enable you to easily exchange data between a
    1010      virtual machine and your host. This feature requires that the
    11       Oracle VM VirtualBox Guest Additions be installed in a virtual machine
     11      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions be installed in a virtual machine
    1212      and is described in detail in <xref href="sharedfolders.dita#sharedfolders"/>.
    1313    </p>
  • trunk/doc/manual/en_US/dita/topics/sharedfolders.dita

    r99497 r99797  
    88               <p>
    99      With the <i>shared folders</i> feature of
    10       Oracle VM VirtualBox, you can access files of your host system from
     10      <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, you can access files of your host system from
    1111      within the guest system. This is similar to how you would use
    1212      network shares in Windows networks, except that shared folders do
    1313      not require networking, only the Guest Additions. Shared folders
    1414      are supported with Windows 2000 or later, Linux, and Oracle
    15       Solaris guests. Oracle VM VirtualBox includes experimental support for
     15      Solaris guests. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> includes experimental support for
    1616      Mac OS X and OS/2 guests.
    1717    </p>
     
    2525    </p>
    2626               <p>
    27       To share a host folder with a virtual machine in Oracle VM VirtualBox,
     27      To share a host folder with a virtual machine in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>,
    2828      you must specify the path of the folder and choose a
    2929      <i>share name</i> that the guest can use to access
     
    5757        </p>
    5858                     <pre xml:space="preserve">VBoxManage sharedfolder add "VM name" --name "sharename" --hostpath "C:\test"</pre>
    59                      <p>
    60           See <xref href="vboxmanage-sharedfolder.dita"/>.
    61         </p>
     59                     <p> See <xref href="vboxmanage-sharedfolder.dita"/>. </p>
    6260                  </li>
    6361               </ul>
     
    7573          Transient shares, that are added at runtime and disappear when
    7674          the VM is powered off. These can be created using a check box
    77           in VirtualBox Manager, or by using the <codeph>--transient</codeph>
     75          in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, or by using the <codeph>--transient</codeph>
    7876          option of the <userinput>VBoxManage sharedfolder add</userinput>
    7977          command.
     
    8684      read files on the host. By default, shared folders are read-write.
    8785      Read-only folders can be created using a check box in the
    88       VirtualBox Manager, or with the <codeph>--readonly option</codeph> of the
     86      <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, or with the <codeph>--readonly option</codeph> of the
    8987      <userinput>VBoxManage sharedfolder add</userinput> command.
    9088    </p>
    9189               <p>
    92       Oracle VM VirtualBox shared folders also support symbolic links, also
     90      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> shared folders also support symbolic links, also
    9391      called <i>symlinks</i>, under the following
    9492      conditions:
  • trunk/doc/manual/en_US/dita/topics/snapshots-contents.dita

    r99016 r99797  
    4242            not the virtual disk itself that is restored when a snapshot
    4343            is restored. Instead, when a snapshot is taken,
    44             Oracle VM VirtualBox creates differencing images which contain
     44            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates differencing images which contain
    4545            only the changes since the snapshot were taken. When the
    46             snapshot is restored, Oracle VM VirtualBox throws away that
     46            snapshot is restored, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> throws away that
    4747            differencing image, thus going back to the previous state.
    4848            This is both faster and uses less disk space. For the
  • trunk/doc/manual/en_US/dita/topics/snapshots-take-restore-delete.dita

    r99183 r99797  
    9090                       </fig>
    9191                        <p>
    92             Oracle VM VirtualBox imposes no limits on the number of snapshots
     92            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> imposes no limits on the number of snapshots
    9393            you can take. The only practical limitation is disk space on
    9494            your host. Each snapshot stores the state of the virtual
     
    142142                           <b outputclass="bold">Delete a snapshot.</b> This
    143143            does not affect the state of the virtual machine, but only
    144             releases the files on disk that Oracle VM VirtualBox used to store
     144            releases the files on disk that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> used to store
    145145            the snapshot data, thus freeing disk space. To delete a
    146146            snapshot, select the snapshot name in the Snapshots window
  • trunk/doc/manual/en_US/dita/topics/snapshots.dita

    r99183 r99797  
    1616               <p>
    1717      To see the snapshots of a virtual machine, click on the machine
    18       name in VirtualBox Manager. In the machine tools menu for the VM, click
     18      name in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. In the machine tools menu for the VM, click
    1919      <b outputclass="bold">Snapshots</b>. The Snapshots tool is
    2020      displayed.
  • trunk/doc/manual/en_US/dita/topics/soft-keyb.dita

    r99182 r99797  
    99  <body>
    1010    <p>
    11       Oracle VM VirtualBox provides a <i>soft keyboard</i> that
     11      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides a <i>soft keyboard</i> that
    1212      enables you to input keyboard characters on the guest. A soft
    1313      keyboard is an on-screen keyboard that can be used as an
     
    2121        For best results, ensure that the keyboard layout configured on
    2222        the guest OS matches the keyboard layout used by the soft
    23         keyboard. Oracle VM VirtualBox does not do this automatically.
     23        keyboard. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> does not do this automatically.
    2424      </p>
    2525    </note>
  • trunk/doc/manual/en_US/dita/topics/solaris-zones.dita

    r99016 r99797  
    33  PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    44<topic xml:lang="en-us" id="solaris-zones">
    5                <title>Configuring a Zone for Running Oracle VM VirtualBox</title>
     5               <title>Configuring a Zone for Running <ph conkeyref="vbox-conkeyref-phrases/product-name"/></title>
    66               
    77               <body>
    88                  <p>
    9         Assuming that Oracle VM VirtualBox has already been installed into
    10         your zone, you need to give the zone access to Oracle VM VirtualBox's
     9        Assuming that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has already been installed into
     10        your zone, you need to give the zone access to <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s
    1111        device node. This is done by performing the following steps.
    1212        Start a root terminal and run the following command:
     
    1616                  <p>
    1717        Replace <varname>vboxzone</varname> with the name of the
    18         zone where you intend to run Oracle VM VirtualBox.
     18        zone where you intend to run <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    1919      </p>
    2020                  <p>
     
    5050                  <p>
    5151        Reboot the zone using <userinput>zoneadm</userinput> and you should
    52         be able to run Oracle VM VirtualBox from within the configured zone.
     52        be able to run <ph conkeyref="vbox-conkeyref-phrases/product-name"/> from within the configured zone.
    5353      </p>
    5454               </body>
  • trunk/doc/manual/en_US/dita/topics/solariscodedumper.dita

    r99016 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="solariscodedumper">
    4   <title>Configuring the Oracle VM VirtualBox CoreDumper on Oracle Solaris Hosts</title>
     4  <title>Configuring the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper on Oracle Solaris Hosts</title>
    55 
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox is capable of producing its own core files for
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is capable of producing its own core files for
    99      extensive debugging when things go wrong. Currently this is only
    1010      available on Oracle Solaris hosts.
    1111    </p>
    1212    <p>
    13       The Oracle VM VirtualBox CoreDumper can be enabled using the following
     13      The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper can be enabled using the following
    1414      command:
    1515    </p>
     
    2323    <p>
    2424      Make sure the directory you specify is on a volume with sufficient
    25       free space and that the Oracle VM VirtualBox process has sufficient
     25      free space and that the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> process has sufficient
    2626      permissions to write files to this directory. If you skip this
    2727      command and do not specify any core dump directory, the current
    28       directory of the Oracle VM VirtualBox executable will be used. This
     28      directory of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> executable will be used. This
    2929      would most likely fail when writing cores as they are protected
    3030      with root permissions. It is recommended you explicitly set a core
     
    3232    </p>
    3333    <p>
    34       You must specify when the Oracle VM VirtualBox CoreDumper should be
     34      You must specify when the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper should be
    3535      triggered. This is done using the following commands:
    3636    </p>
     
    3939    <p>
    4040      At least one of the above two commands will have to be provided if
    41       you have enabled the Oracle VM VirtualBox CoreDumper.
     41      you have enabled the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper.
    4242    </p>
    4343    <p>
    4444      Setting <codeph>CoreDumpReplaceSystemDump</codeph> sets up the
    4545      VM to override the host's core dumping mechanism and in the event
    46       of any crash only the Oracle VM VirtualBox CoreDumper would produce the
     46      of any crash only the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper would produce the
    4747      core file.
    4848    </p>
     
    5757               </pre>
    5858    <p>
    59       The Oracle VM VirtualBox CoreDumper creates core files of the form
     59      The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper creates core files of the form
    6060      <filepath>core.vb.<varname>process-name</varname>.<varname>process-ID</varname>
    6161                  </filepath>
  • trunk/doc/manual/en_US/dita/topics/specialcharacters.dita

    r99016 r99797  
    99        Some OSes expect certain key combinations to initiate certain
    1010        procedures. The key combinations that you type into a VM might
    11         target the host OS, the Oracle VM VirtualBox software, or the guest
     11        target the host OS, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> software, or the guest
    1212        OS. The recipient of these keypresses depends on a number of
    1313        factors, including the key combination itself.
     
    3232            pressing it will usually restart your
    3333            <i>host</i> graphical user interface and kill
    34             all running programs, including Oracle VM VirtualBox, in the
     34            all running programs, including <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, in the
    3535            process.
    3636          </p>
     
    7070                              <p>
    7171                Use special key combinations with the Host key, which is
    72                 normally the right Control key. Oracle VM VirtualBox then
     72                normally the right Control key. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> then
    7373                translates the following key combinations for the VM:
    7474              </p>
     
    107107            For some other keyboard combinations such as
    108108            <b outputclass="bold">Alt+Tab</b> to switch between
    109             open windows, Oracle VM VirtualBox enables you to configure
     109            open windows, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to configure
    110110            whether these combinations will affect the host or the
    111111            guest, if a virtual machine currently has the focus. This is
  • trunk/doc/manual/en_US/dita/topics/startingvboxonlinux.dita

    r99016 r99797  
    33  PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    44<topic xml:lang="en-us" id="startingvboxonlinux">
    5                <title>Starting Oracle VM VirtualBox on Linux</title>
     5               <title>Starting <ph conkeyref="vbox-conkeyref-phrases/product-name"/> on Linux</title>
    66               
    77               <body>
    88                  <p>
    9         The easiest way to start an Oracle VM VirtualBox program is by running
     9        The easiest way to start an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> program is by running
    1010        the program of your choice (<userinput>VirtualBox</userinput>,
    1111        <userinput>VBoxManage</userinput>, or
     
    1616                  <p>
    1717        The following detailed instructions should only be of interest
    18         if you wish to execute Oracle VM VirtualBox without installing it
     18        if you wish to execute <ph conkeyref="vbox-conkeyref-phrases/product-name"/> without installing it
    1919        first. You should start by compiling the
    2020        <userinput>vboxdrv</userinput> kernel module and inserting it into
    21         the Linux kernel. Oracle VM VirtualBox consists of a service daemon,
     21        the Linux kernel. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> consists of a service daemon,
    2222        <userinput>VBoxSVC</userinput>, and several application programs.
    2323        The daemon is automatically started if necessary. All
    24         Oracle VM VirtualBox applications will communicate with the daemon
     24        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> applications will communicate with the daemon
    2525        through UNIX local domain sockets. There can be multiple daemon
    2626        instances under different user accounts and applications can
     
    3333      </p>
    3434                  <p>
    35         All Oracle VM VirtualBox applications (<userinput>VirtualBox</userinput>,
     35        All <ph conkeyref="vbox-conkeyref-phrases/product-name"/> applications (<userinput>VirtualBox</userinput>,
    3636        <userinput>VBoxManage</userinput>, and
    37         <userinput>VBoxHeadless</userinput>) require the Oracle VM VirtualBox
     37        <userinput>VBoxHeadless</userinput>) require the <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    3838        directory to be in the library path, as follows:
    3939      </p>
  • trunk/doc/manual/en_US/dita/topics/storage-bandwidth-limit.dita

    r99016 r99797  
    77            <body>
    88               <p>
    9       Oracle VM VirtualBox supports limiting of the maximum bandwidth used for
     9      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports limiting of the maximum bandwidth used for
    1010      asynchronous I/O. Additionally it supports sharing limits through
    1111      bandwidth groups for several images. It is possible to have more
  • trunk/doc/manual/en_US/dita/topics/storage-cds.dita

    r99497 r99797  
    4040    </p>
    4141               <p>
    42       Medium changes can be prevented by the guest, and Oracle VM VirtualBox
     42      Medium changes can be prevented by the guest, and <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    4343      reflects that by locking the host drive if appropriate. You can
    4444      force a medium removal in such situations by using the VirtualBox
     
    8585                  </li>
    8686               </ul>
    87                <p>
    88       To enable host drive passthrough you can use the
    89       <codeph>--passthrough</codeph> option of the <userinput>VBoxManage
    90       storageattach</userinput> command. See
    91       <xref href="vboxmanage-storageattach.dita"/>.
    92     </p>
     87               <p> To enable host drive passthrough you can use the <codeph>--passthrough</codeph>
     88      option of the <userinput>VBoxManage storageattach</userinput> command. See <xref
     89        href="vboxmanage-storageattach.dita"/>. </p>
    9390               <p>
    9491      Even if passthrough is enabled, unsafe commands, such as updating
     
    9996               <p>
    10097      On Oracle Solaris hosts, passthrough requires running
    101       Oracle VM VirtualBox with real root permissions due to security measures
     98      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with real root permissions due to security measures
    10299      enforced by the host.
    103100    </p>
  • trunk/doc/manual/en_US/dita/topics/storage-iscsi.dita

    r99497 r99797  
    1818    </p>
    1919               <p>
    20       Oracle VM VirtualBox can transparently present iSCSI remote storage to a
     20      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can transparently present iSCSI remote storage to a
    2121      virtual machine as a virtual hard disk. The guest OS will not see
    2222      any difference between a virtual disk image (VDI file) and an
    23       iSCSI target. To achieve this, Oracle VM VirtualBox has an integrated
     23      iSCSI target. To achieve this, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has an integrated
    2424      iSCSI initiator.
    2525    </p>
    26                <p>
    27       Oracle VM VirtualBox's iSCSI support has been developed according to the
    28       iSCSI standard and should work with all standard-conforming iSCSI
    29       targets. To use an iSCSI target with Oracle VM VirtualBox, you must use
    30       the command line. See <xref href="vboxmanage-storageattach.dita"/>.
    31     </p>
     26               <p> <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s iSCSI support has been developed according to the iSCSI
     27      standard and should work with all standard-conforming iSCSI targets. To use an iSCSI target
     28      with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, you must use the command line. See <xref
     29        href="vboxmanage-storageattach.dita"/>. </p>
    3230            </body>
    3331           
  • trunk/doc/manual/en_US/dita/topics/storage.dita

    r99016 r99797  
    88            <p>
    99    As the virtual machine will most probably expect to see a hard disk
    10     built into its virtual computer, Oracle VM VirtualBox must be able to
     10    built into its virtual computer, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> must be able to
    1111    present real storage to the guest as a virtual hard disk. There are
    1212    presently three methods by which to achieve this:
     
    1515               <li>
    1616                  <p>
    17         Oracle VM VirtualBox can use large image files on a real hard disk and
     17        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can use large image files on a real hard disk and
    1818        present them to a guest as a virtual hard disk. This is the most
    1919        common method, described in <xref href="vdidetails.dita#vdidetails"/>.
     
    2222               <li>
    2323                  <p>
    24         iSCSI storage servers can be attached to Oracle VM VirtualBox. This is
     24        iSCSI storage servers can be attached to <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. This is
    2525        described in <xref href="storage-iscsi.dita#storage-iscsi"/>.
    2626      </p>
     
    3737    Each such virtual storage device, such as an image file, iSCSI
    3838    target, or physical hard disk, needs to be connected to the virtual
    39     hard disk controller that Oracle VM VirtualBox presents to a virtual
     39    hard disk controller that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents to a virtual
    4040    machine. This is explained in the next section.
    4141  </p>
  • trunk/doc/manual/en_US/dita/topics/technical-components.dita

    r99016 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="technical-components">
    4   <title>Oracle VM VirtualBox Executables and Components</title>
     4  <title><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Executables and Components</title>
    55 
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox was designed to be modular and flexible. When the
    9       Oracle VM VirtualBox graphical user interface (GUI) is opened and a VM
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> was designed to be modular and flexible. When the
     9      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> graphical user interface (GUI) is opened and a VM
    1010      is started, at least the following three processes are running:
    1111    </p>
    1212    <ul>
    1313      <li>
    14         <p><userinput>VBoxSVC</userinput>, the Oracle VM VirtualBox service process
     14        <p><userinput>VBoxSVC</userinput>, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> service process
    1515          which always runs in the background. This process is started
    16           automatically by the first Oracle VM VirtualBox client process and
     16          automatically by the first <ph conkeyref="vbox-conkeyref-phrases/product-name"/> client process and
    1717          exits a short time after the last client exits. The first
    18           Oracle VM VirtualBox service can be VirtualBox Manager,
     18          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> service can be <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>,
    1919          <userinput>VBoxManage</userinput>,
    2020          <userinput>VBoxHeadless</userinput>, the web service amongst
    2121          others. The service is responsible for bookkeeping,
    2222          maintaining the state of all VMs, and for providing
    23           communication between Oracle VM VirtualBox components. This
     23          communication between <ph conkeyref="vbox-conkeyref-phrases/product-name"/> components. This
    2424          communication is implemented using COM/XPCOM.
    2525        </p>
     
    2828            When we refer to <i>clients</i> here, we mean
    2929            the local clients of a particular <userinput>VBoxSVC</userinput>
    30             server process, not clients in a network. Oracle VM VirtualBox
     30            server process, not clients in a network. <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    3131            employs its own client/server design to allow its processes
    3232            to cooperate, but all these processes run under the same
     
    4141          application based on the cross-platform Qt library. When
    4242          started without the <codeph>--startvm</codeph> option, this
    43           application acts as VirtualBox Manager, displaying the VMs and their
     43          application acts as <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, displaying the VMs and their
    4444          settings. It then communicates settings and state changes to
    4545          <userinput>VBoxSVC</userinput> and also reflects changes effected
     
    5959    </ul>
    6060    <p>
    61       Any Oracle VM VirtualBox front-end, or client, will communicate with the
     61      Any <ph conkeyref="vbox-conkeyref-phrases/product-name"/> front-end, or client, will communicate with the
    6262      service process and can both control and reflect the current
    6363      state. For example, either the VM selector or the VM window or
     
    6666    </p>
    6767    <p>
    68       The Oracle VM VirtualBox GUI application, called VirtualBox Manager, is only one
     68      The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> GUI application, called <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, is only one
    6969      of several available front ends, or clients. The complete list
    70       shipped with Oracle VM VirtualBox is as follows:
     70      shipped with <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is as follows:
    7171    </p>
    7272    <ul>
    7373      <li>
    7474        <p><userinput>VirtualBoxVM</userinput>: The Qt front end implementing
    75           VirtualBox Manager and running VMs.
     75          <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> and running VMs.
    7676        </p>
    7777      </li>
     
    8989      </li>
    9090      <li>
    91         <p><userinput>vboxwebsrv</userinput>: The Oracle VM VirtualBox web service
    92           process which enables control of an Oracle VM VirtualBox host
    93           remotely. This is described in detail in the Oracle VM VirtualBox
     91        <p><userinput>vboxwebsrv</userinput>: The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> web service
     92          process which enables control of an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> host
     93          remotely. This is described in detail in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    9494          Software Development Kit (SDK) reference. See
    9595          <xref href="VirtualBoxAPI.dita"/>.
     
    9898      <li>
    9999        <p>
    100           The Oracle VM VirtualBox Python shell: A Python alternative to
     100          The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Python shell: A Python alternative to
    101101          <userinput>VBoxManage</userinput>. This is also described in the
    102102          SDK reference.
     
    105105    </ul>
    106106    <p>
    107       Internally, Oracle VM VirtualBox consists of many more or less separate
    108       components. You may encounter these when analyzing Oracle VM VirtualBox
     107      Internally, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> consists of many more or less separate
     108      components. You may encounter these when analyzing <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    109109      internal error messages or log files. These include the following:
    110110    </p>
     
    113113        <p>
    114114          IPRT: A portable runtime library which abstracts file access,
    115           threading, and string manipulation. Whenever Oracle VM VirtualBox
     115          threading, and string manipulation. Whenever <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    116116          accesses host operating features, it does so through this
    117117          library for cross-platform portability.
     
    152152          implementations from VMM internals and makes it easy to add
    153153          new emulated devices. Through PDM, third-party developers can
    154           add new virtual devices to Oracle VM VirtualBox without having to
    155           change Oracle VM VirtualBox itself.
     154          add new virtual devices to <ph conkeyref="vbox-conkeyref-phrases/product-name"/> without having to
     155          change <ph conkeyref="vbox-conkeyref-phrases/product-name"/> itself.
    156156        </p>
    157157      </li>
     
    193193      <li>
    194194        <p>
    195           Oracle VM VirtualBox emulates a number of devices to provide the
     195          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> emulates a number of devices to provide the
    196196          hardware environment that various guests need. Most of these
    197197          are standard devices found in many PC compatible machines and
     
    212212        <p>
    213213          The "Main" component is special. It ties all the above bits
    214           together and is the only public API that Oracle VM VirtualBox
     214          together and is the only public API that <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    215215          provides. All the client processes listed above use only this
    216216          API and never access the hypervisor components directly. As a
    217           result, third-party applications that use the Oracle VM VirtualBox
     217          result, third-party applications that use the <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    218218          Main API can rely on the fact that it is always well-tested
    219           and that all capabilities of Oracle VM VirtualBox are fully exposed.
    220           It is this API that is described in the Oracle VM VirtualBox SDK.
     219          and that all capabilities of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> are fully exposed.
     220          It is this API that is described in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> SDK.
    221221          See <xref href="VirtualBoxAPI.dita#VirtualBoxAPI"/>.
    222222        </p>
  • trunk/doc/manual/en_US/dita/topics/teleporting.dita

    r99497 r99797  
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox supports <i>teleporting</i>.
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports <i>teleporting</i>.
    99      Teleporting is moving a virtual machine over a network from one
    10       Oracle VM VirtualBox host to another, while the virtual machine is
     10      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> host to another, while the virtual machine is
    1111      running. This works regardless of the host operating system that
    1212      is running on the hosts. You can teleport virtual machines between
     
    3535        <p>
    3636          On the target host, you must configure a virtual machine in
    37           Oracle VM VirtualBox with exactly the same hardware settings as the
     37          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with exactly the same hardware settings as the
    3838          machine on the source that you want to teleport. This does not
    3939          apply to settings which are merely descriptive, such as the VM
     
    118118        application software that is highly optimized to run on a
    119119        particular CPU without correctly checking that certain CPU
    120         features are actually present. Oracle VM VirtualBox filters what CPU
     120        features are actually present. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> filters what CPU
    121121        capabilities are presented to the guest operating system.
    122122        Advanced users can attempt to restrict these virtual CPU
  • trunk/doc/manual/en_US/dita/topics/ts_categorize-isolate.dita

    r99016 r99797  
    1313      </p>
    1414    <p>
    15         If a true Oracle VM VirtualBox problem is encountered, it helps to
     15        If a true <ph conkeyref="vbox-conkeyref-phrases/product-name"/> problem is encountered, it helps to
    1616        categorize and isolate the problem first. Here are some of the
    1717        questions that should be answered before reporting a problem:
     
    3030            Is the problem specific to a certain host OS? Problems are
    3131            usually not host OS specific, because most of the
    32             Oracle VM VirtualBox code base is shared across all supported
     32            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> code base is shared across all supported
    3333            platforms, but especially in the areas of networking and USB
    3434            support, there are significant differences between host
  • trunk/doc/manual/en_US/dita/topics/ts_debugger.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8         Oracle VM VirtualBox includes a built-in VM debugger, which advanced
     8        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> includes a built-in VM debugger, which advanced
    99        users may find useful. This debugger enables you to examine and,
    1010        to some extent, control the VM state.
     
    2323    <p>
    2424        The VM debugger is available in all regular production versions
    25         of Oracle VM VirtualBox, but it is disabled by default because the
     25        of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, but it is disabled by default because the
    2626        average user will have little use for it. There are two ways to
    2727        access the debugger:
     
    5858            <codeph>VBOX_GUI_DBG_AUTO_SHOW</codeph> environment
    5959            variable to <codeph>true</codeph> before launching the
    60             Oracle VM VirtualBox process. Setting these variables, only their
     60            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> process. Setting these variables, only their
    6161            presence is checked, is effective even when the first
    62             Oracle VM VirtualBox process is the VM selector window. VMs
     62            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> process is the VM selector window. VMs
    6363            subsequently launched from the selector will have the
    6464            debugger enabled.
     
    7575    <p>
    7676        A new <b outputclass="bold">Debug</b> menu entry is added
    77         to the Oracle VM VirtualBox application. This menu enables the user to
     77        to the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> application. This menu enables the user to
    7878        open the debugger console.
    7979      </p>
     
    8282        and IBM debuggers used on DOS, OS/2, and Windows. Users familiar
    8383        with symdeb, CodeView, or the OS/2 kernel debugger will find the
    84         Oracle VM VirtualBox VM debugger familiar.
     84        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VM debugger familiar.
    8585      </p>
    8686    <p>
     
    262262        The output of the <userinput>info</userinput> commands generally
    263263        requires in-depth knowledge of the emulated device or
    264         Oracle VM VirtualBox VMM internals. However, when used properly, the
     264        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VMM internals. However, when used properly, the
    265265        information provided can be invaluable.
    266266      </p>
  • trunk/doc/manual/en_US/dita/topics/ts_guest-core-format.dita

    r99497 r99797  
    55 
    66  <body>
    7     <p>
    8         Oracle VM VirtualBox uses the 64-bit ELF format for its VM core files
    9         created by <userinput>VBoxManage debugvm</userinput>, see
    10         <xref href="vboxmanage-debugvm.dita">VBoxManage debugvm</xref>. The VM core file contain
    11         the memory and CPU dumps of the VM and can be useful for
    12         debugging your guest OS. The 64-bit ELF object format
    13         specification can be obtained at:
    14       </p>
     7    <p> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses the 64-bit ELF format for its VM core files created by
     8        <userinput>VBoxManage debugvm</userinput>, see <xref href="vboxmanage-debugvm.dita"
     9        >VBoxManage debugvm</xref>. The VM core file contain the memory and CPU dumps of the VM and
     10      can be useful for debugging your guest OS. The 64-bit ELF object format specification can be
     11      obtained at: </p>
    1512    <p><ph>http://downloads.openwatcom.org/ftp/devel/docs/elf-64-gen.pdf</ph>.
    1613      </p>
     
    4239    <p>
    4340        The relevant data structures and definitions can be found in the
    44         Oracle VM VirtualBox sources under the following header files:
     41        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> sources under the following header files:
    4542        <filepath>include/VBox/dbgfcorefmt.h</filepath>,
    4643        <filepath>include/iprt/x86.h</filepath> and
  • trunk/doc/manual/en_US/dita/topics/ts_gui-2d-grayed-out.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8         To use 2D Video Acceleration within Oracle VM VirtualBox, your host's
     8        To use 2D Video Acceleration within <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, your host's
    99        video card should support certain OpenGL extensions. On startup,
    10         Oracle VM VirtualBox checks for those extensions, and, if the test
     10        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> checks for those extensions, and, if the test
    1111        fails, this option is silently grayed out.
    1212      </p>
  • trunk/doc/manual/en_US/dita/topics/ts_linux-buggy.dita

    r99016 r99797  
    77    <p>
    88        The following bugs in Linux kernels prevent them from executing
    9         correctly in Oracle VM VirtualBox, causing VM boot crashes:
     9        correctly in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, causing VM boot crashes:
    1010      </p>
    1111    <ul>
     
    1414            The Linux kernel version 2.6.18, and some 2.6.17 versions,
    1515            introduced a race condition that can cause boot crashes in
    16             Oracle VM VirtualBox. Please use a kernel version 2.6.19 or later.
     16            <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. Please use a kernel version 2.6.19 or later.
    1717          </p>
    1818      </li>
  • trunk/doc/manual/en_US/dita/topics/ts_linux-host-cd-dvd-not-found.dita

    r99016 r99797  
    1717      </p>
    1818    <p>
    19         On supported Linux distributions, Oracle VM VirtualBox uses
     19        On supported Linux distributions, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses
    2020        <userinput>udev</userinput> to locate hardware such as CD/DVD drives
    2121        and floppy disk drives.
  • trunk/doc/manual/en_US/dita/topics/ts_linux-host-grsec.dita

    r99016 r99797  
    99        <ph>http://www.grsecurity.net/</ph>, and derivates have
    1010        to disable PAX_MPROTECT for the <userinput>VBox</userinput> binaries
    11         to be able to start a VM. The reason is that Oracle VM VirtualBox has
     11        to be able to start a VM. The reason is that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has
    1212        to create executable code on anonymous memory.
    1313      </p>
  • trunk/doc/manual/en_US/dita/topics/ts_linux-host-ide-messages.dita

    r99016 r99797  
    1010        attempt to access the CD or DVD writer fails and simply results
    1111        in guest kernel error messages for Linux guests or application
    12         error messages for Windows guests. Oracle VM VirtualBox performs the
     12        error messages for Windows guests. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> performs the
    1313        usual consistency checks when a VM is powered up. In particular,
    1414        it aborts with an error message if the device for the CD or DVD
    1515        writer is not writable by the user starting the VM. But
    16         Oracle VM VirtualBox cannot detect all misconfigurations. The
     16        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> cannot detect all misconfigurations. The
    1717        necessary host and guest OS configuration is not specific for
    18         Oracle VM VirtualBox, but a few frequent problems are listed here
    19         which occurred in connection with Oracle VM VirtualBox.
     18        <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, but a few frequent problems are listed here
     19        which occurred in connection with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    2020      </p>
    2121    <p>
     
    3535        or DVD writer is detected in the system, even if the kernel
    3636        would support CD or DVD writers without the module.
    37         Oracle VM VirtualBox supports the use of IDE device files, such as
     37        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports the use of IDE device files, such as
    3838        <filepath>/dev/hdc</filepath>, provided the kernel supports this
    3939        and the <userinput>ide-scsi</userinput> module is not loaded.
  • trunk/doc/manual/en_US/dita/topics/ts_linux-host-vboxsvc.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8         On Linux, Oracle VM VirtualBox makes use of a custom version of
     8        On Linux, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> makes use of a custom version of
    99        Mozilla XPCOM (cross platform component object model) for
    1010        interprocess and intraprocess communication (IPC). The process
    1111        <userinput>VBoxSVC</userinput> serves as a communication hub between
    12         different Oracle VM VirtualBox processes and maintains the global
     12        different <ph conkeyref="vbox-conkeyref-phrases/product-name"/> processes and maintains the global
    1313        configuration, such as the XML database. When starting an
    14         Oracle VM VirtualBox component, the processes
     14        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> component, the processes
    1515        <userinput>VBoxSVC</userinput> and <userinput>VBoxXPCOMIPCD</userinput>
    1616        are started automatically. They are only accessible from the
    1717        user account they are running under. <userinput>VBoxSVC</userinput>
    18         owns the Oracle VM VirtualBox configuration database which normally
     18        owns the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> configuration database which normally
    1919        resides in <filepath>~/.config/VirtualBox</filepath>, or the
    2020        appropriate configuration directory for your operating system.
    2121        While it is running, the configuration files are locked.
    22         Communication between the various Oracle VM VirtualBox components and
     22        Communication between the various <ph conkeyref="vbox-conkeyref-phrases/product-name"/> components and
    2323        <userinput>VBoxSVC</userinput> is performed through a local domain
    2424        socket residing in
    2525        <filepath>/tmp/.vbox-<varname>username</varname>-ipc</filepath>.
    2626        In case there are communication problems, such as an
    27         Oracle VM VirtualBox application cannot communicate with
     27        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> application cannot communicate with
    2828        <userinput>VBoxSVC</userinput>, terminate the daemons and remove the
    2929        local domain socket directory.
  • trunk/doc/manual/en_US/dita/topics/ts_linux-kernelmodule-fails-to-load.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8         If the Oracle VM VirtualBox kernel module, <userinput>vboxdrv</userinput>,
     8        If the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> kernel module, <userinput>vboxdrv</userinput>,
    99        refuses to load you may see an <codeph>Error inserting vboxdrv:
    1010        Invalid argument</codeph> message. As root, check the output of
  • trunk/doc/manual/en_US/dita/topics/ts_sol-host-zfs.dita

    r99016 r99797  
    99        cache if the default system settings are not changed. This may
    1010        lead to a heavy fragmentation of the host memory preventing
    11         Oracle VM VirtualBox VMs from being started. We recommend to limit the
     11        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VMs from being started. We recommend to limit the
    1212        ZFS cache by adding the following line to
    1313        <filepath>/etc/system</filepath>, where
  • trunk/doc/manual/en_US/dita/topics/ts_vboxbugreport.dita

    r99016 r99797  
    88    <p>
    99        The <userinput>VBoxBugReport</userinput> command is used to collect
    10         debug information automatically for an Oracle VM VirtualBox
     10        debug information automatically for an <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    1111        installation. This command can be useful when you need to gather
    1212        information to send to Oracle Support.
     
    1919        By default, the command collects <userinput>VBoxSVC</userinput>
    2020        process logs, device settings, and global configuration data for
    21         an Oracle VM VirtualBox host.
     21        an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> host.
    2222      </p>
    2323    <pre xml:space="preserve">$ VBoxBugReport
  • trunk/doc/manual/en_US/dita/topics/ts_win-dnd-uipi.dita

    r99016 r99797  
    1111    </p>
    1212    <p>
    13       When an Oracle VM VirtualBox VM process is running with a higher so-called
     13      When an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VM process is running with a higher so-called
    1414      privilege level than another process that wants to interact with the
    1515      VM process via drag'n drop (or system clipboard), Windows prevents this
    16       by default due to security reasons. This results in Oracle VM VirtualBox not
     16      by default due to security reasons. This results in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> not
    1717      being able to receive any Windows messages for drag'n drop. To make this work,
    18       the Oracle VM VirtualBox VM process must be running with
     18      the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VM process must be running with
    1919      the same (or lower) privilege level as the process it is interacting with
    2020      using drag'n drop.</p>
  • trunk/doc/manual/en_US/dita/topics/ts_win-guest-active-dir-domain.dita

    r99016 r99797  
    88    <p>
    99        If a Windows guest is a member of an Active Directory domain and
    10         the snapshot feature of Oracle VM VirtualBox is used, it could be
     10        the snapshot feature of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is used, it could be
    1111        removed from the Active Direcory domain after you restore an
    1212        older snapshot.
  • trunk/doc/manual/en_US/dita/topics/ts_win-guest-bluescreen-record-info.dita

    r99016 r99797  
    1515      </p>
    1616    <p>
    17         Oracle VM VirtualBox provides a method of halting a guest when it
     17        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides a method of halting a guest when it
    1818        wants to perform a reset. In order to enable this feature, use
    1919        the following command:
  • trunk/doc/manual/en_US/dita/topics/ts_win-guest-bluescreen.dita

    r99016 r99797  
    3333            Changing the storage controller hardware will cause bootup
    3434            failures as well. This might also apply to you if you copy a
    35             disk image from an older version of Oracle VM VirtualBox to a new
     35            disk image from an older version of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to a new
    3636            virtual machine. The default subtype of IDE controller
    37             hardware used by Oracle VM VirtualBox is PIIX4. Make sure that the
     37            hardware used by <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is PIIX4. Make sure that the
    3838            storage controller settings are identical.
    3939          </p>
  • trunk/doc/manual/en_US/dita/topics/ts_win-guest-shared-folders-access-delay.dita

    r99016 r99797  
    88        The performance for accesses to shared folders from a Windows
    99        guest might be decreased due to delays during the resolution of
    10         the Oracle VM VirtualBox shared folders name service. To fix these
     10        the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> shared folders name service. To fix these
    1111        delays, add the following entries to the file
    1212        <filepath>\windows\system32\drivers\etc\lmhosts</filepath> of
  • trunk/doc/manual/en_US/dita/topics/ts_win-host-bridged-network-adapters.dita

    r99016 r99797  
    2828        <p>
    2929            The maximum number allowed is 14. After a reboot, try to
    30             reinstall Oracle VM VirtualBox.
     30            reinstall <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    3131          </p>
    3232      </li>
     
    3838            package for either the <userinput>sun_VBoxNetFlt</userinput> or
    3939            <userinput>sun_VBoxNetFltmp</userinput> components. The solution
    40             then is to uninstall Oracle VM VirtualBox, remove the INF cache
     40            then is to uninstall <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, remove the INF cache
    4141            (<filepath>%windir%\inf\INFCACHE.1</filepath>), reboot and
    42             try to reinstall Oracle VM VirtualBox.
     42            try to reinstall <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    4343          </p>
    4444      </li>
  • trunk/doc/manual/en_US/dita/topics/ts_win-host-cd-dvd-changes.dita

    r99016 r99797  
    1616        Certain applications may disable this key against Microsoft's
    1717        advice. If it is set to 0, change it to 1 and reboot your
    18         system. Oracle VM VirtualBox relies on Windows notifying it of media
     18        system. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> relies on Windows notifying it of media
    1919        changes.
    2020      </p>
  • trunk/doc/manual/en_US/dita/topics/ts_win-host-com-server.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8         Oracle VM VirtualBox makes use of the Microsoft Component Object Model
     8        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> makes use of the Microsoft Component Object Model
    99        (COM) for interprocess and intraprocess communication. This
    10         enables Oracle VM VirtualBox to share a common configuration among
     10        enables <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to share a common configuration among
    1111        different virtual machine processes and provide several user
    1212        interface options based on a common architecture. All global
    1313        status information and configuration is maintained by the
    1414        process <filepath>VBoxSVC.exe</filepath>, which is an
    15         out-of-process COM server. Whenever an Oracle VM VirtualBox process is
     15        out-of-process COM server. Whenever an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> process is
    1616        started, it requests access to the COM server and Windows
    1717        automatically starts the process. Note that it should never be
     
    2020    <p>
    2121        When the last process disconnects from the COM server, it will
    22         terminate itself after some seconds. The Oracle VM VirtualBox
     22        terminate itself after some seconds. The <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    2323        configuration XML files are maintained and owned by the COM
    2424        server and the files are locked whenever the server runs.
  • trunk/doc/manual/en_US/dita/topics/ts_win-host-host-only-network-adapters.dita

    r99016 r99797  
    77    <p>
    88        If a host-only adapter cannot be created, either with the
    9         VirtualBox Manager or the <userinput>VBoxManage</userinput> command, then
     9        <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> or the <userinput>VBoxManage</userinput> command, then
    1010        the INF cache is probably corrupt. In this case, the install log
    1111        at <filepath>%windir%\inf\setupapi.dev.log</filepath> would
     
    1313        for the <filepath>sun_VBoxNetAdp</filepath> component. Again, as
    1414        with the bridged networking problem described above, the
    15         solution is to uninstall Oracle VM VirtualBox, remove the INF cache
     15        solution is to uninstall <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, remove the INF cache
    1616        (<filepath>%windir%\inf\INFCACHE.1</filepath>), reboot and try
    17         to reinstall Oracle VM VirtualBox.
     17        to reinstall <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    1818      </p>
    1919  </body>
  • trunk/doc/manual/en_US/dita/topics/ts_win-host-iscsi.dita

    r99016 r99797  
    2121        workaround for this problem until Microsoft addresses the issue.
    2222        For example, open a command prompt window and start
    23         Oracle VM VirtualBox like this:
     23        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> like this:
    2424      </p>
    2525    <pre xml:space="preserve">set VBOX_DISABLE_HOST_DISK_CACHE=1
  • trunk/doc/manual/en_US/dita/topics/ts_win-vista-guest-networking.dita

    r99016 r99797  
    77    <p>
    88        With Windows Vista, Microsoft dropped support for the AMD PCNet
    9         card that legacy versions of Oracle VM VirtualBox used to provide as
     9        card that legacy versions of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> used to provide as
    1010        the default virtual network card. For Windows Vista guests,
    11         Oracle VM VirtualBox now uses an Intel E1000 card by default.
     11        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> now uses an Intel E1000 card by default.
    1212      </p>
    1313    <p>
  • trunk/doc/manual/en_US/dita/topics/unattended-guest-install-example.dita

    r99016 r99797  
    3333                              <p>
    3434                The <userinput>VBoxManage list ostypes</userinput> command
    35                 lists the guest OSes supported by Oracle VM VirtualBox,
     35                lists the guest OSes supported by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>,
    3636                including the name used for each OS in the
    3737                <userinput>VBoxManage</userinput> commands.
     
    4141                              <p>
    4242                A 64-bit Oracle Linux 7 VM is created and registered
    43                 with Oracle VM VirtualBox.
     43                with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    4444              </p>
    4545                           </li>
     
    169169                        <p>
    170170            The VM starts in headless mode, which means that the
    171             VirtualBox Manager window does not open.
     171            <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> window does not open.
    172172          </p>
    173173                     </li>
  • trunk/doc/manual/en_US/dita/topics/uninstall-solaris-host.dita

    r99016 r99797  
    77               <body>
    88                  <p>
    9         Uninstallation of Oracle VM VirtualBox on Oracle Solaris requires root
     9        Uninstallation of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> on Oracle Solaris requires root
    1010        permissions. To perform the uninstallation, start a root
    1111        terminal session and run the following command:
     
    1313                  <pre xml:space="preserve">pkgrm SUNWvbox</pre>
    1414                  <p>
    15         After confirmation, this will remove Oracle VM VirtualBox from your
     15        After confirmation, this will remove <ph conkeyref="vbox-conkeyref-phrases/product-name"/> from your
    1616        system.
    1717      </p>
  • trunk/doc/manual/en_US/dita/topics/usb-implementation-notes.dita

    r99016 r99797  
    99        On Windows hosts, a kernel mode device driver provides USB proxy
    1010        support. It implements both a USB monitor, which enables
    11         Oracle VM VirtualBox to capture devices when they are plugged in, and
     11        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to capture devices when they are plugged in, and
    1212        a USB device driver to claim USB devices for a particular
    1313        virtual machine. System reboots are not necessary after
    1414        installing the driver. Also, you do not need to replug devices
    15         for Oracle VM VirtualBox to claim them.
     15        for <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to claim them.
    1616      </p>
    1717                  <p>
    18         On supported Linux hosts, Oracle VM VirtualBox accesses USB devices
    19         through special files in the file system. When Oracle VM VirtualBox is
     18        On supported Linux hosts, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> accesses USB devices
     19        through special files in the file system. When <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is
    2020        installed, these are made available to all users in the
    2121        <codeph>vboxusers</codeph> system group. In order to be able
  • trunk/doc/manual/en_US/dita/topics/usb-over-rdp.dita

    r99016 r99797  
    77    <p>
    88        As a special feature additional to the VRDP support,
    9         Oracle VM VirtualBox also supports remote USB devices over the wire.
    10         That is, an Oracle VM VirtualBox guest that runs on one computer can
     9        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also supports remote USB devices over the wire.
     10        That is, an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> guest that runs on one computer can
    1111        access the USB devices of the remote computer on which the VRDP
    1212        data is being displayed the same way as USB devices that are
    1313        connected to the actual host. This enables running of virtual
    14         machines on an Oracle VM VirtualBox host that acts as a server, where
     14        machines on an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> host that acts as a server, where
    1515        a client can connect from elsewhere that needs only a network
    1616        adapter and a display capable of running an RDP viewer. When USB
    17         devices are plugged into the client, the remote Oracle VM VirtualBox
     17        devices are plugged into the client, the remote <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    1818        server can access them.
    1919      </p>
     
    3030        Ray thin clients, support accessing remote USB devices. RDP
    3131        clients for other platforms will be provided in future
    32         Oracle VM VirtualBox versions.
     32        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> versions.
    3333      </p>
    3434  </body>
  • trunk/doc/manual/en_US/dita/topics/usbip.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox supports passing through USB devices which are
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports passing through USB devices which are
    99      exposed over the network using the USB over IP protocol without
    1010      the need to configure the client side provided by the kernel and
    11       usbip tools. Furthermore, this feature works with Oracle VM VirtualBox
     11      usbip tools. Furthermore, this feature works with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    1212      running on any supported host, rather than just Linux alone, as is
    1313      the case with the official client.
     
    2121    <p>
    2222      USB devices exported on the device server are then accessible
    23       through VirtualBox Manager or <userinput>VBoxManage</userinput>, like any USB
     23      through <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> or <userinput>VBoxManage</userinput>, like any USB
    2424      devices attached locally. This can be used multiple times to
    2525      access different device servers.
  • trunk/doc/manual/en_US/dita/topics/usbtrafficcapturing.dita

    r99016 r99797  
    88      You can capture USB traffic for single USB devices or on the root
    99      hub level, which captures the traffic of all USB devices attached
    10       to the root hub. Oracle VM VirtualBox stores the traffic in a format
     10      to the root hub. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> stores the traffic in a format
    1111      which is compatible with Wireshark. To capture the traffic of a
    1212      specific USB device it must be attached to the VM with
  • trunk/doc/manual/en_US/dita/topics/user-interface.dita

    r99016 r99797  
    2525                     <p>
    2626                        <b outputclass="bold">Mini ToolBar:</b> In full screen
    27           or seamless mode, Oracle VM VirtualBox can display a small toolbar
     27          or seamless mode, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can display a small toolbar
    2828          that contains some of the items that are normally available
    2929          from the virtual machine's menu bar. This toolbar reduces
  • trunk/doc/manual/en_US/dita/topics/vbox-auth.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="vbox-auth">
    44  <title>RDP Authentication</title>
    5  
     5
    66  <body>
    77    <p>
    8         For each virtual machine that is remotely accessible using RDP,
    9         you can individually determine if and how client connections are
    10         authenticated. For this, use the <userinput>VBoxManage
    11         modifyvm</userinput> command with the
    12         <codeph>--vrde-auth-type</codeph> option. See
    13         <xref href="vboxmanage-modifyvm.dita">VBoxManage modifyvm</xref>. The following methods of
    14         authentication are available:
    15       </p>
     8        For each virtual machine that is remotely accessible using RDP, you can individually
     9        determine if and how client connections are authenticated. For this, use the
     10        <userinput>VBoxManage modifyvm</userinput> command with the
     11        <codeph>--vrde-auth-type</codeph> option. See <xref href="vboxmanage-modifyvm.dita">
     12        VBoxManage modifyvm</xref>. The following methods of authentication are available:
     13    </p>
    1614    <ul>
    1715      <li>
     
    2725            The <b outputclass="bold">external</b> method
    2826            provides external authentication through a special
    29             authentication library. Oracle VM VirtualBox ships with two
     27            authentication library. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> ships with two
    3028            special authentication libraries:
    3129          </p>
     
    105103                    <codeph>extradata</codeph> section the password
    106104                    needs to be written, is a plain text file,
    107                     Oracle VM VirtualBox uses hashes to encrypt passwords. The
     105                    <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses hashes to encrypt passwords. The
    108106                    following command must be used:
    109107                  </p>
     
    156154        In addition to the methods described above, you can replace the
    157155        default external authentication module with any other module.
    158         For this, Oracle VM VirtualBox provides a well-defined interface that
     156        For this, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides a well-defined interface that
    159157        enables you to write your own authentication module. This is
    160         described in detail in the Oracle VM VirtualBox Software Development
     158        described in detail in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Software Development
    161159        Kit (SDK) reference. See <xref href="VirtualBoxAPI.dita#VirtualBoxAPI"/>.
    162160      </p>
    163161  </body>
    164  
     162
    165163</topic>
  • trunk/doc/manual/en_US/dita/topics/vboxandsolzvmm.dita

    r99016 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="vboxandsolzvmm">
    4   <title>Oracle VM VirtualBox and Oracle Solaris Kernel Zones</title>
     4  <title><ph conkeyref="vbox-conkeyref-phrases/product-name"/> and Oracle Solaris Kernel Zones</title>
    55 
    66  <body>
    77    <p>
    88      Oracle Solaris kernel zones on x86-based systems make use of
    9       hardware-assisted virtualization features like Oracle VM VirtualBox
    10       does. However, for kernel zones and Oracle VM VirtualBox to share this
     9      hardware-assisted virtualization features like <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
     10      does. However, for kernel zones and <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to share this
    1111      hardware resource, they need to cooperate.
    1212    </p>
    1313    <p>
    14       By default, due to performance reasons, Oracle VM VirtualBox acquires
     14      By default, due to performance reasons, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> acquires
    1515      the hardware-assisted virtualization resource (VT-x/AMD-V)
    1616      globally on the host machine and uses it until the last
    17       Oracle VM VirtualBox VM that requires it is powered off. This prevents
     17      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VM that requires it is powered off. This prevents
    1818      other software from using VT-x/AMD-V during the time
    19       Oracle VM VirtualBox has taken control of it.
     19      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has taken control of it.
    2020    </p>
    2121    <p>
    22       Oracle VM VirtualBox can be instructed to relinquish use of
     22      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can be instructed to relinquish use of
    2323      hardware-assisted virtualization features when not executing guest
    2424      code, thereby allowing kernel zones to make use of them. To do
    25       this, shutdown all Oracle VM VirtualBox VMs and execute the following
     25      this, shutdown all <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VMs and execute the following
    2626      command:
    2727    </p>
     
    2929    <p>
    3030      This command needs to be executed only once as the setting is
    31       stored as part of the global Oracle VM VirtualBox settings which will
    32       continue to persist across host-reboots and Oracle VM VirtualBox
     31      stored as part of the global <ph conkeyref="vbox-conkeyref-phrases/product-name"/> settings which will
     32      continue to persist across host-reboots and <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    3333      upgrades.
    3434    </p>
  • trunk/doc/manual/en_US/dita/topics/vboxbowsolaris11.dita

    r99016 r99797  
    77  <body>
    88    <p>
    9       Oracle VM VirtualBox includes a network filter driver that utilizes
     9      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> includes a network filter driver that utilizes
    1010      Oracle Solaris 11's Crossbow functionality. By default, this new
    1111      driver is installed for Oracle Solaris 11 hosts that have support
     
    1515      To force installation of the older STREAMS based network filter
    1616      driver, execute as root the following command before installing
    17       the Oracle VM VirtualBox package:
     17      the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> package:
    1818    </p>
    1919    <pre xml:space="preserve">$ touch /etc/vboxinst_vboxflt</pre>
     
    2121      To force installation of the Crossbow based network filter driver,
    2222      execute as root the following command before installing the
    23       Oracle VM VirtualBox package:
     23      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> package:
    2424    </p>
    2525    <pre xml:space="preserve">$ touch /etc/vboxinst_vboxbow</pre>
    2626    <p>
    27       To check which driver is currently being used by Oracle VM VirtualBox,
     27      To check which driver is currently being used by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>,
    2828      execute:
    2929    </p>
    3030    <pre xml:space="preserve">$ modinfo | grep vbox</pre>
    3131    <p>
    32       If the output contains "vboxbow", it indicates Oracle VM VirtualBox is
     32      If the output contains "vboxbow", it indicates <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is
    3333      using the Crossbow network filter driver, while the name "vboxflt"
    3434      indicates usage of the older STREAMS network filter.
  • trunk/doc/manual/en_US/dita/topics/vboxbowvnictemplates.dita

    r99016 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="vboxbowvnictemplates">
    4   <title>Oracle VM VirtualBox VNIC Templates for VLANs on Oracle Solaris 11 Hosts</title>
     4  <title><ph conkeyref="vbox-conkeyref-phrases/product-name"/> VNIC Templates for VLANs on Oracle Solaris 11 Hosts</title>
    55 
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox supports Virtual Network Interface (VNIC) templates
    9       for configuring VMs over VLANs. An Oracle VM VirtualBox VNIC template is
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports Virtual Network Interface (VNIC) templates
     9      for configuring VMs over VLANs. An <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VNIC template is
    1010      a VNIC whose name starts with
    1111      <filepath>vboxvnic_template</filepath>. The string is
     
    1919    <p>
    2020      The following is an example of how to use a VNIC template to
    21       configure a VM over a VLAN. Create an Oracle VM VirtualBox VNIC
     21      configure a VM over a VLAN. Create an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VNIC
    2222      template, by executing as root:
    2323    </p>
  • trunk/doc/manual/en_US/dita/topics/vboxconfigdata-XML-files.dita

    r99016 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="vboxconfigdata-XML-files">
    4   <title>Oracle VM VirtualBox XML Files</title>
     4  <title><ph conkeyref="vbox-conkeyref-phrases/product-name"/> XML Files</title>
    55 
    66  <body>
    77    <p>
    8         Oracle VM VirtualBox uses XML for both the machine settings files and
     8        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses XML for both the machine settings files and
    99        the global configuration file,
    1010        <filepath>VirtualBox.xml</filepath>.
    1111      </p>
    1212    <p>
    13         All Oracle VM VirtualBox XML files are versioned. When a new settings
     13        All <ph conkeyref="vbox-conkeyref-phrases/product-name"/> XML files are versioned. When a new settings
    1414        file is created, for example because a new virtual machine is
    15         created, Oracle VM VirtualBox automatically uses the settings format
    16         of the current Oracle VM VirtualBox version. These files may not be
     15        created, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> automatically uses the settings format
     16        of the current <ph conkeyref="vbox-conkeyref-phrases/product-name"/> version. These files may not be
    1717        readable if you downgrade to an earlier version of
    18         Oracle VM VirtualBox. However, when Oracle VM VirtualBox encounters a
     18        <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. However, when <ph conkeyref="vbox-conkeyref-phrases/product-name"/> encounters a
    1919        settings file from an earlier version, such as after upgrading
    20         Oracle VM VirtualBox, it attempts to preserve the settings format as
     20        <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, it attempts to preserve the settings format as
    2121        much as possible. It will only silently upgrade the settings
    2222        format if the current settings cannot be expressed in the old
    2323        format, for example because you enabled a feature that was not
    24         present in an earlier version of Oracle VM VirtualBox.
     24        present in an earlier version of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    2525      </p>
    2626    <p>
    27         In such cases, Oracle VM VirtualBox backs up the old settings file in
     27        In such cases, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> backs up the old settings file in
    2828        the virtual machine's configuration directory. If you need to go
    29         back to the earlier version of Oracle VM VirtualBox, then you will
     29        back to the earlier version of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, then you will
    3030        need to manually copy these backup files back.
    3131      </p>
    3232    <p>
    3333        We intentionally do not document the specifications of the
    34         Oracle VM VirtualBox XML files, as we must reserve the right to modify
     34        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> XML files, as we must reserve the right to modify
    3535        them in the future. We therefore strongly suggest that you do
    36         not edit these files manually. Oracle VM VirtualBox provides complete
     36        not edit these files manually. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides complete
    3737        access to its configuration data through its the
    3838        <userinput>VBoxManage</userinput> command line tool, see
  • trunk/doc/manual/en_US/dita/topics/vboxconfigdata-global.dita

    r99016 r99797  
    77    <p>
    88        In addition to the files for the virtual machines,
    9         Oracle VM VirtualBox maintains global configuration data in the
     9        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> maintains global configuration data in the
    1010        following directory:
    1111      </p>
     
    2525    </ul>
    2626    <p>
    27         Oracle VM VirtualBox creates this configuration directory
     27        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates this configuration directory
    2828        automatically, if necessary. You can specify an alternate
    2929        configuration directory by either setting the
     
    3333        <filepath>VirtualBox.xml</filepath> settings file points to all
    3434        other configuration files, this enables switching between
    35         several Oracle VM VirtualBox configurations.
     35        several <ph conkeyref="vbox-conkeyref-phrases/product-name"/> configurations.
    3636      </p>
    3737    <p>
    38         In this configuration directory, Oracle VM VirtualBox stores its
     38        In this configuration directory, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> stores its
    3939        global settings file, an XML file called
    4040        <filepath>VirtualBox.xml</filepath>. This file includes global
  • trunk/doc/manual/en_US/dita/topics/vboxconfigdata-machine-folder.dita

    r99497 r99797  
    33<topic xml:lang="en-us" id="vboxconfigdata-machine-folder">
    44  <title>The Machine Folder</title>
    5  
     5
    66  <body>
    77    <p>
     
    1414    <p>
    1515        By default, this machine folder is located in a common folder
    16         called <filepath>VirtualBox VMs</filepath>, which Oracle VM VirtualBox
     16        called <filepath>VirtualBox VMs</filepath>, which <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    1717        creates in the current system user's home directory. The
    1818        location of this home directory depends on the conventions of
     
    3737            <codeph>root</codeph> where it is taken from the account
    3838            database. This is a workaround for the frequent trouble
    39             caused by users using Oracle VM VirtualBox in combination with the
     39            caused by users using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> in combination with the
    4040            tool <userinput>sudo</userinput>, which by default does not
    4141            reset the environment variable <filepath>$HOME</filepath>.
     
    5959    <p>
    6060        As an example, when you create a virtual machine called "Example
    61         VM", Oracle VM VirtualBox creates the following:
     61        VM", <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates the following:
    6262      </p>
    6363    <ul>
     
    9292      </p>
    9393    <p>
    94         You can change the default machine folder by selecting
    95         <b outputclass="bold">Preferences</b> from the
    96         <b outputclass="bold">File</b> menu in the Oracle VM VirtualBox
    97         main window. Then, in the displayed window, click on the
    98         <b outputclass="bold">General</b> tab. Alternatively, use
    99         the <userinput>VBoxManage setproperty machinefolder</userinput>
    100         command. See <xref href="vboxmanage-setproperty.dita">VBoxManage setproperty</xref>.
    101       </p>
     94        You can change the default machine folder by selecting <b outputclass="bold">Preferences</b>
     95        from the <b outputclass="bold">File</b> menu in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> main window. Then, in
     96        the displayed window, click on the <b outputclass="bold">General</b> tab. Alternatively, use
     97        the <userinput>VBoxManage setproperty machinefolder</userinput> command. See
     98        <xref href="vboxmanage-setproperty.dita">VBoxManage setproperty</xref>.
     99    </p>
    102100  </body>
    103  
     101
    104102</topic>
  • trunk/doc/manual/en_US/dita/topics/vboxconfigdata-summary-locations.dita

    r99182 r99797  
    77    <p>
    88        The following table gives a brief overview of the configuration
    9         data locations on an Oracle VM VirtualBox host.
     9        data locations on an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> host.
    1010      </p>
    1111    <table id="table-config-summary">
  • trunk/doc/manual/en_US/dita/topics/vboxconfigdata.dita

    r99016 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="vboxconfigdata">
    4   <title>Where Oracle VM VirtualBox Stores its Files</title>
     4  <title>Where <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Stores its Files</title>
    55 
    66  <body>
    77    <p>
    8       In Oracle VM VirtualBox, a virtual machine and its settings are
     8      In <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, a virtual machine and its settings are
    99      described in a virtual machine settings file in XML format. In
    1010      addition, most virtual machines have one or more virtual hard
     
    1515    </p>
    1616    <p>
    17       Global configuration data for Oracle VM VirtualBox is maintained in
     17      Global configuration data for <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is maintained in
    1818      another location on the host. See
    1919      <xref href="vboxconfigdata-global.dita#vboxconfigdata-global"/>.
  • trunk/doc/manual/en_US/dita/topics/vboxexpertstoragemgmt.dita

    r99016 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="vboxexpertstoragemgmt">
    4   <title>Oracle VM VirtualBox Expert Storage Management</title>
     4  <title><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Expert Storage Management</title>
    55 
    66  <body>
    77    <p>
    8       In case the snapshot model of Oracle VM VirtualBox is not sufficient it
     8      In case the snapshot model of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is not sufficient it
    99      is possible to enable a special mode which makes it possible to
    1010      reconfigure storage attachments while the VM is paused. The user
  • trunk/doc/manual/en_US/dita/topics/vboxheadless.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8         While any VM started from VirtualBox Manager is capable of running
     8        While any VM started from <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> is capable of running
    99        virtual machines remotely, it is not convenient to have to run
    1010        the full GUI if you never want to have VMs displayed locally in
     
    1414        a graphical user interface on the server at all. This is
    1515        especially true for Linux or Oracle Solaris hosts, as the
    16         VirtualBox Manager comes with dependencies on the Qt and SDL libraries.
     16        <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> comes with dependencies on the Qt and SDL libraries.
    1717        This is inconvenient if you would rather not have the X Window
    1818        system on your server at all.
    1919      </p>
    2020    <p>
    21         Oracle VM VirtualBox therefore comes with a front-end called
     21        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> therefore comes with a front-end called
    2222        <userinput>VBoxHeadless</userinput>, which produces no visible
    2323        output on the host at all, but still can optionally deliver VRDP
     
    2727    <note>
    2828      <p>
    29           In legacy releases of Oracle VM VirtualBox, the headless server was
     29          In legacy releases of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, the headless server was
    3030          called <userinput>VBoxVRDP</userinput>. For backwards
    31           compatibility, the Oracle VM VirtualBox installation still includes
     31          compatibility, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> installation still includes
    3232          an executable with that name.
    3333        </p>
     
    4444        <pre xml:space="preserve">$ VBoxManage startvm <varname>VM-name</varname> --type headless</pre>
    4545        <p>
    46             The <codeph>--type</codeph> option causes Oracle VM VirtualBox to
     46            The <codeph>--type</codeph> option causes <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to
    4747            use <userinput>VBoxHeadless</userinput> as the front-end to the
    4848            internal virtualization engine, instead of the Qt front-end.
     
    7070      <li>
    7171        <p>
    72             Start <userinput>VBoxHeadless</userinput> from VirtualBox Manager, by
     72            Start <userinput>VBoxHeadless</userinput> from <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, by
    7373            pressing the Shift key when starting a virtual machine or by
    7474            selecting <b outputclass="bold">Headless Start</b>
  • trunk/doc/manual/en_US/dita/topics/vboximg-mount.dita

    r99016 r99797  
    88               <p>
    99                  <userinput>vboximg-mount</userinput> is a command line utility for Mac
    10       OS and Linux hosts that provides raw access to an Oracle VM VirtualBox
     10      OS and Linux hosts that provides raw access to an <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    1111      virtual disk image on the host system. Use this utility to mount,
    1212      view, and optionally modify the disk image contents.
     
    1414               <p>
    1515      The utility is based on Filesystem in Userspace (FUSE) technology
    16       and uses the VirtualBox runtime engine. Ensure that Oracle VM VirtualBox
     16      and uses the VirtualBox runtime engine. Ensure that <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    1717      is running on the host system.
    1818    </p>
     
    6464    </p>
    6565               <p>
    66       When <userinput>vboximg-mount</userinput> mounts an Oracle VM VirtualBox
     66      When <userinput>vboximg-mount</userinput> mounts an <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    6767      disk image, it creates a one level deep file system at a mount
    6868      point that you specify. The file system includes a device node
  • trunk/doc/manual/en_US/dita/topics/vboxmanager-wizards.dita

    r99016 r99797  
    33  PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    44<topic xml:lang="en-us" id="vboxmanager-wizards">
    5                <title>About VirtualBox Manager Wizards</title>
     5               <title>About <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> Wizards</title>
    66               
    77               <body>
    88                  <p>
    9         VirtualBox Manager includes wizards that enable you to complete tasks
     9        <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> includes wizards that enable you to complete tasks
    1010        easily. Examples of such tasks are when you create a new virtual
    11         machine or use the cloud integration features of Oracle VM VirtualBox.
     11        machine or use the cloud integration features of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    1212      </p>
    1313                  <p>
     
    3333            mode.</b>
    3434                           </b> This display mode is designed
    35             for more advanced users of Oracle VM VirtualBox. All settings are
     35            for more advanced users of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. All settings are
    3636            displayed on a single page, enabling quicker completion of
    3737            tasks.
  • trunk/doc/manual/en_US/dita/topics/vboxsvc-session-0-known-issues.dita

    r99016 r99797  
    1111            resources, there might be some issues with accessing network
    1212            shares created in the interactive user session when at least
    13             one of the Oracle VM VirtualBox processes are running in session
     13            one of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> processes are running in session
    1414            0.
    1515          </p>
  • trunk/doc/manual/en_US/dita/topics/vboxsvc-session-0.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox supports executing the VBoxSVC in Windows session
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports executing the VBoxSVC in Windows session
    99      0. This allows VBoxSVC to run like a regular Windows service,
    1010      which in turn enables headless VMs to continue running even if the
  • trunk/doc/manual/en_US/dita/topics/vboxwatchdog-hostisln.dita

    r99016 r99797  
    77    <p>
    88        To detect whether a host is being isolated, that is, the host
    9         cannot reach the Oracle VM VirtualBox server instance anymore, the
     9        cannot reach the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> server instance anymore, the
    1010        host needs to set an alternating value to a global extradata
    1111        value within a time period. If this value is not set within that
  • trunk/doc/manual/en_US/dita/topics/vboxwatchdog-linux.dita

    r99182 r99797  
    2323      </p>
    2424    <table id="table-vboxwatchdog-config-params">
    25       <title>Oracle VM VirtualBox Watchdog Configuration Parameters</title>
    26       <desc>Oracle VM VirtualBox Watchdog Configuration Parameters</desc>
     25      <title><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Watchdog Configuration Parameters</title>
     26      <desc><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Watchdog Configuration Parameters</desc>
    2727      <tgroup cols="3">       
    2828        <thead>
  • trunk/doc/manual/en_US/dita/topics/vboxwatchdog-solaris.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8         On Oracle Solaris hosts, the Oracle VM VirtualBox watchdog service
     8        On Oracle Solaris hosts, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> watchdog service
    99        daemon is integrated into the SMF framework. You can change the
    1010        parameters, but do not have to if the defaults already match
     
    3232    <p>
    3333        When everything is configured correctly you can start the
    34         Oracle VM VirtualBox watchdog service with the following command:
     34        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> watchdog service with the following command:
    3535      </p>
    3636    <pre xml:space="preserve">svcadm enable svc:/application/virtualbox/balloonctrl:default</pre>
  • trunk/doc/manual/en_US/dita/topics/vboxwatchdog.dita

    r99016 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="vboxwatchdog">
    4   <title>Oracle VM VirtualBox Watchdog</title>
     4  <title><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Watchdog</title>
    55 
    66  <body>
     
    3030        <p><b outputclass="bold">Host isolation detection.</b>
    3131          This service provides a way to detect whether the host cannot
    32           reach the specific Oracle VM VirtualBox server instance anymore and
     32          reach the specific <ph conkeyref="vbox-conkeyref-phrases/product-name"/> server instance anymore and
    3333          take appropriate actions, such as shutting down, saving the
    3434          current state or even powering down certain VMs.
  • trunk/doc/manual/en_US/dita/topics/vboxwebsrv-daemon.dita

    r99016 r99797  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="vboxwebsrv-daemon">
    4   <title>Starting the Oracle VM VirtualBox Web Service Automatically</title>
     4  <title>Starting the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Web Service Automatically</title>
    55 
    66  <body>
    77    <p>
    8       The Oracle VM VirtualBox web service, <userinput>vboxwebsrv</userinput>, is
    9       used for controlling Oracle VM VirtualBox remotely. It is documented in
    10       detail in the Oracle VM VirtualBox Software Development Kit (SDK). See
     8      The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> web service, <userinput>vboxwebsrv</userinput>, is
     9      used for controlling <ph conkeyref="vbox-conkeyref-phrases/product-name"/> remotely. It is documented in
     10      detail in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Software Development Kit (SDK). See
    1111      <xref href="VirtualBoxAPI.dita#VirtualBoxAPI"/>. Web service start scripts are
    1212      available for supported host operating systems. The following
    13       sections describe how to use the scripts. The Oracle VM VirtualBox web
     13      sections describe how to use the scripts. The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> web
    1414      service is never started automatically as a result of a standard
    1515      installation.
  • trunk/doc/manual/en_US/dita/topics/vboxwebsrv-osx.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8         On macOS, launchd is used to start the Oracle VM VirtualBox
     8        On macOS, launchd is used to start the <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    99        webservice. An example configuration file can be found in
    1010        <filepath>$HOME/Library/LaunchAgents/org.virtualbox.vboxwebsrv.plist</filepath>.
  • trunk/doc/manual/en_US/dita/topics/vboxwebsrv-solaris.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8         On Oracle Solaris hosts, the Oracle VM VirtualBox web service daemon
     8        On Oracle Solaris hosts, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> web service daemon
    99        is integrated into the SMF framework. You can change the
    1010        parameters, but do not have to if the defaults below already
     
    3333    <p>
    3434        When everything is configured correctly you can start the
    35         Oracle VM VirtualBox web service with the following command:
     35        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> web service with the following command:
    3636      </p>
    3737    <pre xml:space="preserve">svcadm enable svc:/application/virtualbox/webservice:default</pre>
  • trunk/doc/manual/en_US/dita/topics/vdidetails.dita

    r99497 r99797  
    99      Disk image files reside on the host system and are seen by the
    1010      guest systems as hard disks of a certain geometry. When a guest OS
    11       reads from or writes to a hard disk, Oracle VM VirtualBox redirects the
     11      reads from or writes to a hard disk, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> redirects the
    1212      request to the image file.
    1313    </p>
     
    1515      Like a physical disk, a virtual disk has a size, or capacity,
    1616      which must be specified when the image file is created. As opposed
    17       to a physical disk however, Oracle VM VirtualBox enables you to expand
     17      to a physical disk however, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to expand
    1818      an image file after creation, even if it has data already. See
    1919      <xref href="vboxmanage-modifymedium.dita"/>.
    2020    </p>
    2121               <p>
    22       Oracle VM VirtualBox supports the following types of disk image files:
     22      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports the following types of disk image files:
    2323    </p>
    2424               <ul>
    2525                  <li>
    2626                     <p>
    27                         <b outputclass="bold">VDI.</b> Normally, Oracle VM VirtualBox
     27                        <b outputclass="bold">VDI.</b> Normally, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    2828          uses its own container format for guest hard disks. This is
    2929          called a Virtual Disk Image (VDI) file. This format is used
     
    3333                  <li>
    3434                     <p>
    35                         <b outputclass="bold">VMDK.</b> Oracle VM VirtualBox also
     35                        <b outputclass="bold">VMDK.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also
    3636          fully supports the popular and open VMDK container format that
    3737          is used by many other virtualization products, such as VMware.
     
    4040                  <li>
    4141                     <p>
    42                         <b outputclass="bold">VHD.</b> Oracle VM VirtualBox also
     42                        <b outputclass="bold">VHD.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also
    4343          fully supports the VHD format used by Microsoft.
    4444        </p>
     
    8383          drive reaches the maximum capacity chosen when the drive was
    8484          created. While this format takes less space initially, the
    85           fact that Oracle VM VirtualBox needs to expand the image file
     85          fact that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> needs to expand the image file
    8686          consumes additional computing resources, so until the disk
    8787          file size has stabilized, write operations may be slower than
  • trunk/doc/manual/en_US/dita/topics/virt-why-useful.dita

    r99016 r99797  
    77            <body>
    88               <p>
    9       The techniques and features that Oracle VM VirtualBox provides are
     9      The techniques and features that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides are
    1010      useful in the following scenarios:
    1111    </p>
     
    1414                     <p>
    1515                        <b outputclass="bold">Running multiple operating systems
    16           simultaneously.</b> Oracle VM VirtualBox enables you to run
     16          simultaneously.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to run
    1717          more than one OS at a time. This way, you can run software
    1818          written for one OS on another, such as Windows software on
     
    3030          machines to ship entire software configurations. For example,
    3131          installing a complete mail server solution on a real machine
    32           can be a tedious task. With Oracle VM VirtualBox, such a complex
     32          can be a tedious task. With <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, such a complex
    3333          setup, often called an <i>appliance</i>, can be
    3434          packed into a virtual machine. Installing and running a mail
    3535          server becomes as easy as importing such an appliance into
    36           Oracle VM VirtualBox.
     36          <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    3737        </p>
    3838                  </li>
     
    5252        </p>
    5353                     <p>
    54           In addition to that, with the use of another Oracle VM VirtualBox
     54          In addition to that, with the use of another <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    5555          feature called <i>snapshots</i>, one can save a
    5656          particular state of a virtual machine and revert back to that
  • trunk/doc/manual/en_US/dita/topics/virtintro.dita

    r99016 r99797  
    1717                        <b outputclass="bold">Host operating system (host
    1818          OS).</b> This is the OS of the physical computer on
    19           which Oracle VM VirtualBox was installed. There are versions of
    20           Oracle VM VirtualBox for Windows, macOS, Linux, and Oracle Solaris
     19          which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> was installed. There are versions of
     20          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> for Windows, macOS, Linux, and Oracle Solaris
    2121          hosts. See <xref href="hostossupport.dita#hostossupport"/>.
    2222        </p>
    2323                     <p>
    24           Most of the time, this manual discusses all Oracle VM VirtualBox
     24          Most of the time, this manual discusses all <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    2525          versions together. There may be platform-specific differences
    2626          which we will point out where appropriate.
     
    3131                        <b outputclass="bold">Guest operating system (guest
    3232          OS).</b> This is the OS that is running inside the
    33           virtual machine. Theoretically, Oracle VM VirtualBox can run any x86
     33          virtual machine. Theoretically, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can run any x86
    3434          OS such as DOS, Windows, OS/2, FreeBSD, and OpenBSD. But to
    3535          achieve near-native performance of the guest code on your
     
    4747                     <p>
    4848                        <b outputclass="bold">Virtual machine (VM).</b> This is
    49           the special environment that Oracle VM VirtualBox creates for your
     49          the special environment that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates for your
    5050          guest OS while it is running. In other words, you run your
    5151          guest OS <i>in</i> a VM. Normally, a VM is shown
    5252          as a window on your computer's desktop. Depending on which of
    53           the various frontends of Oracle VM VirtualBox you use, the VM might
     53          the various frontends of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> you use, the VM might
    5454          be shown in full screen mode or remotely on another computer.
    5555        </p>
    5656                     <p>
    57           Internally, Oracle VM VirtualBox treats a VM as a set of parameters
     57          Internally, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> treats a VM as a set of parameters
    5858          that specify its behavior. Some parameters describe hardware
    5959          settings, such as the amount of memory and number of CPUs
     
    6262        </p>
    6363                     <p>
    64           You can view these VM settings in VirtualBox Manager, in the
     64          You can view these VM settings in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, in the
    6565          <b outputclass="bold">Settings</b> window, and by
    6666          running the <userinput>VBoxManage</userinput> command. See
     
    7272                        <b outputclass="bold">Guest Additions.</b> This refers
    7373          to special software packages which are shipped with
    74           Oracle VM VirtualBox but designed to be installed
     74          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> but designed to be installed
    7575          <i>inside</i> a VM to improve performance of the
    7676          guest OS and to add extra features. See
  • trunk/doc/manual/en_US/dita/topics/virtual-media-manager.dita

    r99183 r99797  
    77            <body>
    88               <p>
    9       Oracle VM VirtualBox keeps track of all the hard disk, CD/DVD-ROM, and
     9      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> keeps track of all the hard disk, CD/DVD-ROM, and
    1010      floppy disk images which are in use by virtual machines. These are
    1111      often referred to as <i>known media</i> and come
     
    2020                  <li>
    2121                     <p>
    22           Registered media, for compatibility with legacy Oracle VM VirtualBox
     22          Registered media, for compatibility with legacy <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    2323          versions.
    2424        </p>
     
    3030      you access by clicking <b outputclass="bold">Media</b> on
    3131      the global <b outputclass="bold">Tools</b> menu in
    32       VirtualBox Manager.
     32      <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.
    3333    </p>
    3434              <fig id="fig-virtual-media-manager">
     
    5050                  <li>
    5151                     <p>
    52           Hard disk images, either in Oracle VM VirtualBox's own Virtual Disk
     52          Hard disk images, either in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s own Virtual Disk
    5353          Image (VDI) format, or in the third-party formats listed in
    5454          <xref href="vdidetails.dita#vdidetails"/>.
     
    129129                     <p>
    130130          When you use the Virtual Media Manager to move a disk image,
    131           Oracle VM VirtualBox updates all related configuration files
     131          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> updates all related configuration files
    132132          automatically.
    133133        </p>
     
    143143              modifymedium --setlocation</userinput>                       
    144144            command to configure the new path of the disk image on the
    145             host file system. This command updates the Oracle VM VirtualBox
     145            host file system. This command updates the <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    146146            configuration automatically.
    147147          </p>
     
    262262                  <p>
    263263        Do not simply make copies of virtual disk images. If you import
    264         such a second copy into a VM, Oracle VM VirtualBox issues an error
    265         because Oracle VM VirtualBox assigns a universally unique identifier
     264        such a second copy into a VM, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> issues an error
     265        because <ph conkeyref="vbox-conkeyref-phrases/product-name"/> assigns a universally unique identifier
    266266        (UUID) to each disk image to ensure that it is only used one
    267267        time. See <xref href="cloningvdis.dita#cloningvdis"/>. Also, if you want to
    268         copy a VM to another system, use the Oracle VM VirtualBox import and
     268        copy a VM to another system, use the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> import and
    269269        export features. See <xref href="ovf.dita#ovf"/>.
    270270      </p>
  • trunk/doc/manual/en_US/dita/topics/vm-info.dita

    r99016 r99797  
    77            <body>
    88               <p>
    9       VirtualBox Manager includes the following tools for viewing runtime
     9      <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> includes the following tools for viewing runtime
    1010      information and changing the configuration of virtual machines.
    1111    </p>
  • trunk/doc/manual/en_US/dita/topics/vmencryption-addpassword.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8         When Oracle VM VirtualBox has just started up the encrypted VM cannot
     8        When <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has just started up the encrypted VM cannot
    99        be opened and it stays inaccessible. Also, the encrypted VM
    1010        stays inaccessible if it was just registered without a password
    1111        or the password is incorrect. The user needs to provide the
    12         password using VirtualBox Manager or with the following
     12        password using <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> or with the following
    1313        <userinput>VBoxManage</userinput> command:
    1414      </p>
  • trunk/doc/manual/en_US/dita/topics/vmencryption-decryption.dita

    r99016 r99797  
    77    <p>
    88        In some circumstances it might be required to decrypt previously
    9         encrypted VMs. This can be done in VirtualBox Manager or using
     9        encrypted VMs. This can be done in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> or using
    1010        <userinput>VBoxManage</userinput> with the following command:
    1111      </p>
  • trunk/doc/manual/en_US/dita/topics/vmencryption-encryption.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8         Encrypting a VM can be done either using VirtualBox Manager or the
     8        Encrypting a VM can be done either using <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> or the
    99        <userinput>VBoxManage</userinput>. To encrypt an unencrypted VM with
    1010        <userinput>VBoxManage</userinput>, use:
  • trunk/doc/manual/en_US/dita/topics/vmencryption-limitations.dita

    r99016 r99797  
    2929        <p>
    3030            When encrypting or decrypting the VM, the password is passed
    31             in clear text using the Oracle VM VirtualBox API. This needs to be
     31            in clear text using the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> API. This needs to be
    3232            kept in mind, especially when using third party API clients
    3333            which make use of the web service where the password might
  • trunk/doc/manual/en_US/dita/topics/vmencryption.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox enables you to transparently encrypt the VM data
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to transparently encrypt the VM data
    99      stored in the configuration file, saved state, and EFI boot data
    1010      for the guest.
    1111    </p>
    1212    <p>
    13       Oracle VM VirtualBox uses the AES algorithm in various modes. The
     13      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses the AES algorithm in various modes. The
    1414      selected mode depends on the encrypting component of the VM.
    15       Oracle VM VirtualBox supports 128-bit or 256-bit data encryption keys
     15      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports 128-bit or 256-bit data encryption keys
    1616      (DEK). The DEK is stored encrypted in the VM configuration file
    1717      and is decrypted during VM startup.
  • trunk/doc/manual/en_US/dita/topics/vrde-crypt.dita

    r99016 r99797  
    6464              </p>
    6565            <p>
    66                 The version of OpenSSL used by Oracle VM VirtualBox supports
     66                The version of OpenSSL used by <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports
    6767                TLS versions 1.0, 1.1, 1.2, and 1.3.
    6868              </p>
  • trunk/doc/manual/en_US/dita/topics/vrde-multiconnection.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8         The VRDP server of Oracle VM VirtualBox supports multiple simultaneous
     8        The VRDP server of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports multiple simultaneous
    99        connections to the same running VM from different clients. All
    1010        connected clients see the same screen output and share a mouse
  • trunk/doc/manual/en_US/dita/topics/vrde-multimonitor.dita

    r99016 r99797  
    1414        to using the <codeph>domain</codeph> login parameter
    1515        (<codeph>-d</codeph>). If the parameter ends with
    16         <codeph>@</codeph> followed by a number, Oracle VM VirtualBox
     16        <codeph>@</codeph> followed by a number, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    1717        interprets this number as the screen index. The primary guest
    1818        screen is selected with <codeph>@1</codeph>, the first
  • trunk/doc/manual/en_US/dita/topics/vrde.dita

    r99497 r99797  
    66  <body>
    77    <p>
    8       Oracle VM VirtualBox can display virtual machines remotely, meaning that
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can display virtual machines remotely, meaning that
    99      a virtual machine can execute on one computer even though the
    1010      machine will be displayed on a second computer, and the machine
     
    1313    </p>
    1414    <p>
    15       For maximum flexibility, Oracle VM VirtualBox implements remote machine
     15      For maximum flexibility, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> implements remote machine
    1616      display through a generic extension interface called the
    1717      VirtualBox Remote Desktop Extension (VRDE). The base open source
    18       Oracle VM VirtualBox package only provides this interface, while
     18      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> package only provides this interface, while
    1919      implementations can be supplied by third parties with
    20       Oracle VM VirtualBox extension packages, which must be installed
     20      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> extension packages, which must be installed
    2121      separately from the base package. See
    22       <xref href="intro-installing.dita">Installing Oracle VM VirtualBox and Extension Packs</xref>.
     22      <xref href="intro-installing.dita">Installing <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and Extension Packs</xref>.
    2323    </p>
    2424    <p>
    2525      Oracle provides support for the VirtualBox Remote Display Protocol
    26       (VRDP) in such an Oracle VM VirtualBox extension package.
     26      (VRDP) in such an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> extension package.
    2727    </p>
    2828    <p>
     
    3434      Even when the extension is installed, the VRDP server is disabled
    3535      by default. It can easily be enabled on a per-VM basis either from
    36       VirtualBox Manager in the <b outputclass="bold">Display</b>
     36      <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> in the <b outputclass="bold">Display</b>
    3737      settings, see <xref href="settings-display.dita">Display Settings</xref>, or with the
    3838      <userinput>VBoxManage</userinput> command, as follows:
     
    6565      The actual port used by a running VM can be either queried with
    6666      the <userinput>VBoxManage showvminfo</userinput> command or seen in
    67       VirtualBox Manager on the <b outputclass="bold">Runtime</b> tab of
     67      <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> on the <b outputclass="bold">Runtime</b> tab of
    6868      the <b outputclass="bold">Session Information</b> dialog,
    6969      which is accessible from the
     
    7171    </p>
    7272    <p>
    73       Oracle VM VirtualBox supports IPv6. If the host OS supports IPv6 the
     73      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports IPv6. If the host OS supports IPv6 the
    7474      VRDP server will automatically listen for IPv6 connections in
    7575      addition to IPv4.
  • trunk/doc/manual/en_US/dita/topics/warpguest.dita

    r99016 r99797  
    2323        that any time synchronization mechanism will frequently try to
    2424        resynchronize the guest clock with the reference clock, which is
    25         the host clock if the Oracle VM VirtualBox Guest Additions are active.
     25        the host clock if the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions are active.
    2626        Therefore any time synchronization should be disabled if the
    2727        rate of the guest clock is changed as described above. See
  • trunk/doc/manual/en_US/dita/topics/webcam-using-guest.dita

    r99016 r99797  
    66  <body>
    77    <p>
    8         Oracle VM VirtualBox includes a feature called <i>webcam
     8        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> includes a feature called <i>webcam
    99        passthrough</i>, which enables a guest to use a host
    1010        webcam. This complements the general USB passthrough support
     
    1616      <p>
    1717          The webcam passthrough module is shipped as part of the
    18           Oracle VM VirtualBox extension pack, which must be installed
    19           separately. See <xref href="intro-installing.dita">Installing Oracle VM VirtualBox and Extension Packs</xref>.
     18        <ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/>, which must be installed
     19          separately. See <xref href="intro-installing.dita">Installing <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and Extension Packs</xref>.
    2020        </p>
    2121    </note>
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