VirtualBox

Changeset 105293 in vbox for trunk/doc/manual


Ignore:
Timestamp:
Jul 12, 2024 10:45:38 AM (7 months ago)
Author:
vboxsync
Message:

FE/Qt: bugref:10705. Some more merges from docs team repo. white space changes.

Location:
trunk/doc/manual/en_US/dita/topics
Files:
12 edited

Legend:

Unmodified
Added
Removed

  • trunk/doc/manual/en_US/dita/topics/Introduction.dita

    r105289 r105293  
    55 
    66  <body>
    7     <p>
    8     Welcome to <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
    9   </p>
    10     <p>
    11     <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is a cross-platform virtualization application. What
    12     does that mean? For one thing, it installs on your existing Intel or
    13     AMD-based computers, whether they are running Windows, macOS, Linux,
    14     or Oracle Solaris operating systems (OSes). Secondly, it extends the
    15     capabilities of your existing computer so that it can run multiple
    16     OSes, inside multiple virtual machines, at the same time. As an
    17     example, you can run Windows and Linux on your Mac, run Windows
    18     Server on your Linux server, run Linux on your Windows PC, and so
    19     on, all alongside your existing applications. You can install and
    20     run as many virtual machines as you like. The only practical limits
    21     are disk space and memory.
    22   </p>
    23     <p>
    24     <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is deceptively simple yet also very powerful. It can
    25     run everywhere from small embedded systems or desktop class machines
    26     all the way up to datacenter deployments and even Cloud
    27     environments.
    28   </p>
    29     <p>
    30     The following screenshot shows how <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, installed on an
    31     Apple Mac computer, is running Windows Server 2016 in a virtual
    32     machine window.
    33   </p>
     7    <p>Welcome to <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.</p>
     8    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> is a cross-platform virtualization
     9      application. What does that mean? For one thing, it installs on your existing Intel or
     10      AMD-based computers, whether they are running Windows, macOS, Linux, or Oracle Solaris
     11      operating systems (OSes). Second, it extends the capabilities of your existing computer so
     12      that it can run multiple OSes, inside multiple virtual machines, at the same time. As an
     13      example, you can run Windows and Linux on your Mac, run Windows Server on your Linux server,
     14      run Linux on your Windows PC, and so on, all alongside your existing applications. You can
     15      install and run as many virtual machines as you like. The only practical limits are disk space
     16      and memory.</p>
     17    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> is deceptively simple yet also very powerful. It can run
     18      everywhere from small embedded systems or desktop class machines all the way up to data center deployments and
     19      even Cloud environments. </p>
     20    <p>The following screenshot shows how <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, installed on an Apple
     21      Mac computer, is running Windows Server 2016 in a virtual machine window. </p>
    3422    <fig id="fig-win2016-intro">
    3523      <title>Windows Server 2016 Virtual Machine, Displayed on a macOS Host</title>

  • trunk/doc/manual/en_US/dita/topics/cloud-vm-monitor.dita

    r105166 r105293  
    2020    </li>
    2121      <li>
    22         <p> Use the <cmdname>VBoxManage cloud instance</cmdname> command, as follows:</p>
     22        <p>Use the <cmdname>VBoxManage cloud instance</cmdname> command, as follows:</p>
    2323        <ul><li><p><cmdname>VBoxManage cloud instance metriclist</cmdname> shows the available metrics for an
    2424              instance.</p></li>

  • trunk/doc/manual/en_US/dita/topics/cloud-vm.dita

    r105289 r105293  
    3232      </li>
    3333      <li>
    34         <p><b outputclass="bold"> Use an existing <ph conkeyref="vbox-conkeyref-phrases/oci"/>
     34        <p><b outputclass="bold">Use an existing <ph conkeyref="vbox-conkeyref-phrases/oci"/>
    3535            instance.</b> See <xref href="cloud-vm-add.dita#cloud-vm-add"/>.
    3636          </p>

  • trunk/doc/manual/en_US/dita/topics/install-ext-pack-manager.dita

    r99797 r105293  
    33<topic xml:lang="en-us" id="install-ext-pack-manager">
    44  <title>The Extension Pack Manager</title>
    5 
     5 
    66  <body>
    7     <p>
    8         Extension packs can be installed and managed using the
    9         <b outputclass="bold">Extension Pack Manager</b> tool in
    10         <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.
    11       </p>
    12     <p>
    13         The Extension Pack Manager lists the extension packs that are
    14         currently installed on the host, and enables you to install and
    15         uninstall extension packs.
    16       </p>
    17     <p>
    18         To display the Extension Pack Manager, go to the global
    19         <b outputclass="bold">Tools</b> menu and click
    20         <b outputclass="bold">Extensions</b>. The Extension Pack
    21         Manager is shown.
    22       </p>
    23     <p>
    24         To install an extension pack using the Extension Pack Manager,
    25         click <b outputclass="bold">Install</b> and select an
    26         extension package file. The extension pack is installed on the
    27         host and listed in Extension Pack Manager.
    28       </p>
    29     <p>
    30         To uninstall an extension pack with the Extension Pack Manager,
    31         do the following:
    32       </p>
     7    <p>Extension packs can be installed and managed using the <b outputclass="bold">Extension Pack Manager</b> tool in
     8        <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. </p>
     9    <p>The Extension Pack Manager lists the extension packs that are currently installed on the host, and enables you to
     10      install and uninstall extension packs. </p>
     11    <p>To display the Extension Pack Manager, go to the global <b outputclass="bold">Tools</b> menu and click <b
     12        outputclass="bold">Extensions</b>. The Extension Pack Manager is shown. </p>
     13    <p>To install an extension pack using the Extension Pack Manager, click <b outputclass="bold">Install</b> and select
     14      an extension package file. The extension pack is installed on the host and listed in Extension Pack Manager. </p>
     15    <p>To uninstall an extension pack with the Extension Pack Manager, do the following: </p>
    3316    <ol>
    3417      <li>
    35         <p>
    36             Select the extension pack in the Extension Pack Manager
    37             window and click <b outputclass="bold">Uninstall</b>.
    38           </p>
     18        <p>Select the extension pack in the Extension Pack Manager window and click <b outputclass="bold">Uninstall</b>. </p>
    3919      </li>
    4020      <li>
    41         <p>
    42             Click <b outputclass="bold">Remove</b> in the prompt
    43             dialog.
    44           </p>
    45         <p>
    46             The extension pack is uninstalled from the host and removed
    47             from the Extension Pack Manager.
    48           </p>
     21        <p>Click <b outputclass="bold">Remove</b> in the prompt dialog. </p>
     22        <p>The extension pack is uninstalled from the host and removed from the Extension Pack Manager. </p>
    4923      </li>
    5024    </ol>
    51     <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>
     25    <p>Alternatively, you can use the <userinput>VBoxManage</userinput> command line to install and manage an <ph
     26        conkeyref="vbox-conkeyref-phrases/vbox-ext"/>. See <xref href="vboxmanage-extpack.dita"/>. </p>
    5527  </body>
    56 
     28 
    5729</topic>

  • trunk/doc/manual/en_US/dita/topics/install-ext-pack.dita

    r105289 r105293  
    1111    <ol>
    1212      <li>
    13         <p> Double-click the extension package file name. </p>
     13        <p>Double-click the extension package file name. </p>
    1414        <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> extension packs have a
    1515            <filepath>.vbox-extpack</filepath> file name extension. </p>

  • trunk/doc/manual/en_US/dita/topics/legacy-fullscreen-mode.dita

    r99797 r105293  
    66  <body>
    77    <p>
    8         <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses special window manager facilities to switch
    9         a multi-screen machine to full-screen on a multi-monitor host
    10         system. However, not all window managers provide these
    11         facilities correctly. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can be configured to use a
    12         legacy method of switching to full-screen mode instead, by using
    13         the command:
    14       </p>
     8      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses special window manager facilities
     9      to switch a multiscreen machine to full-screen on a multimonitor host system. However, not all
     10      window managers provide these facilities correctly. <ph
     11        conkeyref="vbox-conkeyref-phrases/product-name"/> can be configured to use a legacy method
     12      of switching to full-screen mode instead, by using the command: </p>
    1513    <pre xml:space="preserve">VBoxManage setextradata global GUI/Fullscreen/LegacyMode true</pre>
    1614    <p>

  • trunk/doc/manual/en_US/dita/topics/natforward.dita

    r99797 r105293  
    33<topic xml:lang="en-us" id="natforward">
    44  <title>Configuring Port Forwarding with NAT</title>
    5 
     5 
    66  <body>
    77    <p>
    … …  
    3535        traffic to be routed to a specific port in the guest.
    3636      </p>
    37     <p>
    38         Alternatively, the command line tool <userinput>VBoxManage</userinput> can be used. See
    39         <xref href="vboxmanage-modifyvm.dita"/>.
    40     </p>
     37    <p> Alternatively, the command line tool <userinput>VBoxManage</userinput> can be used. See
     38        <xref href="vboxmanage-modifyvm.dita"/>. </p>
    4139    <p>
    4240        You will need to know which ports on the guest the service uses
    … …  
    8785        guest.
    8886      </p>
    89     <p>
    90         It is possible to configure incoming NAT connections while the VM is running, see <xref
    91         href="vboxmanage-controlvm.dita"/>.
    92     </p>
     87    <p> It is possible to configure incoming NAT connections while the VM is running, see <xref
     88        href="vboxmanage-controlvm.dita"/>. </p>
    9389  </body>
    94 
     90 
    9591</topic>

  • trunk/doc/manual/en_US/dita/topics/network_hostonly.dita

    r105176 r105293  
    7373      </li>
    7474      <li>
    75         <p>
    76           On the command line, use <userinput>VBoxManage modifyvm vmname --nic
    77           <varname>x</varname> hostonly</userinput>. See <xref href="vboxmanage-modifyvm.dita"/>.
    78         </p>
     75        <p> On the command line, use <userinput>VBoxManage modifyvm vmname --nic
     76              <varname>x</varname> hostonly</userinput>. See <xref href="vboxmanage-modifyvm.dita"
     77          />. </p>
    7978      </li>
    8079    </ul>

  • trunk/doc/manual/en_US/dita/topics/network_internal.dita

    r105289 r105293  
    4040      </li>
    4141    </ul>
    42     <p>
    43       Unless you configure the virtual network cards in the guest operating systems that are
     42    <p>Unless you configure the virtual network cards in the guest operating systems that are
    4443      participating in the internal network to use static IP addresses, you may want to use the DHCP
    4544      server that is built into <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to manage IP addresses for the internal
    46       network. See <xref href="vboxmanage-dhcpserver.dita"/>.
    47     </p>
    48     <p>
    49       As a security measure, by default, the Linux implementation of
     45      network. See <xref href="vboxmanage-dhcpserver.dita"/>. </p>
     46    <p>As a security measure, by default, the Linux implementation of
    5047      internal networking only allows VMs running under the same user ID
    5148      to establish an internal network. However, it is possible to
    … …  
    5451    </p>
    5552  </body>
    56 
     53 
    5754</topic>

  • trunk/doc/manual/en_US/dita/topics/networkingdetails.dita

    r99797 r105293  
    33<topic xml:lang="en-us" id="networkingdetails">
    44  <title>Virtual Networking</title>
    5 
     5 
    66  <body>
    77    <p>
    … …  
    2424      </li>
    2525    </ul>
    26     <p>
    27       Four of the network cards can be configured in the <b outputclass="bold">Network</b> section
     26    <p> Four of the network cards can be configured in the <b outputclass="bold">Network</b> section
    2827      of the <b outputclass="bold">Settings</b> window in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. You can configure all
    2928      eight network cards on the command line using <userinput>VBoxManage modifyvm</userinput>. See
    30       <xref href="vboxmanage-modifyvm.dita"/>.
    31     </p>
     29        <xref href="vboxmanage-modifyvm.dita"/>. </p>
    3230    <p>
    3331    This chapter explains the various networking settings in more

  • trunk/doc/manual/en_US/dita/topics/snapshots-take-restore-delete.dita

    r105289 r105293  
    66               
    77               <body>
    8                   <p>
    9         There are three operations related to snapshots, as follows:
    10       </p>
     8                  <p>There are three operations related to snapshots, as follows: </p>
    119                  <ol>
    1210                     <li>
    13                         <p>
    14                            <b outputclass="bold">Take a snapshot.</b> This makes
    15             a copy of the machine's current state, to which you can go
    16             back at any given time later.
    17           </p>
     11                        <p><b outputclass="bold">Take a snapshot.</b> This makes a copy of the machine's current state,
     12          to which you can go back at any given time later. </p>
    1813                        <ul>
    1914                           <li>
    20                               <p>
    21                 If your VM is running:
    22               </p>
    23                               <p>
    24                 Select <b outputclass="bold">Take Snapshot</b>
    25                 from the <b outputclass="bold">Machine</b> menu
    26                 in the VM window.
    27               </p>
    28                               <p>
    29                 The VM is paused while the snapshot is being created.
    30                 After snapshot creation, the VM continues to run as
    31                 normal.
    32               </p>
     15                              <p>If your VM is running: </p>
     16                              <p>Select <b outputclass="bold">Take Snapshot</b> from the <b outputclass="bold"
     17                >Machine</b> menu in the VM window. </p>
     18                              <p>The VM is paused while the snapshot is being created. After snapshot creation, the VM
     19              continues to run as normal. </p>
    3320                           </li>
    3421                           <li>
    35                               <p>
    36                 If your VM is in either the Saved or the Powered Off
    37                 state, as displayed next to the VM name in the machine
    38                 list:
    39               </p>
    40                               <p>
    41                 Display the Snapshots window and do one of the
    42                 following:
    43               </p>
     22                              <p>If your VM is in either the Saved or the Powered Off state, as displayed next to the VM
     23              name in the machine list: </p>
     24                              <p>Display the Snapshots window and do one of the following: </p>
    4425                              <ul>
    4526                                 <li>
    46                                     <p>
    47                     Click <b outputclass="bold">Take</b> in the
    48                     Snapshots window toolbar.
    49                   </p>
     27                                    <p>Click <b outputclass="bold">Take</b> in the Snapshots window toolbar. </p>
    5028                                 </li>
    5129                                 <li>
    52                                     <p> Right-click the <b outputclass="bold">Current State</b> item
    53                   in the list and select <b outputclass="bold">Take</b>. </p>
     30                                    <p>Right-click the <b outputclass="bold">Current State</b> item in the list and
     31                  select <b outputclass="bold">Take</b>. </p>
    5432                                 </li>
    5533                              </ul>
    5634                           </li>
    5735                        </ul>
    58                         <p>
    59             A dialog is displayed, prompting you for a snapshot name.
    60             This name is purely for reference purposes, to help you
    61             remember the state of the snapshot. For example, a useful
    62             name would be "Fresh installation from scratch, no Guest
    63             Additions", or "Service Pack 3 just installed". You can also
    64             add a longer text description in the
    65             <b outputclass="bold">Snapshot Description</b> field.
    66           </p>
    67                         <p>
    68             Your new snapshot will then appear in the snapshots list.
    69             Underneath your new snapshot, you will see an item called
    70             <b outputclass="bold">Current State</b>, signifying
    71             that the current state of your VM is a variation based on
    72             the snapshot you took earlier. If you later take another
    73             snapshot, you will see that they are displayed in sequence,
    74             and that each subsequent snapshot is derived from an earlier
    75             one.
    76           </p>
     36                        <p>A dialog is displayed, prompting you for a snapshot name. This name is purely for reference
     37          purposes, to help you remember the state of the snapshot. For example, a useful name would be <i>Fresh
     38            installation from scratch, no Guest Additions</i>, or <i>Service Pack 3 just installed</i>. You can also add
     39          a longer text description in the <b outputclass="bold">Snapshot Description</b> field. </p>
     40                        <p>Your new snapshot will then appear in the snapshots list. Underneath your new snapshot, you
     41          will see an item called <b outputclass="bold">Current State</b>, signifying that the current state of your VM
     42          is a variation based on the snapshot you took earlier. If you later take another snapshot, you will see that
     43          they are displayed in sequence, and that each subsequent snapshot is derived from an earlier one. </p>
    7744                       <fig id="fig-snapshots-list">
    7845                         <title>Snapshots List For a Virtual Machine</title>

  • trunk/doc/manual/en_US/dita/topics/snapshots.dita

    r105289 r105293  
    1010      virtual machine is thus similar to a machine in Saved state, but there can be many of them, and these saved states
    1111      are preserved. </p>
    12                <p> To see the snapshots of a virtual machine, click the machine name in <ph
     12               <p>To see the snapshots of a virtual machine, click the machine name in <ph
    1313        conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. In the machine tools menu for the VM, click <b outputclass="bold"
    1414        >Snapshots</b>. The Snapshots tool is displayed. </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