VirtualBox

Changeset 87077 in vbox for trunk/doc/manual


Ignore:
Timestamp:
Dec 9, 2020 8:25:51 PM (4 years ago)
Author:
vboxsync
Message:

doc/manual: Integrate a collection of documentation improvements: sensitive terminology, diversity statement, clear messaging on what is eligible for enterprise support, OCI integration docs, export to OCI and incorrect UI doc referring to host-only networking when that place allows configuring NAT Networks

Location:
trunk/doc/manual/en_US
Files:
2 added
14 edited

Legend:

Unmodified
Added
Removed

  • trunk/doc/manual/en_US/oracle-accessibility-en.xml

    r76078 r87077  
    88<simplesect>
    99
    10 <!-- 
    11     Include this statement in the document Preface ONLY if your product 
    12     and/or documentation has been tested for accessibility, is determined 
     10<!--
     11    Include this statement in the document Preface ONLY if your product
     12    and/or documentation has been tested for accessibility, is determined
    1313    to be accessible, and has a VPAT.
    1414  -->
    … …  
    2222<?fo-linebreak?>
    2323
    24     <ulink url="http://www.oracle.com/pls/topic/lookup?ctx=acc&amp;id=docacc">http://www.oracle.com/pls/topic/lookup?ctx=acc&amp;id=docacc</ulink>.
     24    <ulink url="https://www.oracle.com/corporate/accessibility/"/>.
    2525  </para>
    2626

  • trunk/doc/manual/en_US/oracle-support-en.xml

    r76078 r87077  
    77]>
    88<simplesect>
    9  
     9
    1010  <!-- Include this statement in the document Preface -->
    1111
    … …  
    1818<?fo-linebreak?>
    1919
    20     <ulink url="http://www.oracle.com/pls/topic/lookup?ctx=acc&amp;id=info">http://www.oracle.com/pls/topic/lookup?ctx=acc&amp;id=info</ulink>
    21     or visit
    22     <ulink
    23       url="http://www.oracle.com/pls/topic/lookup?ctx=acc&amp;id=trs">http://www.oracle.com/pls/topic/lookup?ctx=acc&amp;id=trs</ulink>
    24     if you are hearing impaired.
     20    <ulink url="https://www.oracle.com/corporate/accessibility/learning-support.html#support-tab"/>.
    2521  </para>
    2622

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

    r85929 r87077  
    2121      When a guest operating system is running in a virtual machine, it
    2222      might be desirable to perform coordinated and automated logins
    23       using credentials from a master login system. Credentials are user
     23      using credentials passed from the host. Credentials are user
    2424      name, password, and domain name, where each value might be empty.
    2525    </para>
    … …  
    14361436          Mac OS X host, instead of the above device specification use
    14371437          for example <filename>/dev/rdisk1</filename>. Note that on Mac
    1438           OS X you can only get access to entire disk if no volume is
     1438          OS X you can only get access to an entire disk if no volume is
    14391439          mounted from it.
    14401440        </para>
    … …  
    28752875
    28762876      <para>
    2877         You can disable, or blacklist, certain entries in the global
    2878         settings page of the VM selector:
     2877        You can disable certain entries in the global settings page of
     2878        the VM selector:
    28792879      </para>
    28802880
    … …  
    30083008
    30093009      <para>
    3010         You can disable, or blacklist, certain menu actions in the VM
    3011         window:
     3010        You can disable certain menu actions in the VM window:
    30123011      </para>
    30133012
    … …  
    31383137
    31393138      <para>
    3140         You can also disable, or blacklist, certain menu actions of
    3141         certain menus. Use the following command to disable certain
    3142         actions of the <emphasis role="bold">Application</emphasis>
    3143         menu. This is only available on Mac OS X hosts.
     3139        You can also disable certain menu actions of certain menus. Use
     3140        the following command to disable certain actions of the
     3141        <emphasis role="bold">Application</emphasis> menu. This is only
     3142        available on Mac OS X hosts.
    31443143      </para>
    31453144
    … …  
    41684167
    41694168      <para>
    4170         You can disable, or blacklist, certain status bar items:
     4169        You can disable certain status bar items:
    41714170      </para>
    41724171
    … …  
    43274326
    43284327      <para>
    4329         You can disable, or blacklist, certain VM visual modes:
     4328        You can disable certain VM visual modes:
    43304329      </para>
    43314330
    … …  
    46774676
    46784677      <para>
    4679         You can disallow, or blacklist, certain actions when terminating
    4680         a VM. To disallow specific actions, use the following command:
     4678        You can disallow certain actions when terminating a VM. To
     4679        disallow specific actions, use the following command:
    46814680      </para>
    46824681
    … …  
    60876086      <para>
    60886087        On Windows, autostart functionality consist of two components.
    6089         First one is configuration file where the administrator can both
    6090         set delayed start of the VMs and temporary disable autostarting
    6091         for the particular user. The configuration file should be located
    6092         in the folder accessible by all required users but it should have
    6093         permissions allowing the only reading by everyone but
    6094         administrators. The configuration file contains several options.
    6095         One is <literal>default_policy</literal> which controls whether the
    6096         autostart service allows or denies to start a VM for users which
    6097         are not in the exception list. The exception list starts with
     6088        The first component is a configuration file where the
     6089        administrator can both set a delayed start for the VMs and
     6090        temporarily disable autostarting for a particular user. The
     6091        configuration file should be located in a folder accessible by
     6092        all required users but it should have permissions allowing only
     6093        reading by everyone but administrators. The configuration file
     6094        contains several options. The
     6095        <literal>default_policy</literal> controls whether the autostart
     6096        service allows or denies starting of a VM for users that are not
     6097        in the exception list. The exception list starts with
    60986098        <literal>exception_list</literal> and contains a comma separated
    6099         list with usernames. Furthermore a separate startup delay can be
    6100         configured for every user to avoid overloading the host. A
     6099        list with usernames. Furthermore, a separate startup delay can
     6100        be configured for every user to avoid overloading the host. A
    61016101        sample configuration is given below:
    61026102      </para>
    61036103
    61046104<screen>
    6105 # Default policy is to deny starting a VM, the other option is "allow".
    6106 default_policy = deny
    6107 
    6108 # Bob is allowed to start virtual machines but starting them
    6109 # will be delayed for 10 seconds
    6110 bob = {
    6111     allow = true
    6112     startup_delay = 10
    6113 }
    6114 
    6115 # Alice is not allowed to start virtual machines, useful to exclude certain users
    6116 # if the default policy is set to allow.
    6117 alice = {
    6118     allow = false
    6119 }
     6105        # Default policy is to deny starting a VM, the other option is "allow".
     6106        default_policy = deny
     6107
     6108        # Bob is allowed to start virtual machines but starting them
     6109        # will be delayed for 10 seconds
     6110        bob = {
     6111            allow = true
     6112            startup_delay = 10
     6113        }
     6114
     6115        # Alice is not allowed to start virtual machines, useful to exclude certain users
     6116        # if the default policy is set to allow.
     6117        alice = {
     6118            allow = false
     6119        }
    61206120</screen>
    61216121
    61226122      <para>
    6123         The user name can be specified using the following forms: "user",
    6124         "domain\user", ".\user" and "user@domain". Administrator must add
    6125         the <literal>VBOXAUTOSTART_CONFIG</literal> environment variable into
    6126         system variables containing the path to the configuration file
    6127         described above. The environment variable tells the autostart services
    6128         what configuration file is used.
    6129       </para>
    6130 
    6131       <para>
    6132         Second component of autostart functionality is Windows service, every
    6133         instance of it works on behalf of particular user using its own
    6134         credentials.
     6123        The user name can be specified using the following forms:
     6124        "user", "domain\user", ".\user" and "user@domain". An
     6125        administrator must add the
     6126        <literal>VBOXAUTOSTART_CONFIG</literal> environment variable
     6127        into system variables containing the path to the configuration
     6128        file described above. The environment variable tells the
     6129        autostart services which configuration file is used.
     6130      </para>
     6131
     6132      <para>
     6133        The second component of autostart functionality is a Windows
     6134        service. Every instance of this works on behalf of a particular
     6135        user using their credentials.
    61356136      </para>
    61366137
    … …  
    61406141      </para>
    61416142
    6142   <screen>VBoxAutostartSvc install --user=<replaceable>user</replaceable> [--password-file=<replaceable>password_file</replaceable>]</screen>
     6143<screen>VBoxAutostartSvc install --user=<replaceable>user</replaceable> [--password-file=<replaceable>password_file</replaceable>]</screen>
    61436144
    61446145      <para>
    … …  
    61536154      </para>
    61546155
    6155   <screen>VBoxAutostartSvc delete --user=<replaceable>user</replaceable></screen>
     6156<screen>VBoxAutostartSvc delete --user=<replaceable>user</replaceable></screen>
    61566157
    61576158      <para>
    … …  
    61646165
    61656166      <para>
    6166         Finally, the particular user should define which VM should be
    6167         started at boot or not. The user should run the following command
    6168         for every VM it desired to start at boot:
    6169       </para>
    6170 
    6171   <screen>VBoxManage modifyvm <replaceable>VM name or UUID</replaceable> --autostart-enabled on</screen>
    6172 
    6173       <para>
    6174         The user can remove the particular VM from the VMs starting at boot
    6175         by running the following command:
    6176       </para>
    6177 
    6178   <screen>VBoxManage modifyvm <replaceable>VM name or UUID</replaceable> --autostart-enabled off</screen>
     6167        Finally, the user should define which VMs should be started at
     6168        boot. The user should run the following command for every VM
     6169        they wish to start at boot:
     6170      </para>
     6171
     6172<screen>VBoxManage modifyvm <replaceable>VM name or UUID</replaceable> --autostart-enabled on</screen>
     6173
     6174      <para>
     6175        The user can remove a particular VM from the VMs starting at
     6176        boot by running the following command:
     6177      </para>
     6178
     6179<screen>VBoxManage modifyvm <replaceable>VM name or UUID</replaceable> --autostart-enabled off</screen>
    61796180
    61806181    </sect2>

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

    r82350 r87077  
    5454    <para>
    5555      Because &product-name; is designed to provide a generic
    56       virtualization environment for x86 systems, it can run operating
    57       systems (OSes) of any kind. However, &product-name; focuses on the
    58       following guest systems:
     56      virtualization environment for x86 systems, it can run guest
     57      operating systems (OSes) of any kind.
     58    </para>
     59
     60    <para>
     61      The following guest OS platforms are supported:
    5962    </para>
    6063
    … …  
    6366      <listitem>
    6467        <para>
    65           <emphasis role="bold">Windows NT 4.0:</emphasis>
    66         </para>
    67 
    68         <itemizedlist>
    69 
    70           <listitem>
    71             <para>
    72               Fully supports all versions, editions, and service packs.
    73               Note that you might encounter issues with some older
    74               service packs, so install at least service pack 6a.
    75             </para>
    76           </listitem>
    77 
    78           <listitem>
    79             <para>
    80               Guest Additions are available with a limited feature set.
    81             </para>
    82           </listitem>
    83 
    84         </itemizedlist>
     68          <emphasis role="bold">Platforms With Full Support.</emphasis>
     69          These guest OS platforms qualify for Oracle Premier Support.
     70          See <xref linkend="table-premier-support"/>.
     71        </para>
    8572      </listitem>
    8673
    8774      <listitem>
    8875        <para>
    89           <emphasis role="bold">Windows 2000, Windows XP, Windows Server
    90           2003, Windows Vista, Windows Server 2008, Windows 7, Windows
    91           Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1,
    92           Windows Server 2012 R2, Windows 10 (non-Insider Preview
    93           releases), Windows Server 2016, Windows Server
    94           2019:</emphasis>
    95         </para>
    96 
    97         <itemizedlist>
    98 
    99           <listitem>
    100             <para>
    101               Fully supports all versions, editions, and service packs,
    102               including 64-bit versions.
    103             </para>
    104           </listitem>
    105 
    106           <listitem>
    107             <para>
    108               Note that you must enable hardware virtualization when
    109               running at least Windows 8.
    110             </para>
    111           </listitem>
    112 
    113           <listitem>
    114             <para>
    115               Guest Additions are available.
    116             </para>
    117           </listitem>
    118 
    119         </itemizedlist>
     76          <emphasis role="bold">Platforms With Limited
     77          Support.</emphasis> These legacy guest OS platforms can be
     78          used with &product-name;, but only qualify for <emphasis>best
     79          effort</emphasis> support. Therefore, resolution of customer
     80          issues is not guaranteed. See
     81          <xref linkend="table-limited-support"/>.
     82        </para>
    12083      </listitem>
    12184
    122       <listitem>
    123         <para>
    124           <emphasis role="bold">MS-DOS, Windows 3.x, Windows 95, Windows
    125           98, Windows ME:</emphasis>
    126         </para>
    127 
    128         <itemizedlist>
    129 
    130           <listitem>
    131             <para>
    132               Limited testing has been performed.
    133             </para>
    134           </listitem>
    135 
    136           <listitem>
    137             <para>
    138               Use beyond legacy installation mechanisms is not
    139               recommended.
    140             </para>
    141           </listitem>
    142 
    143           <listitem>
    144             <para>
    145               Guest Additions are not available.
    146             </para>
    147           </listitem>
    148 
    149         </itemizedlist>
    150       </listitem>
    151 
    152       <listitem>
    153         <para>
    154           <emphasis role="bold">Linux 2.4:</emphasis>
    155         </para>
    156 
    157         <para>
    158           Limited support.
    159         </para>
    160       </listitem>
    161 
    162       <listitem>
    163         <para>
    164           <emphasis role="bold">Linux 2.6:</emphasis>
    165         </para>
    166 
    167         <itemizedlist>
    168 
    169           <listitem>
    170             <para>
    171               Fully supports all versions and editions, both 32-bit and
    172               64-bit.
    173             </para>
    174           </listitem>
    175 
    176           <listitem>
    177             <para>
    178               For best performance, use at least Linux kernel version
    179               2.6.13.
    180             </para>
    181           </listitem>
    182 
    183           <listitem>
    184             <para>
    185               Guest Additions are available.
    186             </para>
    187           </listitem>
    188 
    189         </itemizedlist>
    190 
    191         <note>
    192           <para>
    193             Certain Linux kernel releases have bugs that prevent them
    194             from executing in a virtual environment. See
    195             <xref linkend="ts_linux-buggy" />.
    196           </para>
    197         </note>
    198       </listitem>
    199 
    200       <listitem>
    201         <para>
    202           <emphasis role="bold">Linux 3.x and later:</emphasis>
    203         </para>
    204 
    205         <itemizedlist>
    206 
    207           <listitem>
    208             <para>
    209               Fully supports all versions and editions, both 32-bit and
    210               64-bit.
    211             </para>
    212           </listitem>
    213 
    214           <listitem>
    215             <para>
    216               Guest Additions are available.
    217             </para>
    218           </listitem>
    219 
    220         </itemizedlist>
    221       </listitem>
    222 
    223       <listitem>
    224         <para>
    225           <emphasis role="bold"> Oracle Solaris 10 and Oracle Solaris
    226           11:</emphasis>
    227         </para>
    228 
    229         <itemizedlist>
    230 
    231           <listitem>
    232             <para>
    233               Fully supports all versions starting with Oracle Solaris
    234               10 8/08 and Oracle Solaris 11.
    235             </para>
    236           </listitem>
    237 
    238           <listitem>
    239             <para>
    240               Supports 64-bit prior to Oracle Solaris 11 11/11, and
    241               32-bit.
    242             </para>
    243           </listitem>
    244 
    245           <listitem>
    246             <para>
    247               Guest Additions are available.
    248             </para>
    249           </listitem>
    250 
    251         </itemizedlist>
    252       </listitem>
    253 
    254       <listitem>
    255         <para>
    256           <emphasis role="bold">FreeBSD:</emphasis>
    257         </para>
    258 
    259         <itemizedlist>
    260 
    261           <listitem>
    262             <para>
    263               Limited support.
    264             </para>
    265           </listitem>
    266 
    267           <listitem>
    268             <para>
    269               Note that you must enable hardware virtualization when
    270               running FreeBSD.
    271             </para>
    272           </listitem>
    273 
    274           <listitem>
    275             <para>
    276               Guest Additions are not available.
    277             </para>
    278           </listitem>
    279 
    280         </itemizedlist>
    281       </listitem>
    282 
    283       <listitem>
    284         <para>
    285           <emphasis role="bold"> OpenBSD:</emphasis>
    286         </para>
    287 
    288         <itemizedlist>
    289 
    290           <listitem>
    291             <para>
    292               Supports at least version 3.7.
    293             </para>
    294           </listitem>
    295 
    296           <listitem>
    297             <para>
    298               Note that you must enable hardware virtualization when
    299               running OpenBSD.
    300             </para>
    301           </listitem>
    302 
    303           <listitem>
    304             <para>
    305               Guest Additions are not available.
    306             </para>
    307           </listitem>
    308 
    309         </itemizedlist>
    310       </listitem>
    311 
    312       <listitem>
    313         <para>
    314           <emphasis role="bold">OS/2 Warp 4.5:</emphasis>
    315         </para>
    316 
    317         <itemizedlist>
    318 
    319           <listitem>
    320             <para>
    321               Only MCP2 is supported. Other OS/2 versions might not
    322               work.
    323             </para>
    324           </listitem>
    325 
    326           <listitem>
    327             <para>
    328               Note that you must enable hardware virtualization when
    329               running OS/2 Warp 4.5.
    330             </para>
    331           </listitem>
    332 
    333           <listitem>
    334             <para>
    335               Guest Additions are available with a limited feature set.
    336               See <xref linkend="KnownIssues" />.
    337             </para>
    338           </listitem>
    339 
    340         </itemizedlist>
    341       </listitem>
    342 
    343       <listitem>
    344         <para>
    345           <emphasis role="bold">Mac OS X:</emphasis>
    346         </para>
    347 
    348         <itemizedlist>
    349 
    350           <listitem>
    351             <para>
    352               &product-name; 3.2 added experimental support for Mac OS X
    353               guests, with restrictions. See
    354               <xref linkend="intro-macosxguests"/> and
    355               <xref linkend="KnownIssues" />.
    356             </para>
    357           </listitem>
    358 
    359           <listitem>
    360             <para>
    361               Guest Additions are not available.
    362             </para>
    363           </listitem>
    364 
    365         </itemizedlist>
    366       </listitem>
    367 
    36885    </itemizedlist>
     86
     87    <table id="table-premier-support" tabstyle="oracle-all">
     88      <title>Guest Operating Systems With Full Support</title>
     89      <tgroup cols="2">
     90        <thead>
     91          <row>
     92            <entry><para>
     93                <emphasis role="bold">Operating System</emphasis>
     94              </para></entry>
     95            <entry><para>
     96                <emphasis role="bold">Comments</emphasis>
     97              </para></entry>
     98          </row>
     99        </thead>
     100        <tbody>
     101          <row>
     102            <entry><para>
     103                Windows 10 (32-bit and 64-bit)
     104              </para></entry>
     105            <entry><para>
     106                Insider preview builds are not supported
     107              </para></entry>
     108          </row>
     109          <row>
     110            <entry><para>
     111                Windows 8 and 8.1 (32-bit and 64-bit)
     112              </para></entry>
     113            <entry><para></para></entry>
     114          </row>
     115          <row>
     116            <entry><para>
     117                Windows Server 2019 (64-bit)
     118              </para></entry>
     119            <entry><para></para></entry>
     120          </row>
     121          <row>
     122            <entry><para>
     123                Windows Server 2016 (64-bit)
     124              </para></entry>
     125            <entry><para></para></entry>
     126          </row>
     127          <row>
     128            <entry><para>
     129                Windows Server 2012 and 2012 R2 (64-bit)
     130              </para></entry>
     131            <entry><para></para></entry>
     132          </row>
     133          <row>
     134            <entry><para>
     135                Solaris 11 (32-bit and 64-bit)
     136              </para></entry>
     137            <entry><para></para></entry>
     138          </row>
     139          <row>
     140            <entry><para>
     141                Solaris 10 8/11 Update 10 and later (32-bit and 64-bit)
     142              </para></entry>
     143            <entry><para></para></entry>
     144          </row>
     145          <row>
     146            <entry><para>
     147                Oracle Linux 8 (64-bit)
     148              </para></entry>
     149            <entry><para>
     150                Includes Red Hat Enterprise Linux 8, CentOS 8
     151              </para></entry>
     152          </row>
     153          <row>
     154            <entry><para>
     155                Oracle Linux 7 (64-bit)
     156              </para></entry>
     157            <entry><para>
     158                Includes Red Hat Enterprise Linux 7, CentOS 7
     159              </para></entry>
     160          </row>
     161          <row>
     162            <entry><para>
     163                Oracle Linux 6 (32-bit and 64-bit)
     164              </para></entry>
     165            <entry><para>
     166                Includes Red Hat Enterprise Linux 6, CentOS 6
     167              </para></entry>
     168          </row>
     169          <row>
     170            <entry><para>
     171                Ubuntu 16.04 LTS (Xenial Xerus) (32-bit and 64-bit)
     172              </para></entry>
     173            <entry><para></para></entry>
     174          </row>
     175          <row>
     176            <entry><para>
     177                Ubuntu 18.04 LTS (Bionic Beaver) (64-bit)
     178              </para></entry>
     179            <entry><para></para></entry>
     180          </row>
     181          <row>
     182            <entry><para>
     183                Ubuntu 20.04 LTS (Focal Fossa) (64-bit)
     184              </para></entry>
     185            <entry><para></para></entry>
     186          </row>
     187          <row>
     188            <entry><para>
     189                SUSE Linux Enterprise Server 15 (64-bit)
     190              </para></entry>
     191            <entry><para></para></entry>
     192          </row>
     193          <row>
     194            <entry><para>
     195                SUSE Linux Enterprise Server 12 (64-bit)
     196              </para></entry>
     197            <entry><para></para></entry>
     198          </row>
     199        </tbody>
     200      </tgroup>
     201    </table>
     202
     203    <table id="table-limited-support" tabstyle="oracle-all">
     204      <title>Legacy Guest Operating Systems With Limited Support</title>
     205      <tgroup cols="2">
     206        <thead>
     207          <row>
     208            <entry><para>
     209                <emphasis role="bold">Operating System</emphasis>
     210              </para></entry>
     211            <entry><para>
     212                <emphasis role="bold">Comments</emphasis>
     213              </para></entry>
     214          </row>
     215        </thead>
     216        <tbody>
     217          <row>
     218            <entry><para>
     219                Windows 7 (32-bit and 64-bit)
     220              </para></entry>
     221            <entry><para></para></entry>
     222          </row>
     223          <row>
     224            <entry><para>
     225                Windows Vista SP2 and later (32-bit and 64-bit)
     226              </para></entry>
     227            <entry><para></para></entry>
     228          </row>
     229          <row>
     230            <entry><para>
     231                Windows XP (32-bit)
     232              </para></entry>
     233            <entry><para></para></entry>
     234          </row>
     235          <row>
     236            <entry><para>
     237                Windows Vista (32-bit)
     238              </para></entry>
     239            <entry><para></para></entry>
     240          </row>
     241          <row>
     242            <entry><para>
     243                Windows Server 2008 and 2008 R2 (32-bit and 64-bit)
     244              </para></entry>
     245            <entry><para></para></entry>
     246          </row>
     247          <row>
     248            <entry><para>
     249                Windows Server 2003 (32-bit and 64-bit)
     250              </para></entry>
     251            <entry><para></para></entry>
     252          </row>
     253          <row>
     254            <entry><para>
     255                Oracle Linux 5 (32-bit and 64-bit)
     256              </para></entry>
     257            <entry><para>
     258                Includes Red Hat Enterprise Linux 5, CentOS 5
     259              </para></entry>
     260          </row>
     261          <row>
     262            <entry><para>
     263                Ubuntu 14.04.5 LTS (Trusty Tahr) (32-bit and 64-bit)
     264              </para></entry>
     265            <entry><para></para></entry>
     266          </row>
     267          <row>
     268            <entry><para>
     269                OS/2 Warp 4.5
     270              </para></entry>
     271            <entry><para></para></entry>
     272          </row>
     273        </tbody>
     274      </tgroup>
     275    </table>
    369276
    370277    <sect2 id="intro-macosxguests">
    … …  
    18091716        </imageobject>
    18101717      </mediaobject>
    1811       </figure>
     1718    </figure>
    18121719
    18131720    <para>
    … …  
    18211728        <para>
    18221729          <emphasis role="bold">IDE controller.</emphasis> A virtual
    1823           CD/DVD drive is attached to the secondary master port of the
    1824           IDE controller.
     1730          CD/DVD drive is attached to device 0 on the secondary channel
     1731          of the IDE controller.
    18251732        </para>
    18261733      </listitem>
    … …  
    19191826              The <emphasis role="bold">device slot</emphasis> of the
    19201827              controller that the virtual disk is connected to. IDE
    1921               controllers have four slots which have traditionally been
    1922               called primary master, primary slave, secondary master,
    1923               and secondary slave. By contrast, SATA and SCSI
    1924               controllers offer you up to 30 slots for attaching virtual
    1925               devices.
     1828              controllers have four slots: primary device 0, primary
     1829              device 1, secondary device 0, and secondary device 1. By
     1830              contrast, SATA and SCSI controllers offer you up to 30
     1831              slots for attaching virtual devices.
    19261832            </para>
    19271833          </listitem>

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

    r82350 r87077  
    66]>
    77<glossary id="Glossary">
    8 
    98  <glossdiv>
    109

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

    r86093 r87077  
    200200      <literal>/VirtualBox/GuestAdd/CheckHostVersion</literal> guest
    201201      property to <literal>0</literal>. See
    202       <xref
    203     linkend="guestadd-guestprops" />.
     202      <xref linkend="guestadd-guestprops" />.
    204203    </para>
    205204
    … …  
    986985        running OS/2 in a virtual machine. Due to restrictions of OS/2
    987986        itself, this variant of the Guest Additions has a limited
    988         feature set. See <xref
    989       linkend="KnownIssues" /> for
    990         details.
     987        feature set. See <xref linkend="KnownIssues" /> for details.
    991988      </para>
    992989
    … …  
    10951092        <para>
    10961093          Transient shares, that are added at runtime and disappear when
    1097           the VM is powered off. These can be created using a checkbox
     1094          the VM is powered off. These can be created using a check box
    10981095          in the VirtualBox Manager, or by using the
    10991096          <option>--transient</option> option of the <command>VBoxManage
    … …  
    11081105      that the guest is either allowed to both read and write, or just
    11091106      read files on the host. By default, shared folders are read-write.
    1110       Read-only folders can be created using a checkbox in the
     1107      Read-only folders can be created using a check box in the
    11111108      VirtualBox Manager, or with the <option>--readonly</option> option
    11121109      of the <command>VBoxManage sharedfolder add</command> command.
    … …  
    11651162            shared folder to your Windows guest, open Windows Explorer
    11661163            and look for the folder in <emphasis role="bold">My
    1167             Networking Place</emphasis>s, <emphasis role="bold">Entire
     1164            Networking Places</emphasis>, <emphasis role="bold">Entire
    11681165            Network</emphasis>, <emphasis role="bold">&product-name;
    11691166            Shared Folders</emphasis>. By right-clicking on a shared
    … …  
    13961393      In the context of using drag and drop, the origin of the data is
    13971394      called the <emphasis>source</emphasis>. That is, where the actual
    1398       data comes from and is specified. The <emphasis>destination</emphasis>
    1399       specifies where the data from the source should go to.
    1400       Transferring data from the source to the destination can be done in
    1401       various ways, such as copying, moving, or linking.
     1395      data comes from and is specified. The
     1396      <emphasis>destination</emphasis> specifies where the data from the
     1397      source should go to. Transferring data from the source to the
     1398      destination can be done in various ways, such as copying, moving,
     1399      or linking.
    14021400    </para>
    14031401
    … …  
    14131411      this case is the source, whereas the guest OS is the destination.
    14141412      However, when transferring data from the guest OS to the host, the
    1415       guest OS this time became the source and the host is the destination.
     1413      guest OS this time became the source and the host is the
     1414      destination.
    14161415    </para>
    14171416
    … …  
    14961495        As &product-name; can run on a variety of host operating systems
    14971496        and also supports a wide range of guests, certain data formats
    1498         must be translated after transfer. This is so that the destination
    1499         operating system, which receiving the data, is able to handle
    1500         them in an appropriate manner.
     1497        must be translated after transfer. This is so that the
     1498        destination operating system, which receives the data, is able
     1499        to handle them in an appropriate manner.
    15011500      </para>
    15021501
    … …  
    15621561      <para>
    15631562        On Linux hosts and guests, programs can query for drag and drop
    1564         data while the drag operation still is in progress (e.g. on LXDE
    1565         using the PCManFM file manager). This currently is not supported.
    1566 
    1567         As a workaround, a different file manager (e.g. Nautilus) can
    1568         be used instead.
     1563        data while the drag operation is still in progress. For example,
     1564        on LXDE using the PCManFM file manager. This currently is not
     1565        supported. As a workaround, a different file manager, such as
     1566        Nautilus, can be used instead.
    15691567      </para>
    15701568
    … …  
    21472145
    21482146    <para>
    2149       The Guest Additions for Windows and Linux allow for automatic updating.
    2150       This applies for already installed Guest Additions versions. Also,
    2151       copying files from/to the host as well as various other file system
    2152       operations are available.
     2147      The Guest Additions for Windows allow for automatic updating. This
     2148      applies for already installed Guest Additions versions. Also,
     2149      copying files from host to the guest as well as remotely creating
     2150      guest directories is available.
    21532151    </para>
    21542152
    … …  
    24032401
    24042402      <para>
    2405         The Guest Additions provide necessary services to enable controlling
    2406         the guest system's monitor topology. My monitor topology the resolution
    2407         of each virtual monitor and its state are meant (disabled/enabled). The
    2408         resolution of a virtual monitor can be modified from the host side either
    2409         by resizing the window that hosts the virtual monitor or thru the view menu.
    2410         On guest operating systems with X11/Wayland desktops this is achieved by
    2411         either of two following services:
     2403        The Guest Additions provide services for controlling the guest
     2404        system's monitor topology. Monitor topology means the resolution
     2405        of each virtual monitor and its state (disabled/enabled). The
     2406        resolution of a virtual monitor can be modified from the host
     2407        side either by resizing the window that hosts the virtual monitor,
     2408        through the view menu or through
     2409        <code>VBoxManage controlvm "vmname" setscreenlayout</code>.
     2410        On guest operating systems with X11/Wayland desktops this is
     2411        put into effect by either of two following services:
    24122412      </para>
    24132413
    … …  
    24182418
    24192419      <para>
    2420         Here are some details about guest screen resolution control functionality:
     2420        Here are some details about guest screen resolution control
     2421        functionality:
    24212422      </para>
    24222423
    … …  
    24262427          <para>
    24272428            On X11/Wayland desktops the resizing service is started during
    2428             desktop session initialization, that is desktop login. On X11 desktops
    2429             VBoxClient --vmsvga service handles screen topology thru xrandr calls.
    2430             On Wayland clients VBoxDRMClient is used. The decision of choosing either
    2431             of these clients is done automatically at each desktop session start.
    2432           </para>
    2433         </listitem>
    2434         <listitem>
    2435           <para>
    2436             On 32 bit guest OSs VBoxDRMClient, which is run during desktop
    2437             session start, is used. The guest OS bitness check and choice
    2438             of the service is done automatically.
    2439           </para>
    2440         </listitem>
    2441         <listitem>
    2442           <para>
    2443             Since the mentioned monitor topology control services are initialized during
    2444             the desktop session start, display managers' (gdm, lightdm, etc.) resolution
    2445             cannot be controlled. This default behavior can be changed by setting the
    2446             following guest property of the virtual machine to any value.
    2447             <screen>
    2448               /VirtualBox/GuestAdd/DRMResize
    2449             </screen>
    2450             Please refer to <xref linkend="guestadd-guestprops" /> for how to set/delete
    2451             guest properties. When this guest property is set then VBoxDRMClient is started
    2452             during the guest OS boot and stays active for both display manager's login screen
    2453             and desktop session.
     2429            desktop session initialization, that is desktop login. On X11
     2430            desktops <code>VBoxClient --vmsvga</code> handles screen
     2431            topology through the RandR extension.
     2432            On Wayland clients <code>VBoxDRMClient</code> is used. The
     2433            decision is made automatically at each desktop session start.
     2434          </para>
     2435        </listitem>
     2436        <listitem>
     2437          <para>
     2438            On 32 bit guest operating systems <code>VBoxDRMClient</code>
     2439            is always used, in order to work around bugs.
     2440          </para>
     2441        </listitem>
     2442        <listitem>
     2443          <para>
     2444            Since the mentioned monitor topology control services are
     2445            initialized during the desktop session start, it is impossible
     2446            to control the monitor resolution of display managers such as
     2447            gdm, lightdm. This default behavior can be changed by setting
     2448            the guest property <code>/VirtualBox/GuestAdd/DRMResize</code>
     2449            of the virtual machine to any value. Please refer to
     2450            <xref linkend="guestadd-guestprops" /> for updating guest
     2451            properties. When this guest property is set then
     2452            <code>VBoxDRMClient</code> is started during the guest OS boot
     2453            and stays active all the time, for both ithe display manager
     2454            login screen and the desktop session.
    24542455          </para>
    24552456        </listitem>
    … …  
    24612462        <title>Known Limitations</title>
    24622463        <para>
    2463           VBoxDRMClient is not able to handle arbitrary guest monitor topologies. Specifically,
    2464           disabling a guest monitor (except the last one) invalidates the monitor topology. That
    2465           is, when the guest is configured to have 4 monitors, disabling 2nd or 3rd monitor is not
    2466           recommended.
     2464          <code>VBoxDRMClient</code> is not able to handle arbitrary guest
     2465          monitor topologies. Specifically, disabling a guest monitor
     2466          (except the last one) invalidates the monitor topology due to
     2467          limitations in the Linux kernel module <code>vmwgfx.ko</code>.
     2468          iFor example, when the guest is configured to have 4 monitors
     2469          it is not recommended to disable the 2nd or 3rd monitor.
    24672470        </para>
    24682471

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

    r87049 r87077  
    165165      <listitem>
    166166        <para>
    167           <emphasis role="strong">Host operating system (host
     167          <emphasis role="bold">Host operating system (host
    168168          OS).</emphasis> This is the OS of the physical computer on
    169169          which &product-name; was installed. There are versions of
    … …  
    181181      <listitem>
    182182        <para>
    183           <emphasis role="strong">Guest operating system (guest
     183          <emphasis role="bold">Guest operating system (guest
    184184          OS).</emphasis> This is the OS that is running inside the
    185185          virtual machine. Theoretically, &product-name; can run any x86
    … …  
    200200      <listitem>
    201201        <para>
    202           <emphasis role="strong">Virtual machine (VM).</emphasis> This
    203           is the special environment that &product-name; creates for
    204           your guest OS while it is running. In other words, you run
    205           your guest OS <emphasis>in</emphasis> a VM. Normally, a VM is
    206           shown as a window on your computer's desktop. Depending on
    207           which of the various frontends of &product-name; you use, the
    208           VM might be shown in full screen mode or remotely on another
    209           computer.
     202          <emphasis role="bold">Virtual machine (VM).</emphasis> This is
     203          the special environment that &product-name; creates for your
     204          guest OS while it is running. In other words, you run your
     205          guest OS <emphasis>in</emphasis> a VM. Normally, a VM is shown
     206          as a window on your computer's desktop. Depending on which of
     207          the various frontends of &product-name; you use, the VM might
     208          be shown in full screen mode or remotely on another computer.
    210209        </para>
    211210
    … …  
    228227      <listitem>
    229228        <para>
    230           <emphasis role="strong">Guest Additions.</emphasis> This
    231           refers to special software packages which are shipped with
     229          <emphasis role="bold">Guest Additions.</emphasis> This refers
     230          to special software packages which are shipped with
    232231          &product-name; but designed to be installed
    233232          <emphasis>inside</emphasis> a VM to improve performance of the
    … …  
    672671          <listitem>
    673672            <para>
    674               Red Hat Enterprise Linux 6, 7 and 8
     673              CentOS/Red Hat Enterprise Linux 6, 7 and 8
    675674            </para>
    676675          </listitem>
    … …  
    737736
    738737    <para>
    739       Note that the above list is informal. Oracle support for customers
    740       who have a support contract is limited to a subset of the listed
    741       host OSes. Also, any feature which is marked as
     738      Note that any feature which is marked as
    742739      <emphasis>experimental</emphasis> is not supported. Feedback and
    743740      suggestions about such features are welcome.
    … …  
    791788          functionality of the &product-name; base package. Currently,
    792789          Oracle provides a single extension pack, available from:
    793           <ulink
    794           url="http://www.virtualbox.org" />. The
    795           extension pack provides the following added functionality:
    796         </para>
    797 
    798         <orderedlist>
     790          <ulink url="http://www.virtualbox.org" />. The extension pack
     791          provides the following added functionality:
     792        </para>
     793
     794        <itemizedlist>
    799795
    800796          <listitem>
    … …  
    808804            <para>
    809805              The virtual USB 3.0 (xHCI) device. See
    810               <xref
    811                 linkend="settings-usb" />.
     806              <xref linkend="settings-usb" />.
    812807            </para>
    813808          </listitem>
    … …  
    847842          </listitem>
    848843
    849         </orderedlist>
     844          <listitem>
     845            <para>
     846              Cloud integration features. See <xref linkend="ovf"/>.
     847            </para>
     848          </listitem>
     849
     850        </itemizedlist>
    850851
    851852        <para>
    … …  
    930931    <figure id="fig-vbox-manager-initial">
    931932      <title>VirtualBox Manager Window, After Initial Startup</title>
    932       <mediaobject>
     933    <mediaobject>
    933934        <imageobject>
    934935          <imagedata align="center" fileref="images/virtualbox-main-empty.png"
    … …  
    965966    <figure id="fig-vbox-manager-populated">
    966967      <title>VirtualBox Manager Window, After Creating Virtual Machines</title>
    967       <mediaobject>
     968    <mediaobject>
    968969        <imageobject>
    969970          <imagedata align="center" fileref="images/virtualbox-main.png"
    … …  
    987988    <figure id="fig-new-vm-name">
    988989      <title>Creating a New Virtual Machine: Name and Operating System</title>
    989       <mediaobject>
     990    <mediaobject>
    990991        <imageobject>
    991992          <imagedata align="center" fileref="images/create-vm-1.png"
    … …  
    11111112        <figure id="fig-new-vm-hard-disk">
    11121113          <title>Creating a New Virtual Machine: Hard Disk</title>
    1113          <mediaobject>
     1114        <mediaobject>
    11141115            <imageobject>
    11151116              <imagedata align="center" fileref="images/create-vm-2.png"
    … …  
    12161217        <figure id="fig-new-vm-vdi">
    12171218          <title>Creating a New Virtual Machine: File Location and Size</title>
    1218           <mediaobject>
     1219        <mediaobject>
    12191220            <imageobject>
    12201221              <imagedata align="center" fileref="images/create-vdi-1.png"
    … …  
    14291430          </imageobject>
    14301431        </mediaobject>
     1432
    14311433      </figure>
    14321434
    … …  
    18771879        </imageobject>
    18781880      </mediaobject>
     1881
    18791882    </figure>
    18801883
    … …  
    25672570          <emphasis role="bold">Cloud service formats.</emphasis> Export
    25682571          to and import from cloud services such as &oci; is supported.
    2569           See the following topics:
    2570         </para>
    2571 
    2572         <itemizedlist>
    2573 
    2574           <listitem>
    2575             <para>
    2576               <xref linkend="cloud-export-oci"/>
    2577             </para>
    2578           </listitem>
    2579 
    2580           <listitem>
    2581             <para>
    2582               <xref linkend="cloud-import-oci"/>
    2583             </para>
    2584           </listitem>
    2585 
    2586         </itemizedlist>
    2587 
    2588         <para>
    2589           Before using &product-name; with &oci; there are some initial
    2590           configuration steps you need to consider. See
    2591           <xref linkend="cloud-integration-steps"/>.
    2592         </para>
    2593 
    2594         <para>
    2595           &product-name; can also be used to create new instances from a
    2596           custom image stored on &oci;. See
    2597           <xref linkend="cloud-new-vm"/>
     2572          See <xref linkend="cloud-integration"/>.
    25982573        </para>
    25992574      </listitem>
    … …  
    27252700              </imageobject>
    27262701            </mediaobject>
     2702
    27272703          </figure>
    27282704
    … …  
    29382914    </sect2>
    29392915
     2916  </sect1>
     2917
     2918  <sect1 id="cloud-integration">
     2919
     2920    <title>Integrating with &oci;</title>
     2921
     2922    <para>
     2923      This section describes how to use the features of &product-name;
     2924      to integrate with &oci;.
     2925    </para>
     2926
     2927    <para>
     2928      Integrating with &oci; involves the following steps:
     2929    </para>
     2930
     2931    <itemizedlist>
     2932
     2933      <listitem>
     2934        <para>
     2935          <emphasis role="bold">Prepare for &oci;
     2936          Integration.</emphasis> Before using &product-name; with &oci;
     2937          there are some initial configuration steps you may need to do.
     2938          See <xref linkend="cloud-integration-steps"/>.
     2939        </para>
     2940      </listitem>
     2941
     2942      <listitem>
     2943        <para>
     2944          <emphasis role="bold">Use &product-name; with
     2945          &oci;.</emphasis> <xref linkend="cloud-vbox-oci-tasks"/>
     2946          describes how you can use &product-name; with &oci;.
     2947        </para>
     2948      </listitem>
     2949
     2950    </itemizedlist>
     2951
    29402952    <sect2 id="cloud-integration-steps">
    29412953
    … …  
    29432955
    29442956      <para>
    2945         There are some common configuration steps you need to take
    2946         before using &product-name; to integrate with your &oci;
    2947         account.
    2948       </para>
    2949 
    2950       <itemizedlist>
     2957        Perform the following configuration steps before using
     2958        &product-name; to integrate with your &oci; account.
     2959      </para>
     2960
     2961      <orderedlist>
     2962
     2963        <listitem>
     2964          <para>
     2965            <emphasis role="bold">Install the Extension Pack.</emphasis>
     2966            Cloud integration features are only available when you
     2967            install the &product-name; Extension Pack. See
     2968            <xref linkend="intro-installing"/>.
     2969          </para>
     2970        </listitem>
    29512971
    29522972        <listitem>
    … …  
    29542974            <emphasis role="bold">Create a key pair.</emphasis> Generate
    29552975            an API signing key pair that is used for API requests to
    2956             &oci;.
     2976            &oci;. See <xref linkend="cloud-create-api-keypair"/>.
     2977          </para>
     2978
     2979          <para>
     2980            Upload the public key of the key pair from your client
     2981            device to the cloud service. See
     2982            <xref linkend="cloud-upload-public-key"/>.
     2983          </para>
     2984        </listitem>
     2985
     2986        <listitem>
     2987          <para>
     2988            <emphasis role="bold">Create a cloud profile.</emphasis> The
     2989            cloud profile contains resource identifiers for your cloud
     2990            account, such as your user OCID, and details of your key
     2991            pair. See <xref linkend="cloud-create-cloud-profile"/>.
     2992          </para>
     2993        </listitem>
     2994
     2995      </orderedlist>
     2996
     2997    </sect2>
     2998
     2999    <sect2 id="cloud-create-api-keypair">
     3000
     3001      <title>Creating an API Signing Key Pair</title>
     3002
     3003      <para></para>
     3004
     3005      <para>
     3006        To use the cloud integration features of &product-name;, you
     3007        must generate an API signing key pair that is used for API
     3008        requests to &oci;.
     3009      </para>
     3010
     3011      <para>
     3012        Your API requests are signed with your private key, and &oci;
     3013        uses the public key to verify the authenticity of the request.
     3014        You must upload the public key to the &oci; Console.
     3015      </para>
     3016
     3017      <note>
     3018        <para>
     3019          This key pair is not the same SSH key that you use to access
     3020          compute instances on &oci;.
     3021        </para>
     3022      </note>
     3023
     3024      <orderedlist>
     3025
     3026        <listitem>
     3027          <para>
     3028            (Optional) Create a <filename>.oci</filename> directory to
     3029            store the key pair.
     3030          </para>
     3031
     3032<screen>$ mkdir ~/.oci</screen>
     3033
     3034          <para>
     3035            The key pair is usually installed in the
     3036            <filename>.oci</filename> folder in your home directory. For
     3037            example, <filename>~/.oci</filename> on a Linux system.
     3038          </para>
     3039        </listitem>
     3040
     3041        <listitem>
     3042          <para>
     3043            Generate the private key.
     3044          </para>
     3045
     3046          <para>
     3047            Use the <command>openssl</command> command.
    29573048          </para>
    29583049
    … …  
    29613052            <listitem>
    29623053              <para>
    2963                 The key pair is usually installed in the
    2964                 <filename>.oci</filename> folder in your home directory.
    2965                 For example, <filename>~/.oci</filename> on a Linux
    2966                 system.
     3054                To generate a private key with a passphrase:
    29673055              </para>
     3056
     3057<screen>$ openssl genrsa -out ~/.oci/oci_api_key.pem -aes128 2048 </screen>
    29683058            </listitem>
    29693059
    29703060            <listitem>
    29713061              <para>
    2972                 Upload the public key of the key pair to the cloud
    2973                 service.
     3062                To generate a private key without a passphrase:
    29743063              </para>
     3064
     3065<screen>$ openssl genrsa -out ~/.oci/oci_api_key.pem 2048</screen>
    29753066            </listitem>
    29763067
    29773068          </itemizedlist>
    2978 
    2979           <para>
    2980             For step-by-step instructions for creating and uploading an
    2981             API signing key for &oci;, see:
    2982           </para>
    2983 
    2984           <para>
    2985             <ulink url="https://docs.cloud.oracle.com/iaas/Content/API/Concepts/apisigningkey.htm#How" />
    2986           </para>
    2987         </listitem>
    2988 
    2989         <listitem>
    2990           <para>
    2991             <emphasis role="bold">Create a cloud profile.</emphasis> The
    2992             cloud profile contains resource identifiers for your cloud
    2993             account, such as your user OCID, and the fingerprint for
    2994             your public key. You can create a cloud profile in the
    2995             following ways:
    2996           </para>
    2997 
    2998           <itemizedlist>
    2999 
    3000             <listitem>
    3001               <para>
    3002                 Automatically, by using the <emphasis role="bold">Cloud
    3003                 Profile Manager</emphasis>. See
    3004                 <xref linkend="ovf-cloud-profile-manager"/>.
    3005               </para>
    3006             </listitem>
    3007 
    3008             <listitem>
    3009               <para>
    3010                 Automatically, by using the <command>VBoxManage
    3011                 cloudprofile</command> command. See
    3012                 <xref linkend="vboxmanage-cloudprofile"/>.
    3013               </para>
    3014             </listitem>
    3015 
    3016             <listitem>
    3017               <para>
    3018                 Manually, by creating an <filename>oci_config</filename>
    3019                 file in your &product-name; global configuration
    3020                 directory. For example, this is
    3021                 <filename>$HOME/.config/VirtualBox/oci_config</filename>
    3022                 on a Linux host.
    3023               </para>
    3024             </listitem>
    3025 
    3026             <listitem>
    3027               <para>
    3028                 Manually, by creating a <filename>config</filename> file
    3029                 in your &oci; configuration directory. For example, this
    3030                 is <filename>$HOME/.oci/config</filename> on a Linux
    3031                 host.
    3032               </para>
    3033 
    3034               <para>
    3035                 This is the same file that is used by the &oci; command
    3036                 line interface.
    3037               </para>
    3038 
    3039               <para>
    3040                 &product-name; automatically uses the
    3041                 <filename>config</filename> file if no cloud profile
    3042                 file is present in your global configuration directory.
    3043                 Alternatively, you can import this file manually into
    3044                 the Cloud Profile Manager.
    3045               </para>
    3046             </listitem>
    3047 
    3048           </itemizedlist>
    3049 
    3050           <para>
    3051             For more information about the cloud profile settings used
    3052             by &oci; see:
    3053           </para>
    3054 
    3055           <para>
    3056             <ulink url="https://docs.cloud.oracle.com/iaas/Content/API/Concepts/sdkconfig.htm" />
    3057           </para>
    3058         </listitem>
    3059 
    3060         <listitem>
    3061           <para>
    3062             <emphasis role="bold">Custom Linux images.</emphasis> To
    3063             export a custom Linux image, prepare the VM as described
    3064             here:
    3065           </para>
    3066 
    3067           <para>
    3068             <ulink url="https://docs.cloud.oracle.com/iaas/Content/Compute/Tasks/importingcustomimagelinux.htm" />
    3069           </para>
    3070         </listitem>
    3071 
    3072         <listitem>
    3073           <para>
    3074             <emphasis role="bold">Subnets.</emphasis> When exporting a
    3075             VM to cloud, ensure that the subnets that are used by source
    3076             VMs are available in the target compartment on the cloud
    3077             service.
    3078           </para>
    3079         </listitem>
    3080 
    3081       </itemizedlist>
     3069        </listitem>
     3070
     3071        <listitem>
     3072          <para>
     3073            Change permissions for the private key.
     3074          </para>
     3075
     3076<screen>$ chmod 600 ~/.oci/oci_api_key.pem</screen>
     3077
     3078          <para>
     3079            Generate the public key.
     3080          </para>
     3081
     3082<screen>$ openssl rsa -pubout -in ~/.oci/oci_api_key.pem -out ~/.oci/oci_api_key_public.pem</screen>
     3083        </listitem>
     3084
     3085      </orderedlist>
    30823086
    30833087    </sect2>
    30843088
    3085     <sect2 id="cloud-export-oci">
    3086 
    3087       <title>Exporting an Appliance to &oci;</title>
    3088 
    3089       <para>
    3090         &product-name; supports the export of VMs to an &oci; service.
    3091         The exported VM is stored on &oci; as a custom image. You can
    3092         configure whether a cloud instance is created and started after
    3093         the export process has completed.
    3094       </para>
    3095 
    3096       <para>
    3097         Before you can export a VM to &oci; ensure that you have done
    3098         the required preconfiguration tasks, as described in
    3099         <xref linkend="cloud-integration-steps"/>.
    3100       </para>
    3101 
    3102       <para>
    3103         Perform the following steps to export a VM to &oci;:
     3089    <sect2 id="cloud-upload-public-key">
     3090
     3091      <title>Uploading the Public Key to &oci;</title>
     3092
     3093      <para>
     3094        Use the following steps to upload your public key to &oci;.
    31043095      </para>
    31053096
    … …  
    31083099        <listitem>
    31093100          <para>
    3110             Select <emphasis role="bold">File</emphasis>,
    3111             <emphasis role="bold">Export Appliance</emphasis> to open
    3112             the <emphasis role="bold">Export Virtual
    3113             Appliance</emphasis> wizard.
    3114           </para>
    3115 
    3116           <para>
    3117             Select a VM to export and click
    3118             <emphasis role="bold">Next</emphasis> to open the
    3119             <emphasis role="bold">Appliance Settings</emphasis> screen.
    3120           </para>
    3121         </listitem>
    3122 
    3123         <listitem>
    3124           <para>
    3125             From the <emphasis role="bold">Format</emphasis> drop-down
    3126             list, select <emphasis role="bold">&oci;</emphasis>.
    3127           </para>
    3128 
    3129           <para>
    3130             In the <emphasis role="bold">Account</emphasis> drop-down
    3131             list, select your &oci; account.
    3132           </para>
    3133 
    3134           <para>
    3135             You can set up &oci; accounts by using the Cloud Profile
    3136             Manager.
    3137           </para>
    3138 
    3139           <para>
    3140             The list after the <emphasis role="bold">Account</emphasis>
    3141             field shows the profile settings for your cloud account.
    3142           </para>
    3143 
    3144           <figure id="fig-export-appliance-oci">
    3145             <title>Appliance Settings Screen, Showing Cloud Profile and Machine Creation
    3146               Settings</title>
     3101            Log in to the &oci; Console.
     3102          </para>
     3103        </listitem>
     3104
     3105        <listitem>
     3106          <para>
     3107            Display the <emphasis role="bold">User Settings</emphasis>
     3108            page.
     3109          </para>
     3110
     3111          <para>
     3112            Click <emphasis role="bold">Profile</emphasis>,
     3113            <emphasis role="bold">User Settings</emphasis>.
     3114          </para>
     3115        </listitem>
     3116
     3117        <listitem>
     3118          <para>
     3119            Display your current API signing keys.
     3120          </para>
     3121
     3122          <para>
     3123            Click <emphasis role="bold">Resources</emphasis>,
     3124            <emphasis role="bold">API Keys</emphasis>.
     3125          </para>
     3126        </listitem>
     3127
     3128        <listitem>
     3129          <para>
     3130            Upload the public key.
     3131          </para>
     3132
     3133          <para>
     3134            Click <emphasis role="bold">Add Public Key</emphasis>.
     3135          </para>
     3136
     3137          <para>
     3138            The <emphasis role="bold">Add Public Key</emphasis> dialog
     3139            is displayed.
     3140          </para>
     3141
     3142          <figure id="fig-upload-key-oci">
     3143            <title>Upload Public Key Dialog in &oci; Console</title>
    31473144            <mediaobject>
    31483145              <imageobject>
    3149                 <imagedata align="center" fileref="images/export-appliance-oci.png"
     3146                <imagedata align="center" fileref="images/upload-key.png"
    31503147                  width="12cm" />
    31513148              </imageobject>
    … …  
    31553152
    31563153          <para>
    3157             In the <emphasis role="bold">Machine Creation</emphasis>
    3158             field, select an option to configure settings for a cloud
    3159             instance created when you export to &oci;. The options
    3160             enable you to do one of the following:
     3154            Select one of the following options:
    31613155          </para>
    31623156
    … …  
    31653159            <listitem>
    31663160              <para>
    3167                 Configure settings for the cloud instance
    3168                 <emphasis>after</emphasis> you have finished exporting
    3169                 the VM.
     3161                <emphasis role="bold">Choose Public Key File.</emphasis>
     3162                This option enables you to browse to the public key file
     3163                on your local hard disk.
    31703164              </para>
    31713165            </listitem>
    … …  
    31733167            <listitem>
    31743168              <para>
    3175                 Configure settings for the cloud instance
    3176                 <emphasis>before</emphasis> you start to export the VM.
     3169                <emphasis role="bold">Paste Public Keys.</emphasis> This
     3170                option enables you to paste the contents of the public
     3171                key file into the window in the dialog box.
    31773172              </para>
    31783173            </listitem>
    31793174
    3180             <listitem>
    3181               <para>
    3182                 Do not create a cloud instance when you export the VM.
    3183               </para>
    3184             </listitem>
    3185 
    31863175          </itemizedlist>
    31873176
    31883177          <para>
    3189             Click <emphasis role="bold">Next</emphasis> to make an API
    3190             request to the &oci; service and open the
    3191             <emphasis role="bold">Virtual System Settings</emphasis>
    3192             screen.
    3193           </para>
    3194         </listitem>
    3195 
    3196         <listitem>
    3197           <para>
    3198             Optionally edit storage settings used for the exported
    3199             virtual machine in &oci;. You can change the following
    3200             settings:
    3201           </para>
    3202 
    3203           <itemizedlist>
    3204 
    3205             <listitem>
    3206               <para>
    3207                 The name of the bucket used to store the exported files.
    3208               </para>
    3209             </listitem>
    3210 
    3211             <listitem>
    3212               <para>
    3213                 Whether to store the custom image in &oci;.
    3214               </para>
    3215             </listitem>
    3216 
    3217             <listitem>
    3218               <para>
    3219                 The name for the custom image in &oci;.
    3220               </para>
    3221             </listitem>
    3222 
    3223             <listitem>
    3224               <para>
    3225                 The launch mode for the custom image.
    3226               </para>
    3227 
    3228               <para>
    3229                 <emphasis role="bold">Paravirtualized</emphasis> mode
    3230                 gives improved performance and should be suitable for
    3231                 most &product-name; VMs.
    3232               </para>
    3233 
    3234               <para>
    3235                 <emphasis role="bold">Emulated</emphasis> mode is
    3236                 suitable for legacy OS images.
    3237               </para>
    3238             </listitem>
    3239 
    3240           </itemizedlist>
    3241 
    3242           <para>
    3243             Click <emphasis role="bold">Export</emphasis> to export the
    3244             VM to &oci;.
    3245           </para>
    3246 
    3247           <para>
    3248             Depending on the selection in the
    3249             <emphasis role="bold">Machine Creation</emphasis> field, the
    3250             <emphasis role="bold">Cloud Virtual Machine
    3251             Settings</emphasis> screen may be displayed before or after
    3252             export. This screen enables you to configure settings for
    3253             the cloud instance, such as Shape and Disk Size.
    3254           </para>
    3255 
    3256           <para>
    3257             Click <emphasis role="bold">Create</emphasis>. The VM is
    3258             exported to &oci;.
    3259           </para>
    3260 
    3261           <para>
    3262             Depending on the <emphasis role="bold">Machine
    3263             Creation</emphasis> setting, a cloud instance may be started
    3264             after upload to &oci; is completed.
    3265           </para>
    3266         </listitem>
    3267 
    3268         <listitem>
    3269           <para>
    3270             Monitor the export process by using the &oci; Console.
     3178            Click <emphasis role="bold">Add</emphasis> to upload the
     3179            public key.
    32713180          </para>
    32723181        </listitem>
    … …  
    32743183      </orderedlist>
    32753184
    3276       <para>
    3277         You can also use the <command>VBoxManage export</command>
    3278         command to export a VM to &oci;. See
    3279         <xref linkend="vboxmanage-export-cloud"/>.
    3280       </para>
    3281 
    32823185    </sect2>
    32833186
    3284     <sect2 id="cloud-import-oci">
    3285 
    3286       <title>Importing an Instance from &oci;</title>
    3287 
    3288       <para>
    3289         &product-name; supports the import of cloud instances from an
    3290         &oci; service.
    3291       </para>
    3292 
    3293       <para>
    3294         Before you can import an instance from &oci; ensure that you
    3295         have done the required preconfiguration tasks, as described in
    3296         <xref linkend="cloud-integration-steps"/>.
    3297       </para>
    3298 
    3299       <para>
    3300         Perform the following steps to import an instance from &oci;:
    3301       </para>
    3302 
    3303       <orderedlist>
    3304 
    3305         <listitem>
    3306           <para>
    3307             Select <emphasis role="bold">File</emphasis>,
    3308             <emphasis role="bold">Import Appliance</emphasis> to open
    3309             the <emphasis role="bold">Import Virtual
    3310             Appliance</emphasis> wizard.
    3311           </para>
    3312 
    3313           <para>
    3314             In the <emphasis role="bold">Source</emphasis> drop-down
    3315             list, select <emphasis role="bold">&oci;</emphasis>.
    3316           </para>
    3317 
    3318           <para>
    3319             In the <emphasis role="bold">Account</emphasis> drop-down
    3320             list, select your &oci; account.
    3321           </para>
    3322 
    3323           <para>
    3324             You can set up &oci; accounts by using the Cloud Profile
    3325             Manager.
    3326           </para>
    3327 
    3328           <para>
    3329             The list after the <emphasis role="bold">Account</emphasis>
    3330             field shows the profile settings for your cloud account.
    3331           </para>
    3332 
    3333           <para>
    3334             Choose the required cloud instance from the list in the
    3335             <emphasis role="bold">Machines</emphasis> field.
    3336           </para>
    3337 
    3338           <para>
    3339             Click <emphasis role="bold">Next</emphasis> to make an API
    3340             request to the &oci; service and open the
    3341             <emphasis role="bold">Appliance Settings</emphasis> screen.
    3342           </para>
    3343         </listitem>
    3344 
    3345         <listitem>
    3346           <para>
    3347             Optionally edit settings for the new local virtual machine.
    3348           </para>
    3349 
    3350           <para>
    3351             For example, you can edit the VM name and description.
    3352           </para>
    3353 
    3354           <figure id="fig-import-instance-oci">
    3355             <title>Import Cloud Instance Screen, Showing Profile Settings and VM Settings</title>
    3356            <mediaobject>
    3357               <imageobject>
    3358                 <imagedata align="center" fileref="images/import-instance.png"
    3359                   width="12cm" />
    3360               </imageobject>
    3361            </mediaobject>
    3362           </figure>
    3363 
    3364           <para>
    3365             Click <emphasis role="bold">Import</emphasis> to import the
    3366             instance from the cloud service.
    3367           </para>
    3368         </listitem>
    3369 
    3370         <listitem>
    3371           <para>
    3372             Monitor the import process by using the &oci; Console.
    3373           </para>
    3374         </listitem>
    3375 
    3376       </orderedlist>
    3377 
    3378       <para>
    3379         You can also use the <command>VBoxManage import</command>
    3380         command to import an instance from &oci;. See
    3381         <xref linkend="vboxmanage-import-cloud"/>.
    3382       </para>
    3383 
    3384       <simplesect id="import-instance-sequence">
    3385 
    3386         <title>Importing an Instance: Overview of Events</title>
    3387 
    3388         <para>
    3389           The following describes the sequence of events when you import
    3390           an instance from &oci;.
    3391         </para>
    3392 
    3393         <itemizedlist>
    3394 
    3395           <listitem>
    3396             <para>
    3397               A custom image is created from the boot volume of the
    3398               instance.
    3399             </para>
    3400           </listitem>
    3401 
    3402           <listitem>
    3403             <para>
    3404               The custom image is exported to an &oci; object and is
    3405               stored using Object Storage in the bucket specified by the
    3406               user.
    3407             </para>
    3408           </listitem>
    3409 
    3410           <listitem>
    3411             <para>
    3412               The &oci; object is downloaded to the local host. The
    3413               object is a TAR archive which contains a boot volume of
    3414               the instance in QCOW2 format and a JSON file containing
    3415               metadata related to the instance.
    3416             </para>
    3417           </listitem>
    3418 
    3419           <listitem>
    3420             <para>
    3421               The boot volume of the instance is extracted from the
    3422               archive and a new VMDK image is created by converting the
    3423               boot volume into the VMDK format. The VMDK image is
    3424               registered with &product-name;.
    3425             </para>
    3426           </listitem>
    3427 
    3428           <listitem>
    3429             <para>
    3430               A new VM is created using the VMDK image for the cloud
    3431               instance.
    3432             </para>
    3433 
    3434             <para>
    3435               By default, the new VM is not started after import from
    3436               &oci;.
    3437             </para>
    3438           </listitem>
    3439 
    3440           <listitem>
    3441             <para>
    3442               The downloaded TAR archive is deleted after a successful
    3443               import.
    3444             </para>
    3445           </listitem>
    3446 
    3447         </itemizedlist>
    3448 
    3449       </simplesect>
     3187    <sect2 id="cloud-create-cloud-profile">
     3188
     3189      <title>Creating a Cloud Profile</title>
     3190
     3191      <para>
     3192        &product-name; uses a <emphasis>cloud profile</emphasis> to
     3193        connect to &oci;. A cloud profile is a text file that contains
     3194        details of your key files and Oracle Cloud Identifier (OCID)
     3195        resource identifiers for your cloud account, such as the
     3196        following:
     3197      </para>
     3198
     3199      <itemizedlist>
     3200
     3201        <listitem>
     3202          <para>
     3203            <emphasis role="bold">Fingerprint of the public
     3204            key.</emphasis> To obtain the fingerprint, you can use the
     3205            <command>openssl</command> command:
     3206          </para>
     3207
     3208<screen>$ openssl rsa -pubout -outform DER -in ~/.oci/oci_api_key.pem | openssl md5 -c</screen>
     3209        </listitem>
     3210
     3211        <listitem>
     3212          <para>
     3213            <emphasis role="bold">Location of the private key on the
     3214            client device.</emphasis> Specify the full path to the
     3215            private key.
     3216          </para>
     3217        </listitem>
     3218
     3219        <listitem>
     3220          <para>
     3221            <emphasis role="bold">(Optional) Passphrase for the private
     3222            key.</emphasis>. This is only required if the key is
     3223            encrypted.
     3224          </para>
     3225        </listitem>
     3226
     3227        <listitem>
     3228          <para>
     3229            <emphasis role="bold">Region</emphasis>. Shown on the &oci;
     3230            Console. Click
     3231            <emphasis role="bold">Administration</emphasis>,
     3232            <emphasis role="bold">Tenancy Details</emphasis>.
     3233          </para>
     3234        </listitem>
     3235
     3236        <listitem>
     3237          <para>
     3238            <emphasis role="bold">Tenancy OCID.</emphasis> Shown on the
     3239            &oci; Console. Click
     3240            <emphasis role="bold">Administration</emphasis>,
     3241            <emphasis role="bold">Tenancy Details</emphasis>.
     3242          </para>
     3243
     3244          <para>
     3245            A link enables you to copy the Tenancy OCID.
     3246          </para>
     3247        </listitem>
     3248
     3249        <listitem>
     3250          <para>
     3251            <emphasis role="bold">Compartment OCID.</emphasis> Shown on
     3252            the &oci; Console. Click
     3253            <emphasis role="bold">Identity</emphasis>,
     3254            <emphasis role="bold">Compartments</emphasis>.
     3255          </para>
     3256
     3257          <para>
     3258            A link enables you to copy the Compartment OCID.
     3259          </para>
     3260        </listitem>
     3261
     3262        <listitem>
     3263          <para>
     3264            <emphasis role="bold">User OCID.</emphasis> Shown on the
     3265            &oci; Console. Click
     3266            <emphasis role="bold">Profile</emphasis>,
     3267            <emphasis role="bold">User Settings</emphasis>.
     3268          </para>
     3269
     3270          <para>
     3271            A link enables you to copy the User OCID.
     3272          </para>
     3273        </listitem>
     3274
     3275      </itemizedlist>
     3276
     3277      <para>
     3278        You can create a cloud profile in the following ways:
     3279      </para>
     3280
     3281      <itemizedlist>
     3282
     3283        <listitem>
     3284          <para>
     3285            Automatically, by using the <emphasis role="bold">Cloud
     3286            Profile Manager</emphasis>. See
     3287            <xref linkend="cloud-using-cloud-profile-manager"/>.
     3288          </para>
     3289
     3290          <para>
     3291            The Cloud Profile Manager is a component of &product-name;
     3292            that enables you to create, edit, and manage cloud profiles
     3293            for your cloud service accounts.
     3294          </para>
     3295        </listitem>
     3296
     3297        <listitem>
     3298          <para>
     3299            Automatically, by using the <command>VBoxManage
     3300            cloudprofile</command> command. See
     3301            <xref linkend="vboxmanage-cloudprofile"/>.
     3302          </para>
     3303        </listitem>
     3304
     3305        <listitem>
     3306          <para>
     3307            Manually, by creating an <filename>oci_config</filename>
     3308            file in your &product-name; global configuration directory.
     3309            For example, this is
     3310            <filename>$HOME/.config/VirtualBox/oci_config</filename> on
     3311            a Linux host.
     3312          </para>
     3313        </listitem>
     3314
     3315        <listitem>
     3316          <para>
     3317            Manually, by creating a <filename>config</filename> file in
     3318            your &oci; configuration directory. For example, this is
     3319            <filename>$HOME/.oci/config</filename> on a Linux host.
     3320          </para>
     3321
     3322          <para>
     3323            This is the same file that is used by the &oci; command line
     3324            interface.
     3325          </para>
     3326
     3327          <para>
     3328            &product-name; automatically uses the
     3329            <filename>config</filename> file if no cloud profile file is
     3330            present in your global configuration directory.
     3331            Alternatively, you can import this file manually into the
     3332            Cloud Profile Manager.
     3333          </para>
     3334        </listitem>
     3335
     3336      </itemizedlist>
    34503337
    34513338    </sect2>
    34523339
    3453     <sect2 id="ovf-cloud-profile-manager">
    3454 
    3455       <title>The Cloud Profile Manager</title>
    3456 
    3457       <para>
    3458         The Cloud Profile Manager is a component of &product-name; that
    3459         enables you to create, edit, and manage cloud profiles for your
    3460         cloud service accounts.
     3340    <sect2 id="cloud-using-cloud-profile-manager">
     3341
     3342      <title>Using the Cloud Profile Manager</title>
     3343
     3344      <para>
     3345        This section describes how to use the Cloud Profile Manager to
     3346        create a cloud profile.
     3347      </para>
     3348
     3349      <para>
     3350        To open the Cloud Profile Manager click
     3351        <emphasis role="bold">File</emphasis>,
     3352        <emphasis role="bold">Cloud Profile Manager</emphasis> in the
     3353        VirtualBox Manager window.
    34613354      </para>
    34623355
    … …  
    34723365
    34733366      <para>
    3474         To open the Cloud Profile Manager select
    3475         <emphasis role="bold">File</emphasis>,
    3476         <emphasis role="bold">Cloud Profile Manager</emphasis> from the
    3477         VirtualBox Manager window.
    3478       </para>
    3479 
    3480       <para>
    3481         You can use the Cloud Profile Manager to create a new cloud
    3482         profile automatically or to create a cloud profile by importing
    3483         settings from your &oci; configuration file.
    3484       </para>
     3367        You can use the Cloud Profile Manager in the following ways:
     3368      </para>
     3369
     3370      <itemizedlist>
     3371
     3372        <listitem>
     3373          <para>
     3374            To create a new cloud profile automatically
     3375          </para>
     3376        </listitem>
     3377
     3378        <listitem>
     3379          <para>
     3380            To create a cloud profile by importing settings from your
     3381            &oci; configuration file.
     3382          </para>
     3383        </listitem>
     3384
     3385      </itemizedlist>
    34853386
    34863387      <para>
    34873388        Perform the following steps to create a new cloud profile
    3488         automatically:
     3389        automatically, using the Cloud Profile Manager:
    34893390      </para>
    34903391
    … …  
    35253426            </listitem>
    35263427
    3527             <listitem>
     3428<!--       <listitem>
    35283429              <para>
    35293430                (Optional) Passphrase for the private key, if the key is
    35303431                encrypted
    35313432              </para>
    3532             </listitem>
     3433            </listitem>-->
    35333434
    35343435            <listitem>
    … …  
    35753476      <para>
    35763477        Perform the following steps to import an existing &oci;
    3577         configuration file:
     3478        configuration file into the Cloud Profile Manager:
    35783479      </para>
    35793480
    … …  
    36343535
    36353536      </orderedlist>
     3537
     3538    </sect2>
     3539
     3540    <sect2 id="cloud-vbox-oci-tasks">
     3541
     3542      <title>Using &product-name; With &oci;</title>
     3543
     3544      <para>
     3545        This section describes how you can use &product-name; with &oci;
     3546        to do the following tasks:
     3547      </para>
     3548
     3549      <itemizedlist>
     3550
     3551        <listitem>
     3552          <para>
     3553            Export an &product-name; VM to &oci;. See
     3554            <xref linkend="cloud-export-oci"/>.
     3555          </para>
     3556        </listitem>
     3557
     3558        <listitem>
     3559          <para>
     3560            Import a cloud instance into &product-name;. See
     3561            <xref linkend="cloud-import-oci"/>.
     3562          </para>
     3563        </listitem>
     3564
     3565        <listitem>
     3566          <para>
     3567            Create a new cloud instance from a custom image stored on
     3568            &oci;. See <xref linkend="cloud-new-vm"/>.
     3569          </para>
     3570        </listitem>
     3571
     3572        <listitem>
     3573          <para>
     3574            Use the <command>VBoxManage</command> commands to integrate
     3575            with &oci; and perform cloud operations. See
     3576            <xref linkend="cloud-using-cli"/>.
     3577          </para>
     3578        </listitem>
     3579
     3580      </itemizedlist>
     3581
     3582    </sect2>
     3583
     3584    <sect2 id="cloud-export-oci">
     3585
     3586      <title>Exporting an Appliance to &oci;</title>
     3587
     3588      <para>
     3589        &product-name; supports the export of VMs to an &oci; service.
     3590        The exported VM is stored on &oci; as a custom Linux image. You
     3591        can configure whether a cloud instance is created and started
     3592        after the export process has completed.
     3593      </para>
     3594
     3595      <note>
     3596        <para>
     3597          Before you export a VM to &oci;, you must prepare the VM as
     3598          described in <xref linkend="cloud-export-oci-prepare-vm"/>.
     3599        </para>
     3600      </note>
     3601
     3602      <para>
     3603        Use the following steps to export a VM to &oci;:
     3604      </para>
     3605
     3606      <orderedlist>
     3607
     3608        <listitem>
     3609          <para>
     3610            Select <emphasis role="bold">File</emphasis>,
     3611            <emphasis role="bold">Export Appliance</emphasis> to open
     3612            the <emphasis role="bold">Export Virtual
     3613            Appliance</emphasis> wizard.
     3614          </para>
     3615
     3616          <para>
     3617            Select a VM to export and click
     3618            <emphasis role="bold">Next</emphasis> to open the
     3619            <emphasis role="bold">Appliance Settings</emphasis> screen.
     3620          </para>
     3621        </listitem>
     3622
     3623        <listitem>
     3624          <para>
     3625            From the <emphasis role="bold">Format</emphasis> drop-down
     3626            list, select <emphasis role="bold">&oci;</emphasis>.
     3627          </para>
     3628
     3629          <para>
     3630            In the <emphasis role="bold">Account</emphasis> drop-down
     3631            list, select the cloud profile for your &oci; account.
     3632          </para>
     3633
     3634          <para>
     3635            The list after the <emphasis role="bold">Account</emphasis>
     3636            field shows the profile settings for your cloud account.
     3637          </para>
     3638
     3639          <figure id="fig-export-appliance-oci">
     3640            <title>Appliance Settings Screen, Showing Cloud Profile and Machine Creation
     3641              Settings</title>
     3642           <mediaobject>
     3643              <imageobject>
     3644                <imagedata align="center" fileref="images/export-appliance-oci.png"
     3645                  width="12cm" />
     3646              </imageobject>
     3647            </mediaobject>
     3648          </figure>
     3649
     3650          <para>
     3651            In the <emphasis role="bold">Machine Creation</emphasis>
     3652            field, select an option to configure settings for a cloud
     3653            instance created when you export to &oci;. The options
     3654            enable you to do one of the following:
     3655          </para>
     3656
     3657          <itemizedlist>
     3658
     3659            <listitem>
     3660              <para>
     3661                Configure settings for the cloud instance
     3662                <emphasis>after</emphasis> you have finished exporting
     3663                the VM.
     3664              </para>
     3665            </listitem>
     3666
     3667            <listitem>
     3668              <para>
     3669                Configure settings for the cloud instance
     3670                <emphasis>before</emphasis> you start to export the VM.
     3671              </para>
     3672            </listitem>
     3673
     3674            <listitem>
     3675              <para>
     3676                Do not create a cloud instance when you export the VM.
     3677              </para>
     3678            </listitem>
     3679
     3680          </itemizedlist>
     3681
     3682          <para>
     3683            Click <emphasis role="bold">Next</emphasis> to make an API
     3684            request to the &oci; service and open the
     3685            <emphasis role="bold">Virtual System Settings</emphasis>
     3686            screen.
     3687          </para>
     3688        </listitem>
     3689
     3690        <listitem>
     3691          <para>
     3692            (Optional) Edit storage settings used for the exported
     3693            virtual machine in &oci;. You can change the following
     3694            settings:
     3695          </para>
     3696
     3697          <itemizedlist>
     3698
     3699            <listitem>
     3700              <para>
     3701                The name of the bucket used to store the exported files.
     3702              </para>
     3703            </listitem>
     3704
     3705            <listitem>
     3706              <para>
     3707                Whether to store the custom image in &oci;.
     3708              </para>
     3709            </listitem>
     3710
     3711            <listitem>
     3712              <para>
     3713                The name for the custom image in &oci;.
     3714              </para>
     3715            </listitem>
     3716
     3717            <listitem>
     3718              <para>
     3719                The launch mode for the custom image.
     3720              </para>
     3721
     3722              <para>
     3723                <emphasis role="bold">Paravirtualized</emphasis> mode
     3724                gives improved performance and should be suitable for
     3725                most &product-name; VMs.
     3726              </para>
     3727
     3728              <para>
     3729                <emphasis role="bold">Emulated</emphasis> mode is
     3730                suitable for legacy OS images.
     3731              </para>
     3732            </listitem>
     3733
     3734          </itemizedlist>
     3735
     3736          <para>
     3737            Click <emphasis role="bold">Export</emphasis> to continue.
     3738          </para>
     3739        </listitem>
     3740
     3741        <listitem>
     3742          <para>
     3743            Depending on the selection in the
     3744            <emphasis role="bold">Machine Creation</emphasis> field, the
     3745            <emphasis role="bold">Cloud Virtual Machine
     3746            Settings</emphasis> screen may be displayed before or after
     3747            export. This screen enables you to configure settings for
     3748            the cloud instance, such as Shape and Disk Size.
     3749          </para>
     3750
     3751          <para>
     3752            Click <emphasis role="bold">Create</emphasis>. The VM is
     3753            exported to &oci;.
     3754          </para>
     3755
     3756          <para>
     3757            Depending on the <emphasis role="bold">Machine
     3758            Creation</emphasis> setting, a cloud instance may be started
     3759            after upload to &oci; is completed.
     3760          </para>
     3761        </listitem>
     3762
     3763        <listitem>
     3764          <para>
     3765            Monitor the export process by using the &oci; Console.
     3766          </para>
     3767        </listitem>
     3768
     3769      </orderedlist>
     3770
     3771      <para>
     3772        You can also use the <command>VBoxManage export</command>
     3773        command to export a VM to &oci;. See
     3774        <xref linkend="vboxmanage-export-cloud"/>.
     3775      </para>
     3776
     3777      <sect3 id="cloud-export-oci-prepare-vm">
     3778
     3779        <title>Preparing a VM for Export to &oci;</title>
     3780
     3781        <para>
     3782          &oci; provides the option to import a custom Linux image.
     3783          Before an &product-name; image can be exported to &oci;, the
     3784          custom image needs to be prepared to ensure that instances
     3785          launched from the custom image can boot correctly and that
     3786          network connections will work. This section provides advice on
     3787          how to prepare a Linux image for export from &product-name;.
     3788        </para>
     3789
     3790        <para>
     3791          The following list shows some tasks to consider when preparing
     3792          an Oracle Linux VM for export:
     3793        </para>
     3794
     3795        <itemizedlist>
     3796
     3797          <listitem>
     3798            <para>
     3799              <emphasis role="bold">Use DHCP for network
     3800              addresses.</emphasis> Configure the VM to use a DHCP
     3801              server to allocate network addresses, rather than using a
     3802              static IP address. The &oci; instance will then be
     3803              allocated an IP address automatically.
     3804            </para>
     3805          </listitem>
     3806
     3807          <listitem>
     3808            <para>
     3809              <emphasis role="bold">Do not specify a MAC
     3810              address.</emphasis> The network interface configuration
     3811              for the VM must not specify the MAC address.
     3812            </para>
     3813
     3814            <para>
     3815              Remove the HWADDR setting from the
     3816              <filename>/etc/sysconfig/ifcfg-<replaceable>devicename</replaceable></filename>
     3817              network script.
     3818            </para>
     3819          </listitem>
     3820
     3821          <listitem>
     3822            <para>
     3823              <emphasis role="bold">Disable persistent network device
     3824              naming rules.</emphasis> This means that the &oci;
     3825              instance will use the same network device names as the VM.
     3826            </para>
     3827
     3828            <orderedlist>
     3829
     3830              <listitem>
     3831                <para>
     3832                  Change the GRUB kernel parameters.
     3833                </para>
     3834
     3835                <para>
     3836                  Add <literal>net.ifnames=0</literal> and
     3837                  <literal>biosdevname=0</literal> as kernel parameter
     3838                  values to the <literal>GRUB_CMDLINE_LINUX</literal>
     3839                  variable.
     3840                </para>
     3841              </listitem>
     3842
     3843              <listitem>
     3844                <para>
     3845                  Update the GRUB configuration.
     3846                </para>
     3847
     3848<screen># grub2-mkconfig -o /boot/grub2/grub.cfg</screen>
     3849              </listitem>
     3850
     3851              <listitem>
     3852                <para>
     3853                  Disable any <literal>udev</literal> rules for network
     3854                  device naming.
     3855                </para>
     3856
     3857                <para>
     3858                  For example, if an automated <literal>udev</literal>
     3859                  rule exists for <literal>net-persistence</literal>:
     3860                </para>
     3861
     3862<screen># cd /etc/udev/rules.d
     3863# rm -f 70-persistent-net.rules
     3864# ln -s /dev/null /etc/udev/rules.d/70-persistent-net.rules</screen>
     3865              </listitem>
     3866
     3867            </orderedlist>
     3868          </listitem>
     3869
     3870          <listitem>
     3871            <para>
     3872              <emphasis role="bold">Enable the serial
     3873              console.</emphasis> This enables you to troubleshoot the
     3874              instance when it is running on &oci;.
     3875            </para>
     3876
     3877            <orderedlist>
     3878
     3879              <listitem>
     3880                <para>
     3881                  Edit the <filename>/etc/default/grub</filename> file,
     3882                  as follows:
     3883                </para>
     3884
     3885                <itemizedlist>
     3886
     3887                  <listitem>
     3888                    <para>
     3889                      Remove the <literal>resume</literal> setting from
     3890                      the kernel parameters. This setting slows down
     3891                      boot time significantly.
     3892                    </para>
     3893                  </listitem>
     3894
     3895                  <listitem>
     3896                    <para>
     3897                      Replace <literal>GRUB_TERMINAL="gfxterm"</literal>
     3898                      with <literal>GRUB_TERMINAL="console
     3899                      serial"</literal>. This configures use of the
     3900                      serial console instead of a graphical terminal.
     3901                    </para>
     3902                  </listitem>
     3903
     3904                  <listitem>
     3905                    <para>
     3906                      Add <literal>GRUB_SERIAL_COMMAND="serial --unit=0
     3907                      --speed=115200"</literal>. This configures the
     3908                      serial connection.
     3909                    </para>
     3910                  </listitem>
     3911
     3912                  <listitem>
     3913                    <para>
     3914                      Add <literal>console=tty0
     3915                      console=ttyS0,115200</literal> to the
     3916                      <literal>GRUB_CMDLINE_LINUX</literal> variable.
     3917                      This adds the serial console to the Linux kernel
     3918                      boot parameters.
     3919                    </para>
     3920                  </listitem>
     3921
     3922                </itemizedlist>
     3923              </listitem>
     3924
     3925              <listitem>
     3926                <para>
     3927                  Regenerate the GRUB configuration.
     3928                </para>
     3929
     3930<screen># grub2-mkconfig -o /boot/grub2/grub.cfg</screen>
     3931              </listitem>
     3932
     3933              <listitem>
     3934                <para>
     3935                  To verify the changes, reboot the machine and run the
     3936                  <command>dmesg</command> command to look for the
     3937                  updated kernel parameters.
     3938                </para>
     3939
     3940<screen># dmesg |grep console=ttyS0</screen>
     3941              </listitem>
     3942
     3943            </orderedlist>
     3944          </listitem>
     3945
     3946          <listitem>
     3947            <para>
     3948              <emphasis role="bold">Enable paravirtualized device
     3949              support.</emphasis> You do this by adding the
     3950              <literal>virtio</literal> drivers to the
     3951              <literal>initrd</literal> for the VM.
     3952            </para>
     3953
     3954            <orderedlist>
     3955
     3956              <listitem>
     3957                <para>
     3958                  This procedure works only on machines with a Linux
     3959                  kernel of version 3.4 or later. Check that the VM is
     3960                  running a supported kernel:
     3961                </para>
     3962
     3963<screen># uname -a</screen>
     3964              </listitem>
     3965
     3966              <listitem>
     3967                <para>
     3968                  Use the <literal>dracut</literal> tool to rebuild
     3969                  <literal>initrd</literal>. Add the
     3970                  <literal>qemu</literal> module, as follows:
     3971                </para>
     3972
     3973<screen># dracut –-logfile /var/log/Dracut.log –-force –-add qemu</screen>
     3974              </listitem>
     3975
     3976              <listitem>
     3977                <para>
     3978                  Verify that the <literal>virtio</literal> drivers are
     3979                  now present in <literal>initrd</literal>.
     3980                </para>
     3981
     3982<screen> # lsinitrd |grep virtio</screen>
     3983              </listitem>
     3984
     3985            </orderedlist>
     3986          </listitem>
     3987
     3988        </itemizedlist>
     3989
     3990        <para>
     3991          For more information about importing a custom Linux image into
     3992          &oci;, see also:
     3993        </para>
     3994
     3995        <para>
     3996          <ulink url="https://docs.cloud.oracle.com/iaas/Content/Compute/Tasks/importingcustomimagelinux.htm" />
     3997        </para>
     3998
     3999      </sect3>
     4000
     4001    </sect2>
     4002
     4003    <sect2 id="cloud-import-oci">
     4004
     4005      <title>Importing an Instance from &oci;</title>
     4006
     4007      <para>
     4008        Perform the following steps to import a cloud instance from
     4009        &oci; into &product-name;:
     4010      </para>
     4011
     4012      <orderedlist>
     4013
     4014        <listitem>
     4015          <para>
     4016            Select <emphasis role="bold">File</emphasis>,
     4017            <emphasis role="bold">Import Appliance</emphasis> to open
     4018            the <emphasis role="bold">Import Virtual
     4019            Appliance</emphasis> wizard.
     4020          </para>
     4021
     4022          <para>
     4023            In the <emphasis role="bold">Source</emphasis> drop-down
     4024            list, select <emphasis role="bold">&oci;</emphasis>.
     4025          </para>
     4026
     4027          <para>
     4028            In the <emphasis role="bold">Account</emphasis> drop-down
     4029            list, select the cloud profile for your &oci; account.
     4030          </para>
     4031
     4032          <para>
     4033            The list after the <emphasis role="bold">Account</emphasis>
     4034            field shows the profile settings for your cloud account.
     4035          </para>
     4036
     4037          <para>
     4038            Choose the required cloud instance from the list in the
     4039            <emphasis role="bold">Machines</emphasis> field.
     4040          </para>
     4041
     4042          <para>
     4043            Click <emphasis role="bold">Next</emphasis> to make an API
     4044            request to the &oci; service and display the
     4045            <emphasis role="bold">Appliance Settings</emphasis> screen.
     4046          </para>
     4047        </listitem>
     4048
     4049        <listitem>
     4050          <para>
     4051            (Optional) Edit settings for the new local virtual machine.
     4052          </para>
     4053
     4054          <para>
     4055            For example, you can edit the VM name and description.
     4056          </para>
     4057
     4058          <figure id="fig-import-instance-oci">
     4059            <title>Import Cloud Instance Screen, Showing Profile Settings and VM Settings</title>
     4060           <mediaobject>
     4061              <imageobject>
     4062                <imagedata align="center" fileref="images/import-instance.png"
     4063                  width="12cm" />
     4064              </imageobject>
     4065            </mediaobject>
     4066          </figure>
     4067
     4068          <para>
     4069            Click <emphasis role="bold">Import</emphasis> to import the
     4070            instance from &oci;.
     4071          </para>
     4072        </listitem>
     4073
     4074        <listitem>
     4075          <para>
     4076            Monitor the import process by using the &oci; Console.
     4077          </para>
     4078        </listitem>
     4079
     4080      </orderedlist>
     4081
     4082      <para>
     4083        You can also use the <command>VBoxManage import</command>
     4084        command to import an instance from &oci;. See
     4085        <xref linkend="vboxmanage-import-cloud"/>.
     4086      </para>
     4087
     4088      <simplesect id="import-instance-sequence">
     4089
     4090        <title>Importing an Instance: Overview of Events</title>
     4091
     4092        <para>
     4093          The following describes the sequence of events when you import
     4094          an instance from &oci;.
     4095        </para>
     4096
     4097        <itemizedlist>
     4098
     4099          <listitem>
     4100            <para>
     4101              A custom image is created from the boot volume of the
     4102              instance.
     4103            </para>
     4104          </listitem>
     4105
     4106          <listitem>
     4107            <para>
     4108              The custom image is exported to an &oci; object and is
     4109              stored using Object Storage in the bucket specified by the
     4110              user.
     4111            </para>
     4112          </listitem>
     4113
     4114          <listitem>
     4115            <para>
     4116              The &oci; object is downloaded to the local host. The
     4117              object is a TAR archive which contains a boot volume of
     4118              the instance in QCOW2 format and a JSON file containing
     4119              metadata related to the instance.
     4120            </para>
     4121          </listitem>
     4122
     4123          <listitem>
     4124            <para>
     4125              The boot volume of the instance is extracted from the
     4126              archive and a new VMDK image is created by converting the
     4127              boot volume into the VMDK format. The VMDK image is
     4128              registered with &product-name;.
     4129            </para>
     4130          </listitem>
     4131
     4132          <listitem>
     4133            <para>
     4134              A new VM is created using the VMDK image for the cloud
     4135              instance.
     4136            </para>
     4137
     4138            <para>
     4139              By default, the new VM is not started after import from
     4140              &oci;.
     4141            </para>
     4142          </listitem>
     4143
     4144          <listitem>
     4145            <para>
     4146              The downloaded TAR archive is deleted after a successful
     4147              import.
     4148            </para>
     4149          </listitem>
     4150
     4151        </itemizedlist>
     4152
     4153      </simplesect>
    36364154
    36374155    </sect2>
    … …  
    36554173
    36564174      <para>
    3657         Before you can create a new cloud instance in &oci; ensure that
    3658         you have done the required preconfiguration tasks, as described
    3659         in <xref linkend="cloud-integration-steps"/>.
    3660       </para>
    3661 
    3662       <para>
    36634175        Perform the following steps to create a new cloud instance on
    36644176        &oci;:
    … …  
    36854197          <para>
    36864198            In the <emphasis role="bold">Account</emphasis> drop-down
    3687             list, select your &oci; account.
    3688           </para>
    3689 
    3690           <para>
    3691             You can set up &oci; accounts by using the Cloud Profile
    3692             Manager.
     4199            list, select the cloud profile for your &oci; account.
    36934200          </para>
    36944201
    … …  
    37054212          <figure id="fig-newcloudvm">
    37064213            <title>New Cloud VM Wizard, Showing List of Custom Images</title>
    3707            <mediaobject>
     4214            <mediaobject>
    37084215              <imageobject>
    37094216                <imagedata align="center" fileref="images/newcloudvm.png"
    … …  
    37234230        <listitem>
    37244231          <para>
    3725             Optionally edit settings used for the instance on &oci;.
     4232            (Optional) Edit settings used for the new instance on &oci;.
    37264233          </para>
    37274234
    … …  
    37504257        instance</command> command to create and manage instances on a
    37514258        cloud service. See <xref linkend="vboxmanage-cloud"/>.
     4259      </para>
     4260
     4261    </sect2>
     4262
     4263    <sect2 id="cloud-using-cli">
     4264
     4265      <title>Using VBoxManage Commands With &oci;</title>
     4266
     4267      <para>
     4268        This section includes some examples of how
     4269        <command>VBoxManage</command> commands can be used to integrate
     4270        with &oci; and perform common cloud operations.
     4271      </para>
     4272
     4273      <para>
     4274        <emphasis role="bold">Creating a Cloud Profile</emphasis>
     4275      </para>
     4276
     4277      <para>
     4278        To create a cloud profile called <literal>vbox-oci</literal>:
     4279      </para>
     4280
     4281<screen>VBoxManage cloudprofile --provider "OCI" --profile="vbox-oci" add \
     4282--clouduser="ocid1.user.oc1..."  --keyfile="/home/username/.oci/oci_api_key.pem" \
     4283--tenancy="ocid1.tenancy.oc1..."  --compartment="ocid1.compartment.oc1..."  --region="us-ashburn-1"
     4284</screen>
     4285
     4286      <para>
     4287        The new cloud profile is added to the
     4288        <filename>oci_config</filename> file in your &product-name;
     4289        global configuration directory. For example, this is
     4290        <filename>$HOME/.VirtualBox/oci_config</filename> on a Windows
     4291        host.
     4292      </para>
     4293
     4294      <para>
     4295        <emphasis role="bold">Listing Cloud Instances</emphasis>
     4296      </para>
     4297
     4298      <para>
     4299        To list the instances in your &oci; compartment:
     4300      </para>
     4301
     4302<screen>VBoxManage cloud --provider="OCI" --profile="vbox-oci" list instances
     4303</screen>
     4304
     4305      <para>
     4306        <emphasis role="bold">Exporting an &product-name; VM to the
     4307        Cloud</emphasis>
     4308      </para>
     4309
     4310      <para>
     4311        To export a VM called <literal>myVM</literal> and create a cloud
     4312        instance called <literal>myVM_Cloud</literal>:
     4313      </para>
     4314
     4315<screen>VBoxManage export myVM --output OCI:// --cloud 0 --vmname myVM_Cloud \
     4316--cloudprofile "vbox-oci" --cloudbucket myBucket \
     4317--cloudshape VM.Standard2.1 --clouddomain US-ASHBURN-AD-1 --clouddisksize 50  \
     4318--cloudocivcn ocid1.vcn.oc1... --cloudocisubnet ocid1.subnet.oc1... \
     4319--cloudkeepobject true --cloudlaunchinstance true --cloudpublicip true
     4320      </screen>
     4321
     4322      <para>
     4323        <emphasis role="bold">Importing a Cloud Instance Into
     4324        &product-name;</emphasis>
     4325      </para>
     4326
     4327      <para>
     4328        To import a cloud instance and create an &product-name; VM
     4329        called <literal>oci_Import</literal>:
     4330      </para>
     4331
     4332<screen>VBoxManage import OCI:// --cloud --vmname oci_Import --memory 4000
     4333--cpus 3 --ostype FreeBSD_64 --cloudprofile "vbox-oci"
     4334--cloudinstanceid ocid1.instance.oc1... --cloudbucket myBucket
     4335  </screen>
     4336
     4337      <para>
     4338        <emphasis role="bold">Creating a New Cloud Instance From a
     4339        Custom Image</emphasis>
     4340      </para>
     4341
     4342      <para>
     4343        To create a new cloud instance from a custom image on &oci;:
     4344      </para>
     4345
     4346<screen>VBoxManage cloud --provider="OCI" --profile="vbox-oci" instance create \
     4347--domain-name="oraclecloud.com" --image-id="ocid1.image.oc1..." --display-name="myInstance" \
     4348--shape="VM.Standard2.1" --subnet="ocid1.subnet.oc1..."</screen>
     4349
     4350      <para>
     4351        <emphasis role="bold">Terminating a Cloud Instance</emphasis>
     4352      </para>
     4353
     4354      <para>
     4355        To terminate an instance in your compartment on &oci;:
     4356      </para>
     4357
     4358<screen>VBoxManage cloud --provider="OCI" --profile="vbox-oci" instance terminate \
     4359--id="ocid1.instance.oc1..." </screen>
     4360
     4361      <para>
     4362        For more details about the available commands for cloud
     4363        operations, see <xref linkend="vboxmanage-cloud"/>.
    37524364      </para>
    37534365
    … …  
    38204432        <para>
    38214433          <emphasis role="bold">Network.</emphasis> Enables the user to
    3822           configure the details of Host Only Networks.
     4434          configure the details of NAT networks. See
     4435          <xref linkend="network_nat_service"/>.
    38234436        </para>
    38244437      </listitem>

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

    r85420 r87077  
    3030      </listitem>
    3131
     32      <listitem>
     33        <para>
     34          Hardware 2D video playback acceleration support for Windows
     35          guests
     36        </para>
     37      </listitem>
     38
    3239<!--   <listitem>
    3340        <para>
    … …  
    9097      <listitem>
    9198        <para>
    92           Poor performance when using &product-name; and <emphasis
    93           role="bold">Hyper-V</emphasis> on the same host. To fix this, certain
    94           Windows features like "Hyper-V Platform", "Virtual Machine Platform" and
    95           "Windows Hypervisor Platform" have to be turned off, followed by a host
    96           reboot.
    97         </para>
    98         <para>
    99           Additionally, the "Microsoft Device Guard and Credential Guard hardware
    100           readiness tool" might be used in order to turn off more features,
    101           for example with <screen>.\DG_Readiness_Tool_vX.X.ps1 -Disable -AutoReboot</screen>
    102           <note>
    103             <para>
    104               Disabling Device Guard and Credential Guard features will have an
    105               impact on the overall security of the host. Please contact your Administrator
    106               beforehand regarding this.
    107             </para>
    108           </note>
    109         </para>
     99          Poor performance when using &product-name; and
     100          <emphasis role="bold">Hyper-V</emphasis> on the same host. To
     101          fix this, certain Windows features like "Hyper-V Platform",
     102          "Virtual Machine Platform" and "Windows Hypervisor Platform"
     103          must be turned off, followed by a host reboot.
     104        </para>
     105
     106        <para>
     107          Additionally, the Microsoft Device Guard and Credential Guard
     108          hardware readiness tool might have to be used in order to turn
     109          off more features. For example, by running the following
     110          command:
     111        </para>
     112
     113<screen>.\DG_Readiness_Tool_vX.X.ps1 -Disable -AutoReboot</screen>
     114
     115        <note>
     116          <para>
     117            Disabling Device Guard and Credential Guard features will
     118            have an impact on the overall security of the host. Please
     119            contact your Administrator beforehand regarding this.
     120          </para>
     121        </note>
    110122      </listitem>
    111123

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

    r85107 r87077  
    475475    <note>
    476476      <para>
    477         Even though the NAT engine separates the VM from the host,
    478         the VM has access to the host's loopback interface and the
    479         network services running on it. The host's loopback interface
    480         is accessible as IP address 10.0.2.2. This access to the host's
     477        Even though the NAT engine separates the VM from the host, the
     478        VM has access to the host's loopback interface and the network
     479        services running on it. The host's loopback interface is
     480        accessible as IP address 10.0.2.2. This access to the host's
    481481        loopback interface can be extremely useful in some cases, for
    482482        example when running a web application under development in the
    483         VM and the database server on the loopback interface on the host.
     483        VM and the database server on the loopback interface on the
     484        host.
    484485      </para>
    485486    </note>
    … …  
    811812<screen>VBoxManage list natnetworks</screen>
    812813
     814    <para>
     815      NAT networks can also be created, deleted, and configured using
     816      the VirtualBox Manager. Click
     817      <emphasis role="bold">File</emphasis>,<emphasis role="bold">
     818      Preferences</emphasis> and select the
     819      <emphasis role="bold">Network</emphasis> page.
     820    </para>
     821
    813822    <note>
    814823      <para>
    815         Even though the NAT service separates the VM from the host,
    816         the VM has access to the host's loopback interface and the
    817         network services running on it. The host's loopback interface
    818         is accessible as IP address 10.0.2.2 (assuming the default
     824        Even though the NAT service separates the VM from the host, the
     825        VM has access to the host's loopback interface and the network
     826        services running on it. The host's loopback interface is
     827        accessible as IP address 10.0.2.2 (assuming the default
    819828        configuration, in other configurations it's the respective
    820829        address in the configured IPv4 or IPv6 network range). This
    … …  
    10041013        <para>
    10051014          Use the VM's <emphasis role="bold">Settings</emphasis> dialog
    1006           in the &product-name; graphical user interface. In the
    1007           <emphasis role="bold">Networking</emphasis> category of the
     1015          in the VirtualBox Manager. In the
     1016          <emphasis role="bold">Network</emphasis> category of the
    10081017          settings dialog, select <emphasis role="bold">Internal
    1009           Networking</emphasis> from the drop-down list of networking
     1018          Network</emphasis> from the drop-down list of networking
    10101019          modes. Select the name of an existing internal network from
    10111020          the drop-down list below, or enter a new name into the
    … …  
    10931102
    10941103    <para>
    1095       To change a virtual machine's virtual network interface to Host
    1096       Only mode, do either of the following:
     1104      To enable a host-only network interface for a virtual machine, do
     1105      either of the following:
    10971106    </para>
    10981107
    … …  
    11031112          Go to the <emphasis role="bold">Network</emphasis> page in the
    11041113          virtual machine's <emphasis role="bold">Settings</emphasis>
    1105           dialog and select <emphasis role="bold">Host-Only
    1106           Networking</emphasis>.
    1107         </para>
    1108       </listitem>
    1109 
    1110       <listitem>
    1111         <para>
    1112           On the command line, enter <command>VBoxManage modifyvm
     1114          dialog and select an <emphasis role="bold">Adapter</emphasis>
     1115          tab. Ensure that the <emphasis role="bold">Enable Network
     1116          Adapter</emphasis> check box is selected and choose
     1117          <emphasis role="bold">Host-Only Adapter</emphasis> for the
     1118          <emphasis role="bold">Attached To</emphasis> field.
     1119        </para>
     1120      </listitem>
     1121
     1122      <listitem>
     1123        <para>
     1124          On the command line, use <command>VBoxManage modifyvm
    11131125          <replaceable>"vmname</replaceable>
    11141126          --nic<replaceable>x</replaceable> hostonly</command>. See
    1115           <xref
    1116           linkend="vboxmanage-modifyvm" />.
     1127          <xref linkend="vboxmanage-modifyvm" />.
    11171128        </para>
    11181129      </listitem>
    11191130
    11201131    </itemizedlist>
    1121 
    1122     <para>
    1123       Before you can attach a VM to a host-only network you have to
    1124       create at least one host-only interface. You can use the
    1125       VirtualBox Manager for this. Choose
    1126       <emphasis role="bold">File</emphasis>,
    1127       <emphasis role="bold">Preferences</emphasis>,
    1128       <emphasis role="bold">Network</emphasis>,
    1129       <emphasis role="bold">Host-Only Network</emphasis>,
    1130       <emphasis role="bold">(+)Add Host-Only Network</emphasis>.
    1131     </para>
    1132 
    1133     <para>
    1134       Alternatively, you can use the command line:
    1135     </para>
    1136 
    1137 <screen>VBoxManage hostonlyif create</screen>
    1138 
    1139     <para>
    1140       See <xref linkend="vboxmanage-hostonlyif" />.
    1141     </para>
    11421132
    11431133    <para>
    11441134      For host-only networking, as with internal networking, you may
    11451135      find the DHCP server useful that is built into &product-name;.
    1146       This can be enabled to then manage the IP addresses in the
    1147       host-only network since otherwise you would need to configure all
    1148       IP addresses statically.
     1136      This is enabled by default and manages the IP addresses in the
     1137      host-only network. Without the DHCP server you would need to
     1138      configure all IP addresses statically.
    11491139    </para>
    11501140
    … …  
    11531143      <listitem>
    11541144        <para>
    1155           In the &product-name; graphical user interface, you can
    1156           configure all these items in the global settings by choosing
    1157           <emphasis role="bold">File</emphasis>,
    1158           <emphasis role="bold">Preferences</emphasis>,
    1159           <emphasis role="bold">Network</emphasis>. This lists all
    1160           host-only networks which are presently in use. Click on the
    1161           network name and then on
    1162           <emphasis role="bold">Edit</emphasis>. You can then modify the
    1163           adapter and DHCP settings.
    1164         </para>
    1165       </listitem>
    1166 
    1167       <listitem>
    1168         <para>
    1169           Alternatively, you can use <command>VBoxManage
    1170           dhcpserver</command> on the command line. See
    1171           <xref
    1172           linkend="vboxmanage-dhcpserver" />.
     1145          In the VirtualBox Manager you can configure the DHCP server by
     1146          choosing <emphasis role="bold">File</emphasis>,
     1147          <emphasis role="bold">Host Network Manager</emphasis>. The
     1148          Host Network Manager lists all host-only networks which are
     1149          presently in use. Select the network name and then use the
     1150          <emphasis role="bold">DHCP Server</emphasis> tab to configure
     1151          DHCP server settings.
     1152        </para>
     1153      </listitem>
     1154
     1155      <listitem>
     1156        <para>
     1157          Alternatively, you can use the <command>VBoxManage
     1158          dhcpserver</command> command. See
     1159          <xref linkend="vboxmanage-dhcpserver" />.
    11731160        </para>
    11741161      </listitem>
    … …  
    13781365      For more information on setting up VDE networks, please see the
    13791366      documentation accompanying the software. See also
    1380       <ulink
    1381         url="http://wiki.virtualsquare.org/wiki/index.php/VDE_Basic_Networking" />.
     1367      <ulink url="http://wiki.virtualsquare.org" />.
    13821368    </para>
    13831369

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

    r82350 r87077  
    8888    href="../common/oracle-support-en.xml" />
    8989
     90  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
     91    href="../common/oracle-diversity.xml" />
     92
    9093</preface>

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

    r85107 r87077  
    2222      <listitem>
    2323        <para>
    24           <emphasis role="strong">Keep software up to date</emphasis>.
    25           One of the principles of good security practise is to keep all
     24          <emphasis role="bold">Keep software up to date</emphasis>. One
     25          of the principles of good security practise is to keep all
    2626          software versions and patches up to date. Activate the
    2727          &product-name; update notification to get notified when a new
    … …  
    3535      <listitem>
    3636        <para>
    37           <emphasis role="strong">Restrict network access to critical
     37          <emphasis role="bold">Restrict network access to critical
    3838          services.</emphasis> Use proper means, for instance a
    3939          firewall, to protect your computer and your guests from
    … …  
    4646      <listitem>
    4747        <para>
    48           <emphasis role="strong">Follow the principle of least
     48          <emphasis role="bold">Follow the principle of least
    4949          privilege.</emphasis> The principle of least privilege states
    5050          that users should be given the least amount of privilege
    … …  
    6363      <listitem>
    6464        <para>
    65           <emphasis role="strong">Monitor system activity.</emphasis>
     65          <emphasis role="bold">Monitor system activity.</emphasis>
    6666          System security builds on three pillars: good security
    6767          protocols, proper system configuration and system monitoring.
    … …  
    7575      <listitem>
    7676        <para>
    77           <emphasis role="strong">Keep up to date on latest security
     77          <emphasis role="bold">Keep up to date on latest security
    7878          information.</emphasis> Oracle continually improves its
    7979          software and documentation. Check this note yearly for
    … …  
    9797        The &product-name; base package should be downloaded only from a
    9898        trusted source, for instance the official website
    99         <ulink url="http://www.virtualbox.org" />.
    100         The integrity of the package should be verified with the
    101         provided SHA256 checksum which can be found on the official
    102         website.
     99        <ulink url="http://www.virtualbox.org" />. The integrity of the
     100        package should be verified with the provided SHA256 checksum
     101        which can be found on the official website.
    103102      </para>
    104103
    … …  
    508507          <para>
    509508            When using the &product-name; Extension Pack provided by
    510             Oracle for disk encryption, the data stored in disk images can
    511             optionally be encrypted. See <xref linkend="diskencryption" />.
    512             This feature covers disk image content only. All other data
    513             for a virtual machine is stored unencrypted, including the VM's
    514             memory and device state which is stored as part of a saved
    515             state, both when created explicitly or part of a snapshot of a
    516             running VM.
     509            Oracle for disk encryption, the data stored in disk images
     510            can optionally be encrypted. See
     511            <xref linkend="diskencryption" />. This feature covers disk
     512            image content only. All other data for a virtual machine is
     513            stored unencrypted, including the VM's memory and device
     514            state which is stored as part of a saved state, both when
     515            created explicitly or part of a snapshot of a running VM.
    517516          </para>
    518517        </listitem>
    … …  
    538537      issues. By default VirtualBox will configure the VMs to run in a
    539538      secure manner, however this may not always be possible without
    540       additional user actions (for example host OS / firmware configuration
    541       changes).
     539      additional user actions such as host OS or firmware configuration
     540      changes.
    542541    </para>
    543542
    … …  
    630629          A more aggressive flushing option is provided via the
    631630          <command>VBoxManage modifyvm</command>
    632           <option>--l1d-flush-on-vm-entry</option> option. When
    633           enabled the level 1 data cache will be flushed on every VM
    634           entry. The performance impact is greater than with the default
    635           option, though this of course depends on the workload.
    636           Workloads producing a lot of VM exits (like networking, VGA
    637           access, and similiar) will probably be most impacted.
     631          <option>--l1d-flush-on-vm-entry</option> option. When enabled
     632          the level 1 data cache will be flushed on every VM entry. The
     633          performance impact is greater than with the default option,
     634          though this of course depends on the workload. Workloads
     635          producing a lot of VM exits (like networking, VGA access, and
     636          similiar) will probably be most impacted.
    638637        </para>
    639638
    640639        <para>
    641640          For users not concerned by this security issue, the default
    642           mitigation can be disabled using the <command>VBoxManage modifyvm
    643           name --l1d-flush-on-sched off</command> command.
     641          mitigation can be disabled using the <command>VBoxManage
     642          modifyvm name --l1d-flush-on-sched off</command> command.
    644643        </para>
    645644
    … …  
    706705
    707706        <para>
    708           The <command>VBoxManage modifyvm</command> command provides a more
    709           aggressive flushing option is provided by means of the
    710           <option>--mds-clear-on-vm-entry</option> option. When
    711           enabled the affected buffers will be cleared on every VM
    712           entry. The performance impact is greater than with the default
    713           option, though this of course depends on the workload.
    714           Workloads producing a lot of VM exits (like networking, VGA
    715           access, and similiar) will probably be most impacted.
     707          The <command>VBoxManage modifyvm</command> command provides a
     708          more aggressive flushing option is provided by means of the
     709          <option>--mds-clear-on-vm-entry</option> option. When enabled
     710          the affected buffers will be cleared on every VM entry. The
     711          performance impact is greater than with the default option,
     712          though this of course depends on the workload. Workloads
     713          producing a lot of VM exits (like networking, VGA access, and
     714          similiar) will probably be most impacted.
    716715        </para>
    717716
    718717        <para>
    719718          For users not concerned by this security issue, the default
    720           mitigation can be disabled using the <command>VBoxManage modifyvm
    721           name --mds-clear-on-sched off</command> command.
     719          mitigation can be disabled using the <command>VBoxManage
     720          modifyvm name --mds-clear-on-sched off</command> command.
    722721        </para>
    723722

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

    r82952 r87077  
    5656    <para>
    5757      In a computing device, hard disks and CD/DVD drives are connected
    58       to a device called hard disk controller which drives hard disk
     58      to a device called a hard disk controller, which drives hard disk
    5959      operation and data transfers. &product-name; can emulate the most
    6060      common types of hard disk controllers typically found in computing
    … …  
    7373          support CD-ROM drives and other types of removable media. In
    7474          physical PCs, this standard uses flat ribbon parallel cables
    75           with 40 or 80 wires. Each such cable can connect two devices
    76           to a controller, which have traditionally been called
    77           <emphasis>master</emphasis> and <emphasis>slave</emphasis>.
    78           Typical PCs had two connectors for such cables. As a result,
    79           support for up to four IDE devices was most common.
     75          with 40 or 80 wires. Each such cable can connect two devices,
     76          called device 0 and device 1, to a controller. Typical PCs had
     77          two connectors for such cables. As a result, support for up to
     78          four IDE devices was most common: primary device 0, primary
     79          device 1, secondary device 0, and secondary device 1.
    8080        </para>
    8181
    … …  
    8484          controller enabled, which gives you up to four virtual storage
    8585          devices that you can attach to the machine. By default, one of
    86           these virtual storage devices, the secondary master, is
    87           preconfigured to be the virtual machine's virtual CD/DVD
    88           drive. However, you can change the default setting.
     86          these virtual storage devices, device 0 on the secondary
     87          channel, is preconfigured to be the virtual machine's virtual
     88          CD/DVD drive. However, you can change the default setting.
    8989        </para>
    9090
    … …  
    106106          After you have created a new virtual machine with the
    107107          <emphasis role="bold">New Virtual Machine</emphasis> wizard of
    108           the graphical user interface, you will typically see one IDE
     108          the VirtualBox Manager, you will typically see one IDE
    109109          controller in the machine's
    110110          <emphasis role="bold">Storage</emphasis> settings. The virtual
    … …  
    314314          standard to connect virtual storage devices like hard disks or
    315315          optical drives to a VM. Recent Linux and Windows versions
    316           support these devices (Windows needs additional drivers).
    317           Currently the virtio-scsi controller is experimental.
     316          support these devices, but Windows needs additional drivers.
     317          Currently virtio-scsi controller support is experimental.
    318318        </para>
    319319
    … …  
    321321          <para>
    322322            The virtio-scsi controller will only be seen by OSes with
    323             device support for it. In particular, <emphasis>there is
    324             no built-in support in Windows</emphasis>. So Windows will
    325             not see such disks unless you install additional drivers.
     323            device support for it. In particular, <emphasis>there is no
     324            built-in support in Windows</emphasis>. So Windows will not
     325            see such disks unless you install additional drivers.
    326326          </para>
    327327        </warning>
    … …  
    361361      <listitem>
    362362        <para>
    363           Up to 255 slots attached to the SAS controller, if enabled
    364           and supported by the guest OS.
     363          Up to 255 slots attached to the SAS controller, if enabled and
     364          supported by the guest OS.
    365365        </para>
    366366      </listitem>
    … …  
    382382      <listitem>
    383383        <para>
    384           Up to 256 slots attached to the virtio-scsi controller, if enabled
    385           and supported by the guest OS.
     384          Up to 256 slots attached to the virtio-scsi controller, if
     385          enabled and supported by the guest OS.
    386386        </para>
    387387      </listitem>
    … …  
    544544    <figure id="fig-virtual-media-manager">
    545545      <title>The Virtual Media Manager</title>
    546       <mediaobject>
     546    <mediaobject>
    547547        <imageobject>
    548548          <imagedata align="center" fileref="images/virtual-disk-manager.png"

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

    r86092 r87077  
    763763      <para>
    764764        <literal>[<replaceable>x</replaceable>]</literal> specifies the
    765         disk for IDE. <literal>0</literal> represents the master device
    766         on the first channel, <literal>1</literal> represents the slave
    767         device on the first channel, <literal>2</literal> represents the
    768         master device on the second channel, and <literal>3</literal>
    769         represents the slave device on the second channel. For SATA, use
    770         values between <literal>0</literal> and <literal>29</literal>.
    771         This configuration option applies to disks only. Do not use this
     765        disk. For IDE, <literal>0</literal> represents device 0 on the
     766        primary channel, <literal>1</literal> represents device 1 on the
     767        primary channel, <literal>2</literal> represents device 0 on the
     768        secondary channel, and <literal>3</literal> represents device 1
     769        on the secondary channel. For SATA, use values between
     770        <literal>0</literal> and <literal>29</literal>. This
     771        configuration option applies to disks only. Do not use this
    772772        option for CD or DVD drives.
    773773      </para>
    … …  
    822822      <para>
    823823        <literal>[<replaceable>x</replaceable>]</literal> specifies the
    824         disk. is 0 for the master device on the first channel, 1 for the
    825         slave device on the first channel, 2 for the master device on
    826         the second channel or 3 for the master device on the second
     824        disk. Enter <literal>0</literal> for device 0 on the primary
     825        channel, <literal>1</literal> for device 1 on the primary
     826        channel, <literal>2</literal> for device 0 on the secondary
     827        channel, or <literal>3</literal> for device 1 on the secondary
    827828        channel.
    828829      </para>
    … …  
    13101311  <sect1 id="ts_lin-x11-guests">
    13111312
    1312     <title>Linux and X11/Wayland Guests</title>
     1313    <title>Linux and X11 Guests</title>
    13131314
    13141315    <sect2 id="ts_linux-guest-high-cpu">
    … …  
    13861387    <sect2 id="ts_linux-guest-x11-services">
    13871388
    1388       <title>Shared Clipboard, Auto-Resizing, and Seamless Desktop in X11/Wayland Guests</title>
    1389 
    1390       <para>
    1391         Guest desktop services in guests running the X11/Wayland window system
     1389      <title>Shared Clipboard, Auto-Resizing, and Seamless Desktop in X11 Guests</title>
     1390
     1391      <para>
     1392        Guest desktop services in guests running the X11 window system
    13921393        such as Oracle Solaris and Linux, are provided by a guest
    13931394        service called <command>VBoxClient</command>, which runs under
    … …  
    14001401<screen>$ VBoxClient --clipboard
    14011402$ VBoxClient --display
    1402 $ VBoxClient --seamless
    1403 $ VBoxClient --vmsvga</screen>
     1403$ VBoxClient --seamless</screen>
    14041404
    14051405      <para>

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

    r85929 r87077  
    697697      This command changes the properties of a registered virtual
    698698      machine which is not running. Most of the properties that this
    699       command makes available correspond to the VM settings that
    700       &product-name; graphical user interface displays in each VM's
     699      command makes available correspond to the VM settings that the
     700      VirtualBox Manager displays in each VM's
    701701      <emphasis role="bold">Settings</emphasis> dialog. These are
    702702      described in <xref linkend="BasicConcepts" />. However, some of
    … …  
    60746074      This command is used to change global settings which affect the
    60756075      entire &product-name; installation. Some of these correspond to
    6076       the settings in the <emphasis role="bold">Global
    6077       Settings</emphasis> dialog in the graphical user interface. The
    6078       following properties are available:
     6076      the settings in the <emphasis role="bold">Preferences</emphasis>
     6077      dialog in the VirtualBox Manager. The following properties are
     6078      available:
    60796079    </para>
    60806080
    … …  
    90169016  <xi:include href="user_man_VBoxManage-signova.xml"        xpointer="element(/1)" xmlns:xi="http://www.w3.org/2001/XInclude" />
    90179017
    9018   <xi:include href="user_man_VBoxManage-updatecheck.xml" xpointer="element(/1)" xmlns:xi="http://www.w3.org/2001/XInclude" />
     9018  <xi:include href="user_man_VBoxManage-updatecheck.xml"    xpointer="element(/1)" xmlns:xi="http://www.w3.org/2001/XInclude" />
    90199019
    90209020<!-- TODO: Figure out how we can handle other manpages. The xml is bolted to
Note: See TracChangeset for help on using the changeset viewer.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette