VirtualBox

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.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • 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>
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