Changeset 97032 in vbox for trunk/doc/manual

Timestamp:

Oct 6, 2022 3:11:29 PM (2 years ago)

Author:

vboxsync

Message:

doc/manual: Integrate documentation update.

Location:

trunk/doc/manual/en_US

Files:

• UserManual.xml (modified) (1 diff)
• images/clone-vm-1.png (added)
• images/clone-vm-2.png (added)
• images/clone-vm-3.png (added)
• images/clone-vm.png (deleted)
• images/cloud-profile-manager.png (modified) ( previous)
• images/cloudvm-add.png (added)
• images/cloudvm-new.png (added)
• images/cloudvm-oci-group.png (added)
• images/cloudvm-overview.png (added)
• images/create-vdi-1.png (deleted)
• images/create-vm-1.png (modified) ( previous)
• images/create-vm-2.png (modified) ( previous)
• images/create-vm-3.png (added)
• images/create-vm-4.png (added)
• images/details-pane.png (added)
• images/dnd-modes.png (modified) ( previous)
• images/export-appliance-oci.png (modified) ( previous)
• images/global-tools-menu.png (added)
• images/guest-fm.png (modified) ( previous)
• images/import-instance.png (modified) ( previous)
• images/log-viewer.png (added)
• images/machine-tools-menu.png (added)
• images/newcloudvm.png (deleted)
• images/ovf-import.png (modified) ( previous)
• images/resourcemonitor.png (deleted)
• images/session-information.png (added)
• images/snapshots-1.png (modified) ( previous)
• images/snapshots-2.png (added)
• images/softkeybd.png (modified) ( previous)
• images/vbox-sdl.png (deleted)
• images/virtual-disk-manager-2.png (moved) (moved from trunk/doc/manual/en_US/images/virtual-disk-manager2.png )
• images/virtual-disk-manager.png (modified) ( previous)
• images/virtual-hard-disk-wizard.png (added)
• images/virtualbox-main-empty.png (modified) ( previous)
• images/virtualbox-main.png (modified) ( previous)
• images/vm-activity-overview.png (added)
• images/vm-close.png (modified) ( previous)
• images/vm-groups.png (modified) ( previous)
• images/vm-hostkey.png (modified) ( previous)
• images/vm-settings-harddisk.png (modified) ( previous)
• images/vmperformancemonitor.png (deleted)
• user_AdvancedTopics.xml (modified) (33 diffs)
• user_BasicConcepts.xml (modified) (30 diffs)
• user_Frontends.xml (modified) (7 diffs)
• user_GuestAdditions.xml (modified) (26 diffs)
• user_Installation.xml (modified) (5 diffs)
• user_Introduction.xml (modified) (107 diffs)
• user_KnownIssues.xml (modified) (4 diffs)
• user_Networking.xml (modified) (15 diffs)
• user_Storage.xml (modified) (15 diffs)
• user_Technical.xml (modified) (8 diffs)
• user_Troubleshooting.xml (modified) (3 diffs)

trunk/doc/manual/en_US/UserManual.xml

@@ -21 +21 @@
     SPDX-License-Identifier: GPL-3.0-only
 -->
+
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
   "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"[

trunk/doc/manual/en_US/user_AdvancedTopics.xml

@@ -42 +42 @@
       When a guest operating system is running in a virtual machine, it
       might be desirable to perform coordinated and automated logins
-      using credentials passed from the host. Credentials are user
-      name, password, and domain name, where each value might be empty.
+      using credentials passed from the host. Credentials are user name,
+      password, and domain name, where each value might be empty.
     </para>
 
@@ -852 +852 @@
       When the VM is off, you can then add and remove virtual CPUs with
       the <command>VBoxManage modifyvm --plug-cpu</command> and
-      <command>VBoxManage modifyvm --unplug-cpu</command> commands, which
-      take the number of the virtual CPU as a parameter, as follows:
+      <command>VBoxManage modifyvm --unplug-cpu</command> commands,
+      which take the number of the virtual CPU as a parameter, as
+      follows:
     </para>
 
@@ -1229 +1230 @@
     <sect2 id="webcam-mac-hosts">
 
-      <title>Mac OS X Hosts</title>
-
-      <para>
-        Mac OS X version 10.9 or later is required.
-      </para>
+      <title>macOS Hosts</title>
 
       <para>
@@ -1413 +1410 @@
         image file which defines where the data will be stored. After
         creating such a special VMDK image, you can use it like a
-        regular virtual disk image. For example, you can use the
-        VirtualBox Manager, see <xref linkend="vdis" />, or
+        regular virtual disk image. For example, you can use the Virtual
+        Media Manager, see <xref linkend="virtual-media-manager" />, or
         <command>VBoxManage</command> to assign the image to a virtual
         machine.
@@ -1455 +1452 @@
           On a Windows host, instead of the above device specification,
           for example use <filename>\\.\PhysicalDrive0</filename>. On a
-          Mac OS X host, instead of the above device specification use
-          for example <filename>/dev/rdisk1</filename>. Note that on Mac
-          OS X you can only get access to an entire disk if no volume is
+          macOS host, instead of the above device specification use for
+          example <filename>/dev/rdisk1</filename>. Note that on Mac OS
+          X you can only get access to an entire disk if no volume is
           mounted from it.
         </para>
@@ -1514 +1511 @@
         <para>
           The command is identical to the one for full hard disk access,
-          except for the additional
-          <option>--property Partitions=1,5</option>
-          parameter. This example would create the image
+          except for the additional <option>--property
+          Partitions=1,5</option> parameter. This example would create
+          the image
           <filename><replaceable>path-to-file</replaceable>.vmdk</filename>,
           which must be absolute, and partitions 1 and 5 of
@@ -1533 +1530 @@
           On a Windows host, instead of the above device specification,
           use for example <filename>\\.\PhysicalDrive0</filename>. On a
-          Mac OS X host, instead of the above device specification use
+          macOS host, instead of the above device specification use
           <filename>/dev/rdisk1</filename>, for example. Note that on OS
           X you can only use partitions which are not mounted. Unmount
-          the respective disk first using
-          <emphasis>diskutil unmountDisk <filename>/dev/diskX</filename></emphasis>.
-          Partition numbers are the same on Linux, Windows, and Mac OS X hosts.
+          the respective disk first using <emphasis>diskutil unmountDisk
+          <filename>/dev/diskX</filename></emphasis>. Partition numbers
+          are the same on Linux, Windows, and macOS hosts.
         </para>
 
@@ -1550 +1547 @@
         <para>
           The output lists available drives and their partitions with
-          the partition types and sizes to give the user enough information
-          to identify the partitions necessary for the guest.
+          the partition types and sizes to give the user enough
+          information to identify the partitions necessary for the
+          guest.
         </para>
 
@@ -2727 +2725 @@
   <sect1 id="guitweaks">
 
-    <title>Locking Down the &product-name; GUI</title>
+    <title>Locking Down &vbox-mgr;</title>
 
     <sect2 id="customize-vm-manager">
 
-      <title>Customizing the VirtualBox Manager</title>
+      <title>Customizing &vbox-mgr;</title>
 
       <para>
         There are several advanced customization settings for locking
-        down the VirtualBox Manager. Locking down means removing some
-        features that the user should not see.
+        down &vbox-mgr;. Locking down means removing some features that
+        the user should not see.
       </para>
 
@@ -2755 +2753 @@
           <listitem>
             <para>
-              Do not allow users to start the VirtualBox Manager. Trying
-              to do so will show a window containing a proper error
-              message.
+              Do not allow users to start &vbox-mgr;. Trying to do so
+              will show a window containing a proper error message.
             </para>
           </listitem>
@@ -2789 +2786 @@
 
       <para>
-        To disable any of these VirtualBox Manager customizations use
-        the following command:
+        To disable any of these &vbox-mgr; customizations use the
+        following command:
       </para>
 
@@ -3161 +3158 @@
         the following command to disable certain actions of the
         <emphasis role="bold">Application</emphasis> menu. This is only
-        available on Mac OS X hosts.
+        available on macOS hosts.
       </para>
 
@@ -4167 +4164 @@
               Do not show the <emphasis role="bold">About
               VirtualBox...</emphasis> menu item in this menu. Only for
-              non-Mac OS X hosts.
+              non-macOS hosts.
             </para>
           </listitem>
@@ -5435 +5432 @@
     <sect2 id="vboxwebsrv-osx">
 
-      <title>Mac OS X: Starting the Web Service With launchd</title>
-
-      <para>
-        On Mac OS X, launchd is used to start the &product-name;
+      <title>macOS: Starting the Web Service With launchd</title>
+
+      <para>
+        On macOS, launchd is used to start the &product-name;
         webservice. An example configuration file can be found in
         <filename>$HOME/Library/LaunchAgents/org.virtualbox.vboxwebsrv.plist</filename>.
@@ -5980 +5977 @@
     <para>
       You can start VMs automatically during system boot on Linux,
-      Oracle Solaris, and Mac OS X platforms for all users.
+      Oracle Solaris, and macOS platforms for all users.
     </para>
 
@@ -6069 +6066 @@
     <sect2 id="autostart-osx">
 
-      <title>Mac OS X: Starting the Autostart Service With launchd</title>
-
-      <para>
-        On Mac OS X, launchd is used to start the &product-name;
-        autostart service. An example configuration file can be found in
+      <title>macOS: Starting the Autostart Service With launchd</title>
+
+      <para>
+        On macOS, launchd is used to start the &product-name; autostart
+        service. An example configuration file can be found in
         <filename>/Applications/VirtualBox.app/Contents/MacOS/org.virtualbox.vboxautostart.plist</filename>.
         To enable the service copy the file to
@@ -6113 +6110 @@
         all required users but it should have permissions allowing only
         reading by everyone but administrators. The configuration file
-        contains several options. The
-        <literal>default_policy</literal> controls whether the autostart
-        service allows or denies starting of a VM for users that are not
-        in the exception list. The exception list starts with
-        <literal>exception_list</literal> and contains a comma separated
-        list with usernames. Furthermore, a separate startup delay can
-        be configured for every user to avoid overloading the host. A
-        sample configuration is given below:
+        contains several options. The <literal>default_policy</literal>
+        controls whether the autostart service allows or denies starting
+        of a VM for users that are not in the exception list. The
+        exception list starts with <literal>exception_list</literal> and
+        contains a comma separated list with usernames. Furthermore, a
+        separate startup delay can be configured for every user to avoid
+        overloading the host. A sample configuration is given below:
       </para>
 
@@ -6202 +6198 @@
       <note>
         <para>
-          On Windows hosts, starting VMs via the autostart service might cause some
-          issues, as the virtual machines are starting within the same session as
-          VBoxSVC. For more information see <xref linkend="vboxsvc-session-0" />.
+          On Windows hosts, starting VMs via the autostart service might
+          cause some issues, as the virtual machines are starting within
+          the same session as VBoxSVC. For more information see
+          <xref linkend="vboxsvc-session-0" />.
         </para>
       </note>
@@ -6218 +6215 @@
     <para>
       &product-name; enables you to transparently encrypt the VM data
-      stored in the configuration file, saved state and EFI boot data
+      stored in the configuration file, saved state, and EFI boot data
       for the guest.
     </para>
 
     <para>
-      &product-name; uses the AES algorithm in various modes. The selected
-      mode depends on encrypting component of the VM. &product-name;
-      supports 128-bit or 256-bit data encryption keys (DEK). The DEK
-      is stored encrypted in the VM configuration file and is decrypted
-      during VM opening.
+      &product-name; uses the AES algorithm in various modes. The
+      selected mode depends on the encrypting component of the VM.
+      &product-name; supports 128-bit or 256-bit data encryption keys
+      (DEK). The DEK is stored encrypted in the VM configuration file
+      and is decrypted during VM startup.
     </para>
 
     <para>
       Since the DEK is stored as part of the VM configuration file, it
-      is important that it is kept safe. Losing the DEK means that the
-      data stored in the VM is lost irrecoverably. Having complete and
-      up to date backups of all data related to the VM is the
+      is important that the file is kept safe. Losing the DEK means that
+      the data stored in the VM is lost irrecoverably. Having complete
+      and up to date backups of all data related to the VM is the
       responsibility of the user.
     </para>
 
     <para>
-      The VM, even if it is encrypted, may contain mediums encrypted with
-      different passwords. To deal with this, the password for the VM itself
-      also has password identifier such as passwords for mediums. The password
-      ID is an arbitrary string which uniquely identifies the password in the
-      VM and its mediums. It is allowed to use the same password for VM and
-      its mediums with the same ID.
+      The VM, even if it is encrypted, may contain media encrypted with
+      different passwords. To deal with this, the password for the VM
+      has a password identifier, in the same way as passwords for media.
+      The password ID is an arbitrary string which uniquely identifies
+      the password in the VM and its media. You can use the same
+      password and ID for both the VM and its media.
     </para>
 
@@ -6260 +6257 @@
         <listitem>
           <para>
-            Exporting appliances containing encrypted VM is not
-            possible because the OVF specification does not support
+            Exporting appliances containing an encrypted VM is not
+            possible, because the OVF specification does not support
             this. The VM is therefore decrypted during export.
           </para>
@@ -6281 +6278 @@
             in clear text using the &product-name; API. This needs to be
             kept in mind, especially when using third party API clients
-            which make use of the webservice where the password might be
-            transmitted over the network. The use of HTTPS is mandatory
-            in such a case.
+            which make use of the web service where the password might
+            be transmitted over the network. The use of HTTPS is
+            mandatory in such a case.
           </para>
         </listitem>
@@ -6293 +6290 @@
     <sect2 id="vmencryption-encryption">
 
-      <title>Encrypting VMs</title>
-
-      <para>
-        Encrypting VMs can be done either using the GUI or
-        <command>VBoxManage</command>. To encrypt an unencrypted
-        VM with <command>VBoxManage</command>, use:
+      <title>Encrypting a VM</title>
+
+      <para>
+        Encrypting a VM can be done either using &vbox-mgr; or the
+        <command>VBoxManage</command>. To encrypt an unencrypted VM with
+        <command>VBoxManage</command>, use:
       </para>
 
 <screen>VBoxManage encryptvm <replaceable>uuid</replaceable>|<replaceable>vmname</replaceable> setencryption --new-password <replaceable>filename</replaceable>|- \
---cipher <replaceable>cipher-ID</replaceable> --new-password-id "<replaceable>ID</replaceable></screen>
+--cipher <replaceable>cipher-ID</replaceable> --new-password-id <replaceable>ID</replaceable></screen>
+
+      <para>
+        To supply the encryption password, point
+        <command>VBoxManage</command> to the file where the password is
+        stored or specify <option>-</option> to let
+        <command>VBoxManage</command> prompt for the password on the
+        command line.
+      </para>
+
+      <para>
+        The cipher parameter specifies the cipher to use for encryption
+        and can be either <literal>AES-128</literal> or
+        <literal>AES-256</literal>. The appropriate mode of operation,
+        such as GCM, CTR, or XTS will be selected by the VM depending on
+        the encrypting component. The specified password identifier can
+        be freely chosen by the user and is used for correct
+        identification when supplying multiple passwords for the VM.
+      </para>
+
+    </sect2>
+
+    <sect2 id="vmencryption-addpassword">
+
+      <title>Opening the Encrypted VM</title>
+
+      <para>
+        When &product-name; has just started up the encrypted VM cannot
+        be opened and it stays inaccessible. Also, the encrypted VM
+        stays inaccessible if it was just registered without a password
+        or the password is incorrect. The user needs to provide the
+        password using &vbox-mgr; or with the following
+        <command>VBoxManage</command> command:
+      </para>
+
+<screen>VBoxManage encryptvm <replaceable>uuid</replaceable>|<replaceable>vmname</replaceable> addpassword --password <replaceable>filename</replaceable>|- --password-id <replaceable>ID</replaceable></screen>
 
       <para>
         To supply the encryption password point
         <command>VBoxManage</command> to the file where the password is
-        stored or specify <option>-</option> to let VBoxManage ask you
-        for the password on the command line.
-      </para>
-
-      <para>
-        The cipher parameter specifies the cipher to use for encryption
-        and can be either <literal>AES-128</literal> or
-        <literal>AES-256</literal>. Appropriate mode GCM, CTR or XTS will
-        be selected by VM depending on encrypting component.
-        The specified password identifier can be freely chosen by the user
-        and is used for correct identification when supplying multiple
-        passwords for the VM.
-      </para>
-
-    </sect2>
-
-    <sect2 id="vmencryption-addpassword">
-
-      <title>Opening the encrypted VM</title>
-
-      <para>
-        At the time the &product-name; has just started up the encrypted
-        VM can not be opened and it stays inaccessible. Also the encrypted
-        VM stays inaccessible if it just registered without password or
-        password is incorrect. The user needs to provide the password
-        through either GUI or <command>VBoxManage</command> using the
-        following command:
-      </para>
-
-<screen>VBoxManage encryptvm <replaceable>uuid</replaceable>|<replaceable>vmname</replaceable> addpassword --password <replaceable>filename</replaceable>|- --password-id <replaceable>ID</replaceable></screen>
-
-      <para>
-        To supply the encryption password point
-        <command>VBoxManage</command> to the file where the password is
-        stored or specify <option>-</option> to let VBoxManage ask you
-        for the password on the command line.
+        stored or specify <option>-</option> to let
+        <command>VBoxManage</command> prompt for the password on the
+        command line.
       </para>
 
@@ -6352 +6351 @@
 
       <para>
-        If user needs to remove the entered password from the VM memory
-        it can call <command>VBoxManage</command> using the following
-        command:
+        To remove the entered password from the VM memory, use
+        <command>VBoxManage</command> as follows:
       </para>
 
@@ -6367 +6365 @@
       <note>
         <para>
-          If machine becomes inaccessible all passwords are purged.
-          One has to add required passwords again using
+          If a machine becomes inaccessible all passwords are purged.
+          You have to add required passwords again, using the
           <command>VBoxManage encryptvm
           <replaceable>vmname</replaceable> addpassword</command>
-          command, see <xref linkend="vmencryption-addpassword" />.
+          command. See <xref linkend="vmencryption-addpassword" />.
         </para>
       </note>
@@ -6383 +6381 @@
       <para>
         In some circumstances it might be required to decrypt previously
-        encrypted VMs. This can be done in the GUI or using
+        encrypted VMs. This can be done in &vbox-mgr; or using
         <command>VBoxManage</command> with the following command:
       </para>
@@ -6390 +6388 @@
 
       <para>
-        The only required parameter is the password the VM was
-        encrypted with. The options are the same as for encrypting
-        VMs.
+        The only required parameter is the password the VM was encrypted
+        with. The options are the same as for encrypting VMs.
       </para>
 
@@ -6535 +6532 @@
       This feature makes the host keyboard indicators (LEDs) match those
       of the VM's emulated keyboard when the machine window is active.
-      It is currently implemented for Mac OS X and Windows hosts. This
+      It is currently implemented for macOS and Windows hosts. This
       feature is enabled by default on supported host OSes. You can
       disable this feature by running the following command:
@@ -6742 +6739 @@
 
       <para>
-        Encrypting disk images can be done either using the GUI or
-        <command>VBoxManage</command>. While the GUI is easier to use,
-        it works on a per VM basis and encrypts all disk images attached
-        to the specific VM. With <command>VBoxManage</command> one can
-        encrypt individual images, including all differencing images. To
-        encrypt an unencrypted medium with
+        Encrypting disk images can be done either using &vbox-mgr; or
+        the <command>VBoxManage</command>. While &vbox-mgr; is easier to
+        use, it works on a per VM basis and encrypts all disk images
+        attached to the specific VM. With <command>VBoxManage</command>
+        one can encrypt individual images, including all differencing
+        images. To encrypt an unencrypted medium with
         <command>VBoxManage</command>, use:
       </para>
@@ -6783 +6780 @@
 
       <para>
-        When a VM is started using the GUI, a dialog will open where the
-        user needs to enter all passwords for all encrypted images
+        When a VM is started using &vbox-mgr;, a dialog will open where
+        the user needs to enter all passwords for all encrypted images
         attached to the VM. If another frontend like VBoxHeadless is
         used, the VM will be paused as soon as the guest tries to access
@@ -6815 +6812 @@
       <para>
         In some circumstances it might be required to decrypt previously
-        encrypted images. This can be done in the GUI for a complete VM
-        or using <command>VBoxManage</command> with the following
+        encrypted images. This can be done in &vbox-mgr; for a complete
+        VM or using <command>VBoxManage</command> with the following
         command:
       </para>
@@ -7450 +7447 @@
     <para>
       USB devices exported on the device server are then accessible
-      through the GUI or <command>VBoxManage</command>, like any USB
+      through &vbox-mgr; or <command>VBoxManage</command>, like any USB
       devices attached locally. This can be used multiple times to
       access different device servers.
@@ -7600 +7597 @@
       <listitem>
         <para>
-          From the VirtualBox Manager, select the
-          <emphasis role="bold">Enable Nested VT-x/AMD-V</emphasis>
-          check box on the <emphasis role="bold">Processor</emphasis>
-          tab. To disable the feature, deselect the check box.
+          From &vbox-mgr;, select the <emphasis role="bold">Enable
+          Nested VT-x/AMD-V</emphasis> check box on the
+          <emphasis role="bold">Processor</emphasis> tab. To disable the
+          feature, deselect the check box.
         </para>
       </listitem>
@@ -7622 +7619 @@
   <sect1 id="vboxsvc-session-0">
 
-    <title>VBoxSVC running in Windows session 0</title>
-
-    <para>
-      &product-name; supports executing the VBoxSVC in Windows session 0.
-      This allows VBoxSVC to run like a regular Windows service, which in turn
-      enables headless VMs to continue running even if the user logs out.
+    <title>VBoxSVC running in Windows Session 0</title>
+
+    <para>
+      &product-name; supports executing the VBoxSVC in Windows session
+      0. This allows VBoxSVC to run like a regular Windows service,
+      which in turn enables headless VMs to continue running even if the
+      user logs out.
+
       <note>
-        <para>This feature currently is marked as being <emphasis role="bold">experimental</emphasis>!</para>
+        <para>
+          This is currently an experimental feature.
+        </para>
       </note>
     </para>
 
     <para>
-      The feature is disabled by default and can be enabled by creating a REG_DWORD
-      value <literal>ServerSession0</literal> in the key
-      <literal>HKEY_LOCAL_MACHINE\Software\Oracle\VirtualBox\VBoxSDS</literal> of the
-      Windows registry. Specifying <literal>1</literal> as the value's data to
-      enable the feature, or <literal>0</literal> to disable the feature again.
-      A host reboot is needed in order to make the change effective.
+      The feature is disabled by default and can be enabled by creating
+      a REG_DWORD value <literal>ServerSession0</literal> in the key
+      <literal>HKEY_LOCAL_MACHINE\Software\Oracle\VirtualBox\VBoxSDS</literal>
+      of the Windows registry. Specify <literal>1</literal> as the
+      value's data to enable the feature, or <literal>0</literal> to
+      disable the feature. A host reboot is needed in order to make the
+      change effective.
     </para>
 
     <sect2 id="vboxsvc-session-0-known-issues">
 
-      <title>Known issues</title>
+      <title>Known Issues</title>
 
       <itemizedlist>
+
         <listitem>
           <para>
-            Due to different Windows sessions having their own set of resources,
-            there might be some issues with accessing network shares created in
-           the interactive user session when at least one of &product-name;
-            processes are running in session 0.
+            Due to different Windows sessions having their own set of
+            resources, there might be some issues with accessing network
+            shares created in the interactive user session when at least
+            one of the &product-name; processes are running in session
+            0.
           </para>
+
           <para>
-            For accessing network shares within session 0, a possible workaround
-            is to establish permanent access to the share and restart the host after that.
-            This might change in the future, however.
+            For accessing network shares within session 0, a possible
+            workaround is to establish permanent access to the share and
+            then restart the host.
           </para>
         </listitem>
+
       </itemizedlist>
+
     </sect2>
 

trunk/doc/manual/en_US/user_BasicConcepts.xml

@@ -122 +122 @@
           <row>
             <entry><para>
+                Windows 11 (64-bit)
+              </para></entry>
+            <entry><para>
+                Insider preview builds are not supported
+              </para></entry>
+          </row>
+          <row>
+            <entry><para>
                 Windows 10 (32-bit and 64-bit)
               </para></entry>
@@ -392 +400 @@
           for virtual machines that you intend to use in 64-bit mode.
           This is especially true for 64-bit Windows VMs. See
-          <xref linkend="settings-general-advanced" />. For 64-bit
-          Windows guests, ensure that the VM uses the
+          <xref linkend="settings-motherboard" />. For 64-bit Windows
+          guests, ensure that the VM uses the
           <emphasis role="bold">Intel networking device</emphasis>
           because there is no 64-bit driver support for the AMD PCNet
@@ -402 +410 @@
       <para>
         If you use the <emphasis role="bold">Create VM</emphasis> wizard
-        of the VirtualBox Manager, &product-name; automatically uses the
-        correct settings for each selected 64-bit OS type. See
-        <xref linkend="gui-createvm" />.
+        of &vbox-mgr;, &product-name; automatically uses the correct
+        settings for each selected 64-bit OS type. See
+        <xref linkend="create-vm-wizard" />.
       </para>
 
@@ -422 +430 @@
 
     <para>
-      Performing an unattended guest installation involves the following
-      steps:
+      You can perform an unattended guest installation in the following
+      ways:
     </para>
 
@@ -430 +438 @@
       <listitem>
         <para>
-          <emphasis role="bold">Create a new VM.</emphasis> Use one of
-          the following methods:
-        </para>
-
-        <itemizedlist>
-
-          <listitem>
-            <para>
-              The VirtualBox Manager, see
-              <xref linkend="gui-createvm" />.
-            </para>
-          </listitem>
-
-          <listitem>
-            <para>
-              The <command>VBoxManage createvm</command> command, see
-              <xref linkend="vboxmanage-createvm" />.
-            </para>
-          </listitem>
-
-        </itemizedlist>
-
-        <para>
-          For the new VM, choose the guest OS type and accept the
-          default settings for that OS. The following sections in this
-          chapter describe how to change the settings for a VM.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          <emphasis role="bold">Prepare the VM for unattended guest
-          installation.</emphasis> Use the <command>VBoxManage
-          unattended</command> command, see
-          <xref linkend="vboxmanage-unattended" />.
+          <emphasis role="bold">Use the Create Virtual Machine
+          wizard.</emphasis> An optional step in the wizard enables you
+          to configure unattended installation. You can specify the
+          default user credentials for the guest OS and also whether to
+          install the Guest Additions automatically. See
+          <xref linkend="create-vm-wizard"/>.
         </para>
 
@@ -476 +455 @@
       <listitem>
         <para>
-          <emphasis role="bold">Start the VM.</emphasis> Use the
-          VirtualBox Manager or the <command>VBoxManage
-          startvm</command> command.
-        </para>
-
-        <para>
-          When you start the VM, the unattended installation is
-          performed automatically.
-        </para>
-
-        <para>
-          The installation operation changes the boot device order to
-          boot the virtual hard disk first and then the virtual DVD
-          drive. If the virtual hard disk is empty prior to the
-          automatic installation, the VM boots from the virtual DVD
-          drive and begins the installation.
-        </para>
-
-        <para>
-          If the virtual hard disk contains a bootable OS, the
-          installation operation exits. In this case, change the boot
-          device order manually by pressing F12 during the BIOS splash
-          screen.
+          <emphasis role="bold">Use the <command>VBoxManage</command>
+          commands.</emphasis>
+          <xref linkend="unattended-guest-install-example"/> describes
+          how to perform an unattended guest installation for an Oracle
+          Linux guest.
         </para>
       </listitem>
@@ -505 +466 @@
 
     <para>
-      <xref linkend="unattended-guest-install-example"/> describes how
-      to perform an unattended guest installation for an Oracle Linux
-      guest.
+      When you first start a VM that has been configured for unattended
+      installation, the guest OS installation is performed
+      automatically.
+    </para>
+
+    <para>
+      The installation operation changes the boot device order to boot
+      the virtual hard disk first and then the virtual DVD drive. If the
+      virtual hard disk is empty prior to the automatic installation,
+      the VM boots from the virtual DVD drive and begins the
+      installation.
+    </para>
+
+    <para>
+      If the virtual hard disk contains a bootable OS, the installation
+      operation exits. In this case, change the boot device order
+      manually by pressing F12 during the BIOS splash screen.
     </para>
 
     <sect2 id="unattended-guest-install-example">
 
-      <title>An Example of Unattended Guest Installation</title>
+      <title>Using VBoxManage Commands for Unattended Guest Installation</title>
 
       <para>
@@ -718 +693 @@
           <para>
             The VM starts in headless mode, which means that the
-            VirtualBox Manager window does not open.
+            &vbox-mgr; window does not open.
           </para>
         </listitem>
@@ -885 +860 @@
             OS for the VM. This is the same setting that is specified in
             the <emphasis role="bold">New Virtual Machine</emphasis>
-            wizard. See <xref linkend="gui-createvm" />.
+            wizard. See <xref linkend="create-vm-wizard" />.
           </para>
 
@@ -902 +877 @@
             specified in the <emphasis role="bold">New Virtual
             Machine</emphasis> wizard. See
-            <xref linkend="gui-createvm" />.
+            <xref linkend="create-vm-wizard" />.
           </para>
         </listitem>
@@ -1037 +1012 @@
         <para>
           All files related to the virtual machine except disk images
-          are stored unencrypted.
+          are stored unencrypted. To encrypt these files, use the
+          <command>VBoxManage encryptvm</command> command as described
+          in <xref linkend="vmencryption"/>.
         </para>
       </note>
@@ -1090 +1067 @@
             running. This is the same setting that was specified in the
             <emphasis role="bold">New Virtual Machine</emphasis> wizard,
-            as described in <xref linkend="gui-createvm" />.
+            as described in <xref linkend="create-vm-wizard" />.
           </para>
 
@@ -1139 +1116 @@
         <listitem>
           <para>
+            <emphasis role="bold">TPM:</emphasis> Enables support for a
+            Trusted Platform Module (TPM) security processor. Choose
+            from the supported TPM versions.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
             <emphasis role="bold">Pointing Device:</emphasis> The
             default virtual pointing device for some guest OSes is the
@@ -1201 +1186 @@
         <listitem>
           <para>
-            <emphasis role="bold">Enable EFI:</emphasis> Enables
-            Extensible Firmware Interface (EFI), which replaces the
-            legacy BIOS and may be useful for certain advanced use
-            cases. See <xref linkend="efi" />.
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
             <emphasis role="bold">Hardware Clock in UTC Time:</emphasis>
             If selected, &product-name; will report the system time in
@@ -1216 +1192 @@
             and may be useful for UNIX-like guest OSes, which typically
             expect the hardware clock to be set to UTC.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Enable EFI:</emphasis> Enables
+            Extensible Firmware Interface (EFI), which replaces the
+            legacy BIOS and may be useful for certain advanced use
+            cases. See <xref linkend="efi" />.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Enable Secure Boot:</emphasis> Enables
+            Secure Boot, to provide a secure environment for starting
+            the guest OS.
           </para>
         </listitem>
@@ -1425 +1418 @@
 
           <para>
-            The GUI will show a warning if the amount of video memory is
-            too small to be able to switch the VM into full screen mode.
-            The minimum value depends on the number of virtual monitors,
-            the screen resolution and the color depth of the host
-            display as well as on the use of <emphasis>3D
+            &vbox-mgr; will show a warning if the amount of video memory
+            is too small to be able to switch the VM into full screen
+            mode. The minimum value depends on the number of virtual
+            monitors, the screen resolution and the color depth of the
+            host display as well as on the use of <emphasis>3D
             acceleration</emphasis> and <emphasis>2D video
             acceleration</emphasis>. A rough estimate is
@@ -1484 +1477 @@
           <para>
             You can set a default scale factor for all VMs. Use the
-            <emphasis role="bold">Display</emphasis> tab in the Global
-            Settings dialogs.
+            <emphasis role="bold">Display</emphasis> tab in the
+            Preferences window.
           </para>
         </listitem>
@@ -1552 +1545 @@
             select here whether the guest should support accelerated 3D
             graphics. See <xref linkend="guestadd-3d" />.
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
-            <emphasis role="bold">Enable 2D Video
-            Acceleration:</emphasis> If a virtual machine with Microsoft
-            Windows has Guest Additions installed, you can select here
-            whether the guest should support accelerated 2D video
-            graphics. See <xref linkend="guestadd-2d" />.
           </para>
         </listitem>
@@ -1724 +1707 @@
 
     <para>
-      If you have used the <emphasis role="bold">Create VM</emphasis>
-      wizard to create a machine, you will normally see something like
-      the following:
+      If you have used the <emphasis role="bold">Create Virtual
+      Machine</emphasis> wizard to create a machine, you will normally
+      see something like the following:
     </para>
 
@@ -1736 +1719 @@
                      width="10cm" />
         </imageobject>
-      </mediaobject>
+      </mediaobject>     
     </figure>
 
@@ -1895 +1878 @@
       Removable media, such as CD/DVDs and floppies, can be changed
       while the guest is running. Since the
-      <emphasis role="bold">Settings</emphasis> dialog is not available
+      <emphasis role="bold">Settings</emphasis> window is not available
       at that time, you can also access these settings from the
       <emphasis role="bold">Devices</emphasis> menu of your virtual
@@ -1925 +1908 @@
         <para>
           <emphasis role="bold">Host Audio Driver:</emphasis> The audio
-          driver that &product-name; uses on the host. On a Linux host,
-          depending on your host configuration, you can select between
-          the OSS, ALSA, or the PulseAudio subsystem. On newer Linux
-          distributions, the PulseAudio subsystem is preferred.
+          driver that &product-name; uses on the host.
+        </para>
+
+        <para>
+          The <emphasis role="bold">Default</emphasis> option is enabled
+          by default for all new VMs. This option selects the best audio
+          driver for the host platform automatically. This enables you
+          to move VMs between different platforms without having to
+          change the audio driver.
+        </para>
+
+        <para>
+          On a Linux host, depending on your host configuration, you can
+          select between the OSS, ALSA, or the PulseAudio subsystem. On
+          newer Linux distributions, the PulseAudio subsystem is
+          preferred.
         </para>
 
@@ -1989 +1984 @@
       virtualize networking. It supports many virtual network cards per
       virtual machine. The first four virtual network cards can be
-      configured in detail in the VirtualBox Manager window. Additional
-      network cards can be configured using the
-      <command>VBoxManage</command> command.
+      configured in detail in &vbox-mgr;. Additional network cards can
+      be configured using the <command>VBoxManage</command> command.
     </para>
 
@@ -2197 +2191 @@
           <listitem>
             <para>
-              <emphasis role="bold">TCP Socket:</emphasis> Useful for
+              <emphasis role="bold">TCP:</emphasis> Useful for
               forwarding serial traffic over TCP/IP, acting as a server,
               or it can act as a TCP client connecting to other servers.
@@ -2347 +2341 @@
 
           </itemizedlist>
-
         </listitem>
 
@@ -2515 +2508 @@
     <para>
       The <emphasis role="bold">User Interface</emphasis> section
-      enables you to change certain aspects of the user interface of
-      this VM.
+      enables you to change certain aspects of the user interface of the
+      selected VM.
     </para>
 
@@ -2524 +2517 @@
         <para>
           <emphasis role="bold">Menu Bar:</emphasis> This widget enables
-          you to disable menus by clicking on the menu to release it,
-          menu entries by deselecting the check box of the entry to
-          disable it and the complete menu bar by deselecting the
-          rightmost check box.
+          you to disable a complete menu, by clicking on the menu name
+          to deselect it. Menu entries can be disabled, by deselecting
+          the check box next to the entry. On Windows and Linux hosts,
+          the complete menu bar can be disabled by deselecting the check
+          box on the right.
         </para>
       </listitem>
@@ -2539 +2533 @@
           itself to a small gray line unless you move the mouse over it.
           With the toolbar, you can return from full screen or seamless
-          mode, control machine execution or enable certain devices. If
-          you do not want to see the toolbar, disable this setting.
-        </para>
-
-        <para>
-          The second setting enables you to show the toolbar at the top
-          of the screen, instead of showing it at the bottom.
+          mode, control machine execution, or enable certain devices. If
+          you do not want to see the toolbar, disable the
+          <emphasis role="bold">Show in Full Screen/Seamless</emphasis>
+          setting.
+        </para>
+
+        <para>
+          The <emphasis role="bold">Show at Top of Screen</emphasis>
+          setting enables you to show the toolbar at the top of the
+          screen, instead of showing it at the bottom.
+        </para>
+
+        <para>
+          The Mini Toolbar is not available on macOS hosts.
         </para>
       </listitem>
@@ -2552 +2553 @@
         <para>
           <emphasis role="bold">Status Bar:</emphasis> This widget
-          enables you to disable icons on the status bar by deselecting
-          the check box of an icon to disable it, to rearrange icons by
-          dragging and dropping the icon, and to disable the complete
-          status bar by deselecting the leftmost check box.
+          enables you to disable and reorder icons on the status bar.
+          Deselect the check box of an icon to disable it, or rearrange
+          icons by dragging and dropping the icon. To disable the
+          complete status bar deselect the check box on the left.
         </para>
       </listitem>
@@ -2578 +2579 @@
       machines. To use EFI for a given virtual machine, you can enable
       EFI in the machine's <emphasis role="bold">Settings</emphasis>
-      dialog. See <xref linkend="settings-motherboard"/>. Alternatively,
+      window. See <xref linkend="settings-motherboard"/>. Alternatively,
       use the <command>VBoxManage</command> command line interface as
       follows:

trunk/doc/manual/en_US/user_Frontends.xml

@@ -66 +66 @@
     <para>
       Even when the extension is installed, the VRDP server is disabled
-      by default. It can easily be enabled on a per-VM basis either in
-      the VirtualBox Manager in the
-      <emphasis role="bold">Display</emphasis> settings, see
-      <xref linkend="settings-display" />, or with the
+      by default. It can easily be enabled on a per-VM basis either from
+      &vbox-mgr; in the <emphasis role="bold">Display</emphasis>
+      settings, see <xref linkend="settings-display" />, or with the
       <command>VBoxManage</command> command, as follows:
     </para>
@@ -103 +102 @@
       The actual port used by a running VM can be either queried with
       the <command>VBoxManage showvminfo</command> command or seen in
-      the GUI on the <emphasis role="bold">Runtime</emphasis> tab of the
-      <emphasis role="bold">Session Information</emphasis> dialog, which
-      is accessible from the <emphasis role="bold">Machine</emphasis>
-      menu of the VM window.
+      &vbox-mgr; on the <emphasis role="bold">Runtime</emphasis> tab of
+      the <emphasis role="bold">Session Information</emphasis> dialog,
+      which is accessible from the
+      <emphasis role="bold">Machine</emphasis> menu of the VM window.
     </para>
 
@@ -251 +250 @@
 
       <para>
-        While any VM started from the VirtualBox Manager is capable of
-        running virtual machines remotely, it is not convenient to have
-        to run the full GUI if you never want to have VMs displayed
-        locally in the first place. In particular, if you are running
-        server hardware whose only purpose is to host VMs, and all your
-        VMs are supposed to run remotely over VRDP, then it is pointless
-        to have a graphical user interface on the server at all. This is
+        While any VM started from &vbox-mgr; is capable of running
+        virtual machines remotely, it is not convenient to have to run
+        the full GUI if you never want to have VMs displayed locally in
+        the first place. In particular, if you are running server
+        hardware whose only purpose is to host VMs, and all your VMs are
+        supposed to run remotely over VRDP, then it is pointless to have
+        a graphical user interface on the server at all. This is
         especially true for Linux or Oracle Solaris hosts, as the
-        VirtualBox Manager comes with dependencies on the Qt and SDL
-        libraries. This is inconvenient if you would rather not have the
-        X Window system on your server at all.
+        &vbox-mgr; comes with dependencies on the Qt and SDL libraries.
+        This is inconvenient if you would rather not have the X Window
+        system on your server at all.
       </para>
 
@@ -325 +324 @@
         <listitem>
           <para>
-            Start <command>VBoxHeadless</command> from the VirtualBox
-            Manager GUI, by pressing the Shift key when starting a
-            virtual machine or by selecting
-            <emphasis role="bold">Headless Start</emphasis> from the
-            <emphasis role="bold">Machine</emphasis> menu.
+            Start <command>VBoxHeadless</command> from &vbox-mgr;, by
+            pressing the Shift key when starting a virtual machine or by
+            selecting <emphasis role="bold">Headless Start</emphasis>
+            from the <emphasis role="bold">Machine</emphasis> menu.
           </para>
         </listitem>
@@ -574 +572 @@
       </para>
 
-    </sect2>
+      </sect2>
 
     <sect2 id="vbox-auth">
@@ -638 +636 @@
                 <listitem>
                   <para>
-                    On Mac OS X hosts, <command>VBoxAuth.dylib</command>
+                    On macOS hosts, <command>VBoxAuth.dylib</command>
                     authenticates users against the host's directory
                     service.
@@ -1069 +1067 @@
       running. This works regardless of the host operating system that
       is running on the hosts. You can teleport virtual machines between
-      Oracle Solaris and Mac OS X hosts, for example.
+      Oracle Solaris and macOS hosts, for example.
     </para>
 

trunk/doc/manual/en_US/user_GuestAdditions.xml

@@ -367 +367 @@
               <emphasis role="bold">Choose/Create a Disk
               Image</emphasis>. This displays the Virtual Media Manager,
-              described in <xref linkend="vdis" />.
+              described in <xref linkend="virtual-media-manager" />.
             </para>
           </listitem>
@@ -392 +392 @@
               <listitem>
                 <para>
-                  On Mac OS X hosts, this file is in the application
-                  bundle of &product-name;. Right-click on the
-                  &product-name; icon in Finder and choose
-                  <emphasis role="bold">Show Package
-                  Contents</emphasis>. The file is located in the
-                  <filename>Contents/MacOS</filename> folder.
+                  On macOS hosts, this file is in the application bundle
+                  of &product-name;. Right-click on the &product-name;
+                  icon in Finder and choose <emphasis role="bold">Show
+                  Package Contents</emphasis>. The file is located in
+                  the <filename>Contents/MacOS</filename> folder.
                 </para>
               </listitem>
@@ -503 +502 @@
       <sect3 id="additions-windows-install-unattended">
 
-        <title>Unattended Installation</title>
-
-        <para>
-          To avoid popups when performing an unattended installation of
-          the &product-name; Guest Additions, the code signing
-          certificates used to sign the drivers needs to be installed in
-          the correct certificate stores on the guest operating system.
-          Failure to do this will cause a typical Windows installation
-          to display multiple dialogs asking whether you want to install
-          a particular driver.
-        </para>
-
-        <note>
-          <para>
-            On some Windows versions, such as Windows 2000 and Windows
-            XP, the user intervention popups mentioned above are always
-            displayed, even after importing the Oracle certificates.
-          </para>
-        </note>
-
-        <para>
-          Installing the code signing certificates on a Windows guest
-          can be done automatically. Use the
-          <filename>VBoxCertUtil.exe</filename> utility from the
-          <filename>cert</filename> folder on the Guest Additions
-          installation CD.
-        </para>
-
-        <para>
-          Use the following steps:
-        </para>
-
-        <orderedlist>
-
-          <listitem>
+        <title>Unattended Installation of the Windows Guest Additions</title>
+
+        <para>
+          You can configure unattended installation of the
+          &product-name; Guest Additions when you create a new VM using
+          the <emphasis role="bold">Create Virtual Machine</emphasis>
+          wizard. Select the <emphasis role="bold">Guest
+          Additions</emphasis> check box on the
+          <emphasis role="bold">Unattended Guest OS Install</emphasis>
+          page of the wizard.
+        </para>
+
+        <para>
+          Guest Additions are installed automatically, following
+          completion of the guest OS installation.
+        </para>
+
+        <simplesect id="additions-windows-install-unattended-certs">
+
+          <title>Installing Code Signing Certificates</title>
+
+          <para>
+            To avoid popups when performing an unattended installation
+            of the &product-name; Guest Additions, the code signing
+            certificates used to sign the drivers needs to be installed
+            in the correct certificate stores on the guest operating
+            system. Failure to do this will cause a typical Windows
+            installation to display multiple dialogs asking whether you
+            want to install a particular driver.
+          </para>
+
+          <note>
             <para>
-              Log in as Administrator on the guest.
+              On some legacy Windows versions, such as Windows 2000 and
+              Windows XP, the user intervention popups mentioned above
+              are always displayed, even after importing the Oracle
+              certificates.
             </para>
-          </listitem>
-
-          <listitem>
+          </note>
+
+          <para>
+            Installing the code signing certificates on a Windows guest
+            can be done automatically. Use the
+            <filename>VBoxCertUtil.exe</filename> utility from the
+            <filename>cert</filename> folder on the Guest Additions
+            installation CD.
+          </para>
+
+          <para>
+            Use the following steps:
+          </para>
+
+          <orderedlist>
+
+            <listitem>
+              <para>
+                Log in as Administrator on the guest.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                Mount the &product-name; Guest Additions .ISO.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                Open a command line window on the guest and change to
+                the <filename>cert</filename> folder on the
+                &product-name; Guest Additions CD.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                Run the following command:
+              </para>
+
+<screen>VBoxCertUtil.exe add-trusted-publisher vbox*.cer --root vbox*.cer</screen>
+
+              <para>
+                This command installs the certificates to the
+                certificate store. When installing the same certificate
+                more than once, an appropriate error will be displayed.
+              </para>
+            </listitem>
+
+          </orderedlist>
+
+          <para>
+            To allow for completely unattended guest installations, you
+            can specify a command line parameter to the install
+            launcher:
+          </para>
+
+<screen>VBoxWindowsAdditions.exe /S</screen>
+
+          <para>
+            This automatically installs the right files and drivers for
+            the corresponding platform, either 32-bit or 64-bit.
+          </para>
+
+          <note>
             <para>
-              Mount the &product-name; Guest Additions .ISO.
+              By default on an unattended installation on a Vista or
+              Windows 7 guest, there will be the XPDM graphics driver
+              installed. This graphics driver does not support Windows
+              Aero / Direct3D on the guest. Instead, the WDDM graphics
+              driver needs to be installed. To select this driver by
+              default, add the command line parameter
+              <literal>/with_wddm</literal> when invoking the Windows
+              Guest Additions installer. This is only required for Vista
+              and Windows 7.
             </para>
-          </listitem>
-
-          <listitem>
+          </note>
+
+          <note>
             <para>
-              Open a command line window on the guest and change to the
-              <filename>cert</filename> folder on the &product-name;
-              Guest Additions CD.
+              For Windows Aero to run correctly on a guest, the guest's
+              VRAM size needs to be configured to at least 128 MB.
             </para>
-          </listitem>
-
-          <listitem>
-            <para>
-              Run the following command:
-            </para>
-
-<screen>VBoxCertUtil.exe add-trusted-publisher vbox*.cer --root vbox*.cer</screen>
-
-            <para>
-              This command installs the certificates to the certificate
-              store. When installing the same certificate more than
-              once, an appropriate error will be displayed.
-            </para>
-          </listitem>
-
-        </orderedlist>
-
-        <para>
-          To allow for completely unattended guest installations, you
-          can specify a command line parameter to the install launcher:
-        </para>
-
-<screen>VBoxWindowsAdditions.exe /S</screen>
-
-        <para>
-          This automatically installs the right files and drivers for
-          the corresponding platform, either 32-bit or 64-bit.
-        </para>
-
-        <note>
-          <para>
-            By default on an unattended installation on a Vista or
-            Windows 7 guest, there will be the XPDM graphics driver
-            installed. This graphics driver does not support Windows
-            Aero / Direct3D on the guest. Instead, the WDDM graphics
-            driver needs to be installed. To select this driver by
-            default, add the command line parameter
-            <literal>/with_wddm</literal> when invoking the Windows
-            Guest Additions installer. This is only required for Vista
-            and Windows 7.
-          </para>
-        </note>
-
-        <note>
-          <para>
-            For Windows Aero to run correctly on a guest, the guest's
-            VRAM size needs to be configured to at least 128 MB.
-          </para>
-        </note>
-
-        <para>
-          For more options regarding unattended guest installations,
-          consult the command line help by using the command:
-        </para>
+          </note>
+
+          <para>
+            For more options regarding unattended guest installations,
+            consult the command line help by using the command:
+          </para>
 
 <screen>VBoxWindowsAdditions.exe /?</screen>
+
+        </simplesect>
 
       </sect3>
@@ -779 +801 @@
       </sect3>
 
+      <sect3 id="additions-linux-install-unattended">
+
+        <title>Unattended Installation of the Linux Guest Additions</title>
+
+        <para>
+          You can configure unattended installation of the
+          &product-name; Guest Additions when you create a new VM using
+          the <emphasis role="bold">Create Virtual Machine</emphasis>
+          wizard. Select the <emphasis role="bold">Guest
+          Additions</emphasis> check box on the
+          <emphasis role="bold">Unattended Guest OS Install</emphasis>
+          page of the wizard.
+        </para>
+
+        <para>
+          Guest Additions are installed automatically, following
+          completion of the guest OS installation.
+        </para>
+
+      </sect3>
+
       <sect3 id="additions-linux-graphics-mouse">
 
@@ -822 +865 @@
           Starting from &product-name; 7, Linux guest screen resize
           functionality for guests running VMSVGA graphics configuration
-          has been changed. Since then, this functionality consists
-          of a standalone daemon called VBoxDRMClient and its Desktop
+          has been changed. Since then, this functionality consists of a
+          standalone daemon called VBoxDRMClient and its Desktop
           Environment helper counterpart.
         </para>
 
         <para>
-          VBoxDRMClient is running as a root process and, in fact, is
-          a bridge between host and guest's vmwgfx driver. This means that
-          VBoxDRMClient listens to screen resize hints from host and
-          forwards them to vmwgfx driver. This allows to make guest screen resize
-          functionality available before user performed graphical log-in.
+          VBoxDRMClient runs as a root process and is a bridge between
+          the host and the guest's vmwgfx driver. This means that
+          VBoxDRMClient listens to screen resize hints from the host and
+          forwards them to the vmwgfx driver. This enables guest screen
+          resize functionality to be available before the user has
+          performed a graphical login.
         </para>
 
         <para>
           In order to perform Desktop Environment specific actions, such
-          as setting primary screen in multi monitor setup, a Desktop Environment
-          helper is used. Once user performed graphical log-in operation,
-          helper daemon starts in scope of user session and attempts to
-          connect to VBoxDRMClient using IPC connection. Once VBoxDRMClient received
-          corresponding command from host, it is forwarded to helper daemon
-          over IPC and action then performed.
-        </para>
-
-        <para>
-          By default, VBoxDRMClient allows any process to connect to its IPC
-          socket. This can be restricted once two actions are taken. Starting
-          from &product-name; 7, Guest Additions Linux installer will also
-          create 'vboxdrmipc' user group. Corresponding user needs to be added
-          into this group. The last action is to set the following guest property:
+          as setting the primary screen in a multimonitor setup, a
+          Desktop Environment helper is used. Once the user has
+          performed a graphical login operation, the helper daemon
+          starts with user session scope and attempts to connect to
+          VBoxDRMClient using an IPC connection. When VBoxDRMClient has
+          received a corresponding command from the host, it is
+          forwarded to the helper daemon over IPC and the action is then
+          performed.
+        </para>
+
+        <para>
+          By default, VBoxDRMClient allows any process to connect to its
+          IPC socket. This can be restricted by using the following
+          steps:
+        </para>
+
+        <orderedlist>
+
+          <listitem>
+            <para>
+              The Guest Additions Linux installer creates a
+              <literal>vboxdrmipc</literal> user group. A corresponding
+              user needs to be added to this group.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              You must set the <literal>DRMIpcRestricted</literal> guest
+              property, as follows:
+            </para>
 
 <screen>VBoxManage guestproperty set "VM name" /VirtualBox/GuestAdd/DRMIpcRestricted 1 \
 --flags RDONLYGUEST</screen>
-        </para>
-
-        <para>
-          Note, it is important to set RDONLYGUEST flag to the property, so
-          it cannot be changed from inside guest. All actions are required. If one of
-          them is missing, all processes will have access to IPC socket. Restricted
-          mode can be disabled by deleting guest property:
+
+            <para>
+              It is important to set only the RDONLYGUEST flag for the
+              property, so that it cannot be changed from inside the
+              guest.
+            </para>
+          </listitem>
+
+        </orderedlist>
+
+        <note>
+          <para>
+            Both steps are required. If one of them is missing, all
+            processes will have access to the IPC socket.
+          </para>
+        </note>
+
+        <para>
+          Restricted mode can be disabled by unsetting the guest
+          property, as follows:
+        </para>
 
 <screen>VBoxManage guestproperty unset "VM name" /VirtualBox/GuestAdd/DRMIpcRestricted</screen>
-        </para>
 
       </sect3>
@@ -980 +1054 @@
               as your Oracle Solaris guest's virtual CD-ROM drive,
               exactly the same way as described for a Windows guest in
-              <xref
-            linkend="mountingadditionsiso" />.
+              <xref linkend="mountingadditionsiso" />.
             </para>
 
@@ -1015 +1088 @@
       </sect3>
 
+      <sect3 id="additions-solaris-install-unattended">
+
+        <title>Unattended Installation of the Oracle Solaris Guest Additions</title>
+
+        <para>
+          You can configure unattended installation of the
+          &product-name; Guest Additions when you create a new VM using
+          the <emphasis role="bold">Create Virtual Machine</emphasis>
+          wizard. Select the <emphasis role="bold">Guest
+          Additions</emphasis> check box on the
+          <emphasis role="bold">Unattended Guest OS Install</emphasis>
+          page of the wizard.
+        </para>
+
+        <para>
+          Guest Additions are installed automatically, following
+          completion of the guest OS installation.
+        </para>
+
+      </sect3>
+
       <sect3 id="additions-solaris-uninstall">
 
@@ -1125 +1219 @@
           If a VM is not currently running, you can configure shared
           folders in the virtual machine's
-          <emphasis role="bold">Settings</emphasis> dialog.
+          <emphasis role="bold">Settings</emphasis> window.
         </para>
       </listitem>
@@ -1160 +1254 @@
           Transient shares, that are added at runtime and disappear when
           the VM is powered off. These can be created using a check box
-          in the VirtualBox Manager, or by using the
-          <option>--transient</option> option of the <command>VBoxManage
-          sharedfolder add</command> command.
+          in &vbox-mgr;, or by using the <option>--transient</option>
+          option of the <command>VBoxManage sharedfolder add</command>
+          command.
         </para>
       </listitem>
@@ -1173 +1267 @@
       read files on the host. By default, shared folders are read-write.
       Read-only folders can be created using a check box in the
-      VirtualBox Manager, or with the <option>--readonly</option> option
-      of the <command>VBoxManage sharedfolder add</command> command.
+      &vbox-mgr;, or with the <option>--readonly</option> option of the
+      <command>VBoxManage sharedfolder add</command> command.
     </para>
 
@@ -1188 +1282 @@
         <para>
           The host operating system must support symlinks. For example,
-          a Mac OS X, Linux, or Oracle Solaris host is required.
+          a macOS, Linux, or Oracle Solaris host is required.
         </para>
       </listitem>
@@ -1279 +1373 @@
             Replace <replaceable>sharename</replaceable>, use a
             lowercase string, with the share name specified with
-            <command>VBoxManage</command> or the VirtualBox Manager.
-            Replace <replaceable>mountpoint</replaceable> with the path
-            where you want the share to be mounted on the guest, such as
+            <command>VBoxManage</command> or &vbox-mgr;. Replace
+            <replaceable>mountpoint</replaceable> with the path where
+            you want the share to be mounted on the guest, such as
             <filename>/mnt/share</filename>. The usual mount rules
             apply. For example, create this directory first if it does
@@ -1493 +1587 @@
     <figure id="fig-drag-drop-options">
       <title>Drag and Drop Menu Options</title>
-    <mediaobject>
+     <mediaobject>
         <imageobject>
           <imagedata align="center" fileref="images/dnd-modes.png"
@@ -1542 +1636 @@
       <para>
         Drag and drop support depends on the frontend being used. At the
-        moment, only the VirtualBox Manager frontend provides this
+        moment, only the &vbox-mgr; frontend provides this
         functionality.
       </para>
@@ -1799 +1893 @@
         acceleration hardware instead of performing overlay stretching
         and color conversion in software, which would be slow. This
-        currently works for Windows, Linux and Mac OS X host platforms,
+        currently works for Windows, Linux and macOS host platforms,
         provided that your host operating system can make use of 2D
         video acceleration in the first place.
@@ -1886 +1980 @@
     <figure id="fig-seamless-windows">
       <title>Seamless Windows on a Host Desktop</title>
-    <mediaobject>
+     <mediaobject>
         <imageobject>
           <imagedata align="center" fileref="images/seamless.png" width="14cm" />
@@ -2097 +2191 @@
     </para>
 
+    <para>
+      This feature is useful when the VM window of a guest is not
+      visible. For example, when the guest is running in headless mode.
+    </para>
+
+    <note>
+      <para>
+        To use the Guest Control File Manager, the guest must be
+        running. For powered-off guests, it is disabled automatically.
+      </para>
+    </note>
+
     <figure id="fig-guest-control-fm">
       <title>Guest Control File Manager</title>
-    <mediaobject>
+     <mediaobject>
         <imageobject>
           <imagedata align="center" fileref="images/guest-fm.png"
@@ -2105 +2211 @@
         </imageobject>
       </mediaobject>
+
     </figure>
 
@@ -2126 +2233 @@
         <listitem>
           <para>
-            Open the Guest Control File Manager.
-          </para>
-
-          <para>
-            In the guest VM, select
-            <emphasis role="bold">Machine</emphasis>,
-            <emphasis role="bold">File Manager</emphasis>.
-          </para>
+            Open the Guest Control File Manager. Do either of the
+            following:
+          </para>
+
+          <itemizedlist>
+
+            <listitem>
+              <para>
+                In the guest VM, select
+                <emphasis role="bold">Machine</emphasis>,
+                <emphasis role="bold">File Manager</emphasis>.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                In &vbox-mgr;, click on the machine name. Click
+                <emphasis role="bold">File Manager</emphasis> in the
+                machine tools menu for the VM.
+              </para>
+            </listitem>
+
+          </itemizedlist>
 
           <para>
@@ -2167 +2289 @@
 
           <para>
-            You can copy and move files from a guest to the host system
-            or from the host system to the guest.
+            You can copy and move files from the guest to the host
+            system or from the host system to the guest.
           </para>
         </listitem>
@@ -2251 +2373 @@
             <para>
               &product-name; supports memory ballooning only on 64-bit
-              hosts. It is not supported on Mac OS X hosts.
+              hosts. It is not supported on macOS hosts.
             </para>
           </listitem>
@@ -2358 +2480 @@
         <para>
           &product-name; supports Page Fusion only on 64-bit hosts, and
-          it is not supported on Mac OS X hosts. Page Fusion currently
+          it is not supported on macOS hosts. Page Fusion currently
           works only with Windows 2000 and later guests.
         </para>
@@ -2469 +2591 @@
         of each virtual monitor and its state (disabled/enabled). The
         resolution of a virtual monitor can be modified from the host
-        side either by resizing the window that hosts the virtual monitor,
-        through the view menu or through
-        <code>VBoxManage controlvm "vmname" setscreenlayout</code>.
-        On guest operating systems with X11/Wayland desktops this is
-        put into effect by either of two following services:
-      </para>
-
-      <screen>
+        side either by resizing the window that hosts the virtual
+        monitor, by using the <emphasis role="bold">View</emphasis> menu
+        or the <command>VBoxManage controlvm
+        <replaceable>vmname</replaceable> setscreenlayout</command>
+        command. On guest operating systems with X11/Wayland desktops
+        this is put into effect by either of the following two services:
+      </para>
+
+<screen>
         VBoxClient --vmsvga
         VBoxDRMClient
@@ -2482 +2605 @@
 
       <para>
-        Here are some details about guest screen resolution control
-        functionality:
+        The following are some details about guest screen resolution
+        control functionality:
       </para>
 
@@ -2490 +2613 @@
         <listitem>
           <para>
-            On X11/Wayland desktops the resizing service is started during
-            desktop session initialization, that is desktop login. On X11
-            desktops <code>VBoxClient --vmsvga</code> handles screen
-            topology through the RandR extension.
-            On Wayland clients <code>VBoxDRMClient</code> is used. The
-            decision is made automatically at each desktop session start.
-          </para>
-        </listitem>
-        <listitem>
-          <para>
-            On 32 bit guest operating systems <code>VBoxDRMClient</code>
-            is always used, in order to work around bugs.
-          </para>
-        </listitem>
-        <listitem>
-          <para>
-            Since the mentioned monitor topology control services are
-            initialized during the desktop session start, it is impossible
-            to control the monitor resolution of display managers such as
-            gdm, lightdm. This default behavior can be changed by setting
-            the guest property <code>/VirtualBox/GuestAdd/DRMResize</code>
-            of the virtual machine to any value. Please refer to
-            <xref linkend="guestadd-guestprops" /> for updating guest
-            properties. When this guest property is set then
-            <code>VBoxDRMClient</code> is started during the guest OS boot
-            and stays active all the time, for both ithe display manager
-            login screen and the desktop session.
+            On X11/Wayland desktops the resizing service is started
+            during desktop session initialization, that is desktop
+            login. On X11 desktops <code>VBoxClient --vmsvga</code>
+            handles screen topology through the RandR extension. On
+            Wayland clients <code>VBoxDRMClient</code> is used. The
+            decision is made automatically at each desktop session
+            start.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            On 32-bit guest operating systems
+            <command>VBoxDRMClient</command> is always used, in order to
+            work around bugs.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Since the monitor topology control services are initialized
+            during the desktop session start, it is impossible to
+            control the monitor resolution of display managers such as
+            GDM or LightDM. This default behavior can be changed by
+            setting the guest property
+            <literal>/VirtualBox/GuestAdd/DRMResize</literal> of the
+            virtual machine to any value. See
+            <xref linkend="guestadd-guestprops" /> for details of how to
+            update guest properties. When this guest property is set
+            then <command>VBoxDRMClient</command> is started during the
+            guest OS boot and stays active all the time, for both the
+            display manager login screen and the desktop session.
           </para>
         </listitem>
@@ -2525 +2653 @@
 
         <title>Known Limitations</title>
-        <para>
-          <code>VBoxDRMClient</code> is not able to handle arbitrary guest
-          monitor topologies. Specifically, disabling a guest monitor
-          (except the last one) invalidates the monitor topology due to
-          limitations in the Linux kernel module <code>vmwgfx.ko</code>.
-          iFor example, when the guest is configured to have 4 monitors
-          it is not recommended to disable the 2nd or 3rd monitor.
+
+        <para>
+          <command>VBoxDRMClient</command> is not able to handle
+          arbitrary guest monitor topologies. Specifically, disabling a
+          guest monitor that is not the last one invalidates the monitor
+          topology due to limitations in the
+          <literal>vmwgfx.ko</literal> Linux kernel module. For example,
+          when the guest is configured to have four monitors it is not
+          recommended to disable the second or third monitor.
         </para>
 

trunk/doc/manual/en_US/user_Installation.xml

@@ -33 +33 @@
     As installation of &product-name; varies depending on your host
     operating system, the following sections provide installation
-    instructions for Windows, Mac OS X, Linux, and Oracle Solaris.
+    instructions for Windows, macOS, Linux, and Oracle Solaris.
   </para>
 
@@ -419 +419 @@
   <sect1 id="installation-mac">
 
-    <title>Installing on Mac OS X Hosts</title>
+    <title>Installing on macOS Hosts</title>
 
     <sect2 id="install-mac-performing">
@@ -426 +426 @@
 
       <para>
-        For Mac OS X hosts, &product-name; ships in a
+        For macOS hosts, &product-name; ships in a
         <filename>dmg</filename> disk image file. Perform the following
-        steps to install on a Mac OS X host:
+        steps to install on a macOS host:
       </para>
 
@@ -565 +565 @@
         system kernel. The kernel is the part of the operating system
         which controls your processor and physical hardware. Without
-        this kernel module, you can still use the VirtualBox Manager to
-        configure virtual machines, but they will not start.
+        this kernel module, you can still use &vbox-mgr; to configure
+        virtual machines, but they will not start.
       </para>
 
@@ -1424 +1424 @@
   </sect1>
 
+  <sect1 id="install-ext-pack">
+
+    <title>Installing an Extension Pack</title>
+
+    <para>
+      Extension packs provide extra functionality to the &product-name;
+      base package, such as extended USB device support and cloud
+      integration features. See <xref linkend="intro-installing"/>.
+    </para>
+
+    <para>
+      To install an &product-name; extension pack, do the following:
+    </para>
+
+    <orderedlist>
+
+      <listitem>
+        <para>
+          Double-click on the extension package file name.
+        </para>
+
+        <para>
+          &product-name; extension packs have a
+          <filename>.vbox-extpack</filename> file name extension.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Follow the on-screen instructions to install the extension
+          pack.
+        </para>
+      </listitem>
+
+    </orderedlist>
+
+    <para>
+      You can also use the Extension Pack Manager tool to install an
+      extension pack. See <xref linkend="install-ext-pack-manager"/>.
+    </para>
+
+    <sect2 id="install-ext-pack-manager">
+
+      <title>The Extension Pack Manager</title>
+
+      <para>
+        Extension packs can be installed and managed using the
+        <emphasis role="bold">Extension Pack Manager</emphasis> tool in
+        &vbox-mgr;.
+      </para>
+
+      <para>
+        The Extension Pack Manager lists the extension packs that are
+        currently installed on the host, and enables you to install and
+        uninstall extension packs.
+      </para>
+
+      <para>
+        To display the Extension Pack Manager, go to the global
+        <emphasis role="bold">Tools</emphasis> menu and click
+        <emphasis role="bold">Extensions</emphasis>. The Extension Pack
+        Manager is shown.
+      </para>
+
+      <para>
+        To install an extension pack using the Extension Pack Manager,
+        click <emphasis role="bold">Install</emphasis> and select an
+        extension package file. The extension pack is installed on the
+        host and listed in Extension Pack Manager.
+      </para>
+
+      <para>
+        To uninstall an extension pack with the Extension Pack Manager,
+        do the following:
+      </para>
+
+      <orderedlist>
+
+        <listitem>
+          <para>
+            Select the extension pack in the Extension Pack Manager
+            window and click <emphasis role="bold">Uninstall</emphasis>.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Click <emphasis role="bold">Remove</emphasis> in the prompt
+            dialog.
+          </para>
+
+          <para>
+            The extension pack is uninstalled from the host and removed
+            from the Extension Pack Manager.
+          </para>
+        </listitem>
+
+      </orderedlist>
+
+      <para>
+        Alternatively, you can use the <command>VBoxManage</command>
+        command line to install and manage &product-name; extension
+        packs. See <xref linkend="vboxmanage-extpack" />.
+      </para>
+
+    </sect2>
+
+  </sect1>
+
 </chapter>

trunk/doc/manual/en_US/user_Introduction.xml

@@ -37 +37 @@
     &product-name; is a cross-platform virtualization application. What
     does that mean? For one thing, it installs on your existing Intel or
-    AMD-based computers, whether they are running Windows, macOS,
-    Linux, or Oracle Solaris operating systems (OSes). Secondly, it
-    extends the capabilities of your existing computer so that it can
-    run multiple OSes, inside multiple virtual machines, at the same
-    time. As an example, you can run Windows and Linux on your Mac, run
-    Windows Server 2016 on your Linux server, run Linux on your Windows
-    PC, and so on, all alongside your existing applications. You can
-    install and run as many virtual machines as you like. The only
-    practical limits are disk space and memory.
+    AMD-based computers, whether they are running Windows, macOS, Linux,
+    or Oracle Solaris operating systems (OSes). Secondly, it extends the
+    capabilities of your existing computer so that it can run multiple
+    OSes, inside multiple virtual machines, at the same time. As an
+    example, you can run Windows and Linux on your Mac, run Windows
+    Server on your Linux server, run Linux on your Windows PC, and so
+    on, all alongside your existing applications. You can install and
+    run as many virtual machines as you like. The only practical limits
+    are disk space and memory.
   </para>
 
@@ -136 +136 @@
 
         <para>
-          On top of that, with the use of another &product-name; feature
-          called <emphasis>snapshots</emphasis>, one can save a
+          Using virtual machines enables you to build and test a
+          multi-node networked service, for example. Issues with
+          networking, operating system, and software configuration can
+          be investigated easily.
+        </para>
+
+        <para>
+          In addition to that, with the use of another &product-name;
+          feature called <emphasis>snapshots</emphasis>, one can save a
           particular state of a virtual machine and revert back to that
           state, if necessary. This way, one can freely experiment with
@@ -189 +196 @@
           OS).</emphasis> This is the OS of the physical computer on
           which &product-name; was installed. There are versions of
-          &product-name; for Windows, macOS, Linux, and Oracle
-          Solaris hosts. See <xref linkend="hostossupport" />.
+          &product-name; for Windows, macOS, Linux, and Oracle Solaris
+          hosts. See <xref linkend="hostossupport" />.
         </para>
 
@@ -239 +246 @@
 
         <para>
-          You can view these VM settings in the VirtualBox Manager
-          window, the <emphasis role="bold">Settings</emphasis> dialog,
-          and by running the <command>VBoxManage</command> command. See
+          You can view these VM settings in &vbox-mgr;, in the
+          <emphasis role="bold">Settings</emphasis> window, and by
+          running the <command>VBoxManage</command> command. See
           <xref linkend="vboxmanage" />.
         </para>
@@ -284 +291 @@
           2</emphasis> hypervisor. Whereas a
           <emphasis>bare-metal</emphasis> or <emphasis>type 1</emphasis>
-          hypervisor would run directly on the hardware, &product-name;
+          hypervisor runs directly on the hardware, &product-name;
           requires an existing OS to be installed. It can thus run
           alongside existing applications on that host.
@@ -295 +302 @@
           machines created on one host on another host with a different
           host OS. For example, you can create a virtual machine on
-          Windows and then run it under Linux.
+          Windows and then run it on Linux.
         </para>
 
@@ -339 +346 @@
       <listitem>
         <para>
-          <emphasis role="bold">Great hardware support.</emphasis> Among
-          other features, &product-name; supports the following:
+          <emphasis role="bold">Comprehensive hardware
+          support.</emphasis> Among other features, &product-name;
+          supports the following:
         </para>
 
@@ -636 +644 @@
           <xref linkend="KnownIssues" />.
         </para>
+
+        <para>
+          An installer package is available for macOS/Arm64, for systems
+          using an Apple silicon CPU. With this package, you can run
+          some guest operating systems for Intel x86/x64 CPUs in an
+          emulation.
+        </para>
+
+        <para>
+          The macOS/Arm64 installer package for Apple silicon platform
+          is available as a Developer Preview release. This package
+          represents a work in progress project and the performance is
+          very modest.
+        </para>
+
+        <note>
+          <para>
+            Developer Preview is a public release for developers, which
+            provides early access to unsupported software release and
+            features.
+          </para>
+        </note>
       </listitem>
 
@@ -660 +690 @@
           <listitem>
             <para>
-              Oracle Linux 7 and 8
-            </para>
-          </listitem>
-
-          <listitem>
-            <para>
-              CentOS/Red Hat Enterprise Linux 7 and 8
+              Oracle Linux 7, 8 and 9
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              CentOS/Red Hat Enterprise Linux 7, 8 and 9
             </para>
           </listitem>
@@ -825 +855 @@
           <listitem>
             <para>
-              Cloud integration features. See <xref linkend="ovf"/>.
+              Cloud integration features. See
+              <xref linkend="cloud-integration"/>.
             </para>
           </listitem>
@@ -832 +863 @@
 
         <para>
-          &product-name; extension packages have a
-          <filename>.vbox-extpack</filename> file name extension. To
-          install an extension, simply double-click on the package file
-          and a <emphasis role="bold">Network Operations
-          Manager</emphasis> window is shown to guide you through the
-          required steps.
-        </para>
-
-        <para>
-          To view the extension packs that are currently installed,
-          start the VirtualBox Manager, as shown in
-          <xref linkend="intro-starting"/>. From the
-          <emphasis role="bold">File</emphasis> menu, select
-          <emphasis role="bold">Preferences</emphasis>. In the window
-          that displays, go to the
-          <emphasis role="bold">Extensions</emphasis> category. This
-          shows you the extensions which are currently installed, and
-          enables you to remove a package or add a new package.
-        </para>
-
-        <para>
-          Alternatively, you can use the <command>VBoxManage</command>
-          command line. See <xref linkend="vboxmanage-extpack" />.
+          For details of how to install an extension pack, see
+          <xref linkend="install-ext-pack"/>.
         </para>
       </listitem>
@@ -874 +884 @@
       <listitem>
         <para>
-          On a Windows host, in the
+          <emphasis role="bold">Windows hosts.</emphasis> In the
           <emphasis role="bold">Programs</emphasis> menu, click on the
           item in the <emphasis role="bold">VirtualBox</emphasis> group.
@@ -885 +895 @@
       <listitem>
         <para>
-          On a macOS host, in the Finder, double-click on the
+          <emphasis role="bold">macOS hosts.</emphasis> In the Finder,
+          double-click on the
           <emphasis role="bold">VirtualBox</emphasis> item in the
           Applications folder. You may want to drag this item onto your
@@ -894 +905 @@
       <listitem>
         <para>
-          On a Linux or Oracle Solaris host, depending on your desktop
-          environment, an &product-name; item may have been placed in
-          either the System or System Tools group of your
+          <emphasis role="bold">Linux or Oracle Solaris
+          hosts</emphasis>. Depending on your desktop environment, an
+          &product-name; item may have been placed in either the System
+          or System Tools group of your
           <emphasis role="bold">Applications</emphasis> menu.
           Alternatively, you can enter <command>VirtualBox</command> in
@@ -906 +918 @@
 
     <para>
-      When you start &product-name; for the first time, a window like
-      the following is displayed:
+      When you start &product-name;, the &vbox-mgr; interface is shown.
+      See <xref linkend="gui-virtualboxmanager"/>.
     </para>
 
+  </sect1>
+
+  <sect1 id="gui-virtualboxmanager">
+
+    <title>&vbox-mgr;</title>
+
+    <para>
+      &vbox-mgr; is the user interface for &product-name;. You can use
+      &vbox-mgr; to create, configure, and manage your virtual machines.
+    </para>
+
+    <para>
+      This section describes the main features of the &vbox-mgr; user
+      interface. Subsequent sections and chapters describe how to use
+      &vbox-mgr; to perform tasks in &product-name;.
+    </para>
+
+    <para>
+      When you start &product-name;, the
+      <emphasis role="bold">&vbox-mgr;</emphasis> window is displayed.
+    </para>
+
+    <para>
+      <xref linkend="fig-vbox-manager-initial"/> shows &vbox-mgr; the
+      first time you start &product-name;, before you have created any
+      virtual machines.
+    </para>
+
     <figure id="fig-vbox-manager-initial">
-      <title>VirtualBox Manager Window, After Initial Startup</title>
-    <mediaobject>
+      <title>&vbox-mgr;, Showing Welcome Screen After Initial Startup</title>
+      <mediaobject>
         <imageobject>
           <imagedata align="center" fileref="images/virtualbox-main-empty.png"
@@ -921 +961 @@
 
     <para>
-      This window is called the <emphasis role="bold">VirtualBox
-      Manager</emphasis>. The left pane will later list all your virtual
-      machines. Since you have not yet created any virtual machines,
-      this list is empty. The <emphasis role="bold">Tools</emphasis>
-      button provides access to user tools, such as the Virtual Media
-      Manager.
+      <xref linkend="fig-vbox-manager-populated"/> shows how &vbox-mgr;
+      might look after you have created some virtual machines.
     </para>
 
-    <para>
-      The pane on the right displays the properties of the currently
-      selected virtual machine. Since you do not have any machines yet,
-      the pane displays a welcome message.
-    </para>
-
-    <para>
-      The buttons on the right pane are used to create and work with
-      VMs.
-    </para>
-
-    <para>
-      The following figure gives an idea of what &product-name; might
-      look like after you have created some VMs.
-    </para>
-
     <figure id="fig-vbox-manager-populated">
-      <title>VirtualBox Manager Window, After Creating Virtual Machines</title>
-    <mediaobject>
+      <title>&vbox-mgr; Window, After Creating Virtual Machines</title>
+      <mediaobject>
         <imageobject>
           <imagedata align="center" fileref="images/virtualbox-main.png"
@@ -955 +975 @@
     </figure>
 
+    <para>
+      The main components of the &vbox-mgr; window are as follows:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">The machine list.</emphasis> The left
+          pane of the <emphasis role="bold">VirtualBox
+          Manager</emphasis> window lists all your virtual machines. If
+          you have not yet created any virtual machines, this list is
+          empty. See <xref linkend="gui-machine-list"/>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">The Details pane.</emphasis> The pane on
+          the right displays the properties of the currently selected
+          virtual machine. If you do not have any machines yet, the pane
+          displays a welcome message.
+        </para>
+
+        <para>
+          The toolbar buttons on the Details pane can be used to create
+          and work with virtual machines. See
+          <xref linkend="gui-details"/>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Help Viewer.</emphasis> A window that
+          displays context-sensitive help topics for &vbox-mgr; tasks.
+          See <xref linkend="help-viewer"/>.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+    <sect2 id="gui-machine-list">
+
+      <title>The Machine List</title>
+
+      <para>
+        The list of virtual machines in the left pane is called the
+        <emphasis>machine list</emphasis>.
+      </para>
+
+      <para>
+        The following methods can be used to control and configure
+        virtual machines in the machine list:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            Right-click on the virtual machine name, to display menu
+            options.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Click on the Machine Tools menu, to the right of the virtual
+            machine name. See <xref linkend="gui-tools-machine"/>.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Click a button in the toolbar in the Details pane. See
+            <xref linkend="gui-details"/>.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+    </sect2>
+
+    <sect2 id="gui-details">
+
+      <title>The Details Pane</title>
+
+      <para>
+        The Details pane shows configuration information for a virtual
+        machine that is selected in the machine list. The pane also
+        includes a toolbar for performing tasks.
+      </para>
+
+      <figure id="fig-vbox-details-pane">
+        <title>&vbox-mgr; Details Pane, Including Toolbar</title>
+      <mediaobject>
+        <imageobject>
+          <imagedata align="center" fileref="images/details-pane.png"
+                     width="12cm" />
+        </imageobject>
+      </mediaobject>
+      </figure>
+
+      <para>
+        The Details pane includes the following:
+      </para>
+
+      <simplesect id="gui-details-toolbar">
+
+        <title>&vbox-mgr; Toolbar</title>
+
+        <para>
+          A toolbar at the top of the Details pane contains buttons that
+          enable you to configure the selected virtual machine, or to
+          create a new virtual machine.
+        </para>
+
+        <para>
+          The toolbar includes the following buttons:
+        </para>
+
+        <itemizedlist>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">New.</emphasis> Creates a new
+              virtual machine, and adds it to the machine list.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Add.</emphasis> Adds an existing
+              virtual machine to the machine list.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Settings.</emphasis> Displays the
+              <emphasis role="bold">Settings</emphasis> window for the
+              virtual machine, enabling you to make configuration
+              changes.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Discard.</emphasis> For a running
+              virtual machine, discards the saved state for the virtual
+              machine and closes it down.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Show/Start.</emphasis> For a running
+              virtual machine, <emphasis role="bold">Show</emphasis>
+              displays the virtual machine window. For a stopped virtual
+              machine, <emphasis role="bold">Start</emphasis> displays
+              options for powering up the virtual machine.
+            </para>
+          </listitem>
+
+        </itemizedlist>
+
+      </simplesect>
+
+      <simplesect id="gui-details-settings">
+
+        <title>Settings</title>
+
+        <para>
+          A summary of settings is shown for the virtual machine.
+        </para>
+
+        <para>
+          You can change some virtual machine settings, by clicking on
+          the setting in the Details pane.
+        </para>
+
+        <note>
+          <para>
+            If a virtual machine is running, some settings cannot be
+            altered. You must stop the virtual machine first in order to
+            change the setting.
+          </para>
+        </note>
+
+        <para>
+          Virtual machine settings can also be changed using the
+          <emphasis role="bold">Settings</emphasis> button on the
+          &vbox-mgr; toolbar.
+        </para>
+
+        <para>
+          The virtual machine settings on the Details pane are organized
+          in sections that correspond to those used in the
+          <emphasis role="bold">Settings</emphasis> window. See
+          <xref linkend="BasicConcepts"/>.
+        </para>
+
+        <para>
+          Click the arrow icon to hide or show each section.
+        </para>
+
+      </simplesect>
+
+      <simplesect id="gui-details-preview">
+
+        <title>Preview Window</title>
+
+        <para>
+          The virtual machine display is shown in a small window.
+        </para>
+
+        <para>
+          You can use the Preview window to check if your virtual
+          machine has finished booting up.
+        </para>
+
+        <para>
+          Click the arrow icon to hide or show the Preview window.
+        </para>
+
+      </simplesect>
+
+      <simplesect id="gui-notification-center">
+
+        <title>Notification Center</title>
+
+        <para>
+          Notification messages may be shown in a sliding panel on the
+          right of the Details pane, called the
+          <emphasis role="bold">Notification Center</emphasis>. Click
+          the warning triangle to show the notification messages.
+        </para>
+
+        <para>
+          Most system messages that do not require user interaction are
+          displayed in the Notification Center, including task failure
+          alerts.
+        </para>
+
+        <para>
+          The progress of some tasks can be observed and stopped using
+          the Notification Center.
+        </para>
+
+      </simplesect>
+
+    </sect2>
+
+    <sect2 id="gui-tools">
+
+      <title>&vbox-mgr; Tools</title>
+
+      <para>
+        &vbox-mgr; provides two types of user tools, to enable you to
+        perform common tasks easily.
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Global Tools.</emphasis> These tools
+            apply to <emphasis>all</emphasis> virtual machines. See
+            <xref linkend="gui-tools-global"/>.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Machine Tools.</emphasis> These tools
+            apply to a <emphasis>specific</emphasis> virtual machine.
+            See <xref linkend="gui-tools-machine"/>.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+      <simplesect id="gui-tools-global">
+
+        <title>Global Tools</title>
+
+        <para>
+          In the left pane of the &vbox-mgr; window, click the
+          <emphasis role="bold">Menu</emphasis> icon in the
+          <emphasis role="bold">Tools</emphasis> banner located above
+          the machine list. The <emphasis role="bold">Global
+          Tools</emphasis> menu is displayed.
+        </para>
+
+        <figure id="fig-global-tools-menu">
+          <title>Global Tools Menu</title>
+      <mediaobject>
+        <imageobject>
+          <imagedata align="center" fileref="images/global-tools-menu.png"
+                     width="10cm" />
+        </imageobject>
+      </mediaobject>
+        </figure>
+
+        <para>
+          A drop-down list enables you to select from the following
+          global tools:
+        </para>
+
+        <itemizedlist>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Welcome.</emphasis> Displays the
+              &vbox-mgr; welcome message. The &vbox-mgr; toolbar is also
+              included, to enable you to get started with using
+              &product-name;. See
+              <xref linkend="fig-vbox-manager-initial"/>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Extensions.</emphasis> Displays the
+              <emphasis role="bold">Extension Pack Manager</emphasis>
+              tool. This tool is used to install and uninstall
+              &product-name; Extension Packs. See
+              <xref linkend="install-ext-pack-manager"/>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Media.</emphasis> Displays the
+              <emphasis role="bold">Virtual Media Manager</emphasis>
+              tool. This tool is used to manage the disk images used by
+              &product-name;. See
+              <xref linkend="virtual-media-manager"/>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Network.</emphasis> Displays the
+              <emphasis role="bold">Network Manager</emphasis> tool.
+              This tool is used to create and configure some types of
+              networks used by &product-name;. See
+              <xref linkend="network-manager"/>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Cloud.</emphasis> Displays the
+              <emphasis role="bold">Cloud Profile Editor</emphasis>
+              tool. This tool is used to configure connections to a
+              cloud service, such as &oci;. See
+              <xref linkend="cloud-using-cloud-profile-manager"/>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Activities.</emphasis> Displays the
+              <emphasis role="bold">VM Activity Overview</emphasis>
+              tool. This tool is used to monitor performance and
+              resource usage of virtual machines. See
+              <xref linkend="vm-info"/>.
+            </para>
+          </listitem>
+
+        </itemizedlist>
+
+        <para>
+          The <emphasis role="bold">Pin</emphasis> icon is used to keep
+          the <emphasis role="bold">Tools</emphasis> banner visible as
+          you scroll down the entries in the machine list.
+        </para>
+
+      </simplesect>
+
+      <simplesect id="gui-tools-machine">
+
+        <title>Machine Tools</title>
+
+        <para>
+          In the machine list in the left pane of the &vbox-mgr; window,
+          select a virtual machine.
+        </para>
+
+        <para>
+          Click the <emphasis role="bold">Menu</emphasis> icon to the
+          right of the virtual machine name. The
+          <emphasis role="bold">Machine Tools</emphasis> menu is
+          displayed.
+        </para>
+
+        <figure id="fig-machine-tools-menu">
+          <title>Machine Tools Menu</title>
+      <mediaobject>
+        <imageobject>
+          <imagedata align="center" fileref="images/machine-tools-menu.png"
+                     width="10cm" />
+        </imageobject>
+      </mediaobject>
+        </figure>
+
+        <para>
+          A drop-down list enables you to select from the following
+          machine tools:
+        </para>
+
+        <itemizedlist>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Details.</emphasis> Displays the
+              Details pane for the selected virtual machine. See
+              <xref linkend="gui-details"/>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Snapshots.</emphasis> Displays the
+              <emphasis role="bold">Snapshots</emphasis> tool. This tool
+              enables you to view and manage snapshots for the virtual
+              machine. See <xref linkend="snapshots"/>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Logs.</emphasis> Displays the
+              <emphasis role="bold">Log Viewer</emphasis> tool. This
+              tool enables you to view and search system logs for the
+              virtual machine. See <xref linkend="log-viewer"/>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Activity.</emphasis> Displays the
+              <emphasis role="bold">VM Activity</emphasis> page of the
+              <emphasis role="bold">Session Information</emphasis>
+              dialog. This dialog enables you to view and analyze
+              performance metrics for the virtual machine. See
+              <xref linkend="vm-info"/>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">File Manager.</emphasis> Displays
+              the <emphasis role="bold">Guest Control File
+              Manager</emphasis> tool. This tool enables you to manage
+              files on the guest system. See
+              <xref linkend="guestadd-gc-file-manager"/>.
+            </para>
+          </listitem>
+
+        </itemizedlist>
+
+      </simplesect>
+
+    </sect2>
+
+    <sect2 id="help-viewer">
+
+      <title>Help Viewer</title>
+
+      <para>
+        The Help Viewer is a window that displays context-sensitive help
+        to assist you in completing common &vbox-mgr; tasks. You can
+        display the Help Viewer in the following ways:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            In a &vbox-mgr; wizard or dialog, click
+            <emphasis role="bold">Help</emphasis> to display the
+            relevant help topic.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            In &vbox-mgr; or from a guest VM, do either of the
+            following:
+          </para>
+
+          <itemizedlist>
+
+            <listitem>
+              <para>
+                Select the <emphasis role="bold">Help</emphasis>,
+                <emphasis role="bold">Contents</emphasis> menu option.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                Press the <emphasis role="bold">F1</emphasis> button.
+              </para>
+
+              <para>
+                The keyboard shortcut used to access the Help Viewer can
+                be configured in the
+                <emphasis role="bold">Preferences</emphasis> window.
+              </para>
+            </listitem>
+
+          </itemizedlist>
+        </listitem>
+
+      </itemizedlist>
+
+      <para>
+        The Help Viewer has the following features:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Navigation tools.</emphasis> The left
+            hand pane contains the following navigation tools:
+          </para>
+
+          <itemizedlist>
+
+            <listitem>
+              <para>
+                <emphasis role="bold">Contents.</emphasis> Displays the
+                help topic location in the &product-name; documentation.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                <emphasis role="bold">Search.</emphasis> Enables you to
+                search the documentation for help topics.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                <emphasis role="bold">Bookmarks.</emphasis> Enables you
+                to bookmark useful help topics.
+              </para>
+            </listitem>
+
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Tabbed browsing.</emphasis> Help
+            topics that you have visited are displayed in tabs in the
+            main window pane.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Zoomable topics.</emphasis> Zoom
+            controls enable you to enlarge help topic details.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Printing.</emphasis> Help topics can
+            be printed to PDF file or to a local printer.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+    </sect2>
+
+    <sect2 id="vboxmanager-wizards">
+
+      <title>About &vbox-mgr; Wizards</title>
+
+      <para>
+        &vbox-mgr; includes wizards that enable you to complete tasks
+        easily. Examples of such tasks are when you create a new virtual
+        machine or use the cloud integration features of &product-name;.
+      </para>
+
+      <para>
+        To display a help topic for the wizard, click the
+        <emphasis role="bold">Help</emphasis> button.
+      </para>
+
+      <para>
+        Some wizards can be displayed in either of the following modes:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Guided mode.</emphasis> This is the
+            default display mode. Wizards are shown in the conventional
+            manner, using a series of pages with descriptions to guide
+            the user through the steps for a task.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold"><emphasis role="bold">Expert
+            mode.</emphasis></emphasis> This display mode is designed
+            for more advanced users of &product-name;. All settings are
+            displayed on a single page, enabling quicker completion of
+            tasks.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+      <para>
+        Click the button at the bottom of the wizard window to switch
+        between Guided mode and Expert mode.
+      </para>
+
+    </sect2>
+
   </sect1>
 
-  <sect1 id="gui-createvm">
+  <sect1 id="create-vm-wizard">
 
     <title>Creating Your First Virtual Machine</title>
 
     <para>
-      Selecting <emphasis role="bold">New</emphasis> menu item from
-      <emphasis role="bold">Machine</emphasis> menu of the Manager Window
-      shows a wizard which guides you through setting up a new virtual
-      machine (VM).
+      Click <emphasis role="bold">New</emphasis> in the VirtualBox
+      Manager window. The <emphasis role="bold">Create Virtual
+      Machine</emphasis> wizard is shown, to guide you through the
+      required steps for setting up a new virtual machine (VM).
     </para>
 
-    <figure id="fig-new-vm-name">
-      <title>Creating a New Virtual Machine: Name and Operating System</title>
-    <mediaobject>
+    <para>
+      The <emphasis role="bold">Create Virtual Machine</emphasis> wizard
+      pages are described in the following sections.
+    </para>
+
+    <sect2 id="create-vm-wizard-name-os">
+
+      <title>Create Virtual Machine Wizard: Name and Operating System</title>
+
+      <figure id="fig-create-vm-name">
+        <title>Creating a Virtual Machine: Name and Operating System</title>
+      <mediaobject>
         <imageobject>
           <imagedata align="center" fileref="images/create-vm-1.png"
@@ -976 +1636 @@
         </imageobject>
       </mediaobject>
-    </figure>
-
-    <para>
-      On the following pages, the wizard will ask you for the bare
-      minimum of information that is needed to create a VM, in
-      particular:
-    </para>
-
-    <orderedlist>
-      <listitem>
-        <para>
-          The first page lets you specify name, location, and guest
-          operating system type. Additionally you can enable the unattended
-          guest operating system install feature (<xref linkend="gui-wizard-unattended"/>.).
-        </para>
-        <itemizedlist>
-          <listitem>
-            <para>
-              The <emphasis role="bold">Name</emphasis> of the VM you choose
-              is shown in the machine list of the VirtualBox Manager window
-              and is also used for the VM's files on disk.
-            </para>
-            <para>
-              Be sure to assign each VM an informative name that describes
-              the OS and software running on the VM. For example,
-              <literal>Windows 10 with Visio</literal>.
-            </para>
-          </listitem>
-          <listitem>
-            <para>
-              The <emphasis role="bold">Folder</emphasis> is the location
-              where VMs are stored on your computer. The default folder
-              location is shown.
-            </para>
-          </listitem>
-          <listitem>
-            <para>
-              The <emphasis role="bold">ISO Image</emphasis> is ISO file which
-              may be used to install the guest operating system or to be attached
-              to DVD drive of the new virtual machine. Note that selecting
-              an ISO image is optional. Please see the section <xref linkend="gui-wizard-unattended"/>.
-            </para>
-          </listitem>
-          <listitem>
-            <para>
-              For <emphasis role="bold">Type</emphasis>,
-              select the OS that you want to install. The supported OSes are
-              grouped. If you want to install something very unusual that is
-              not listed, select <emphasis role="bold">Other</emphasis>.
-              Depending on your selection, &product-name; will enable or
-              disable certain VM settings that your guest OS may require.
-              This is particularly important for 64-bit guests. See
-              <xref linkend="intro-64bitguests" />. It is therefore
-              recommended to always set it to the correct value. Also note
-              that if an ISO image is selected and &product-name; is able to detect
-              an operating system from that ISO, <emphasis role="bold">Type</emphasis>
-              and <emphasis role="bold">Version</emphasis> controls are populated
-              accordingly and disabled.
-            </para>
-          </listitem>
-          <listitem>
-            <para>
-              The checkox <emphasis role="bold">Skip Unattended Installation</emphasis>
-              can be used to disable unattended guest OS installation even if an ISO
-              image is selected that supports unattended install. In that case the
-              selected ISO image is inserted DVD drive of the new virtual machine.
-            </para>
-          </listitem>
-        </itemizedlist>
-      </listitem>
-      <listitem>
-        <para>
-          If unattended install is enabled then the second page of the wizard
-          will show some controls which can be used to input values needed during
-          unattended installation. These include username, password, host name,
-          product key (only applies to some guest operating system type), etc.
-          If for some reason unattended install is not enabled, this page is
-          skipped.
-        </para>
-      </listitem>
-      <listitem>
-        <para>
-          On the next page, select the <emphasis role="bold">Base Memory
-          </emphasis> that &product-name; should allocate every
-          time the virtual machine is started. The amount of memory
-          given here will be taken away from your host machine and
-          presented to the guest OS, which will report this size as the
-          virtual computer's installed RAM. <emphasis role="bold">Processor(s)
-          </emphasis> control determines how many virtual processors are to be
-          assigned to new virtual machine.
-        </para>
-        <caution>
-          <para>
-            Choose this setting carefully. The memory you give to the VM
-            will not be available to your host OS while the VM is
-            running, so do not specify more than you can spare.
-            Also note that it is not advised to assign more than
-            half of the processor threads the host machine has.
-          </para>
-          <para>
-            For example, if your host machine has 4 GB of RAM and you
-            enter 2048 MB as the amount of RAM for a particular virtual
-            machine, you will only have 2 GB left for all the other
-            software on your host while the VM is running. If you run
-            two VMs at the same time, even more memory will be allocated
-            for the second VM, which may not even be able to start if
-            that memory is not available.
-          </para>
-          <para>
-            On the other hand, you should specify as much as your guest
-            OS and your applications will require to run properly. A
-            guest OS may require at least 1 or 2 GB of memory to install
-            and boot up. For best performance, more memory than that may
-            be required.
-          </para>
-        </caution>
-        <para>
-          Always ensure that the host OS has enough RAM remaining. If
-          insufficient RAM remains, the system might excessively swap
-          memory to the hard disk, which effectively brings the host
-          system to a standstill.
-        </para>
-        <para>
-          As with the other settings, you can change this setting later,
-          after you have created the VM.
-        </para>
-      </listitem>
-       <listitem>
-        <para>
-          Next, you must specify a <emphasis role="bold">Virtual Hard
-          Disk</emphasis> for your VM.
-        </para>
-        <para>
-          There are many and potentially complicated ways in which
-          &product-name; can provide hard disk space to a VM, see
-          <xref linkend="storage" />, but the most common way is to use
-          a large image file on your physical hard disk, whose contents
-          &product-name; presents to your VM as if it were a complete
-          hard disk. This file then represents an entire hard disk, so
-          you can even copy it to another host and use it with another
-          &product-name; installation.
-        </para>
-        <para>
-          The wizard displays the following page:
-        </para>
-        <figure id="fig-new-vm-hard-disk">
-          <title>Creating a New Virtual Machine: Hard Disk</title>
+      </figure>
+
+      <para>
+        Use this page to specify a name and operating system (OS) for
+        the virtual machine and to change the storage location used for
+        VMs.
+      </para>
+
+      <para>
+        You can also choose to disable the unattended guest operating
+        system install feature. See also
+        <xref linkend="create-vm-wizard-unattended-install"/>.
+      </para>
+
+      <para>
+        The following fields are available on this wizard page:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Name.</emphasis> A name for the new
+            VM. The name you enter is shown in the machine list of
+            &vbox-mgr; and is also used for the virtual machine's files
+            on disk.
+          </para>
+
+          <para>
+            Be sure to assign each VM an informative name that describes
+            the OS and software running on the VM. For example, a name
+            such as <literal>Windows 10 with Visio</literal>.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Folder.</emphasis> The location where
+            VMs are stored on your computer, called the
+            <emphasis>machine folder</emphasis>. The default folder
+            location is shown.
+          </para>
+
+          <para>
+            Ensure that the folder location has enough free space,
+            especially if you intend to use the snapshots feature. See
+            also <xref linkend="vboxconfigdata-machine-folder"/>.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">ISO Image.</emphasis> Select an ISO
+            image file. The image file can be used to install an OS on
+            the new virtual machine or it can be attached to a DVD drive
+            on the new virtual machine.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Type and Version.</emphasis> These
+            fields are used to select the OS that you want to install on
+            the new virtual machine.
+          </para>
+
+          <para>
+            The supported OSes are grouped into types. If you want to
+            install something very unusual that is not listed, select
+            the <emphasis role="bold">Other</emphasis> type. Depending
+            on your selection, &product-name; will enable or disable
+            certain VM settings that your guest OS may require. This is
+            particularly important for 64-bit guests. See
+            <xref linkend="intro-64bitguests" />. It is therefore
+            recommended to always set this field to the correct value.
+          </para>
+
+          <para>
+            If an ISO image is selected and &product-name; detects the
+            operating system for the ISO, the
+            <emphasis role="bold">Type</emphasis> and
+            <emphasis role="bold">Version</emphasis> fields are
+            populated automatically and are disabled.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Skip Unattended
+            Installation.</emphasis> Disables unattended guest OS
+            installation, even if an ISO image is selected that supports
+            unattended installation. In that case, the selected ISO
+            image is mounted automatically on the DVD drive of the new
+            virtual machine and user interaction is required to complete
+            the OS installation.
+          </para>
+
+          <para>
+            The unattended installation step in the wizard is skipped.
+          </para>
+
+          <note>
+            <para>
+              This option is disabled if you do not select an
+              installation medium in the <emphasis role="bold">ISO
+              Image</emphasis> field.
+            </para>
+          </note>
+        </listitem>
+
+      </itemizedlist>
+
+      <para>
+        Click <emphasis role="bold">Next</emphasis> to go to the next
+        wizard page.
+      </para>
+
+    </sect2>
+
+    <sect2 id="create-vm-wizard-unattended-install">
+
+      <title>(Optional) Create Virtual Machine Wizard: Unattended Guest OS Install</title>
+
+      <para>
+        Unattended guest OS installation enables you to install the OS
+        on a virtual machine automatically.
+      </para>
+
+      <note>
+        <para>
+          This page is optional. It is not displayed if you have
+          selected the <emphasis role="bold">Skip Unattended
+          Installation</emphasis> option on the initial wizard page.
+        </para>
+      </note>
+
+      <para>
+        Use this page to set up the required parameters for unattended
+        guest OS installation and to configure automatic installation of
+        the &product-name; Guest Additions. See also
+        <xref linkend="create-vm-wizard-unattended-examples"/> for some
+        typical scenarios when using automated installation.
+      </para>
+
+      <figure id="fig-create-vm-unattended-install">
+        <title>Creating a Virtual Machine: Unattended Guest OS Installation</title>
+      <mediaobject>
+        <imageobject>
+          <imagedata align="center" fileref="images/create-vm-2.png"
+                     width="10cm" />
+        </imageobject>
+      </mediaobject>
+      </figure>
+
+      <para>
+        The following fields are available on this wizard page:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Username and Password.</emphasis>
+            Enter the credentials for a default user on the guest OS.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Guest Additions.</emphasis> Enables
+            automatic installation of the Guest Additions, following
+            installation of the guest OS. Use the drop-down list to
+            select the location of the ISO image file for the Guest
+            Additions.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Additional Options.</emphasis> The
+            following options enable you to perform extra configuration
+            of the guest OS:
+          </para>
+
+          <itemizedlist>
+
+            <listitem>
+              <para>
+                <emphasis role="bold">Product Key.</emphasis> For
+                Windows guests only. Enter the product key required for
+                Windows installation.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                <emphasis role="bold">Hostname.</emphasis> Host name for
+                the guest. By default, this is the same as the VM name.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                <emphasis role="bold">Domain Name.</emphasis> Domain
+                name for the guest.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                <emphasis role="bold">Install in Background.</emphasis>
+                Enable headless mode for the VM, where a graphical user
+                interface is not shown.
+              </para>
+            </listitem>
+
+          </itemizedlist>
+        </listitem>
+
+      </itemizedlist>
+
+      <para>
+        Click <emphasis role="bold">Next</emphasis> to go to the next
+        wizard page.
+      </para>
+
+    </sect2>
+
+    <sect2 id="create-vm-wizard-hardware">
+
+      <title>Create Virtual Machine Wizard: Hardware</title>
+
+      <para>
+        Use this page to configure hardware settings for the virtual
+        machine.
+      </para>
+
+      <figure id="fig-create-vm-hardware">
+        <title>Creating a Virtual Machine: Hardware</title>
+       <mediaobject>
+        <imageobject>
+          <imagedata align="center" fileref="images/create-vm-3.png"
+                     width="10cm" />
+        </imageobject>
+      </mediaobject>
+      </figure>
+
+      <para>
+        The following fields are available on this wizard page:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Base Memory.</emphasis> Select the
+            amount of RAM that &product-name; should allocate every time
+            the virtual machine is started. The amount of memory
+            selected here will be taken away from your host machine and
+            presented to the guest OS, which will report this size as
+            the virtual machines installed RAM.
+          </para>
+
+          <caution>
+            <para>
+              Choose this setting carefully. The memory you give to the
+              VM will not be available to your host OS while the VM is
+              running, so do not specify more than you can spare.
+            </para>
+
+            <para>
+              For example, if your host machine has 4 GB of RAM and you
+              enter 2048 MB as the amount of RAM for a particular
+              virtual machine, you will only have 2 GB left for all the
+              other software on your host while the VM is running. If
+              you run two VMs at the same time, even more memory will be
+              allocated for the second VM, which may not even be able to
+              start if that memory is not available.
+            </para>
+
+            <para>
+              On the other hand, you should specify as much as your
+              guest OS and your applications will require to run
+              properly. A guest OS may require at least 1 or 2 GB of
+              memory to install and boot up. For best performance, more
+              memory than that may be required.
+            </para>
+          </caution>
+
+          <para>
+            Always ensure that the host OS has enough RAM remaining. If
+            insufficient RAM remains, the system might excessively swap
+            memory to the hard disk, which effectively brings the host
+            system to a standstill.
+          </para>
+
+          <para>
+            As with other <emphasis role="bold">Create Virtual
+            Machine</emphasis> wizard settings, you can change this
+            setting later, after you have created the VM.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Processor(s).</emphasis> Select the
+            number of virtual processors to assign to the VM.
+          </para>
+
+          <para>
+            It is not advised to assign more than half of the total
+            processor threads from the host machine.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Enable EFI.</emphasis> Enables
+            Extensible Firware Interface (EFI) booting for the guest OS.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+      <para>
+        Click <emphasis role="bold">Next</emphasis> to go to the next
+        wizard page.
+      </para>
+
+    </sect2>
+
+    <sect2 id="create-vm-wizard-virtual-hard-disk">
+
+      <title>Create Virtual Machine Wizard: Virtual Hard Disk</title>
+
+      <para>
+        Use this page to specify a virtual hard disk for the virtual
+        machine.
+      </para>
+
+      <para>
+        There are many ways in which &product-name; can provide hard
+        disk space to a VM, see <xref linkend="storage" />. The most
+        common way is to use a large image file on your physical hard
+        disk, whose contents &product-name; presents to your VM as if it
+        were a complete hard disk. This file then represents an entire
+        hard disk, so you can even copy it to another host and use it
+        with another &product-name; installation.
+      </para>
+
+      <figure id="fig-create-vm-hard-disk">
+        <title>Creating a New Virtual Machine: Virtual Hard Disk</title>
         <mediaobject>
             <imageobject>
-              <imagedata align="center" fileref="images/create-vm-2.png"
+              <imagedata align="center" fileref="images/create-vm-4.png"
                            width="10cm" />
             </imageobject>
           </mediaobject>
-        </figure>
-        <para>
-          At this screen, you have the following options:
-        </para>
-        <itemizedlist>
-        <listitem>
-          <para>
-            To create a new, empty virtual hard disk, please select
-            <emphasis role="bold">Create a Virtual Hard Disk Now</emphasis>.
-            This will create a new disk image file in the new virtual
-            machine's folder.
-          </para>
-          <para>
-            The checkbox <emphasis role="bold">Pre-allocate Full Size</emphasis>
-            is initially not checked. This results in having a so called
-            <emphasis role="bold">dynamically allocated file</emphasis>
-            which only grows in size when the guest actually
-            stores data on its virtual hard disk. Therefore, this file
-            is small initially. As the drive is filled with data, the
-            file grows to the specified size. When the mentioned checkbox
-            is checked then &product-name; creates a
-            <emphasis role="bold">fixed-size file</emphasis> which
-            immediately occupies the file specified, even if only a
-            fraction of that virtual hard disk space is actually in
-            use. While occupying much more space, a fixed-size file
-            incurs less overhead and is therefore slightly faster than
-            a dynamically allocated file.
-          </para>
-          <para>
-            For more details on the differences between
-            <emphasis role="bold">dynamically allocated file</emphasis> and
-            <emphasis role="bold">fixed-size file</emphasis> please  see
-            <xref linkend="vdidetails" />.
-          </para>
-          <para>
-            To prevent your physical hard disk (host OS) from filling up,
-            &product-name; limits the size of the image file. But the
-            image file must be large enough to hold the contents of the
-            guest OS and the applications you want to install. For a
-            Windows or Linux guest, you will probably need several
-            gigabytes for any serious use. The limit of the image file
-            size can be changed later, see
-            <xref linkend="vboxmanage-modifymedium"/>.
-          </para>
-        </listitem>
-        <listitem>
-            <para>
-              You can pick an existing disk image
-              file by selecting <emphasis role="bold">Use
-              a Existing Virtual Hard Disk File </emphasis>.
-            </para>
-
-            <para>
-              The drop-down list presented in the window lists all disk
-              images which are currently remembered by &product-name;.
-              These disk images are currently attached to a virtual
-              machine, or have been attached to a virtual machine.
-            </para>
-
-            <para>
-              Alternatively, click on the small
-              <emphasis role="bold">folder icon</emphasis> next to the
-              drop-down list. In the displayed file dialog, you can
-              click <emphasis role="bold">Add</emphasis> to select any
-              disk image file on your host disk.
-            </para>
-          </listitem>
-          <listitem>
-            <para>
-              You can skip attaching a virtual hard disk file to the
-              new virtual machine you are creating. Note that you will
-              need to attach an hard disk later on in order to install a
-              guest operating system.
-            </para>
-          </listitem>
+      </figure>
+
+      <para>
+        The following fields are available on this wizard page:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Create a Virtual Hard Disk
+            Now</emphasis>. Creates a new empty virtual hard disk image,
+            located in the VM's machine folder.
+          </para>
+
+          <para>
+            Enter the following settings:
+          </para>
+
+          <itemizedlist>
+
+            <listitem>
+              <para>
+                <emphasis role="bold">Disk Size</emphasis>. Use the
+                slider to select a maximum size for the hard disk in the
+                new VM.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                <emphasis role="bold">Pre-Allocate Full Size.</emphasis>
+                This setting determines the type of image file used for
+                the disk image. Select this setting to use a
+                <emphasis>fixed-size file</emphasis> for the disk image.
+                Deselect this setting to use a <emphasis>dynamically
+                allocated file</emphasis> for the disk image.
+              </para>
+
+              <para>
+                The different types of image file behave as follows:
+              </para>
+
+              <itemizedlist>
+
+                <listitem>
+                  <para>
+                    <emphasis role="bold">Dynamically allocated
+                    file.</emphasis> This type of image file only grows
+                    in size when the guest actually stores data on its
+                    virtual hard disk. Therefore, this file is small
+                    initially. As the drive is filled with data, the
+                    file grows to the specified size.
+                  </para>
+                </listitem>
+
+                <listitem>
+                  <para>
+                    <emphasis role="bold">Fixed-size file.</emphasis>
+                    This type of image file immediately occupies the
+                    file specified, even if only a fraction of that
+                    virtual hard disk space is actually in use. While
+                    occupying much more space, a fixed-size file incurs
+                    less overhead and is therefore slightly faster than
+                    a dynamically allocated file.
+                  </para>
+                </listitem>
+
+              </itemizedlist>
+
+              <para>
+                For more details about the differences, see
+                <xref linkend="vdidetails" />.
+              </para>
+            </listitem>
+
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Use an Existing Hard Disk
+            File.</emphasis> Enables you to select an
+            <emphasis>existing</emphasis> disk image file to use with
+            the new VM.
+          </para>
+
+          <para>
+            The drop-down list presented in the window lists all disk
+            images which are known by &product-name;. These disk images
+            are currently attached to a virtual machine, or have been
+            attached to a virtual machine.
+          </para>
+
+          <para>
+            Alternatively, click on the small folder icon next to the
+            drop-down list. In the <emphasis role="bold">Hard Disk
+            Selector</emphasis> window that is displayed, click
+            <emphasis role="bold">Add</emphasis> to select a disk image
+            file on your host disk.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Do Not Add a Virtual Hard
+            Disk.</emphasis> The new VM is created without a hard disk.
+          </para>
+        </listitem>
+
       </itemizedlist>
-        <para>
-          If you are using &product-name; for the first time, you will
-          want to create a new disk image. Select
-          <emphasis role="bold">Create a Virtual Hard Disk Now</emphasis> button.
-        </para>
-        <para>
-          After having selected or created your image file, click
-          <emphasis role="bold">Next</emphasis> to go to the next page.
-        </para>
-      </listitem>
-      <listitem>
-        <para>The next page summarizes several attributes of the virtual
-        machine to be created. If you are not appy if any of them you
-        can use <emphasis role="bold">Back</emphasis> button to go
-        back to corresponding page to modify it.</para>
-        <para>
-          Alternatively you can click <emphasis role="bold">Finish</emphasis>,
-          to create your new virtual machine. The virtual machine is displayed
-          in the list on the left side of the VirtualBox Manager window, with
-          the name that you entered initially.
-        </para>
-      </listitem>
-    </orderedlist>
-    <note>
-      <para>
-        After becoming familiar with the use of wizards, consider using
-        the Expert Mode available in some wizards. Where available, this
-        is selectable using a button, and speeds up the process of using
-        wizards.
-      </para>
-    </note>
-    <sect2 id="gui-wizard-unattended">
-      <title>Unattended Install</title>
-      <para>
-        When supported by the selected ISO &product-name; attempts to install
-        the guest OS without any user input. When an ISO image is selected
-        &product-name; tries to determine type of the OS. If this succeeds and
-        if the selected OS is supported for the unattended install then the
-        newly created virtual machine is started after this wizard is closed
-        and OS install kicks off. Note that it is also possible to skip the
-        unattended install by ticking the checkbox "Skip unattended installation".
-        In this case the selected ISO is inserted to DVD drive of the new vm. The
-        guest OS will need to be installed manually. If OS cannot be determined
-        from the selected ISO or determined OS is not supported for the unattended
-        installation then again ISO is inserted to the DVD drive of the new virtual
-        machine and a manual guest OS install will be necessary.
-      </para>
+
+      <para>
+        To prevent your physical hard disk on the host OS from filling
+        up, &product-name; limits the size of the image file. But the
+        image file must be large enough to hold the contents of the
+        guest OS and the applications you want to install. For a Windows
+        or Linux guest, you will probably need several gigabytes for any
+        serious use. The limit of the image file size can be changed
+        later, see <xref linkend="vboxmanage-modifymedium"/>.
+      </para>
+
+      <note>
+        <para>
+          You can skip attaching a virtual hard disk file to the new
+          virtual machine you are creating. But you will then need to
+          attach an hard disk later on, in order to install a guest
+          operating system.
+        </para>
+      </note>
+
+      <para>
+        After having selected or created your image file, click
+        <emphasis role="bold">Next</emphasis> to go to the next wizard
+        page.
+      </para>
+
     </sect2>
+
+    <sect2 id="create-vm-wizard-summary">
+
+      <title>Create Virtual Machine Wizard: Summary</title>
+
+      <para>
+        This page displays a summary of the configuration for the
+        virtual machine.
+      </para>
+
+      <para>
+        If you are not happy with any of the settings, use the
+        <emphasis role="bold">Back</emphasis> button to return to the
+        corresponding page and modify the setting.
+      </para>
+
+      <para>
+        Click <emphasis role="bold">Finish</emphasis> to create your new
+        virtual machine. The virtual machine is displayed in the machine
+        list on the left side of the &vbox-mgr; window, with the name
+        that you entered on the first page of the wizard.
+      </para>
+
+    </sect2>
+
+    <sect2 id="create-vm-wizard-unattended-examples">
+
+      <title>Some Examples of Unattended Installation</title>
+
+      <para>
+        To configure unattended installation, you typically just need to
+        specify an ISO image in the <emphasis role="bold">Create Virtual
+        Machine</emphasis> wizard. &product-name; then detects the OS
+        type and the unattended installation process is done
+        automatically when the wizard is completed. However, in some
+        situations the installation may need be completed manually.
+      </para>
+
+      <para>
+        The following list describes some common scenarios for
+        unattended installation:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">OS type is detected
+            automatically.</emphasis> The following outcomes are
+            possible:
+          </para>
+
+          <itemizedlist>
+
+            <listitem>
+              <para>
+                If unattended installation is supported for the selected
+                ISO, the guest OS is installed automatically. No user
+                input is required.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                If unattended installation is not supported for the
+                selected ISO, the ISO image is inserted automatically
+                into the DVD drive of the new VM. The guest OS
+                installation must then be completed manually.
+              </para>
+            </listitem>
+
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">OS type is not detected
+            automatically.</emphasis> You must configure
+            <emphasis role="bold">Type</emphasis> and
+            <emphasis role="bold">Version</emphasis> settings in the
+            wizard.
+          </para>
+
+          <para>
+            The ISO image is inserted automatically into the DVD drive
+            of the new VM. The guest OS installation must then be
+            completed manually.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Unattended Installation is
+            disabled.</emphasis> Users can disable unattended
+            installation, by selecting the <emphasis role="bold">Skip
+            Unattended Installation</emphasis> check box on the initial
+            wizard page.
+          </para>
+
+          <para>
+            The ISO image is inserted automatically into the DVD drive
+            of the new VM. The guest OS installation must then be
+            completed manually.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+      <para>
+        See also <xref linkend="basic-unattended"/> for details of how
+        to perform unattended installation from the command line.
+      </para>
+
+    </sect2>
+
   </sect1>
 
@@ -1260 +2254 @@
 
     <para>
-      To start a virtual machine, you have several options:
+      To start a virtual machine, you have the following options:
     </para>
 
@@ -1267 +2261 @@
       <listitem>
         <para>
-          Double-click on the VM's entry in the list in the VirtualBox
-          Manager window.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          Select the VM's entry in the list in the VirtualBox Manager
-          window, and click <emphasis role="bold">Start</emphasis> at
+          Double-click on the VM's entry in the machine list in
+          &vbox-mgr;.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Select the VM's entry in the machine list in &vbox-mgr;, and
+          click <emphasis role="bold">Start</emphasis> in the toolbar
           the top of the window.
         </para>
@@ -1296 +2290 @@
       machine which you selected will boot up. Everything which would
       normally be seen on the virtual system's monitor is shown in the
-      window. See the screenshot image in
-      <xref linkend="Introduction"/>.
+      window. See <xref linkend="fig-win2016-intro"/>.
     </para>
 
     <para>
       In general, you can use the virtual machine as you would use a
-      real computer. There are couple of points worth mentioning
-      however.
+      real computer. The following topics describe a few points to note
+      when running a VM.
     </para>
 
@@ -1311 +2304 @@
 
       <para>
-        When a VM is started for the first time, the
-        <emphasis role="bold">First Start Wizard</emphasis>, is
-        displayed. This wizard helps you to select an installation
-        medium. Since the VM is created empty, it would otherwise behave
-        just like a real computer with no OS installed. It will do
-        nothing and display an error message that no bootable OS was
-        found.
-      </para>
-
-      <para>
-        For this reason, the wizard helps you to select a medium to
-        install an OS from.
-      </para>
-
-      <itemizedlist>
-
-        <listitem>
-          <para>
-            If you have physical CD or DVD media from which you want to
-            install your guest OS, such as a Windows installation CD or
-            DVD, put the media into your host's CD or DVD drive.
-          </para>
-
-          <para>
-            In the wizard's drop-down list of installation media, select
-            <emphasis role="bold">Host Drive</emphasis> with the correct
-            drive letter. In the case of a Linux host, choose a device
-            file. This will allow your VM to access the media in your
-            host drive, and you can proceed to install from there.
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
-            If you have downloaded installation media from the Internet
-            in the form of an ISO image file such as with a Linux
-            distribution, you would normally burn this file to an empty
-            CD or DVD and proceed as described above. With
-            &product-name; however, you can skip this step and mount the
-            ISO file directly. &product-name; will then present this
-            file as a CD or DVD-ROM drive to the virtual machine, much
-            like it does with virtual hard disk images.
-          </para>
-
-          <para>
-            In this case, the wizard's drop-down list contains a list of
-            installation media that were previously used with
-            &product-name;.
-          </para>
-
-          <para>
-            If your medium is not in the list, especially if you are
-            using &product-name; for the first time, click the small
-            folder icon next to the drop-down list to display a standard
-            file dialog. Here you can pick an image file on your host
-            disks.
-          </para>
-        </listitem>
-
-      </itemizedlist>
-
-      <para>
-        After completing the choices in the wizard, you will be able to
-        install your OS.
-      </para>
+        When you start a VM for the first time the OS installation
+        process is started automatically, using the ISO image file
+        specified in the <emphasis role="bold">Create Virtual
+        Machine</emphasis> wizard.
+      </para>
+
+      <para>
+        Follow the onscreen instructions to install your OS.
+      </para>
+
+<!--  <para>
+        If you have physical CD or DVD media from which you want to
+        install your guest OS, such as a Windows installation CD or DVD,
+        put the media into your host's CD or DVD drive.
+      </para>
+
+      <para>
+        If you have downloaded installation media from the Internet in
+        the form of an ISO image file such as with a Linux distribution,
+        you could burn this file to an empty CD or DVD and proceed as
+        described above. With &product-name; however, you can skip this
+        step and mount the ISO file directly. &product-name; will then
+        present this file as a CD or DVD-ROM drive to the virtual
+        machine, much like it does with virtual hard disk images.
+      </para>-->
 
     </sect2>
@@ -1404 +2357 @@
       <para>
         After installing a guest OS and before you install the Guest
-        Additions, described later, either your VM or the rest of your
-        computer can "own" the keyboard and the mouse. Both cannot own
-        the keyboard and mouse at the same time. You will see a
+        Additions, described in <xref linkend="guestadditions"/>, either
+        your VM or the rest of your computer can
+        <emphasis>own</emphasis> the keyboard and the mouse. Both cannot
+        own the keyboard and mouse at the same time. You will see a
         <emphasis>second</emphasis> mouse pointer which is always
         confined to the limits of the VM window. You activate the VM by
@@ -1418 +2372 @@
         <emphasis>right Ctrl key</emphasis> on your keyboard. On a Mac
         host, the default Host key is the left Command key. You can
-        change this default in the &product-name; Global Settings. See
-        <xref linkend="globalsettings" />. The current setting for the
-        Host key is always displayed at the bottom right of your VM
-        window.
+        change this default using the Preferences window. See
+        <xref linkend="preferences" />. The current setting for the Host
+        key is always displayed at the bottom right of your VM window.
       </para>
 
       <figure id="fig-host-key">
-        <title>Host Key Setting on the Virtual Machine Task Bar</title>
+        <title>Host Key Setting on the Virtual Machine Taskbar</title>
         <mediaobject>
           <imageobject>
@@ -1432 +2385 @@
           </imageobject>
         </mediaobject>
-
       </figure>
 
@@ -1525 +2477 @@
             For example, you cannot use the
             <emphasis role="bold">Ctrl+Alt+Delete</emphasis> combination
-            to reboot the guest OS in your VM because this key
-            combination is usually hard-wired into the host OS. So, even
-            though both the Windows and Linux OSes intercept this key
-            combination, only the host OS would be rebooted.
+            to reboot the guest OS in your VM, because this key
+            combination is reserved by the host OS. Even though both
+            Windows and Linux OSes can intercept this key combination,
+            the host OS is rebooted automatically.
           </para>
 
@@ -1662 +2614 @@
       <para>
         The settings are the same as those available for the VM in the
-        <emphasis role="bold">Settings</emphasis> dialog of the
-        &product-name; main window. But as the
-        <emphasis role="bold">Settings</emphasis> dialog is disabled
-        while the VM is in the Running or Saved state, the
+        <emphasis role="bold">Settings</emphasis> window of &vbox-mgr;.
+        But as the <emphasis role="bold">Settings</emphasis> window is
+        disabled while the VM is in the Running or Saved state, the
         <emphasis role="bold">Devices</emphasis> menu saves you from
         having to shut down and restart the VM every time you want to
@@ -1694 +2645 @@
       </para>
 
-      <orderedlist>
+      <itemizedlist>
 
         <listitem>
@@ -1754 +2705 @@
         </listitem>
 
-      </orderedlist>
+      </itemizedlist>
 
     </sect2>
@@ -1837 +2788 @@
             As an exception, if your virtual machine has any snapshots,
             see <xref linkend="snapshots"/>, you can use this option to
-            quickly <emphasis
-          role="bold">restore the current
+            quickly <emphasis role="bold">restore the current
             snapshot</emphasis> of the virtual machine. In that case,
-            powering off the machine will not disrupt its state, but any
-            changes made since that snapshot was taken will be lost.
+            powering off the machine will discard the current state and
+            any changes made since the previous snapshot was taken will
+            be lost.
           </para>
         </listitem>
@@ -1849 +2800 @@
       <para>
         The <emphasis role="bold">Discard</emphasis> button in the
-        VirtualBox Manager window discards a virtual machine's saved
-        state. This has the same effect as powering it off, and the same
-        warnings apply.
+        &vbox-mgr; window discards a virtual machine's saved state. This
+        has the same effect as powering it off, and the same warnings
+        apply.
       </para>
 
@@ -1863 +2814 @@
 
     <para>
-      VM groups enable the user to create ad hoc groups of VMs, and to
-      manage and perform functions on them collectively, as well as
-      individually.
+      VM groups are groups of VMs that you can create as and when
+      required. You can manage and perform functions on them
+      collectively, as well as individually.
     </para>
 
@@ -1881 +2832 @@
         </imageobject>
       </mediaobject>
-
     </figure>
 
@@ -1892 +2842 @@
       <listitem>
         <para>
-          Create a group using the VirtualBox Manager. Do one of the
-          following:
+          Create a group using &vbox-mgr;. Do one of the following:
         </para>
 
@@ -1900 +2849 @@
           <listitem>
             <para>
-              Drag one VM on top of another VM.
+              Drag a VM on top of another VM.
             </para>
           </listitem>
@@ -1931 +2880 @@
 
             <para>
-              This command creates a group "TestGroup" and attaches the
-              VM "vm01" to that group.
+              This command creates a group <literal>TestGroup</literal>
+              and attaches the VM <literal>vm01</literal> to that group.
             </para>
           </listitem>
@@ -1945 +2894 @@
 
             <para>
-              This command detaches all groups from the VM "vm01" and
-              deletes the empty group.
+              This command detaches all groups from the VM
+              <literal>vm01</literal> and deletes the empty group.
             </para>
           </listitem>
@@ -1961 +2910 @@
 
         <para>
-          This command creates the groups "TestGroup" and "TestGroup2",
-          if they do not exist, and attaches the VM "vm01" to both of
-          them.
+          This command creates the groups <literal>TestGroup</literal>
+          and <literal>TestGroup2</literal>, if they do not exist, and
+          attaches the VM <literal>vm01</literal> to both of them.
         </para>
       </listitem>
@@ -1975 +2924 @@
 
         <para>
-          This command attaches the VM "vm01" to the subgroup
-          "TestGroup2" of the "TestGroup" group.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          The following is a summary of group commands: Start, Pause,
-          Reset, Close (save state, send shutdown signal, poweroff),
-          Discard Saved State, Show in File System, Sort.
+          This command attaches the VM <literal>vm01</literal> to the
+          subgroup <literal>TestGroup2</literal> of the
+          <literal>TestGroup</literal> group.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Use &vbox-mgr; menu options to control and manage all the VMs
+          in a group. For example:
+          <emphasis role="bold">Start</emphasis>,
+          <emphasis role="bold">Pause</emphasis>,
+          <emphasis role="bold">Reset</emphasis>,
+          <emphasis role="bold">Close</emphasis> (save state, send
+          shutdown signal, poweroff), <emphasis role="bold">Discard
+          Saved State</emphasis>, <emphasis role="bold">Show in
+          Explorer</emphasis>, <emphasis role="bold">Sort</emphasis>.
         </para>
       </listitem>
@@ -2007 +2963 @@
     <para>
       To see the snapshots of a virtual machine, click on the machine
-      name in VirtualBox Manager. Then click the
-      <emphasis role="bold">List</emphasis> icon next to the machine
-      name, and select <emphasis role="bold">Snapshots</emphasis>. Until
-      you take a snapshot of the machine, the list of snapshots will be
-      empty except for the <emphasis role="bold">Current
-      State</emphasis> item, which represents the "now" point in the
-      lifetime of the virtual machine.
+      name in &vbox-mgr;. In the machine tools menu for the VM, click
+      <emphasis role="bold">Snapshots</emphasis>. The Snapshots tool is
+      displayed.
     </para>
 
+    <figure id="fig-snapshots-tool">
+      <title>Snapshots Tool, Showing Snapshot Properties</title>
+       <mediaobject>
+        <imageobject>
+          <imagedata align="center" fileref="images/snapshots-1.png"
+                   width="10cm" />
+        </imageobject>
+      </mediaobject>
+    </figure>
+
+    <para>
+      If you select multiple VMs in the machine list, all snapshots are
+      listed for each VM.
+    </para>
+
+    <para>
+      Until you take a snapshot of the virtual machine, the list of
+      snapshots will be empty, except for the
+      <emphasis role="bold">Current State</emphasis> item. This item
+      represents the current point in the lifetime of the virtual
+      machine.
+    </para>
+
+    <para>
+      The Snapshots window includes a toolbar, enabling you to perform
+      the following snapshot operations:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Take.</emphasis> Takes a snapshot of the
+          selected VM. See
+          <xref linkend="snapshots-take-restore-delete"/>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Delete.</emphasis> Removes a snapshot
+          from the list of snapshots. See
+          <xref linkend="snapshots-take-restore-delete"/>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Restore.</emphasis> Restores the VM
+          state to be the same as the selected snapshot. See
+          <xref linkend="snapshots-take-restore-delete"/>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Properties.</emphasis> Displays the
+          properties for the selected snapshot. The
+          <emphasis role="bold">Attributes</emphasis> tab is used to
+          specify a Name and Description for the snapshot. The
+          <emphasis role="bold">Information</emphasis> tab shows VM
+          settings for the snapshot.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Clone.</emphasis> Displays the
+          <emphasis role="bold">Clone Virtual Machine</emphasis> wizard.
+          This enables you to create a clone of the VM, based on the
+          selected snapshot.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Settings.</emphasis> Available for the
+          Current State snapshot only. Displays the
+          <emphasis role="bold">Settings</emphasis> window for the VM,
+          enabling you to make configuration changes.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Discard.</emphasis> For a running VM,
+          discards the saved state for the VM and closes it down.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Start.</emphasis> Start the VM. This
+          operation is available for the <emphasis role="bold">Current
+          State</emphasis> item.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
     <sect2 id="snapshots-take-restore-delete">
 
@@ -2028 +3080 @@
         <listitem>
           <para>
-            <emphasis role="bold">Take a snapshot</emphasis>. This makes
+            <emphasis role="bold">Take a snapshot.</emphasis> This makes
             a copy of the machine's current state, to which you can go
             back at any given time later.
@@ -2037 +3089 @@
             <listitem>
               <para>
-                If your VM is running, select <emphasis role="bold">Take
-                Snapshot</emphasis> from the
-                <emphasis role="bold">Machine</emphasis> pull-down menu
-                of the VM window.
+                If your VM is running:
+              </para>
+
+              <para>
+                Select <emphasis role="bold">Take Snapshot</emphasis>
+                from the <emphasis role="bold">Machine</emphasis> menu
+                in the VM window.
+              </para>
+
+              <para>
+                The VM is paused while the snapshot is being created.
+                After snapshot creation, the VM continues to run as
+                normal.
               </para>
             </listitem>
@@ -2047 +3108 @@
               <para>
                 If your VM is in either the Saved or the Powered Off
-                state, as displayed next to the VM name in the
-                &product-name; main window, click the
-                <emphasis role="bold">List</emphasis> icon next to the
-                machine name and select
-                <emphasis role="bold">Snapshots</emphasis>. The
-                snapshots window is shown. Do one of the following:
+                state, as displayed next to the VM name in the machine
+                list:
+              </para>
+
+              <para>
+                Display the Snapshots window and do one of the
+                following:
               </para>
 
@@ -2059 +3121 @@
                 <listitem>
                   <para>
-                    Click the <emphasis role="bold">Take</emphasis>
-                    icon.
+                    Click <emphasis role="bold">Take</emphasis> in the
+                    Snapshots window toolbar.
                   </para>
                 </listitem>
@@ -2078 +3140 @@
 
           <para>
-            In either case, a window is displayed prompting you for a
-            snapshot name. This name is purely for reference purposes to
-            help you remember the state of the snapshot. For example, a
-            useful name would be "Fresh installation from scratch, no
-            Guest Additions", or "Service Pack 3 just installed". You
-            can also add a longer text in the
-            <emphasis role="bold">Description</emphasis> field.
+            A dialog is displayed, prompting you for a snapshot name.
+            This name is purely for reference purposes, to help you
+            remember the state of the snapshot. For example, a useful
+            name would be "Fresh installation from scratch, no Guest
+            Additions", or "Service Pack 3 just installed". You can also
+            add a longer text description in the
+            <emphasis role="bold">Snapshot Description</emphasis> field.
           </para>
 
@@ -2100 +3162 @@
           <figure id="fig-snapshots-list">
             <title>Snapshots List For a Virtual Machine</title>
-           <mediaobject>
+            <mediaobject>
               <imageobject>
-                <imagedata align="center" fileref="images/snapshots-1.png"
+                <imagedata align="center" fileref="images/snapshots-2.png"
                              width="10cm" />
               </imageobject>
@@ -2120 +3182 @@
         <listitem>
           <para>
-            <emphasis role="bold">Restore a snapshot</emphasis>. In the
-            list of snapshots, right-click on any snapshot you have
-            taken and select <emphasis role="bold">Restore</emphasis>.
-            By restoring a snapshot, you go back or forward in time. The
-            current state of the machine is lost, and the machine is
-            restored to the exact state it was in when the snapshot was
-            taken.
+            <emphasis role="bold">Restore a snapshot.</emphasis> In the
+            Snapshots window, select the snapshot you have taken and
+            click <emphasis role="bold">Restore</emphasis> in the
+            toolbar. By restoring a snapshot, you go back or forward in
+            time. The current state of the machine is lost, and the
+            machine is restored to the exact state it was in when the
+            snapshot was taken.
           </para>
 
@@ -2158 +3220 @@
             alternate reality and to switch between these different
             histories of the virtual machine. This can result in a whole
-            tree of virtual machine snapshots, as shown in the
-            screenshot above.
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
-            <emphasis role="bold">Delete a snapshot</emphasis>. This
+            tree of virtual machine snapshots.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Delete a snapshot.</emphasis> This
             does not affect the state of the virtual machine, but only
             releases the files on disk that &product-name; used to store
             the snapshot data, thus freeing disk space. To delete a
-            snapshot, right-click on the snapshot name in the snapshots
-            tree and select <emphasis role="bold">Delete</emphasis>.
-            Snapshots can be deleted even while a machine is running.
+            snapshot, select the snapshot name in the Snapshots window
+            and click <emphasis role="bold">Delete</emphasis> in the
+            toolbar. Snapshots can be deleted even while a machine is
+            running.
           </para>
 
@@ -2306 +3368 @@
         The <emphasis role="bold">Settings</emphasis> button is disabled
         while a VM is either in the Running or Saved state. This is
-        because the <emphasis role="bold">Settings</emphasis> dialog
+        because the <emphasis role="bold">Settings</emphasis> window
         enables you to change fundamental characteristics of the virtual
         machine that is created for your guest OS. For example, the
@@ -2343 +3405 @@
         <para>
           <emphasis role="bold">Removing a VM.</emphasis> To remove a
-          VM, right-click on the VM in the VirtualBox Manager's machine
-          list and select <emphasis role="bold">Remove</emphasis>.
+          VM, right-click on the VM in the &vbox-mgr; machine list and
+          select <emphasis role="bold">Remove</emphasis>.
         </para>
 
@@ -2363 +3425 @@
           <emphasis role="bold">Moving a VM.</emphasis> To move a VM to
           a new location on the host, right-click on the VM in the
-          VirtualBox Manager's machine list and select
-          <emphasis
-          role="bold">Move</emphasis>.
+          &vbox-mgr;'s machine list and select
+          <emphasis role="bold">Move</emphasis>.
         </para>
 
@@ -2393 +3454 @@
     <para>
       For information about removing or moving a disk image file from
-      &product-name;, see <xref linkend="vdis"/>.
+      &product-name;, see <xref linkend="virtual-media-manager"/>.
     </para>
 
@@ -2414 +3475 @@
     </para>
 
-    <figure id="fig-clone-wizard">
-      <title>The Clone Virtual Machine Wizard</title>
+    <para>
+      You can start the Clone Virtual Machine wizard in one of the
+      following ways:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          Click the VM name in the machine list and then select
+          <emphasis role="bold">Clone</emphasis> from the
+          <emphasis role="bold">Machine</emphasis> menu.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Click <emphasis role="bold">Clone</emphasis> in the
+          <emphasis role="bold">Snapshots</emphasis> window for the
+          selected VM.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+    <note>
+      <para>
+        The <emphasis role="bold">Clone</emphasis> menu item is disabled
+        while a virtual machine is running.
+      </para>
+    </note>
+
+    <para>
+      The <emphasis role="bold">New Machine Name and Path</emphasis>
+      page is displayed.
+    </para>
+
+    <figure id="fig-clone-wizard-name-path">
+      <title>Clone Virtual Machine Wizard: New Machine Name and Path</title>
       <mediaobject>
         <imageobject>
-          <imagedata align="center" fileref="images/clone-vm.png"
+          <imagedata align="center" fileref="images/clone-vm-1.png"
                    width="10cm" />
         </imageobject>
@@ -2425 +3523 @@
 
     <para>
-      Start the wizard by clicking
-      <emphasis role="bold">Clone</emphasis> in the right-click menu of
-      the VirtualBox Manager's machine list or in the
-      <emphasis role="bold">Snapshots</emphasis> view of the selected
-      VM.
-    </para>
-
-    <para>
-      Specify a new <emphasis role="bold">Name</emphasis> for the clone.
-      You can choose a <emphasis role="bold">Path</emphasis> for the
-      cloned virtual machine, otherwise &product-name; uses the default
-      machines folder.
-    </para>
-
-    <para>
-      The <emphasis role="bold">Clone Type</emphasis> option specifies
-      whether to create a clone linked to the source VM or to create a
-      fully independent clone:
-    </para>
-
-    <itemizedlist>
-
-      <listitem>
-        <para>
-          <emphasis role="bold">Full Clone:</emphasis> Copies all
-          dependent disk images to the new VM folder. A full clone can
-          operate fully without the source VM.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          <emphasis role="bold">Linked Clone:</emphasis> Creates new
-          differencing disk images based on the source VM disk images.
-          If you select the current state of the source VM as the clone
-          point, &product-name; creates a new snapshot.
-        </para>
-      </listitem>
-
-    </itemizedlist>
-
-    <para>
-      The <emphasis role="bold">Snapshots</emphasis> option specifies
-      whether to create a clone of the current machine state only or of
-      everything.
-    </para>
-
-    <itemizedlist>
-
-      <listitem>
-        <para>
-          <emphasis role="bold">Everything:</emphasis> Clones the
-          current machine state and all its snapshots.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          <emphasis role="bold">Current Machine State and All
-          Children:</emphasis>. Clones a VM snapshot and all its child
-          snapshots.
-        </para>
-      </listitem>
-
-    </itemizedlist>
-
-    <para>
       The following clone options are available:
     </para>
@@ -2499 +3530 @@
       <listitem>
         <para>
+          <emphasis role="bold">Name:</emphasis> A name for the cloned
+          machine.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Path:</emphasis> Choose a location for
+          the cloned virtual machine, otherwise &product-name; uses the
+          default machines folder.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           <emphasis role="bold">MAC Address Policy:</emphasis> Specifies
-          how to retain network card MAC addresses when cloning the VM.
+          whether to retain network card MAC addresses when cloning the
+          VM.
         </para>
 
@@ -2532 +3579 @@
 
     <para>
+      Click <emphasis role="bold">Next</emphasis>. The
+      <emphasis role="bold">Clone Type</emphasis> page is displayed.
+    </para>
+
+    <figure id="fig-clone-wizard-clone-type">
+      <title>Clone Virtual Machine Wizard: Clone Type</title>
+      <mediaobject>
+        <imageobject>
+          <imagedata align="center" fileref="images/clone-vm-2.png"
+                   width="10cm" />
+        </imageobject>
+      </mediaobject>
+    </figure>
+
+    <para>
+      The <emphasis role="bold">Clone Type</emphasis> option specifies
+      whether to create a clone that is linked to the source VM or to
+      create a fully independent clone:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Full Clone:</emphasis> Copies all
+          dependent disk images to the new VM folder. A full clone can
+          operate fully without the source VM.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Linked Clone:</emphasis> Creates new
+          differencing disk images based on the source VM disk images.
+          If you select the current state of the source VM as the clone
+          point, &product-name; creates a new snapshot.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+    <para>
+      (Optional) Click <emphasis role="bold">Next</emphasis>. The
+      <emphasis role="bold">Snapshots</emphasis> page is displayed.
+    </para>
+
+    <note>
+      <para>
+        The Snapshots page is only displayed for machines that have
+        snapshots and the selected clone type is
+        <emphasis role="bold">Full Clone</emphasis>.
+      </para>
+    </note>
+
+    <figure id="fig-clone-wizard-snapshots">
+      <title>Clone Virtual Machine Wizard: Snapshots</title>
+        <mediaobject>
+        <imageobject>
+          <imagedata align="center" fileref="images/clone-vm-3.png"
+                   width="10cm" />
+        </imageobject>
+      </mediaobject>
+    </figure>
+
+    <para>
+      You use this page to select which parts of the snapshot tree to
+      include in the clone. The available options are as follows:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Current Machine State:</emphasis> Clones
+          the current state of the VM. Snapshots are not included.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Everything:</emphasis> Clones the
+          current machine state and all its snapshots.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+    <para>
+      Click <emphasis role="bold">Finish</emphasis> to start the clone
+      operation.
+    </para>
+
+    <para>
       The duration of the clone operation depends on the size and number
       of attached disk images. In addition, the clone operation saves
@@ -2538 +3678 @@
 
     <para>
-      Note that the <emphasis role="bold">Clone</emphasis> menu item is
-      disabled while a machine is running.
-    </para>
-
-    <para>
       You can also use the <command>VBoxManage clonevm</command> command
       to clone a VM. See <xref linkend="vboxmanage-clonevm" />.
@@ -2587 +3722 @@
         virtual machines that can then be imported into a hypervisor
         such as &product-name;. &product-name; makes OVF import and
-        export easy to do, using the VirtualBox Manager window or the
-        command-line interface.
+        export easy to do, using &vbox-mgr; or the command-line
+        interface.
       </para>
 
@@ -2674 +3809 @@
             for any OVF and OVA files on your host OS.
           </para>
-        </listitem>
-
-        <listitem>
-          <para>
-            Select <emphasis role="bold">File</emphasis>,
-            <emphasis role="bold">Import Appliance</emphasis> from the
-            VirtualBox Manager window.
-          </para>
-
-          <para>
-            From the file dialog, go to the file with either the
-            <filename>.ovf</filename> or the <filename>.ova</filename>
-            file extension.
-          </para>
-
-          <para>
-            Click <emphasis role="bold">Import</emphasis> to open the
-            <emphasis role="bold">Appliance Settings</emphasis> screen.
+
+          <para>
+            The <emphasis role="bold">Appliance Settings</emphasis> page
+            of the <emphasis role="bold">Import Virtual
+            Appliance</emphasis> wizard is shown.
           </para>
 
           <figure id="fig-import-appliance">
-            <title>Appliance Settings Screen for Import Appliance</title>
+            <title>Import Virtual Appliance Wizard: Appliance Settings</title>
             <mediaobject>
               <imageobject>
@@ -2702 +3824 @@
               </imageobject>
             </mediaobject>
-
           </figure>
-
-          <para>
-            This screen shows the VMs described in the OVF or OVA file
-            and enables you to change the VM settings.
+        </listitem>
+
+        <listitem>
+          <para>
+            The <emphasis role="bold">Appliance Settings</emphasis> page
+            shows the VMs described in the OVF or OVA file and enables
+            you to change the VM settings.
           </para>
 
@@ -2714 +3838 @@
             for VMs that were initially exported from &product-name;.
             You can change this behavior by using the
-            <emphasis
-            role="bold">Primary Group</emphasis>
-            setting for the VM.
+            <emphasis role="bold">Primary Group</emphasis> setting for
+            the VM.
           </para>
 
@@ -2764 +3887 @@
         <listitem>
           <para>
-            Click <emphasis role="bold">Import</emphasis> to import the
+            Click <emphasis role="bold">Finish</emphasis> to import the
             appliance.
           </para>
@@ -2771 +3894 @@
             &product-name; copies the disk images and creates local VMs
             with the settings described on the
-            <emphasis role="bold">Appliance Settings</emphasis> screen.
+            <emphasis role="bold">Appliance Settings</emphasis> page.
             The imported VMs are shown in the list of VMs in VirtualBox
             Manager.
@@ -2808 +3931 @@
           <para>
             Select <emphasis role="bold">File</emphasis>,
-            <emphasis role="bold"> Export Appliance</emphasis> to open
-            the <emphasis role="bold">Export Virtual
+            <emphasis role="bold"> Export Appliance</emphasis> to
+            display the <emphasis role="bold">Export Virtual
             Appliance</emphasis> wizard.
           </para>
 
           <para>
-            From the initial window, you can combine several VMs into an
-            OVF appliance.
+            On the initial <emphasis role="bold">Virtual
+            Machines</emphasis> page, you can combine several VMs into
+            an OVF appliance.
           </para>
 
@@ -2826 +3950 @@
         <listitem>
           <para>
-            The <emphasis role="bold">Appliance Settings</emphasis>
-            screen enables you to select the following settings:
+            The <emphasis role="bold">Format Settings</emphasis> page
+            enables you to configure the following settings:
           </para>
 
@@ -2883 +4007 @@
           <para>
             Click <emphasis role="bold">Next</emphasis> to show the
-            <emphasis role="bold">Virtual System Settings</emphasis>
-            screen.
+            <emphasis role="bold">Appliance Settings</emphasis> page.
           </para>
 
@@ -2901 +4024 @@
         <listitem>
           <para>
-            Click <emphasis role="bold">Export</emphasis> to begin the
+            Click <emphasis role="bold">Finish</emphasis> to begin the
             export process. Note that this operation might take several
             minutes.
@@ -3144 +4267 @@
           <figure id="fig-upload-key-oci">
             <title>Upload Public Key Dialog in &oci; Console</title>
-            <mediaobject>
+           <mediaobject>
               <imageobject>
                 <imagedata align="center" fileref="images/upload-key.png"
@@ -3150 +4273 @@
               </imageobject>
             </mediaobject>
-
           </figure>
 
@@ -3222 +4344 @@
           <para>
             <emphasis role="bold">(Optional) Passphrase for the private
-            key.</emphasis>. This is only required if the key is
+            key.</emphasis> This is only required if the key is
             encrypted.
           </para>
@@ -3291 +4413 @@
 
           <para>
-            The Cloud Profile Manager is a component of &product-name;
-            that enables you to create, edit, and manage cloud profiles
-            for your cloud service accounts.
+            The Cloud Profile Manager is a &vbox-mgr; tool that enables
+            you to create, edit, and manage cloud profiles for your
+            cloud service accounts.
           </para>
         </listitem>
@@ -3352 +4474 @@
         To open the Cloud Profile Manager click
         <emphasis role="bold">File</emphasis>,
-        <emphasis role="bold">Cloud Profile Manager</emphasis> in the
-        VirtualBox Manager window.
+        <emphasis role="bold">Cloud Profile Manager</emphasis> in
+        &vbox-mgr;.
       </para>
 
@@ -3463 +4585 @@
         <listitem>
           <para>
+            (Optional) If you are using the cloud profile to connect to
+            cloud virtual machines, select the
+            <emphasis role="bold">Show VMs</emphasis> check box.
+          </para>
+
+          <para>
+            This creates a new subgroup of the
+            <emphasis role="bold">OCI</emphasis> group in &vbox-mgr;.
+            See <xref linkend="cloud-vm-oci-group"/>.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
             Click <emphasis role="bold">Apply</emphasis> to save your
             changes.
@@ -3468 +4604 @@
 
           <para>
-            The cloud profile settings are saved in the
+            The cloud profile settings are saved to the
             <filename>oci_config</filename> file in your &product-name;
             global settings directory.
@@ -3553 +4689 @@
         <listitem>
           <para>
+            Create, add, and manage &oci; cloud instances using
+            &vbox-mgr;. See <xref linkend="cloud-vm"/>.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
             Export an &product-name; VM to &oci;. See
             <xref linkend="cloud-export-oci"/>.
@@ -3567 +4710 @@
         <listitem>
           <para>
-            Create a new cloud instance from a custom image stored on
-            &oci;. See <xref linkend="cloud-new-vm"/>.
+            Connect from a local VM to an &oci; cloud subnet. See
+            <xref linkend="cloud-using-cloud-networks"/>.
           </para>
         </listitem>
@@ -3581 +4724 @@
 
       </itemizedlist>
+
+    </sect2>
+
+    <sect2 id="cloud-vm">
+
+      <title>Using Cloud Virtual Machines</title>
+
+      <para>
+        A cloud virtual machine (<emphasis>cloud VM</emphasis>) is a
+        type of VM that represents an instance on a cloud service. Cloud
+        VMs are shown in the machine list in &vbox-mgr;, in the same way
+        as local VMs are.
+      </para>
+
+      <para>
+        By using cloud VMs you can create, manage, and control your
+        &oci; instances from &vbox-mgr;.
+      </para>
+
+      <note>
+        <para>
+          Cloud VMs do not install, export, or import instances to the
+          &product-name; host. All operations are done remotely on the
+          cloud service.
+        </para>
+      </note>
+
+      <figure id="fig-cloud-vm-overview">
+        <title>Cloud VMs, Shown in &vbox-mgr;</title>
+       <mediaobject>
+          <imageobject>
+            <imagedata align="center" fileref="images/cloudvm-overview.png"
+              width="12cm" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+
+      <para>
+        Cloud VMs can be used to do the following tasks in &oci;:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Create a new &oci;
+            instance.</emphasis> See <xref linkend="cloud-vm-new"/>.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold"> Use an existing &oci;
+            instance.</emphasis> See <xref linkend="cloud-vm-add"/>.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Configure an &oci;
+            instance.</emphasis> You can change settings for the
+            instance, such as display name and shape. See
+            <xref linkend="cloud-vm-settings"/>.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Control an &oci; instance.</emphasis>
+            Stop, start, and terminate the instance. See
+            <xref linkend="cloud-vm-control"/>
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Create a console connection to an
+            &oci; instance</emphasis>. See
+            <xref linkend="cloud-vm-instance-console"/>.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+      <sect3 id="cloud-vm-oci-group">
+
+        <title>About the OCI VM Group</title>
+
+        <para>
+          All cloud VMs are shown in the machine list in &vbox-mgr;, in
+          a special VM group called
+          <emphasis role="bold">OCI</emphasis>.
+        </para>
+
+        <para>
+          Cloud VMs are further grouped according to the cloud profile
+          used to connect to them. The cloud profile identifies the user
+          and compartment for the cloud VM and includes details of the
+          key pair used to connect to cloud instances. See
+          <xref linkend="cloud-create-cloud-profile"/>.
+        </para>
+
+        <figure id="fig-cloud-vm-oci-group">
+          <title>OCI Group, Containing Cloud VMs</title>
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" fileref="images/cloudvm-oci-group.png"
+              width="10cm" />
+          </imageobject>
+        </mediaobject>
+       </figure>
+
+        <para>
+          All cloud profiles registered with &product-name; are listed
+          automatically in the OCI group.
+        </para>
+
+        <para>
+          To enable or disable listing of cloud VMs in &vbox-mgr; for a
+          specific cloud profile, do the following:
+        </para>
+
+        <para>
+          Display the <emphasis role="bold">Cloud Profile
+          Manager</emphasis> and select or deselect the
+          <emphasis role="bold">List VMs</emphasis> check box for each
+          cloud profile.
+        </para>
+
+      </sect3>
+
+      <sect3 id="cloud-vm-new">
+
+        <title>Creating a New Cloud VM</title>
+
+        <para>
+          When you create a new cloud VM, a <emphasis>new</emphasis>
+          &oci; instance is created and associated with the cloud VM.
+        </para>
+
+        <para>
+          Perform the following steps to create a new cloud VM:
+        </para>
+
+        <orderedlist>
+
+          <listitem>
+            <para>
+              Click on a cloud profile in the
+              <emphasis role="bold">OCI</emphasis> group.
+            </para>
+
+            <para>
+              The cloud VMs for the selected cloud profile are
+              displayed.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              Select <emphasis role="bold">Group</emphasis>,
+              <emphasis role="bold">New Machine</emphasis>.
+            </para>
+
+            <para>
+              The <emphasis role="bold">Create Cloud Virtual
+              Machine</emphasis> wizard is displayed.
+            </para>
+
+            <figure id="fig-cloudvm-new">
+              <title>Create Cloud Virtual Machine Wizard</title>
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" fileref="images/cloudvm-new.png"
+              width="12cm" />
+          </imageobject>
+        </mediaobject>
+            </figure>
+          </listitem>
+
+          <listitem>
+            <para>
+              On the initial page, configure the following settings for
+              the new cloud VM:
+            </para>
+
+            <itemizedlist>
+
+              <listitem>
+                <para>
+                  <emphasis role="bold">Location:</emphasis> The cloud
+                  service provider that will host the new instance.
+                  Select <emphasis role="bold">&oci;</emphasis>.
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <emphasis role="bold">Profile:</emphasis> The cloud
+                  profile used to connect to the new instance. Select
+                  from the available cloud profiles.
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <emphasis role="bold">Source:</emphasis> The image
+                  that the new instance is based on. Choose from the
+                  available images and boot volumes.
+                </para>
+              </listitem>
+
+            </itemizedlist>
+          </listitem>
+
+          <listitem>
+            <para>
+              Click <emphasis role="bold">Next</emphasis> to display the
+              <emphasis role="bold">Cloud Virtual Machine
+              Settings</emphasis> page.
+            </para>
+
+            <para>
+              You can use this page to change the default settings for
+              the new &oci; instance, such as the display name, shape,
+              and networking configuration.
+            </para>
+
+            <para>
+              To add an SSH key to the instance, click the
+              <emphasis role="bold">SSH Authorised Keys</emphasis> field
+              and paste the public key into the displayed dialog.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              Click <emphasis role="bold">Finish</emphasis> to create a
+              new &oci; instance using the selected image or boot
+              volume. The new instance is started automatically.
+            </para>
+
+            <para>
+              The new cloud VM is shown in the
+              <emphasis role="bold">OCI</emphasis> group in &vbox-mgr;.
+            </para>
+          </listitem>
+
+        </orderedlist>
+
+      </sect3>
+
+      <sect3 id="cloud-vm-add">
+
+        <title>Adding a Cloud VM</title>
+
+        <para>
+          When you add a cloud VM, an <emphasis>existing</emphasis>
+          &oci; instance is associated with the cloud VM. You can only
+          add one cloud VM for each instance.
+        </para>
+
+        <para>
+          Perform the following steps to add a cloud VM:
+        </para>
+
+        <orderedlist>
+
+          <listitem>
+            <para>
+              Click on a cloud profile in the
+              <emphasis role="bold">OCI</emphasis> group.
+            </para>
+
+            <para>
+              The cloud VMs for the selected cloud profile are
+              displayed.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              Select <emphasis role="bold">Group</emphasis>,
+              <emphasis role="bold">Add Machine</emphasis>.
+            </para>
+
+            <para>
+              The <emphasis role="bold">Add Cloud Virtual
+              Machine</emphasis> wizard is displayed.
+            </para>
+
+            <figure id="fig-cloudvm-add">
+              <title>Add Cloud Virtual Machine Wizard</title>
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" fileref="images/cloudvm-add.png"
+              width="12cm" />
+          </imageobject>
+        </mediaobject>
+            </figure>
+          </listitem>
+
+          <listitem>
+            <para>
+              Configure the following settings:
+            </para>
+
+            <itemizedlist>
+
+              <listitem>
+                <para>
+                  <emphasis role="bold">Source:</emphasis> The cloud
+                  service provider that hosts the instance used for the
+                  cloud VM. Select
+                  <emphasis role="bold">&oci;</emphasis>.
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <emphasis role="bold">Profile:</emphasis> The cloud
+                  profile used to connect to the running instance.
+                  Select from the available cloud profiles.
+                </para>
+              </listitem>
+
+              <listitem>
+                <para>
+                  <emphasis role="bold">Instances:</emphasis> The
+                  instance to use for the cloud VM. Choose from the
+                  available instances on your cloud service.
+                </para>
+              </listitem>
+
+            </itemizedlist>
+          </listitem>
+
+          <listitem>
+            <para>
+              Click <emphasis role="bold">Finish</emphasis> to add a
+              cloud VM based on the selected instance.
+            </para>
+
+            <para>
+              A cloud VM with the same name as the instance is added to
+              the <emphasis role="bold">OCI</emphasis> group in
+              &vbox-mgr;.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              (Optional) To change the display name for the instance,
+              click <emphasis role="bold">Settings</emphasis> and edit
+              the <emphasis role="bold">Display Name</emphasis> field.
+            </para>
+
+            <para>
+              The cloud VM name in &vbox-mgr; is updated automatically.
+            </para>
+          </listitem>
+
+        </orderedlist>
+
+      </sect3>
+
+      <sect3 id="cloud-vm-settings">
+
+        <title>Changing Settings for a Cloud VM</title>
+
+        <para>
+          Select the cloud VM in &vbox-mgr; and click
+          <emphasis role="bold">Settings</emphasis>.
+        </para>
+
+        <itemizedlist>
+
+          <listitem>
+            <para>
+              For a <emphasis>new</emphasis> cloud VM, you can change
+              many settings for the &oci; instance, such as the display
+              name, shape, and disk size.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              When you <emphasis>add</emphasis> a cloud VM based on an
+              existing &oci; instance you can only change the display
+              name.
+            </para>
+          </listitem>
+
+        </itemizedlist>
+
+      </sect3>
+
+      <sect3 id="cloud-vm-control">
+
+        <title>Controlling a Cloud VM</title>
+
+        <para>
+          You can use &vbox-mgr; to control a cloud VM as follows:
+        </para>
+
+        <itemizedlist>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Start.</emphasis> Use the
+              <emphasis role="bold">Start</emphasis> button in the
+              &vbox-mgr; toolbar.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Stop.</emphasis> Right-click on the
+              cloud VM name, to display the
+              <emphasis role="bold">Close</emphasis> menu. Options to
+              shut down and power off the cloud VM are available.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              <emphasis role="bold">Terminate.</emphasis> Use the
+              <emphasis role="bold">Terminate</emphasis> button in the
+              &vbox-mgr; toolbar.
+            </para>
+
+            <caution>
+              <para>
+                This action deletes the instance from &oci;.
+              </para>
+            </caution>
+          </listitem>
+
+        </itemizedlist>
+
+        <para>
+          When you control a cloud VM in &vbox-mgr; the machine list is
+          updated automatically with the current instance state, such as
+          <emphasis role="bold">Stopped</emphasis> or
+          <emphasis role="bold">Running</emphasis>.
+        </para>
+
+        <para>
+          When you control an instance using the &oci; console,
+          &vbox-mgr; updates the status for the corresponding cloud VM
+          automatically.
+        </para>
+
+      </sect3>
+
+      <sect3 id="cloud-vm-remove">
+
+        <title>Removing a Cloud VM</title>
+
+        <para>
+          You can use &vbox-mgr; to remove a cloud VM as follows:
+        </para>
+
+        <para>
+          Right-click on the cloud VM name and select
+          <emphasis role="bold">Remove</emphasis>.
+        </para>
+
+        <itemizedlist>
+
+          <listitem>
+            <para>
+              Click <emphasis role="bold">Remove Only</emphasis> to
+              remove the cloud VM from the machine list in VirtualBox
+              Manager.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              Click <emphasis role="bold">Delete Everything</emphasis>
+              to remove the cloud VM from &vbox-mgr; and also to delete
+              the &oci; instance and any associated boot volumes.
+            </para>
+          </listitem>
+
+        </itemizedlist>
+
+      </sect3>
+
+      <sect3 id="cloud-vm-instance-console">
+
+        <title>Creating an Instance Console Connection for a Cloud VM</title>
+
+        <para>
+          To create a instance console connection, the cloud VM must be
+          in <emphasis role="bold">Running</emphasis> state.
+        </para>
+
+        <orderedlist>
+
+          <listitem>
+            <para>
+              Right-click on the cloud VM name and select
+              <emphasis role="bold">Console</emphasis>,
+              <emphasis role="bold">Create Connection</emphasis>.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              The <emphasis role="bold">Public Key</emphasis> dialog is
+              displayed. Paste the public key used for the instance
+              connection into the dialog and click
+              <emphasis role="bold">OK</emphasis>.
+            </para>
+
+            <para>
+              By default, either the first entry in your SSH keys folder
+              or the public key used for your previous instance console
+              connection is used.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              Click <emphasis role="bold">Connect</emphasis> to connect
+              to the instance. An instance console is displayed
+              automatically on the host.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
+              (Optional) Click <emphasis role="bold">Show Log</emphasis>
+              to display log messages for the instance console
+              connection.
+            </para>
+          </listitem>
+
+        </orderedlist>
+
+        <para>
+          See the &oci; documentation for details about how you can use
+          an instance console connection to troubleshoot instance
+          problems.
+        </para>
+
+      </sect3>
 
     </sect2>
@@ -3618 +5310 @@
           <para>
             Select a VM to export and click
-            <emphasis role="bold">Next</emphasis> to open the
-            <emphasis role="bold">Appliance Settings</emphasis> screen.
+            <emphasis role="bold">Next</emphasis> to display the
+            <emphasis role="bold">Format Settings</emphasis> page.
           </para>
         </listitem>
@@ -3630 +5322 @@
 
           <para>
-            In the <emphasis role="bold">Account</emphasis> drop-down
-            list, select the cloud profile for your &oci; account.
-          </para>
-
-          <para>
-            The list after the <emphasis role="bold">Account</emphasis>
-            field shows the profile settings for your cloud account.
+            In the <emphasis role="bold">Profile</emphasis> drop-down
+            list, select the cloud profile used for your &oci; account.
           </para>
 
           <figure id="fig-export-appliance-oci">
-            <title>Appliance Settings Screen, Showing Cloud Profile and Machine Creation
-              Settings</title>
-           <mediaobject>
+            <title>Export Virtual Appliance Wizard: Format Settings</title>
+          <mediaobject>
               <imageobject>
                 <imagedata align="center" fileref="images/export-appliance-oci.png"
@@ -3652 +5338 @@
           <para>
             In the <emphasis role="bold">Machine Creation</emphasis>
-            field, select an option to configure settings for a cloud
+            field, select an option to configure settings for the cloud
             instance created when you export to &oci;. The options
             enable you to do one of the following:
@@ -3685 +5371 @@
             Click <emphasis role="bold">Next</emphasis> to make an API
             request to the &oci; service and open the
-            <emphasis role="bold">Virtual System Settings</emphasis>
-            screen.
+            <emphasis role="bold">Appliance Settings</emphasis> page.
           </para>
         </listitem>
@@ -3713 +5398 @@
             <listitem>
               <para>
-                The name for the custom image in &oci;.
+                The display name for the custom image in &oci;.
               </para>
             </listitem>
@@ -3737 +5422 @@
 
           <para>
-            Click <emphasis role="bold">Export</emphasis> to continue.
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
-            Depending on the selection in the
+            Click <emphasis role="bold">Finish</emphasis> to continue.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            (Optional) Depending on the selection in the
             <emphasis role="bold">Machine Creation</emphasis> field, the
-            <emphasis role="bold">Cloud Virtual Machine
-            Settings</emphasis> screen may be displayed before or after
-            export. This screen enables you to configure settings for
-            the cloud instance, such as Shape and Disk Size.
-          </para>
-
-          <para>
-            Click <emphasis role="bold">Create</emphasis>. The VM is
+            <emphasis role="bold">Appliance Settings</emphasis> page may
+            be displayed before or after export. This screen enables you
+            to configure settings for the cloud instance, such as Shape
+            and Disk Size.
+          </para>
+
+          <para>
+            Click <emphasis role="bold">Finish</emphasis>. The VM is
             exported to &oci;.
           </para>
@@ -3973 +5658 @@
                 </para>
 
-<screen># dracut --logfile /var/log/Dracut.log --force --add qemu</screen>
+<screen># dracut –-logfile /var/log/Dracut.log --force --add qemu</screen>
               </listitem>
 
@@ -4028 +5713 @@
 
           <para>
-            In the <emphasis role="bold">Account</emphasis> drop-down
+            In the <emphasis role="bold">Profile</emphasis> drop-down
             list, select the cloud profile for your &oci; account.
-          </para>
-
-          <para>
-            The list after the <emphasis role="bold">Account</emphasis>
-            field shows the profile settings for your cloud account.
           </para>
 
@@ -4045 +5725 @@
             Click <emphasis role="bold">Next</emphasis> to make an API
             request to the &oci; service and display the
-            <emphasis role="bold">Appliance Settings</emphasis> screen.
+            <emphasis role="bold">Appliance Settings</emphasis> page.
           </para>
         </listitem>
@@ -4059 +5739 @@
 
           <figure id="fig-import-instance-oci">
-            <title>Import Cloud Instance Screen, Showing Profile Settings and VM Settings</title>
+            <title>Import Cloud Instance Wizard: Appliance Settings</title>
            <mediaobject>
               <imageobject>
@@ -4069 +5749 @@
 
           <para>
-            Click <emphasis role="bold">Import</emphasis> to import the
+            Click <emphasis role="bold">Finish</emphasis> to import the
             instance from &oci;.
           </para>
@@ -4157 +5837 @@
     </sect2>
 
-    <sect2 id="cloud-new-vm">
-
-      <title>Creating New Cloud Instances from a Custom Image</title>
-
-      <para>
-        You can use &product-name; to create new instances from a custom
-        image on your cloud service.
-      </para>
-
-      <para>
-        <xref linkend="cloud-export-oci"/> describes how to create a
-        custom image when you are exporting a VM to &oci;. Using a
-        custom image means that you can quickly create cloud instances
-        without having to upload your image to the cloud service every
-        time.
-      </para>
-
-      <para>
-        Perform the following steps to create a new cloud instance on
-        &oci;:
+    <sect2 id="cloud-using-cloud-networks">
+
+      <title>Using a Cloud Network</title>
+
+      <para>
+        A cloud network is a type of network that can be used for
+        connections from a local VM to a remote &oci; cloud instance.
+      </para>
+
+      <para>
+        To create and use a cloud network, do the following:
       </para>
 
@@ -4183 +5854 @@
         <listitem>
           <para>
-            Select <emphasis role="bold">File</emphasis>,
-            <emphasis role="bold">New Cloud VM</emphasis> to open the
-            <emphasis role="bold">Create Cloud Virtual
-            Machine</emphasis> wizard.
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
-            From the <emphasis role="bold">Destination</emphasis>
-            drop-down list, select
-            <emphasis role="bold">&oci;</emphasis>.
-          </para>
-
-          <para>
-            In the <emphasis role="bold">Account</emphasis> drop-down
-            list, select the cloud profile for your &oci; account.
-          </para>
-
-          <para>
-            The list after the <emphasis role="bold">Account</emphasis>
-            field shows the profile settings for your cloud account.
-          </para>
-
-          <para>
-            In the <emphasis role="bold">Images</emphasis> list, select
-            from the custom images available on &oci;.
-          </para>
-
-          <figure id="fig-newcloudvm">
-            <title>New Cloud VM Wizard, Showing List of Custom Images</title>
-            <mediaobject>
-              <imageobject>
-                <imagedata align="center" fileref="images/newcloudvm.png"
-                  width="12cm" />
-              </imageobject>
-            </mediaobject>
-          </figure>
-
-          <para>
-            Click <emphasis role="bold">Next</emphasis> to make an API
-            request to the &oci; service and open the
-            <emphasis role="bold">Cloud Virtual Machine
-            Settings</emphasis> screen.
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
-            (Optional) Edit settings used for the new instance on &oci;.
-          </para>
-
-          <para>
-            For example, you can edit the Disk Size and Shape used for
-            the VM instance and the networking configuration.
-          </para>
-
-          <para>
-            Click <emphasis role="bold">Create</emphasis> to create the
-            new cloud instance.
-          </para>
-        </listitem>
-
-        <listitem>
-          <para>
-            Monitor the instance creation process by using the &oci;
-            Console.
+            Set up a virtual cloud network on &oci;.
+          </para>
+
+          <para>
+            The following steps create and configure a virtual cloud
+            network (VCN) on &oci;. The VCN is used to tunnel network
+            traffic across the cloud.
+          </para>
+
+          <orderedlist>
+
+            <listitem>
+              <para>
+                Ensure that you have a cloud profile for connecting to
+                &oci;. See <xref linkend="cloud-create-cloud-profile"/>.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                Run the following <command>VBoxManage cloud</command>
+                command:
+              </para>
+
+<screen>VBoxManage cloud --provider="OCI" --profile="vbox-oci" network setup</screen>
+
+              <para>
+                where <literal>vbox-oci</literal> is the name of your
+                cloud profile.
+              </para>
+
+              <para>
+                Other options are available for the <command>VBoxManage
+                cloud network setup</command> command, to enable you to
+                configure details for the VCN. For example, you can
+                configure the operating system used for the cloud
+                gateway instance and the IP address range used by the
+                tunneling network. See
+                <xref linkend="vboxmanage-cloud"/>.
+              </para>
+
+              <para>
+                For best results, use an Oracle Linux 7 instance for the
+                cloud gateway. This is the default option.
+              </para>
+            </listitem>
+
+          </orderedlist>
+        </listitem>
+
+        <listitem>
+          <para>
+            Register the new cloud network with &product-name;.
+          </para>
+
+          <para>
+            Use the <emphasis role="bold">Cloud Networks</emphasis> tab
+            in the <emphasis role="bold">Network Manager</emphasis>
+            tool. See
+            <xref linkend="network-manager-cloud-network-tab"/>.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Add cloud network adaptors to the local VMs that will use
+            the cloud network. See <xref linkend="network_cloud"/>.
           </para>
         </listitem>
 
       </orderedlist>
-
-      <para>
-        You can also use the <command>VBoxManage cloud
-        instance</command> command to create and manage instances on a
-        cloud service. See <xref linkend="vboxmanage-cloud"/>.
-      </para>
 
     </sect2>
@@ -4370 +6035 @@
   </sect1>
 
-  <sect1 id="globalsettings">
-
-    <title>Global Settings</title>
+  <sect1 id="preferences">
+
+    <title>Preferences</title>
 
     <para>
-      The <emphasis role="bold">Global Settings</emphasis> dialog can be
-      displayed using the <emphasis role="bold">File</emphasis> menu, by
-      clicking the <emphasis role="bold">Preferences</emphasis> item.
-      This dialog offers a selection of settings, most of which apply to
-      all virtual machines of the current user. The
-      <emphasis role="bold">Extensions</emphasis> option applies to the
-      entire system.
+      The Preferences window offers a selection of settings, which apply
+      to all virtual machines of the current user.
     </para>
+
+    <para>
+      To display the Preferences window, do either of the following:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          Select <emphasis role="bold">File</emphasis>,
+          <emphasis role="bold">Preferences</emphasis>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Click <emphasis role="bold">Preferences</emphasis> on the
+          Welcome screen in &vbox-mgr;.
+        </para>
+      </listitem>
+
+    </itemizedlist>
 
     <para>
@@ -4392 +6074 @@
       <listitem>
         <para>
-          <emphasis role="bold">General.</emphasis> Enables the user to
+          <emphasis role="bold">General.</emphasis> Enables you to
           specify the default folder or directory for VM files, and the
           VRDP Authentication Library.
@@ -4400 +6082 @@
       <listitem>
         <para>
-          <emphasis role="bold">Input.</emphasis> Enables the user to
-          specify the Host key. This is the key that toggles whether the
+          <emphasis role="bold">Input.</emphasis> Enables you to specify
+          keyboard shortcuts, such as the <emphasis role="bold">Host
+          key</emphasis>. This is the key that toggles whether the
           cursor is in the focus of the VM or the Host OS windows, see
           <xref linkend="keyb_mouse_normal"/>. The Host key is also used
@@ -4411 +6094 @@
       <listitem>
         <para>
-          <emphasis role="bold">Update.</emphasis> Enables the user to
+          <emphasis role="bold">Update.</emphasis> Enables you to
           specify various settings for Automatic Updates.
         </para>
@@ -4418 +6101 @@
       <listitem>
         <para>
-          <emphasis role="bold">Language.</emphasis> Enables the user to
-          specify the GUI language.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          <emphasis role="bold">Display.</emphasis> Enables the user to
+          <emphasis role="bold">Language.</emphasis> Enables you to
+          specify the language used for menus, labels, and text in
+          &vbox-mgr;.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Display.</emphasis> Enables you to
           specify the screen resolution, and its width and height. A
           default scale factor can be specified for all guest screens.
@@ -4433 +6117 @@
       <listitem>
         <para>
-          <emphasis role="bold">Network.</emphasis> Enables the user to
-          configure the details of NAT networks. See
-          <xref linkend="network_nat_service"/>.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          <emphasis role="bold">Extensions.</emphasis> Enables the user
-          to list and manage the installed extension packages.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          <emphasis role="bold">Proxy.</emphasis> Enables the user to
-          configure a HTTP Proxy Server.
-        </para>
+          <emphasis role="bold">Proxy.</emphasis> Enables you to
+          configure an HTTP Proxy Server.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Interface.</emphasis> Enables you to
+          select a color theme for the &vbox-mgr; user interface.
+        </para>
+
+        <note>
+          <para>
+            This setting is only available on Windows host platforms.
+          </para>
+        </note>
       </listitem>
 
@@ -4466 +6148 @@
       you to use multiple interfaces to control the same virtual
       machines. For example, you can start a virtual machine with the
-      VirtualBox Manager window and then stop it from the command line.
-      With &product-name;'s support for the Remote Desktop Protocol
-      (RDP), you can even run virtual machines remotely on a headless
-      server and have all the graphical output redirected over the
-      network.
+      &vbox-mgr; window and then stop it from the command line. With
+      &product-name;'s support for the Remote Desktop Protocol (RDP),
+      you can even run virtual machines remotely on a headless server
+      and have all the graphical output redirected over the network.
     </para>
 
@@ -4483 +6164 @@
         <para>
           <emphasis role="bold">VirtualBox.</emphasis> This is the
-          VirtualBox Manager, a graphical user interface that uses the
-          Qt toolkit. This interface is described throughout this
-          manual. While this is the simplest and easiest front-end to
-          use, some of the more advanced &product-name; features are not
-          included.
+          &vbox-mgr;, a graphical user interface that uses the Qt
+          toolkit. This interface is described throughout this manual.
+          While this is the simplest and easiest front-end to use, some
+          of the more advanced &product-name; features are not included.
         </para>
       </listitem>
@@ -4550 +6230 @@
     <figure id="fig-soft-keyb">
       <title>Soft Keyboard in a Guest Virtual Machine</title>
-    <mediaobject>
+     <mediaobject>
       <imageobject>
         <imagedata align="center" fileref="images/softkeybd.png"
@@ -4631 +6311 @@
           <para>
             The name of the current keyboard layout is displayed in the
-            task bar of the soft keyboard window. This is the previous
+            toolbar of the soft keyboard window. This is the previous
             keyboard layout that was used.
           </para>
@@ -4637 +6317 @@
           <para>
             Click the <emphasis role="bold">Layout List</emphasis> icon
-            in the task bar of the soft keyboard window. The
+            in the toolbar of the soft keyboard window. The
             <emphasis role="bold">Layout List</emphasis> window is
             displayed.
@@ -4679 +6359 @@
                 To change the look of the soft keyboard, click the
                 <emphasis role="bold">Settings</emphasis> icon in the
-                task bar. You can change colors used in the keyboard
+                toolbar. You can change colors used in the keyboard
                 graphic, and can hide or show sections of the keyboard,
                 such as the NumPad or multimedia keys.
@@ -4704 +6384 @@
         <para>
           To permananently save a custom keyboard layout, you must save
-          it to file. Otherwise, any changes you make are discarded when
-          you close down the <emphasis role="bold">Soft
+          it to a file. Otherwise, any changes you make are discarded
+          when you close down the <emphasis role="bold">Soft
           Keyboard</emphasis> window.
         </para>
@@ -4728 +6408 @@
           <para>
             Click the <emphasis role="bold">Layout List</emphasis> icon
-            in the task bar of the soft keyboard window.
+            in the toolbar of the soft keyboard window.
           </para>
         </listitem>
@@ -4777 +6457 @@
         <listitem>
           <para>
-            (Optional) Save the layout to file. This means that your
+            (Optional) Save the layout to a file. This means that your
             custom keyboard layout will be available for future use.
           </para>
@@ -4803 +6483 @@
   <sect1 id="vm-info">
 
-    <title>Configuration Details and Runtime Information of Virtual Machines</title>
+    <title>Monitoring of Virtual Machines</title>
+
     <para>
-      &product-name; GUI offers several possibilities for obtaining
-      configuration and runtime information of virtual machines.
+      &vbox-mgr; includes the following tools for viewing runtime
+      information and changing the configuration of virtual machines.
     </para>
 
-    <sect2 id="vm-details-tool">
-      <title>Virtual Machine Details Widget</title>
-      <para>
-        The VM details widget is an interactive tool through which
-        settings of the guest system can be viewed and modified.
-      </para>
-    </sect2>
-    <sect2 id="vm-activity-overview-widget">
-
-      <title>Resource Monitor</title>
-
-      <para>
-        The Resource Monitor widget shows several performance metrics
-        of running virtual machines. This enables users to have a quick
-        overview of system resources of individual virtual machines and
-        those of host system. The widget displays several performance
-        metrics of each running virtual machine. It is possible to
-        configure the set of metrics to be shown and select a metric
-        with respect to which the list of virtual machines is sorted.
-        It is also possible to open the virtual machine's performance
-        monitor (See <xref linkend="vm-session-information"/>) by activating
-        To Performance action which is located in the tool bar and
-        in the context menu.
-      </para>
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          <emphasis role="bold"> VM Activity Overview.</emphasis>
+          Displays an overview of performance metrics for all running
+          VMs.
+        </para>
+
+        <para>
+          See <xref linkend="vm-activity-overview"/>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Session Information Dialog.</emphasis>
+          Displays configuration and runtime information for the
+          selected guest system.
+        </para>
+
+        <para>
+          See <xref linkend="vm-activity-session-information"/>
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+    <sect2 id="vm-activity-overview">
+
+      <title>VM Activity Overview</title>
+
+      <para>
+        The VM Activity Overview tool displays several performance
+        metrics for all running virtual machines and for the host
+        system. This provides an overview of system resources used by
+        individual virtual machines and the host system.
+      </para>
+
+      <para>
+        To display the VM Activity Overview tool, do the following:
+      </para>
+
+      <para>
+        Go to the global <emphasis role="bold">Tools</emphasis> menu and
+        click <emphasis role="bold">Activities</emphasis>. The
+        <emphasis role="bold">VM Activity Overview</emphasis> window is
+        shown.
+      </para>
+
       <figure id="fig-vm-activity-overview-widget">
-        <title>Resource Monitor</title>
+        <title>VM Activity Overview Tool</title>
         <mediaobject>
-          <imageobject>
-            <imagedata align="center" fileref="images/resourcemonitor.png"
+       <imageobject>
+            <imagedata align="center" fileref="images/vm-activity-overview.png"
                        width="14cm" />
           </imageobject>
@@ -4843 +6550 @@
       </figure>
 
+      <para>
+        To show metrics for <emphasis>all</emphasis> virtual machines,
+        including those that are not running, right-click on the list of
+        virtual machines and select <emphasis role="bold">List All
+        Virtual Machines</emphasis>.
+      </para>
+
+      <para>
+        To configure the set of metrics to be shown, click
+        <emphasis role="bold">Columns</emphasis> in the toolbar. You can
+        then sort the list of virtual machines by a particular metric.
+      </para>
+
+      <para>
+        To see more performance information for a virtual machine,
+        select the VM name and click <emphasis role="bold">VM
+        Activity</emphasis> in the toolbar. The <emphasis role="bold">VM
+        Activity</emphasis> tab of the <emphasis role="bold">Session
+        Information</emphasis> dialog is shown, see
+        <xref linkend="vm-activity-session-information"/>.
+      </para>
+
     </sect2>
 
-    <sect2 id="vm-session-information">
+    <sect2 id="vm-activity-session-information">
+
       <title>Session Information Dialog</title>
-      <para>
-        The guest VM window includes a multi tabbed dialog which conveys
-        important configuration and runtime information of the guest
-        system. The tabs of the dialog are:
+
+      <para>
+        The Session Information dialog includes multiple tabs which show
+        important configuration and runtime information for the guest
+        system. The tabs of the dialog are as follows:
       </para>
 
       <itemizedlist>
-      <listitem>
-        <para>
-          <emphasis role="bold">Configuration Details</emphasis> tab
-          displays system configuration of the virtual machine in a
-          tabular format. The displayed information includes storage
-          configuration, audio settings, etc.
-        </para>
-      </listitem>
-      <listitem>
-        <para>
-          <emphasis role="bold">Runtime Information</emphasis> tab
-          shows the information that can change between the guest
-          sessions in tabular format similar to the Configuration
-          Details tab.
-        </para>
-      </listitem>
-      <listitem>
-        <para>
-          <emphasis role="bold">Performance Monitor</emphasis> tab
-          has several time series charts which monitors guests resource
-          usage including CPU, RAM, Disk I/O, and Network. Note that
-          RAM chart requires the guest additions to be running on the guest
-          system to work. The Performance Monitor is also available from
-          the machine menu in the manager UI.
-        </para>
-      </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Configuration Details.</emphasis>
+            Displays the system configuration of the virtual machine in
+            a tabular format. The displayed information includes details
+            such as storage configuration and audio settings.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Runtime Information.</emphasis>
+            Displays runtime information for the guest session in a
+            tabular format similar to the Configuration Details tab.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">VM Activity.</emphasis> Includes
+            several time series charts which monitor guest resource
+            usage including CPU, RAM, Disk I/O, and Network. Note that
+            the RAM chart requires the Guest Additions to be running on
+            the guest system. The VM Activity tab can also be accessed
+            directly from the VM Activity Overview tool. See
+            <xref linkend="vm-activity-overview"/>.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Guest Control</emphasis>. Details of
+            processes used by the Guest Control File Manager. See
+            <xref linkend="guestadd-gc-file-manager"/>.
+          </para>
+        </listitem>
+
       </itemizedlist>
-      <figure id="fig-vm-performance-monitor">
-        <title>VM Performance Monitor</title>
+
+      <para>
+        To display the Session Information dialog, select
+        <emphasis role="bold">Machine</emphasis>,
+        <emphasis role="bold">Session Information</emphasis> in the
+        guest VM.
+      </para>
+
+      <figure id="fig-vm-session-information">
+        <title>Session Information Dialog, Showing VM Activity Tab</title>
         <mediaobject>
-          <imageobject>
-            <imagedata align="center" fileref="images/vmperformancemonitor.png"
-                       width="14cm" />
-          </imageobject>
+       <imageobject>
+            <imagedata align="center" fileref="images/session-information.png"
+                       width="12cm" />
+         </imageobject>
         </mediaobject>
       </figure>
 
-
     </sect2>
 
   </sect1>
+
+  <sect1 id="log-viewer">
+
+    <title>The Log Viewer</title>
+
+    <para>
+      Every time you start up a VM, &product-name; creates a log file
+      that records system configuration and events. The
+      <emphasis role="bold">Log Viewer</emphasis> is a &vbox-mgr; tool
+      that enables you to view and analyze system logs.
+    </para>
+
+    <figure id="fig-log-viewer-tool">
+      <title>Log Viewer Tool, Showing System Events</title>
+     <mediaobject>
+        <imageobject>
+          <imagedata align="center" fileref="images/log-viewer.png"
+                   width="10cm" />
+        </imageobject>
+      </mediaobject>
+
+    </figure>
+
+    <para>
+      To display the Log Viewer, do either of the following:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          Click the VM name in the machine list and select
+          <emphasis role="bold">Logs</emphasis> from the machine tools
+          menu.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          In the guest VM, select
+          <emphasis role="bold">Machine</emphasis>,
+          <emphasis role="bold">Show Log</emphasis>.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+    <para>
+      Log messages for the VM are displayed in tabs in the Log Viewer
+      window. See <xref linkend="collect-debug-info"/> for details of
+      the various log files generated by &product-name;.
+    </para>
+
+    <para>
+      If you select multiple VMs in the machine list, logs are listed
+      for each VM.
+    </para>
+
+    <para>
+      The toolbar of the Log Viewer includes the following options:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Save:</emphasis> Exports the contents of
+          the selected log file to a text file. Specify the destination
+          filename and location in the displayed dialog.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Find:</emphasis> Searches for a text
+          string in the log file.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Filter:</emphasis> Uses filter terms to
+          display specific types of log messages. Common log message
+          terms used by &product-name;, such as Audio and NAT, are
+          included by default. Select one or more terms from the
+          drop-down list. To add your own filter term, enter the text
+          string in the text box field.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Bookmark:</emphasis> Saves the location
+          of a log message, enabling you to find it quickly. To create a
+          bookmark, either click on the line number, or select some text
+          and then click <emphasis role="bold">Bookmark</emphasis>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Options:</emphasis> Configures the text
+          display used in the log message window.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Refresh:</emphasis> Refreshes the log
+          file you are currently viewing. Only log messages in the
+          current tab are updated.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Reload:</emphasis> Refreshes all log
+          files. Log messages in every tab are updated.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Settings:</emphasis> Displays the
+          <emphasis role="bold">Settings</emphasis> window for the VM,
+          enabling you to make configuration changes.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Discard:</emphasis> For a running VM,
+          discards the saved state for the VM and closes it down.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Show/Start:</emphasis> For a running VM,
+          <emphasis role="bold">Show</emphasis> displays the VM window.
+          For a stopped VM, <emphasis role="bold">Start</emphasis>
+          displays options for powering up the VM.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+  </sect1>
+
 </chapter>

trunk/doc/manual/en_US/user_KnownIssues.xml

@@ -66 +66 @@
       <listitem>
         <para>
-          Mac OS X guests (Mac OS X hosts only)
+          Mac OS X guests (macOS hosts only)
         </para>
       </listitem>
@@ -115 +115 @@
 
     <itemizedlist>
+
+      <listitem>
+        <para>
+          The macOS installer packages for &product-name; 7 currently do
+          not include the Internal Networking feature, which is
+          available on all other platforms. This will be addressed with
+          an update of &product-name; 7. For setups which depend on this
+          functionality it is best to keep using &product-name; 6.1.
+        </para>
+      </listitem>
 
       <listitem>
@@ -278 +288 @@
         <para>
           Preserving the aspect ratio in scale mode works only on
-          Windows hosts and on Mac OS X hosts.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          On <emphasis role="bold">Mac OS X hosts,</emphasis> the
-          following features are not yet implemented:
+          Windows hosts and on macOS hosts.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          On <emphasis role="bold">macOS hosts</emphasis>, the following
+          features are not yet implemented:
         </para>
 
@@ -309 +319 @@
 
         </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">macOS/ARM64 (Apple silicon) host
+          package</emphasis>
+        </para>
       </listitem>
 

trunk/doc/manual/en_US/user_Networking.xml

@@ -57 +57 @@
     Four of the network cards can be configured in the
     <emphasis role="bold">Network</emphasis> section of the
-    <emphasis role="bold">Settings</emphasis> dialog in the graphical
-    user interface of &product-name;. You can configure all eight
-    network cards on the command line using <command>VBoxManage
-    modifyvm</command>. See <xref linkend="vboxmanage-modifyvm" />.
+    <emphasis role="bold">Settings</emphasis> window in &vbox-mgr;. You
+    can configure all eight network cards on the command line using
+    <command>VBoxManage modifyvm</command>. See
+    <xref linkend="vboxmanage-modifyvm" />.
   </para>
 
@@ -265 +265 @@
           similar to a loopback interface, is created on the host,
           providing connectivity among virtual machines and the host.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Cloud networking.</emphasis> This can be
+          used to connect a local VM to a subnet on a remote cloud
+          service.
         </para>
       </listitem>
@@ -550 +558 @@
         To configure port forwarding you can use the graphical
         <emphasis role="bold">Port Forwarding</emphasis> editor which
-        can be found in the <emphasis role="bold">Network
-        Settings</emphasis> dialog for network adaptors configured to
-        use NAT. Here, you can map host ports to guest ports to allow
-        network traffic to be routed to a specific port in the guest.
+        can be found in the <emphasis role="bold">Network</emphasis>
+        settings dialog for network adaptors configured to use NAT.
+        Here, you can map host ports to guest ports to allow network
+        traffic to be routed to a specific port in the guest.
       </para>
 
@@ -572 +580 @@
       </para>
 
-<screen>VBoxManage modifyvm "VM name" --natpf1 "guestssh,tcp,,2222,,22"</screen>
+<screen>VBoxManage modifyvm "VM name" --nat-pf1 "guestssh,tcp,,2222,,22"</screen>
 
       <para>
@@ -582 +590 @@
         <literal>guestssh</literal> is purely descriptive and will be
         auto-generated if omitted. The number after
-        <option>--nat-pf</option> denotes the network card, as with other
-        <command>VBoxManage</command> commands.
+        <option>--nat-pf</option> denotes the network card, as with
+        other <command>VBoxManage</command> commands.
       </para>
 
@@ -696 +704 @@
             <emphasis role="bold">Forwarding host ports below
             1024.</emphasis> On UNIX-based hosts, such as Linux, Oracle
-            Solaris, and Mac OS X, it is not possible to bind to ports
+            Solaris, and macOS, it is not possible to bind to ports
             below 1024 from applications that are not run by
             <literal>root</literal>. As a result, if you try to
@@ -835 +843 @@
     <para>
       NAT networks can also be created, deleted, and configured using
-      the VirtualBox Manager. Click
-      <emphasis role="bold">File</emphasis>,<emphasis role="bold">
-      Preferences</emphasis> and select the
-      <emphasis role="bold">Network</emphasis> page.
+      the Network Manager tool in &vbox-mgr;. Click
+      <emphasis role="bold">File</emphasis>, <emphasis role="bold">
+      Tools</emphasis>, <emphasis role="bold">Network
+      Manager</emphasis>. See <xref linkend="network-manager"/>.
     </para>
 
@@ -926 +934 @@
       <listitem>
         <para>
-          <emphasis role="bold">Mac OS X hosts.</emphasis> Functionality
-          is limited when using AirPort, the Mac's wireless networking
+          <emphasis role="bold">macOS hosts.</emphasis> Functionality is
+          limited when using AirPort, the Mac's wireless networking
           system, for bridged networking. Currently, &product-name;
           supports only IPv4 and IPv6 over AirPort. For other protocols,
@@ -1033 +1041 @@
       <listitem>
         <para>
-          Use the VM's <emphasis role="bold">Settings</emphasis> dialog
-          in the VirtualBox Manager. In the
-          <emphasis role="bold">Network</emphasis> category of the
-          settings dialog, select <emphasis role="bold">Internal
-          Network</emphasis> from the drop-down list of networking
-          modes. Select the name of an existing internal network from
-          the drop-down list below, or enter a new name into the
+          Use the VM's <emphasis role="bold">Settings</emphasis> window
+          in &vbox-mgr;. In the <emphasis role="bold">Network</emphasis>
+          category of the Settings window, select
+          <emphasis role="bold">Internal Network</emphasis> from the
+          drop-down list of networking modes. Select the name of an
+          existing internal network from the drop-down list below, or
+          enter a new name into the
           <emphasis role="bold">Name</emphasis> field.
         </para>
@@ -1112 +1120 @@
     <note>
       <para>
-        Hosts running recent Mac OS X versions do not support host-only
+        Hosts running recent macOS versions do not support host-only
         adapters. These adapters are replaced by host-only networks,
-        which definine a network mask and an IP address range, where the
+        which define a network mask and an IP address range, where the
         host network interface receives the lowest address in the range.
       </para>
-      <para>
-        The host network interface gets added and removed dynamically
-        by the operating system, whenever a host-only network is used
-        by virtual machines.
+
+      <para>
+        The host network interface gets added and removed dynamically by
+        the operating system, whenever a host-only network is used by
+        virtual machines.
+      </para>
+
+      <para>
+        On macOS hosts, choose the <emphasis role="bold">Host-Only
+        Network</emphasis> option when configuring a network adapter.
+        The <emphasis role="bold">Host-Only Adapter</emphasis> option is
+        provided for legacy support.
       </para>
     </note>
@@ -1158 +1174 @@
         <para>
           On the command line, use <command>VBoxManage modifyvm
-          <replaceable>"vmname</replaceable>
+          <replaceable>vmname</replaceable>
           --nic<replaceable>x</replaceable> hostonly</command>. See
           <xref linkend="vboxmanage-modifyvm" />.
@@ -1178 +1194 @@
       <listitem>
         <para>
-          In the VirtualBox Manager you can configure the DHCP server by
-          choosing <emphasis role="bold">File</emphasis>,
-          <emphasis role="bold">Host Network Manager</emphasis>. The
-          Host Network Manager lists all host-only networks which are
+          In &vbox-mgr; you can configure the DHCP server by choosing
+          <emphasis role="bold">File</emphasis>,
+          <emphasis role="bold">Tools</emphasis>,
+          <emphasis role="bold">Network Manager</emphasis>. The Network
+          Manager window lists all host-only networks which are
           presently in use. Select the network name and then use the
           <emphasis role="bold">DHCP Server</emphasis> tab to configure
-          DHCP server settings.
+          DHCP server settings. See <xref linkend="network-manager"/>.
         </para>
       </listitem>
@@ -1200 +1217 @@
     <note>
       <para>
-        On Linux and Mac OS X hosts the number of host-only interfaces
-        is limited to 128. There is no such limit for Oracle Solaris and
+        On Linux and macOS hosts the number of host-only interfaces is
+        limited to 128. There is no such limit for Oracle Solaris and
         Windows hosts.
       </para>
@@ -1207 +1224 @@
 
     <para>
-      On Linux, Mac OS X and Solaris &product-name; will only allow IP
+      On Linux, macOS and Solaris &product-name; will only allow IP
       addresses in 192.168.56.0/21 range to be assigned to host-only
       adapters. For IPv6 only link-local addresses are allowed. If other
       ranges are desired, they can be enabled by creating
-      <filename>/etc/vbox/networks.conf</filename> and specifying allowed
-      ranges there. For example, to allow 10.0.0.0/8 and 192.168.0.0/16
-      IPv4 ranges as well as 2001::/64 range put the following lines into
-      <filename>/etc/vbox/networks.conf</filename>:
-      <screen>
+      <filename>/etc/vbox/networks.conf</filename> and specifying
+      allowed ranges there. For example, to allow 10.0.0.0/8 and
+      192.168.0.0/16 IPv4 ranges as well as 2001::/64 range put the
+      following lines into <filename>/etc/vbox/networks.conf</filename>:
+    </para>
+
+<screen>
       * 10.0.0.0/8 192.168.0.0/16
       * 2001::/64
       </screen>
-      Lines starting with the hash <command>#</command> are ignored. Next
-      example allows any addresses, effectively disabling range control:
-      <screen>
+
+    <para>
+      Lines starting with the hash <command>#</command> are ignored. The
+      following example allows any addresses, effectively disabling
+      range control:
+    </para>
+
+<screen>
       * 0.0.0.0/0 ::/0
       </screen>
-      If the file exists, but no ranges are specified in it, no addresses
-      will be assigned to host-only adapters. The following example
-      effectively disables all ranges:
-      <screen>
+
+    <para>
+      If the file exists, but no ranges are specified in it, no
+      addresses will be assigned to host-only adapters. The following
+      example effectively disables all ranges:
+    </para>
+
+<screen>
       # No addresses are allowed for host-only adapters
       </screen>
-    </para>
 
   </sect1>
@@ -1428 +1455 @@
       <ulink url="http://wiki.virtualsquare.org" />.
     </para>
+
+  </sect1>
+
+  <sect1 id="network_cloud">
+
+    <title>Cloud Networks</title>
+
+    <para>
+      Cloud networks can be used for connections from a local VM to a
+      subnet on a remote &oci; instance. See
+      <xref linkend="network-manager-cloud-network-tab"/> for details of
+      how to create and configure a cloud network using the Network
+      Manager tool in &vbox-mgr;.
+    </para>
+
+    <para>
+      To enable a cloud network interface for a virtual machine, do
+      either of the following:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          Go to the <emphasis role="bold">Network</emphasis> page in the
+          virtual machine's <emphasis role="bold">Settings</emphasis>
+          dialog and select an <emphasis role="bold">Adapter</emphasis>
+          tab. Ensure that the <emphasis role="bold">Enable Network
+          Adapter</emphasis> check box is selected and choose
+          <emphasis role="bold">Cloud Network</emphasis> for the
+          <emphasis role="bold">Attached To</emphasis> field.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          On the command line, use <command>VBoxManage modifyvm
+          <replaceable>vmname</replaceable>
+          --nic<replaceable>x</replaceable> cloud</command>. See
+          <xref linkend="vboxmanage-modifyvm" />.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+  </sect1>
+
+  <sect1 id="network-manager">
+
+    <title>Network Manager</title>
+
+    <para>
+      The <emphasis role="bold">Network Manager</emphasis> tool in
+      &vbox-mgr; enables you to create, delete, and configure the
+      following types of networks used by &product-name;:
+    </para>
+
+    <itemizedlist>
+
+      <listitem>
+        <para>
+          Host-only networks. See
+          <xref linkend="network-manager-host-only-tab"/>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          NAT networks. See
+          <xref linkend="network-manager-nat-network-tab"/>.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          Cloud networks. See
+          <xref linkend="network-manager-cloud-network-tab"/>.
+        </para>
+      </listitem>
+
+    </itemizedlist>
+
+    <para>
+      To display the Network Manager, go to the global
+      <emphasis role="bold">Tools</emphasis> menu and click
+      <emphasis role="bold">Network</emphasis>.
+    </para>
+
+    <sect2 id="network-manager-host-only-tab">
+
+      <title>Host-Only Networks Tab</title>
+
+      <para>
+        The Host-Only Networks tab in Network Manager lists all
+        host-only networks that are currently in use.
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            Click <emphasis role="bold">Create</emphasis> to add a new
+            host-only network to the list.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Click <emphasis role="bold">Remove</emphasis> to remove a
+            host-only network from the list.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Click <emphasis role="bold">Properties</emphasis> to show or
+            hide settings for the selected host-only network.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+      <para>
+        To configure a host-only network, select the network name in the
+        <emphasis role="bold">Name</emphasis> field and do the
+        following:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            Use the <emphasis role="bold">Adapter</emphasis> tab to
+            configure the network adapter for the host-only network.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Use the <emphasis role="bold">DHCP Server</emphasis> tab to
+            configure settings for the DHCP server used by the host-only
+            network. The DHCP server is built into &product-name; and
+            manages IP addresses for the network automatically.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+    </sect2>
+
+    <sect2 id="network-manager-nat-network-tab">
+
+      <title>NAT Networks Tab</title>
+
+      <para>
+        The NAT Networks tab in Network Manager lists all NAT networks
+        that are currently in use.
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            Click <emphasis role="bold">Create</emphasis> to add a new
+            NAT network to the list.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Click <emphasis role="bold">Remove</emphasis> to remove a
+            NAT network from the list.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Click <emphasis role="bold">Properties</emphasis> to show or
+            hide settings for the selected NAT network.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+      <para>
+        To configure a NAT network, select the network name in the
+        <emphasis role="bold">Name</emphasis> field and do the
+        following:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            Use the <emphasis role="bold">General Options</emphasis> tab
+            to configure the network settings used by the NAT network.
+            For example, the network address and mask of the NAT service
+            interface.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Use the <emphasis role="bold">Port Forwarding</emphasis> tab
+            to configure port forwarding rules used by the NAT network.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+    </sect2>
+
+    <sect2 id="network-manager-cloud-network-tab">
+
+      <title>Cloud Networks Tab</title>
+
+      <para>
+        The Cloud Networks tab in Network Manager lists all cloud
+        networks that are currently in use.
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            Click <emphasis role="bold">Create</emphasis> to add a new
+            cloud network to the list.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Click <emphasis role="bold">Remove</emphasis> to remove a
+            cloud network from the list.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Click <emphasis role="bold">Properties</emphasis> to show or
+            hide settings for the selected cloud network.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+      <para>
+        To configure a cloud network, select the network name in the
+        <emphasis role="bold">Name</emphasis> field and specify the
+        following:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Name:</emphasis> The name used for the
+            cloud network.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Provider:</emphasis> The cloud service
+            provider, such as &oci;.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Profile:</emphasis> The cloud profile
+            used to connect to the cloud network.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">ID:</emphasis> The OCID for the cloud
+            tunneling network. Click the
+            <emphasis role="bold">Network</emphasis> icon to view the
+            subnets on &oci; that are available for tunneling traffic.
+          </para>
+
+          <para>
+            See <xref linkend="cloud-using-cloud-networks"/> for details
+            of how you can use the <command>VBoxManage cloud</command>
+            command to create and configure a virtual cloud network
+            (VCN) on &oci;.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
+    </sect2>
 
   </sect1>

trunk/doc/manual/en_US/user_Storage.xml

@@ -126 +126 @@
         <para>
           After you have created a new virtual machine with the
-          <emphasis role="bold">New Virtual Machine</emphasis> wizard of
-          the VirtualBox Manager, you will typically see one IDE
-          controller in the machine's
-          <emphasis role="bold">Storage</emphasis> settings. The virtual
-          CD/DVD drive will be attached to one of the four ports of this
-          controller.
+          <emphasis role="bold">New Virtual Machine</emphasis> wizard in
+          &vbox-mgr;, you will typically see one IDE controller in the
+          machine's <emphasis role="bold">Storage</emphasis> settings.
+          The virtual CD/DVD drive will be attached to one of the four
+          ports of this controller.
         </para>
       </listitem>
@@ -174 +173 @@
             SATA after installation by installing the SATA drivers and
             changing the controller type in the VM
-            <emphasis role="bold">Settings</emphasis> dialog.
+            <emphasis role="bold">Settings</emphasis> window.
           </para>
 
@@ -191 +190 @@
           following. Go to the <emphasis role="bold">Storage</emphasis>
           page of the machine's
-          <emphasis role="bold">Settings</emphasis> dialog, click
+          <emphasis role="bold">Settings</emphasis> window, click
           <emphasis role="bold">Add Controller</emphasis> under the
           Storage Tree box and then select <emphasis role="bold">Add
@@ -227 +226 @@
           To enable a SCSI controller, on the
           <emphasis role="bold">Storage</emphasis> page of a virtual
-          machine's <emphasis role="bold">Settings</emphasis> dialog,
+          machine's <emphasis role="bold">Settings</emphasis> window,
           click <emphasis role="bold">Add Controller</emphasis> under
           the Storage Tree box and then select <emphasis role="bold">Add
@@ -488 +487 @@
     <para>
       Irrespective of the disk capacity and format, as mentioned in
-      <xref linkend="gui-createvm" />, there are two options for
+      <xref linkend="create-vm-wizard" />, there are two options for
       creating a disk image: fixed-size or dynamically allocated.
     </para>
@@ -528 +527 @@
   </sect1>
 
-  <sect1 id="vdis">
+  <sect1 id="virtual-media-manager">
 
     <title>The Virtual Media Manager</title>
@@ -558 +557 @@
     <para>
       The known media can be viewed and changed using the
-      <emphasis role="bold">Virtual Media Manager</emphasis>, which you
-      can access from the <emphasis role="bold">File</emphasis> menu in
-      the VirtualBox Manager window.
+      <emphasis role="bold">Virtual Media Manager</emphasis> tool, which
+      you access by clicking <emphasis role="bold">Media</emphasis> on
+      the global <emphasis role="bold">Tools</emphasis> menu in
+      &vbox-mgr;.
     </para>
 
     <figure id="fig-virtual-media-manager">
-      <title>The Virtual Media Manager</title>
-    <mediaobject>
+      <title>The Virtual Media Manager, Showing Hard Disk Images</title>
+      <mediaobject>
         <imageobject>
           <imagedata align="center" fileref="images/virtual-disk-manager.png"
@@ -630 +630 @@
           <listitem>
             <para>
-              For virtual hard disks, the <emphasis role="bold">Create
-              Virtual Hard Disk</emphasis> wizard is shown.
+              For hard disks, the <emphasis role="bold">Create Virtual
+              Hard Disk</emphasis> wizard is shown. See
+              <xref linkend="create-virtual-hard-disk-image"/>.
             </para>
           </listitem>
@@ -638 +639 @@
             <para>
               For optical disks, the <emphasis role="bold">VISO
-              Creator</emphasis> screen is shown. This enables you to
-              create a virtual ISO from selected files on the host.
+              Creator</emphasis> tool is shown. See
+              <xref linkend="create-optical-disk-image"/>.
             </para>
           </listitem>
@@ -646 +647 @@
             <para>
               For floppy disks, the <emphasis role="bold">Floppy Disk
-              Creator</emphasis> screen is shown.
+              Creator</emphasis> tool is shown. See
+              <xref linkend="create-floppy-disk-image"/>.
             </para>
           </listitem>
@@ -713 +715 @@
           attached to a VM as a virtual hard disk.
         </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <emphasis role="bold">Clear</emphasis> all inaccessible disk
+          images from the list. The disk images are released from the
+          VMs they are attached to and removed from the known media.
+        </para>
+
+        <note>
+          <para>
+            This option is for optical disks and floppy disks only.
+          </para>
+        </note>
       </listitem>
 
@@ -794 +810 @@
       <listitem>
         <para>
-          Click an icon in the Virtual Media Manager task bar.
+          Click an icon in the Virtual Media Manager toolbar.
         </para>
       </listitem>
@@ -808 +824 @@
     <para>
       Use the <emphasis role="bold">Storage</emphasis> page in a VM's
-      <emphasis role="bold">Settings</emphasis> dialog to create a new
+      <emphasis role="bold">Settings</emphasis> window to create a new
       disk image. By default, disk images are stored in the VM's folder.
     </para>
@@ -831 +847 @@
     </note>
 
+    <sect2 id="create-virtual-hard-disk-image">
+
+      <title>Creating a Virtual Hard Disk Image</title>
+
+      <para>
+        Use the <emphasis role="bold">Create Virtual Hard
+        Disk</emphasis> wizard to create a hard disk image.
+      </para>
+
+      <orderedlist>
+
+        <listitem>
+          <para>
+            Display the <emphasis role="bold">Hard Disks</emphasis> tab
+            in Virtual Media Manager and click
+            <emphasis role="bold">Create</emphasis>.
+          </para>
+
+          <para>
+            The <emphasis role="bold">Create Virtual Hard
+            Disk</emphasis> wizard is shown.
+          </para>
+
+          <figure id="fig-virtual-hard-disk-wizard">
+            <title>Create Virtual Hard Disk Wizard</title>
+      <mediaobject>
+        <imageobject>
+          <imagedata align="center" fileref="images/virtual-hard-disk-wizard.png"
+                     width="12cm" />
+        </imageobject>
+      </mediaobject>
+          </figure>
+        </listitem>
+
+        <listitem>
+          <para>
+            On the <emphasis role="bold">Virtual Hard Disk File
+            Type</emphasis> page, select a file type for the new virtual
+            hard disk image.
+          </para>
+
+          <para>
+            Click <emphasis role="bold">Next</emphasis>.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            On the <emphasis role="bold">Storage on Physical Hard
+            Disk</emphasis> page, select whether the size of the virtual
+            hard disk file is dynamically allocated or is of fixed size.
+          </para>
+
+          <para>
+            Click <emphasis role="bold">Next</emphasis>.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            On the <emphasis role="bold">File Location and
+            Size</emphasis> page, configure the location of the virtual
+            hard disk file and use the slider to set the size limit for
+            the virtual hard disk.
+          </para>
+
+          <para>
+            Click <emphasis role="bold">Finish</emphasis> to create the
+            virtual hard disk file.
+          </para>
+
+          <para>
+            The virtual hard disk image is created in the specified
+            location and added to the <emphasis role="bold">Hard
+            Disks</emphasis> tab in Virtual Media Manager.
+          </para>
+        </listitem>
+
+      </orderedlist>
+
+    </sect2>
+
+    <sect2 id="create-optical-disk-image">
+
+      <title>Creating a Virtual Optical Disk Image</title>
+
+      <para>
+        Use the <emphasis role="bold">VISO Creator</emphasis> tool to
+        create a virtual optical disk image. This enables you to create
+        a virtual ISO from selected files on the host.
+      </para>
+
+      <orderedlist>
+
+        <listitem>
+          <para>
+            Display the <emphasis role="bold">Optical Disks</emphasis>
+            tab in Virtual Media Manager and click
+            <emphasis role="bold">Create</emphasis>.
+          </para>
+
+          <para>
+            The <emphasis role="bold">VISO Creator</emphasis> tool is
+            shown.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Create the virtual ISO file.
+          </para>
+
+          <orderedlist>
+
+            <listitem>
+              <para>
+                Configure the name of the ISO file.
+              </para>
+
+              <para>
+                Click <emphasis role="bold">Configuration</emphasis> and
+                enter a name in the <emphasis role="bold">Viso
+                Name</emphasis> field.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                Add files to your virtual ISO.
+              </para>
+
+              <para>
+                In the <emphasis role="bold">Host File System</emphasis>
+                pane, select files to copy from the host system to the
+                virtual ISO.
+              </para>
+
+              <para>
+                Click <emphasis role="bold">Add Items To
+                VISO</emphasis>. The files are displayed in the
+                <emphasis role="bold">VISO Content</emphasis> pane.
+              </para>
+
+              <para>
+                The following file operations are also available:
+              </para>
+
+              <itemizedlist>
+
+                <listitem>
+                  <para>
+                    To create folders on the virtual ISO, click
+                    <emphasis role="bold">Create New
+                    Directory</emphasis>.
+                  </para>
+                </listitem>
+
+                <listitem>
+                  <para>
+                    To remove files from the virtual ISO, select files
+                    in the <emphasis role="bold">VISO Content</emphasis>
+                    pane and click <emphasis role="bold">Remove Items
+                    From VISO</emphasis>.
+                  </para>
+                </listitem>
+
+                <listitem>
+                  <para>
+                    To remove <emphasis>all</emphasis> files from the
+                    virtual ISO, click <emphasis role="bold">Reset the
+                    VISO Content</emphasis>.
+                  </para>
+                </listitem>
+
+              </itemizedlist>
+            </listitem>
+
+          </orderedlist>
+        </listitem>
+
+        <listitem>
+          <para>
+            Create the virtual ISO image.
+          </para>
+
+          <para>
+            Click <emphasis role="bold">Create</emphasis>.
+          </para>
+
+          <para>
+            A virtual ISO file with the specified name and content is
+            created.
+          </para>
+        </listitem>
+
+      </orderedlist>
+
+    </sect2>
+
+    <sect2 id="create-floppy-disk-image">
+
+      <title>Creating a Virtual Floppy Disk Image</title>
+
+      <para>
+        Use the <emphasis role="bold">Floppy Disk Creator</emphasis>
+        tool to create a floppy disk image.
+      </para>
+
+      <orderedlist>
+
+        <listitem>
+          <para>
+            Display the <emphasis role="bold">Floppy Disks</emphasis>
+            tab in Virtual Media Manager and click
+            <emphasis role="bold">Create</emphasis>.
+          </para>
+
+          <para>
+            The <emphasis role="bold">Floppy Disk Creator</emphasis>
+            tool is shown.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Configure the following settings:
+          </para>
+
+          <itemizedlist>
+
+            <listitem>
+              <para>
+                <emphasis role="bold">File Path:</emphasis> The name and
+                location of the floppy disk image.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                <emphasis role="bold">Size:</emphasis> Select from the
+                list of supported floppy disk sizes.
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                <emphasis role="bold">Format Disk as FAT 12:</emphasis>
+                This is the default format used for most floppy disks.
+                For an unformatted disk, do not select this option.
+              </para>
+            </listitem>
+
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para>
+            Create the floppy disk image file.
+          </para>
+
+          <para>
+            Click <emphasis role="bold">Create</emphasis>.
+          </para>
+
+          <para>
+            The floppy disk image is created in the specified location
+            and added to the <emphasis role="bold">Floppy
+            Disks</emphasis> tab in Virtual Media Manager.
+          </para>
+        </listitem>
+
+      </orderedlist>
+
+    </sect2>
+
   </sect1>
 
@@ -1121 +1412 @@
       <mediaobject>
         <imageobject>
-          <imagedata align="center" fileref="images/virtual-disk-manager2.png"
+          <imagedata align="center" fileref="images/virtual-disk-manager-2.png"
                      width="12cm" />
         </imageobject>

trunk/doc/manual/en_US/user_Technical.xml

@@ -92 +92 @@
         <listitem>
           <para>
-            On Linux, Mac OS X, and Oracle Solaris, this is generally
+            On Linux, macOS, and Oracle Solaris, this is generally
             taken from the environment variable
             <filename>$HOME</filename>, except for the user
@@ -105 +105 @@
             A typical location on Linux and Oracle Solaris is
             <filename>/home/<replaceable>username</replaceable></filename>
-            and on Mac OS X is
+            and on macOS is
             <filename>/Users/<replaceable>username</replaceable></filename>.
           </para>
@@ -152 +152 @@
         This is the default layout if you use the
         <emphasis role="bold">Create New Virtual Machine</emphasis>
-        wizard described in <xref linkend="gui-createvm" />. Once you
+        wizard described in <xref linkend="create-vm-wizard" />. Once you
         start working with the VM, additional files are added. Log files
         are in a subfolder called <filename>Logs</filename>, and if you
@@ -200 +200 @@
         <listitem>
           <para>
-            <emphasis role="bold">Mac OS X:</emphasis>
+            <emphasis role="bold">macOS:</emphasis>
             <filename>$HOME/Library/VirtualBox</filename>.
           </para>
@@ -362 +362 @@
           automatically by the first &product-name; client process and
           exits a short time after the last client exits. The first
-          &product-name; service can be the GUI,
+          &product-name; service can be &vbox-mgr;,
           <command>VBoxManage</command>,
           <command>VBoxHeadless</command>, the web service amongst
@@ -389 +389 @@
           application based on the cross-platform Qt library. When
           started without the <option>--startvm</option> option, this
-          application acts as the VirtualBox Manager, displaying the VMs
-          and their settings. It then communicates settings and state
-          changes to <command>VBoxSVC</command> and also reflects
-          changes effected through other means, such as the
-          <command>VBoxManage</command> command.
+          application acts as &vbox-mgr;, displaying the VMs and their
+          settings. It then communicates settings and state changes to
+          <command>VBoxSVC</command> and also reflects changes effected
+          through other means, such as the <command>VBoxManage</command>
+          command.
         </para>
       </listitem>
@@ -418 +418 @@
 
     <para>
-      The &product-name; GUI application is only one of several
-      available front ends, or clients. The complete list shipped with
-      &product-name; is as follows:
+      The &product-name; GUI application, called &vbox-mgr;, is only one
+      of several available front ends, or clients. The complete list
+      shipped with &product-name; is as follows:
     </para>
 
@@ -428 +428 @@
         <para>
           <command>VirtualBoxVM</command>: The Qt front end implementing
-          the VirtualBox Manager and running VMs.
+          &vbox-mgr; and running VMs.
         </para>
       </listitem>

trunk/doc/manual/en_US/user_Troubleshooting.xml

@@ -168 +168 @@
 
       <para>
-        For convenience, for each virtual machine, the VirtualBox
-        Manager window can show these logs in a window. To access it,
-        select a virtual machine from the list on the left and select
-        <emphasis role="bold">Show Log</emphasis> from the
-        <emphasis role="bold">Machine</emphasis> menu.
+        For convenience, for each virtual machine, &vbox-mgr; can show
+        these logs in a window. Select a virtual machine from the
+        machine list on the left and click
+        <emphasis role="bold">Logs</emphasis> in the machine tools menu.
       </para>
 
@@ -192 +191 @@
         <emphasis>crash dumps</emphasis>. This is true for both host and
         guest crashes. For information about enabling core dumps on
-        Linux, Oracle Solaris, and Mac OS X systems, refer to the
-        following core dump article on the &product-name; website:
+        Linux, Oracle Solaris, and macOS systems, refer to the following
+        core dump article on the &product-name; website:
       </para>
 
@@ -1672 +1671 @@
       <para>
         If a host-only adapter cannot be created, either with the
-        VirtualBox Manager or the <command>VBoxManage</command> command,
-        then the INF cache is probably corrupt. In this case, the
-        install log at
-        <filename>%windir%\inf\setupapi.dev.log</filename> would
+        &vbox-mgr; or the <command>VBoxManage</command> command, then
+        the INF cache is probably corrupt. In this case, the install log
+        at <filename>%windir%\inf\setupapi.dev.log</filename> would
         typically mention the failure to find a suitable driver package
         for the <filename>sun_VBoxNetAdp</filename> component. Again, as