summaryrefslogtreecommitdiff
path: root/man/virt-clone.rst
blob: 1d5d128cfcb0bd966f4102f529b8e66af105aa00 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
==========
virt-clone
==========

-------------------------------------
clone existing virtual machine images
-------------------------------------

:Manual section: 1
:Manual group: Virtualization Support


SYNOPSIS
========


``virt-clone`` [OPTION]...


DESCRIPTION
===========


``virt-clone`` is a command line tool for cloning existing virtual machine
images using the ``libvirt`` hypervisor management library. It will copy
the disk images of any existing virtual machine, and define a new guest
with an identical virtual hardware configuration. Elements which require
uniqueness will be updated to avoid a clash between old and new guests.

By default, virt-clone will show an error if the necessary information to
clone the guest is not provided. The --auto-clone option will generate
all needed input, aside from the source guest to clone.

Please note, virt-clone does not change anything _inside_ the guest OS, it
only duplicates disks and does host side changes. So things like changing
passwords, changing static IP address, etc are outside the scope of this
tool. For these types of changes, please see ``virt-sysprep``.


GENERAL OPTIONS
===============

Most options are not required. Minimum requirements are --original or
--original-xml (to specify the guest to clone), --name, and appropriate
storage options via -file.


``--connect`` URI
    Connect to a non-default hypervisor. See virt-install(1) for details


``-o``, ``--original`` ORIGINAL_GUEST
    Name of the original guest to be cloned. This guest must be shut off.


``--original-xml`` ORIGINAL_XML
    Libvirt guest xml file to use as the original guest. The guest does not need to
    be defined on the libvirt connection. This takes the place of the
    ``--original`` parameter.


``--auto-clone``
    Generate a new guest name, and paths for new storage.

    An example of possible generated output:

    .. code-block::

        Original name        : MyVM
        Generated clone name : MyVM-clone

        Original disk path   : /home/user/foobar.img
        Generated disk path  : /home/user/foobar-clone.img


    If generated names collide with existing VMs or storage, a number is appended,
    such as foobar-clone-1.img, or MyVM-clone-3.


``-n``, ``--name`` NAME
    Name of the new guest virtual machine instance. This must be unique amongst
    all guests known to the hypervisor connection, including those not
    currently active.


``-u``, ``--uuid`` UUID
    UUID for the guest; if none is given a random UUID will be generated. If you
    specify UUID, you should use a 32-digit hexadecimal number. UUID are intended
    to be unique across the entire data center, and indeed world. Bear this in
    mind if manually specifying a UUID


``-f``, ``--file`` PATH
    Path to the file, disk partition, or logical volume to use as the backing store
    for the new guest's virtual disk. If the original guest has multiple disks,
    this parameter must be repeated multiple times, once per disk in the original
    virtual machine.


``--nvram`` NVRAMFILE
    Optional path to the new nvram VARS file, if no path is specified and the
    guest has nvram the new nvram path will be auto-generated. If the guest
    doesn't have nvram this option will be ignored.

``--force-copy`` TARGET
    Force cloning the passed disk target ('hdc', 'sda', etc.). By default,
    ``virt-clone`` will skip certain disks, such as those marked 'readonly' or
    'shareable'.


``--skip-copy`` TARGET
    Skip cloning the passed disk target ('hdc', 'sda', etc.). By default,
    ``virt-clone`` will clone certain disk images, typically read/write
    devices. Use this to skip copying of a specific device, so the new
    VM uses the same storage path as the original VM.


``--nonsparse``
    Fully allocate the new storage if the path being cloned is a sparse file.
    See virt-install(1) for more details on sparse vs. nonsparse.


``--preserve-data``
    No storage is cloned: disk images specific by --file are preserved as is,
    and referenced in the new clone XML. This is useful if you want to clone
    a VM XML template, but not the storage contents.


``--reflink``
    When --reflink is specified, perform a lightweight copy. This is much faster
    if source images and destination images are all on the same btrfs filesystem.
    If COW copy is not possible, then virt-clone fails.


``-m``, ``--mac`` MAC
    Fixed MAC address for the guest; If this parameter is omitted, or the value
    ``RANDOM`` is specified a suitable address will be randomly generated. Addresses
    are applied sequentially to the networks as they are listed in the original
    guest XML.


``--print-xml``
    Print the generated clone XML and exit without cloning.


``--replace``
    Shutdown and remove any existing guest with the passed ``--name`` before
    cloning the original guest.


``-h``, ``--help``
    Show the help message and exit


``--version``
    Show program's version number and exit


``--check``
    Enable or disable some validation checks. See virt-install(1) for more details.


``-q``, ``--quiet``
    Suppress non-error output.


``-d``, ``--debug``
    Print debugging information to the terminal when running the install process.
    The debugging information is also stored in
    ``~/.cache/virt-manager/virt-clone.log`` even if this parameter is omitted.


EXAMPLES
========

Clone the guest called ``demo`` on the default connection, auto generating
a new name and disk clone path.

.. code-block::

   # virt-clone \
        --original demo \
        --auto-clone


Clone the guest called ``demo`` which has a single disk to copy

.. code-block::

   # virt-clone \
        --original demo \
        --name newdemo \
        --file /var/lib/xen/images/newdemo.img


Clone a QEMU guest with multiple disks

.. code-block::

   # virt-clone \
        --connect qemu:///system \
        --original demo \
        --name newdemo \
        --file /var/lib/xen/images/newdemo.img \
        --file /var/lib/xen/images/newdata.img


Clone a guest to a physical device which is at least as big as the
original guests disks. If the destination device is bigger, the
new guest can do a filesystem resize when it boots.

.. code-block::

   # virt-clone \
        --connect qemu:///system \
        --original demo \
        --name newdemo \
        --file /dev/HostVG/DemoVM \
        --mac 52:54:00:34:11:54


BUGS
====

Please see https://virt-manager.org/bugs


COPYRIGHT
=========

Copyright (C) Fujitsu Limited, Copyright (C) Red Hat, Inc,
and various contributors.
This is free software. You may redistribute copies of it under the terms
of the GNU General Public License https://www.gnu.org/licenses/gpl.html.
There is NO WARRANTY, to the extent permitted by law.


SEE ALSO
========

``virt-sysprep(1)``, ``virsh(1)``, ``virt-install(1)``, ``virt-manager(1)``, the project website https://virt-manager.org