VirtualBox

Changeset 38265 in vbox for trunk/doc/manual/en_US


Ignore:
Timestamp:
Aug 1, 2011 2:28:10 PM (13 years ago)
Author:
vboxsync
Message:

Manual: updated clone VM GUI docu

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/manual/en_US/user_Introduction.xml

    r38089 r38265  
    14581458
    14591459    <para>To experiment with a VM configuration, test different guest OS levels
    1460     or to simply backup a VM, VirtualBox can create a full copy of an existing
    1461     VM.<footnote>Cloning support was introduced with VirtualBox
     1460    or to simply backup a VM, VirtualBox can create a full or a linked copy of
     1461    an existing VM.<footnote>Cloning support was introduced with VirtualBox
    14621462    4.1.</footnote></para>
    14631463   
     
    14721472   
    14731473    <para>This wizard can be invoked from the context menu of the Manager's VM
    1474     list (select "Clone") or the "Snapshots" view of the selected VM. You have
    1475     the choice to create a exact copy of the current state without any
    1476     snapshots or with all snapshots included.<!-- If you
    1477     invoke the clone VM wizard from the latter place and have selected a
    1478     specific snapshot you can additional decide if you want to clone that
    1479     snapshot including all child's, but without any independent snapshots in
    1480     the tree.--></para>
     1474    list (select "Clone") or the "Snapshots" view of the selected VM. First
     1475    choose a new name for the clone. When you select <emphasis
     1476    role="bold">Reinitialize the MAC address of all network cards</emphasis>
     1477    every network card get a new MAC address assigned. This is useful when
     1478    both, the source VM and the cloned VM, have to operate on the same network.
     1479    If you leave this unchanged, all network cards have the same MAC address
     1480    like the one in the source VM. Depending on how you invoke the wizard you
     1481    have different choices for the cloning operation. First you need to decide
     1482    if the clone should be linked to the source VM or a fully independent clone
     1483    should be created:</para>
     1484    <itemizedlist>
     1485      <listitem>
     1486         <para><emphasis role="bold">Full clone:</emphasis> In this mode all
     1487             depending disk images are copied to the new VM folder. The clone
     1488             can fully operate without the source VM.
     1489         </para>
     1490      </listitem>
     1491
     1492      <listitem>
     1493         <para><emphasis role="bold">Linked clone:</emphasis> In this mode new
     1494             differencing disk images are created where the parent disk images
     1495             are the source disk images. If you selected the current state of
     1496             the source VM as clone point, a new snapshot will be created
     1497             implicitly.
     1498         </para>
     1499      </listitem>
     1500    </itemizedlist>
     1501       
     1502    <para>After selecting the clone mode, you need to decide about what exactly
     1503    should be cloned. You can always create a clone of the <emphasis
     1504        role="italic">current state</emphasis> only or <emphasis
     1505        role="italic">all</emphasis>. When you select <emphasis
     1506        role="italic">all</emphasis>, the current state and in addition all
     1507    snapshots are cloned. Have you started from a snapshot which has additional
     1508    children, you can also clone the <emphasis role="italic">current state and
     1509        all children</emphasis>. This creates a clone starting with this
     1510    snapshot and includes all child snaphots.</para>
    14811511
    14821512    <para>The clone operation itself can be a lengthy operation depending on
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