132132.\" ========================================================================
133133.\"
134134.IX Title " VIRT-CLONE 1"
135- .TH VIRT-CLONE 1 "2009-01-26 " "perl v5.10.0" "Virtual Machine Install Tools"
135+ .TH VIRT-CLONE 1 "2009-03-03 " "perl v5.10.0" "Virtual Machine Install Tools"
136136.\" For nroff, turn off justification. Always turn off hyphenation; it makes
137137.\" way too many mistakes in technical documents.
138138.if n .ad l
@@ -149,78 +149,76 @@ images using the \f(CW\*(C`libvirt\*(C'\fR hypervisor management library. It wil
149149the disk images of any existing virtual machine, and define a new guest
150150with an identical virtual hardware configuration. Elements which require
151151uniqueness will be updated to avoid a clash between old and new guests.
152- .PP
153- Given suitable command line arguments, \f(CW \*( C` virt \- clone \*( C' \fR is capable of running
154- completely unattended, with the guest 'kickstarting' itself too. This allows
155- for easy automation of guest installs. A companion tool \f(CW \*( C` virt \- clone(1) \*( C' \fR is
156- provided for cloning pre-existing guests if their installation cannot be easily
157- automated from pristine media.
158152.SH "OPTIONS"
159153.IX Header " OPTIONS"
160- Any of the options can be omitted, in which case \f(CW \*( C` virt \- clone \*( C' \fR will run
161- interactively prompting for input as required.
154+ Most options are not required. Minimum requirements are \-\- original or
155+ \& \-\- original\- xml (to specify the guest to clone), \-\- name, and appropriate
156+ storage options via \- file.
162157.IP " \- h, \-\- help" 4
163158.IX Item " -h, --help"
164159Show the help message and exit
165- .IP " \- o \s- 1 ORIGINAL_GUEST\s 0 , \-\- original=ORIGINAL_GUEST" 4
160+ .IP " \-\- connect=CONNECT" 4
161+ .IX Item " --connect=CONNECT"
162+ Connect to a non-default hypervisor. See \fI virt \- install \fR \| (1) for details
163+ .Sh " General Options"
164+ .IX Subsection " General Options"
165+ General configuration parameters that apply to all guest clones.
166+ .IP " \- o \s- 1 ORIGINAL_GUEST\s 0 , \-\- original=ORIGINAL_GUEST" 2
166167.IX Item " -o ORIGINAL_GUEST, --original=ORIGINAL_GUEST"
167- Name or uuid for the original guest to be cloned. This guest must be shut
168- off since it is not possible to safely clone active guests at this time.
169- .IP " \- n \s- 1 NAME\s 0 , \-\- name=NAME" 4
168+ Name of the original guest to be cloned. This guest must be shut off or paused
169+ since it is not possible to safely clone active guests at this time.
170+ .IP " \-\- original\- xml=ORIGINAL_XML" 2
171+ .IX Item " --original-xml=ORIGINAL_XML"
172+ Libvirt guest xml file to use as the original guest. The guest does not need to
173+ be defined on the libvirt connection. This takes the place of the
174+ \& \f(CW \*( C` \-\- original \*( C' \fR parameter.
175+ .IP " \- n \s- 1 NAME\s 0 , \-\- name=NAME" 2
170176.IX Item " -n NAME, --name=NAME"
171177Name of the new guest virtual machine instance. This must be unique amongst
172- all guests known to the hypervisor on this machine, including those not
173- currently active. To re-define an existing guest, use the \f(CW virsh(1) \fR tool
174- to shut it down & delete it prior to running \f(CW \*( C` virt \- clone \*( C' \fR . This parameter
175- will be prompted for if omitted on the command line.
176- .IP " \- u \s- 1 UUID\s 0 , \-\- uuid=UUID" 4
178+ all guests known to the hypervisor connection, including those not
179+ currently active.
180+ .IP " \- u \s- 1 UUID\s 0 , \-\- uuid=UUID" 2
177181.IX Item " -u UUID, --uuid=UUID"
178- \& \s- 1 UUID\s 0 for the guest; if none is given a random \s- 1 UUID\s 0 will be generated. If you
182+ \& \s- 1 UUID\s 0 for the guest; if none is given a random \s- 1 UUID\s 0 will be generated. If you
179183specify \s- 1 UUID\s 0 , you should use a 32\- digit hexadecimal number. \s- 1 UUID\s 0 are intended
180184to be unique across the entire data center, and indeed world. Bear this in
181185mind if manually specifying a \s- 1 UUID\s 0
182- .IP " \- f \s- 1 DISKFILE\s 0 , \-\- file=DISKFILE" 4
186+ .Sh " Storage Configuration"
187+ .IX Subsection " Storage Configuration"
188+ .IP " \- f \s- 1 DISKFILE\s 0 , \-\- file=DISKFILE" 2
183189.IX Item " -f DISKFILE, --file=DISKFILE"
184190Path to the file, disk partition, or logical volume to use as the backing store
185191for the new guest's virtual disk. If the original guest has multiple disks,
186192this parameter must be repeated multiple times, once per disk in the original
187193virtual machine.
188- .IP " \- m \s- 1 MAC\s 0 , \-\- mac=MAC" 4
189- .IX Item " -m MAC, --mac=MAC"
190- Fixed \s- 1 MAC\s 0 address for the guest; If this parameter is omitted, or the value
191- \& \f(CW \*( C` RANDOM \*( C' \fR is specified a suitable address will be randomly generated. For
192- Xen virtual machines it is required that the first 3 pairs in the \s- 1 MAC\s 0 address
193- be the sequence '00:16:3e', while for \s- 1 QEMU\s 0 or \s- 1 KVM\s 0 virtual machines it must
194- be '54:52:00'.
195- .IP " \-\- connect=CONNECT Connect to hypervisor with \s- 1 URI\s 0 " 4
196- .IX Item " --connect=CONNECT Connect to hypervisor with URI"
197- Connect to a non-default hypervisor. The default connection is chosen based
198- on the following rules:
199- .RS 4
200- .IP " xen" 4
201- .IX Item " xen"
202- If running on a host with the Xen kernel (checks against /proc/xen)
203- .IP " qemu:///system" 4
204- .IX Item " qemu:///system"
205- If running on a bare metal kernel as root
206- .IP " qemu:///session" 4
207- .IX Item " qemu:///session"
208- If running on a bare metal kernel as non-root
209- .RE
210- .RS 4
211- .Sp
212- It is only necessary to provide the \f(CW \*( C` \-\- connect \*( C' \fR argument if this default
213- prioritization is incorrect, eg if wanting to use \s- 1 QEMU\s 0 while on a Xen kernel.
214- .RE
215- .IP " \-\- preserve\- data" 4
194+ .IP " \-\- force\- copy=TARGET" 2
195+ .IX Item " --force-copy=TARGET"
196+ Force cloning the passed disk target ('hdc', 'sda', etc.). By default,
197+ \& \f(CW \*( C` virt \- clone \*( C' \fR will skip certain disks, such as those marked 'readonly' or
198+ \& 'shareable'.
199+ .IP " \-\- nonsparse" 2
200+ .IX Item " --nonsparse"
201+ Fully allocate the new storage if the path being cloned is a sparse file.
202+ See \fI virt \- install \fR \| (1) for more details on sparse vs. nonsparse.
203+ .IP " \-\- preserve\- data" 2
216204.IX Item " --preserve-data"
217205Preserve a new file to use as the disk image for the new guest.
218- .IP " \- d, \-\- debug" 4
206+ .Sh " Networking Configuration"
207+ .IX Subsection " Networking Configuration"
208+ .IP " \- m \s- 1 MAC\s 0 , \-\- mac=MAC" 2
209+ .IX Item " -m MAC, --mac=MAC"
210+ Fixed \s- 1 MAC\s 0 address for the guest; If this parameter is omitted, or the value
211+ \& \f(CW \*( C` RANDOM \*( C' \fR is specified a suitable address will be randomly generated. Addresses
212+ are applied sequentially to the networks as they are listed in the original
213+ guest \s- 1 XML\s 0 .
214+ .Sh " Miscellaneous Options"
215+ .IX Subsection " Miscellaneous Options"
216+ .IP " \- d, \-\- debug" 2
219217.IX Item " -d, --debug"
220218Print debugging information to the terminal when running the install process.
221219The debugging information is also stored in \f(CW \*( C` $HOME/.virtinst/virt \- clone.log \*( C' \fR
222220even if this parameter is omitted.
223- .IP " \-\- force" 4
221+ .IP " \-\- force" 2
224222.IX Item " --force"
225223Prevent interactive prompts. If the intended prompt was a yes/no prompt, always
226224say yes. For any other prompts, the application will exit.
0 commit comments