1virt-v2v(1) Virtualization Support virt-v2v(1)
2
6 virt-v2v - Convert a guest to use KVM
7
9 virt-v2v [-i mode] [other -i* options]
10 [-o mode] [other -o* options]
11 [guest|filename]
12
14 Virt-v2v converts a single guest from a foreign hypervisor to run on
15 KVM. It can read Linux and Windows guests running on VMware, Xen,
16 Hyper-V and some other hypervisors, and convert them to KVM managed by
17 libvirt, OpenStack, oVirt, Red Hat Virtualisation (RHV) or several
18 other targets. It can modify the guest to make it bootable on KVM and
19 install virtio drivers so it will run quickly.
20 There is also a companion front-end called virt-p2v(1) which comes as
22 an ISO, CD or PXE image that can be booted on physical machines to
23 virtualize those machines (physical to virtual, or p2v).
24 To estimate the disk space needed before conversion, see
26 virt-v2v-inspector(1).
27 For in-place conversion, there is a separate tool called
29 virt-v2v-in-place(1).
30 Input and Output
32 You normally run virt-v2v with several -i* options controlling the
33 input mode and also several -o* options controlling the output mode.
34 In this sense, "input" refers to the source foreign hypervisor such as
35 VMware, and "output" refers to the target KVM-based management system
36 such as oVirt or OpenStack.
37 The input and output sides of virt-v2v are separate and unrelated.
39 Virt-v2v can read from any input and write to any output. Therefore
40 these sides of virt-v2v are documented separately in this manual.
41 Virt-v2v normally copies from the input to the output, called "copying
43 mode". In this case the source guest is always left unchanged. In-
44 place conversions may be done using virt-v2v-in-place(1).
45 Other virt-v2v topics
47 virt-v2v-support(1) — Supported hypervisors, virtualization management
48 systems, guests.
49 virt-v2v-input-vmware(1) — Input from VMware.
51 virt-v2v-input-xen(1) — Input from Xen.
53 virt-v2v-output-local(1) — Output to local files or local libvirt.
55 virt-v2v-output-rhv(1) — Output to oVirt or RHV.
57 virt-v2v-output-openstack(1) — Output to OpenStack.
59 virt-v2v-release-notes-1.42(1) — Release notes for 1.42 release.
61 virt-v2v-release-notes-2.0(1) — Release notes for 2.0 release.
63 virt-v2v-release-notes-2.2(1) — Release notes for 2.2 release.
65
67 Convert from VMware vCenter server to local libvirt
68 You have a VMware vCenter server called "vcenter.example.com", a
69 datacenter called "Datacenter", and an ESXi hypervisor called "esxi".
70 You want to convert a guest called "vmware_guest" to run locally under
71 libvirt.
72 virt-v2v -ic vpx://vcenter.example.com/Datacenter/esxi vmware_guest
74 In this case you will most likely have to run virt-v2v as "root", since
76 it needs to talk to the system libvirt daemon and copy the guest disks
77 to /var/lib/libvirt/images.
78 For more information see virt-v2v-input-vmware(1).
80 Convert from VMware to RHV/oVirt
82 This is the same as the previous example, except you want to send the
83 guest to a RHV Data Domain using the RHV REST API. Guest network
84 interface(s) are connected to the target network called "ovirtmgmt".
85 virt-v2v -ic vpx://vcenter.example.com/Datacenter/esxi vmware_guest \
87 -o rhv-upload -oc https://ovirt-engine.example.com/ovirt-engine/api \
88 -os ovirt-data -op /tmp/ovirt-admin-password -of raw \
89 -oo rhv-cafile=/tmp/ca.pem --bridge ovirtmgmt
90 In this case the host running virt-v2v acts as a conversion server.
92 For more information see virt-v2v-output-rhv(1).
94 Convert from ESXi hypervisor over SSH to local libvirt
96 You have an ESXi hypervisor called "esxi.example.com" with SSH access
97 enabled. You want to convert from VMFS storage on that server to a
98 local file.
99 virt-v2v \
101 -i vmx -it ssh \
102 "ssh://root@esxi.example.com/vmfs/volumes/datastore1/guest/guest.vmx" \
103 -o local -os /var/tmp
104 The guest must not be running. Virt-v2v would not need to be run as
106 root in this case.
107 For more information about converting from VMX files see
109 virt-v2v-input-vmware(1).
110 Convert disk image to OpenStack
112 Given a disk image from another hypervisor that you want to convert to
113 run on OpenStack (only KVM-based OpenStack is supported), you can run
114 virt-v2v inside an OpenStack VM (called "v2v-vm" below), and do:
115 virt-v2v -i disk disk.img -o openstack -oo server-id=v2v-vm
117 See virt-v2v-output-openstack(1).
119 Convert disk image to disk image
121 Given a disk image from another hypervisor that you want to convert to
122 run on KVM, you have two options. The simplest way is to try:
123 virt-v2v -i disk disk.img -o local -os /var/tmp
125 where virt-v2v guesses everything about the input disk.img and (in this
127 case) writes the converted result to /var/tmp.
128 A more complex method is to write some libvirt XML describing the input
130 guest (if you can get the source hypervisor to provide you with libvirt
131 XML, then so much the better). You can then do:
132 virt-v2v -i libvirtxml guest-domain.xml -o local -os /var/tmp
134 Since guest-domain.xml contains the path(s) to the guest disk image(s)
136 you do not need to specify the name of the disk image on the command
137 line.
138 To convert a local disk image and immediately boot it in local qemu,
140 do:
141 virt-v2v -i disk disk.img -o qemu -os /var/tmp -oo qemu-boot
143
145 --help
146 Display help.
147 --bandwidth bps
149 --bandwidth-file filename
150 Some input methods are able to limit the network bandwidth they
151 will use statically or dynamically. In the first variant this sets
152 the bandwidth limit statically in bits per second. Formats like
153 "10M" may be used (meaning 10 megabits per second).
154 In the second variant the bandwidth is limited dynamically from the
156 content of the file (also in bits per second, in the same formats
157 supported by the first variant). You may use both parameters
158 together, meaning: first limit to a static rate, then you can
159 create the file while virt-v2v is running to adjust the rate
160 dynamically.
161 This is only supported for:
163 • input from Xen
165 • input from VMware VMX when using the SSH transport method
167 • input from VDDK
169 • -i libvirtxml when using HTTP or HTTPS disks
171 • input from VMware vCenter server
173 The options are silently ignored for other input methods.
175 -b ...
177 --bridge ...
178 See --network below.
179 --block-driver virtio-blk
181 --block-driver virtio-scsi
182 When choosing a block driver for Windows guests, prefer
183 "virtio-blk" or "virtio-scsi". The default is "virtio-blk".
184 Note this has no effect for Linux guests at the moment. That may
186 be added in future.
187 --colors
189 --colours
190 Use ANSI colour sequences to colourize messages. This is the
191 default when the output is a tty. If the output of the program is
192 redirected to a file, ANSI colour sequences are disabled unless you
193 use this option.
194 --compressed
196 This is the same as -oo compressed.
197 --echo-keys
199 When prompting for keys and passphrases, virt-v2v normally turns
200 echoing off so you cannot see what you are typing. If you are not
201 worried about Tempest attacks and there is no one else in the room
202 you can specify this flag to see what you are typing.
203 Note this options only applies to keys and passphrases for
205 encrypted devices and partitions, not for passwords used to connect
206 to remote servers.
207 -i disk
209 Set the input method to disk.
210 In this mode you can read a virtual machine disk image with no
212 metadata. virt-v2v tries to guess the best default metadata. This
213 is usually adequate but you can get finer control (eg. of memory
214 and vCPUs) by using -i libvirtxml instead. Only guests that use a
215 single disk can be imported this way.
216 -i libvirt
218 Set the input method to libvirt. This is the default.
219 In this mode you have to specify a libvirt guest name or UUID on
221 the command line. You may also specify a libvirt connection URI
222 (see -ic).
223 See "Starting the libvirt system instance" below.
225 -i libvirtxml
227 Set the input method to libvirtxml.
228 In this mode you have to pass a libvirt XML file on the command
230 line. This file is read in order to get metadata about the source
231 guest (such as its name, amount of memory), and also to locate the
232 input disks. See "Minimal XML for -i libvirtxml option" below.
233 -i local
235 This is the same as -i disk.
236 -i ova
238 Set the input method to ova.
239 In this mode you can read a VMware ova file. Virt-v2v will read
241 the ova manifest file and check the vmdk volumes for validity
242 (checksums) as well as analyzing the ovf file, and then convert the
243 guest. See virt-v2v-input-vmware(1).
244 -i vmx
246 Set the input method to vmx.
247 In this mode you can read a VMware vmx file directly or over SSH.
249 This is useful when VMware VMs are stored on an NFS server which
250 you can mount directly, or where you have access by SSH to an ESXi
251 hypervisor. See virt-v2v-input-vmware(1).
252 -ic libvirtURI
254 Specify a libvirt connection URI to use when reading the guest.
255 This is only used when -i libvirt.
256 Only local libvirt connections, VMware vCenter connections, or RHEL
258 5 Xen remote connections can be used. Other remote libvirt
259 connections will not work in general.
260 See also virt-v2v-input-vmware(1), virt-v2v-input-xen(1).
262 -if format
264 For -i disk only, this specifies the format of the input disk
265 image. For other input methods you should specify the input format
266 in the metadata.
267 -io OPTION=VALUE
269 Set input option(s) related to the current input mode or transport.
270 To display short help on what options are available you can use:
271 virt-v2v -it vddk -io "?"
273 -io vddk-libdir=LIBDIR
275 Set the VDDK library directory. This directory should contain
276 subdirectories called include, lib64 etc., but do not include lib64
277 actually in the parameter.
278 In most cases this parameter is required when using the -it vddk
280 (VDDK) transport. See virt-v2v-input-vmware(1) for details.
281 -io vddk-thumbprint=xx:xx:xx:...
283 Set the thumbprint of the remote VMware server.
284 This parameter is required when using the -it vddk (VDDK)
286 transport. See virt-v2v-input-vmware(1) for details.
287 -io vddk-config=FILENAME
289 -io vddk-cookie=COOKIE
290 -io vddk-nfchostport=PORT
291 -io vddk-port=PORT
292 -io vddk-snapshot=SNAPSHOT-MOREF
293 -io vddk-transports=MODE:MODE:...
294 When using VDDK mode, these options are passed unmodified to the
295 nbdkit(1) VDDK plugin. Please refer to nbdkit-vddk-plugin(1). Do
296 not use these options unless you know what you are doing. These
297 are all optional.
298 -ip filename
300 Supply a file containing a password to be used when connecting to
301 the target hypervisor. If this is omitted then the input
302 hypervisor may ask for the password interactively. Note the file
303 should contain the whole password, without any trailing newline,
304 and for security the file should have mode 0600 so that others
305 cannot read it.
306 -it ssh
308 When using -i vmx, this enables the ssh transport. See
309 virt-v2v-input-vmware(1).
310 -it vddk
312 Use VMware VDDK as a transport to copy the input disks. See
313 virt-v2v-input-vmware(1). If you use this parameter then you may
314 need to use other -io vddk* options to specify how to connect
315 through VDDK.
316 --key SELECTOR
318 Specify a key for LUKS, to automatically open a LUKS device when
319 using the inspection.
320 --key NAME:key:KEY_STRING
322 --key UUID:key:KEY_STRING
323 --key all:key:KEY_STRING
324 "NAME" is the libguestfs device name (eg. "/dev/sda1"). "UUID"
325 is the device UUID. "all" means try the key against any
326 encrypted device.
327 Use the specified "KEY_STRING" as passphrase.
329 --key NAME:file:FILENAME
331 --key UUID:file:FILENAME
332 --key all:file:FILENAME
333 Read the passphrase from FILENAME.
334 --key NAME:clevis
336 --key UUID:clevis
337 --key all:clevis
338 Attempt passphrase-less unlocking for the device with Clevis,
339 over the network. Please refer to "ENCRYPTED DISKS" in
340 guestfs(3) for more information on network-bound disk
341 encryption (NBDE).
342 Note that if any such option is present on the command line,
344 QEMU user networking will be automatically enabled for the
345 libguestfs appliance.
346 --keys-from-stdin
348 Read key or passphrase parameters from stdin. The default is to
349 try to read passphrases from the user by opening /dev/tty.
350 If there are multiple encrypted devices then you may need to supply
352 multiple keys on stdin, one per line.
353 Note --keys-from-stdin only applies to keys and passphrases for
355 encrypted devices and partitions, not for passwords used to connect
356 to remote servers.
357 --mac aa:bb:cc:dd:ee:ff:network:out
359 --mac aa:bb:cc:dd:ee:ff:bridge:out
360 Map source NIC MAC address to a network or bridge.
361 See "Networks and bridges" below.
363 --mac aa:bb:cc:dd:ee:ff:ip:ipaddr[,gw[,len[,ns,ns,...]]]
365 Force a particular interface (controlled by its MAC address) to
366 have a static IP address after boot.
367 The fields in the parameter are: "ipaddr" is the IP address. "gw"
369 is the optional gateway IP address. "len" is the subnet mask
370 length (an integer). The final parameters are zero or more
371 nameserver IP addresses.
372 This option can be supplied zero or more times.
374 You only need to use this option for certain broken guests such as
376 Windows which are unable to preserve MAC to static IP address
377 mappings automatically. You don't need to use it if Windows is
378 using DHCP. It is currently ignored for Linux guests since they do
379 not have this problem.
380 --machine-readable
382 --machine-readable=format
383 This option is used to make the output more machine friendly when
384 being parsed by other programs. See "Machine readable output"
385 below.
386 -n in:out
388 -n out
389 --network in:out
390 --network out
391 -b in:out
392 -b out
393 --bridge in:out
394 --bridge out
395 Map network (or bridge) called "in" to network (or bridge) called
396 "out". If no "in:" prefix is given, all other networks (or
397 bridges) are mapped to "out".
398 See "Networks and bridges" below.
400 -o disk
402 This is the same as -o local.
403 -o glance
405 This is a legacy option. You should probably use -o openstack
406 instead.
407 Set the output method to OpenStack Glance. In this mode the
409 converted guest is uploaded to Glance. See
410 virt-v2v-output-openstack(1).
411 -o kubevirt
413 Set the output method to kubevirt. Note the way this mode works is
414 experimental and will change in future.
415 In this mode, the converted guest is written to a local directory
417 specified by -os /dir (the directory must exist). The converted
418 guest’s disks are written to:
419 /dir/name-sda
421 /dir/name-sdb
422 [etc]
423 and guest metadata is created in the associated YAML file:
425 /dir/name.yaml
427 where "name" is the guest name.
429 -o libvirt
431 Set the output method to libvirt. This is the default.
432 In this mode, the converted guest is created as a libvirt guest.
434 You may also specify a libvirt connection URI (see -oc).
435 See "Starting the libvirt system instance" below, and
437 virt-v2v-output-local(1).
438 -o local
440 Set the output method to local.
441 In this mode, the converted guest is written to a local directory
443 specified by -os /dir (the directory must exist). The converted
444 guest’s disks are written as:
445 /dir/name-sda
447 /dir/name-sdb
448 [etc]
449 and a libvirt XML file is created containing guest metadata:
451 /dir/name.xml
453 where "name" is the guest name.
455 -o null
457 Set the output method to null.
458 The guest is converted and copied but the results are thrown away
460 and no metadata is written.
461 -o openstack
463 Set the output method to OpenStack. See
464 virt-v2v-output-openstack(1).
465 -o ovirt
467 This is the same as -o rhv.
468 -o ovirt-upload
470 This is the same as -o rhv-upload.
471 -o qemu
473 Set the output method to qemu.
474 This is similar to -o local, except that a shell script is written
476 which you can use to boot the guest in qemu. The converted disks
477 and shell script are written to the directory specified by -os.
478 When using this output mode, you can also specify the -oo qemu-boot
480 option which boots the guest under qemu immediately.
481 -o rhev
483 This is the same as -o rhv.
484 -o rhv
486 Set the output method to rhv.
487 The converted guest is written to a RHV Export Storage Domain. The
489 -os parameter must also be used to specify the location of the
490 Export Storage Domain. Note this does not actually import the
491 guest into RHV. You have to do that manually later using the UI.
492 See virt-v2v-output-rhv(1).
494 -o rhv-upload
496 Set the output method to rhv-upload.
497 The converted guest is written directly to a RHV Data Domain. This
499 is a faster method than -o rhv, but requires oVirt or RHV ≥ 4.2.
500 See virt-v2v-output-rhv(1).
502 -o vdsm
504 Set the output method to vdsm.
505 This mode is similar to -o rhv, but the full path to the data
507 domain must be given:
508 /rhv/data-center/<data-center-uuid>/<data-domain-uuid>. This mode
509 is only used when virt-v2v runs under VDSM control.
510 -oa sparse
512 -oa preallocated
513 Set the output file allocation mode. The default is "sparse".
514 -oc URI
516 Specify a connection URI to use when writing the converted guest.
517 For -o libvirt this is the libvirt URI. Only local libvirt
519 connections can be used. Remote libvirt connections will not work.
520 See virt-v2v-output-local(1) for further information.
521 -of format
523 When converting the guest, convert the disks to the given format.
524 If not specified, then the input format is used.
526 -on name
528 Rename the guest when converting it. If this option is not used
529 then the output name is the same as the input name.
530 -oo OPTION=VALUE
532 Set output option(s) related to the current output mode. To
533 display short help on what options are available you can use:
534 virt-v2v -o rhv-upload -oo "?"
536 -oo compressed
538 For outputs which support qcow2 format (-of qcow2), this writes a
539 compressed qcow2 file. It is the equivalent to the -c option of
540 qemu-img(1).
541 -oo guest-id="ID"
543 For -o openstack (virt-v2v-output-openstack(1)) only, set a guest
544 ID which is saved on each Cinder volume in the "virt_v2v_guest_id"
545 volume property.
546 -oo qemu-boot
548 When using -o qemu only, this boots the guest immediately after
549 virt-v2v finishes.
550 -oo verify-server-certificate
552 -oo verify-server-certificate="true|false"
553 For -o openstack (virt-v2v-output-openstack(1)) only, this can be
554 used to disable SSL certification validation when connecting to
555 OpenStack by specifying -oo verify-server-certificate=false.
556 -oo os-*=*
558 For -o openstack (virt-v2v-output-openstack(1)) only, set optional
559 OpenStack authentication. For example -oo os-username=NAME is
560 equivalent to "openstack --os-username=NAME".
561 -oo rhv-cafile=ca.pem
563 For -o rhv-upload (virt-v2v-output-rhv(1)) only, the ca.pem file
564 (Certificate Authority), copied from /etc/pki/ovirt-engine/ca.pem
565 on the oVirt engine.
566 -oo rhv-cluster="CLUSTERNAME"
568 For -o rhv-upload (virt-v2v-output-rhv(1)) only, set the RHV
569 Cluster Name. If not given it uses "Default".
570 -oo rhv-proxy
572 For -o rhv-upload (virt-v2v-output-rhv(1)) only, proxy the upload
573 through oVirt Engine. This is slower than uploading directly to
574 the oVirt node but may be necessary if you do not have direct
575 network access to the nodes.
576 -oo rhv-verifypeer
578 For -o rhv-upload (virt-v2v-output-rhv(1)) only, verify the
579 oVirt/RHV server’s identity by checking the server‘s certificate
580 against the Certificate Authority.
581 -oo server-id="NAME|UUID"
583 For -o openstack (virt-v2v-output-openstack(1)) only, set the name
584 of the conversion appliance where virt-v2v is running.
585 -oo vdsm-compat=0.10
587 -oo vdsm-compat=1.1
588 If -o vdsm and the output format is qcow2, then we add the qcow2
589 compat=0.10 option to the output file for compatibility with RHEL 6
590 (see https://bugzilla.redhat.com/1145582).
591 If -oo vdsm-compat=1.1 is used then modern qcow2 (compat=1.1) files
593 are generated instead.
594 Currently -oo vdsm-compat=0.10 is the default, but this will change
596 to -oo vdsm-compat=1.1 in a future version of virt-v2v (when we can
597 assume that everyone is using a modern version of qemu).
598 Note this option only affects -o vdsm output. All other output
600 modes (including -o rhv) generate modern qcow2 compat=1.1 files,
601 always.
602 If this option is available, then "vdsm-compat-option" will appear
604 in the --machine-readable output.
605 -oo vdsm-image-uuid=UUID
607 -oo vdsm-vol-uuid=UUID
608 -oo vdsm-vm-uuid=UUID
609 -oo vdsm-ovf-output=DIR
610 Normally the RHV output mode chooses random UUIDs for the target
611 guest. However VDSM needs to control the UUIDs and passes these
612 parameters when virt-v2v runs under VDSM control. The parameters
613 control:
614 • the image directory of each guest disk (-oo vdsm-image-uuid)
616 (this option is passed once for each guest disk)
617 • UUIDs for each guest disk (-oo vdsm-vol-uuid) (this option is
619 passed once for each guest disk)
620 • the OVF file name (-oo vdsm-vm-uuid).
622 • the OVF output directory (default current directory) (-oo vdsm-
624 ovf-output).
625 The format of UUIDs is: "12345678-1234-1234-1234-123456789abc"
627 (each hex digit can be "0-9" or "a-f"), conforming to OSF DCE 1.1.
628 These options can only be used with -o vdsm.
630 -oo vdsm-ovf-flavour=flavour
632 This option controls the format of the OVF generated at the end of
633 conversion. Currently there are two possible flavours:
634 rhvexp
636 The OVF format used in RHV export storage domain.
637 ovirt
639 The OVF format understood by oVirt REST API.
640 For backward compatibility the default is rhvexp, but this may
642 change in the future.
643 -op file
645 Supply a file containing a password to be used when connecting to
646 the target hypervisor. Note the file should contain the whole
647 password, without any trailing newline, and for security the file
648 should have mode 0600 so that others cannot read it.
649 -os storage
651 The location of the storage for the converted guest.
652 For -o libvirt, this is a libvirt directory pool (see
654 "virsh pool-list") or pool UUID.
655 For -o local and -o qemu, this is a directory name. The directory
657 must exist.
658 For -o rhv-upload, this is the name of the destination Storage
660 Domain.
661 For -o openstack, this is the optional Cinder volume type.
663 For -o rhv, this can be an NFS path of the Export Storage Domain of
665 the form "<host>:<path>", eg:
666 rhv-storage.example.com:/rhv/export
668 The NFS export must be mountable and writable by the user and host
670 running virt-v2v, since the virt-v2v program has to actually mount
671 it when it runs. So you probably have to run virt-v2v as "root".
672 Or: You can mount the Export Storage Domain yourself, and point -os
674 to the mountpoint. Note that virt-v2v will still need to write to
675 this remote directory, so virt-v2v will still need to run as
676 "root".
677 You will get an error if virt-v2v is unable to mount/write to the
679 Export Storage Domain.
680 --print-source
682 Print information about the source guest and stop. This option is
683 useful when you are setting up network and bridge maps. See
684 "Networks and bridges".
685 --qemu-boot
687 This is the same as -oo qemu-boot.
688 -q
690 --quiet
691 This disables progress bars and other unnecessary output.
692 --root ask
694 --root single
695 --root first
696 --root /dev/sdX
697 --root /dev/VG/LV
698 Choose the root filesystem to be converted.
699 In the case where the virtual machine is dual-boot or multi-boot,
701 or where the VM has other filesystems that look like operating
702 systems, this option can be used to select the root filesystem
703 (a.k.a. "C:" drive or /) of the operating system that is to be
704 converted. The Windows Recovery Console, certain attached DVD
705 drives, and bugs in libguestfs inspection heuristics, can make a
706 guest look like a multi-boot operating system.
707 The default in virt-v2v ≤ 0.7.1 was --root single, which causes
709 virt-v2v to die if a multi-boot operating system is found.
710 Since virt-v2v ≥ 0.7.2 the default is now --root ask: If the VM is
712 found to be multi-boot, then virt-v2v will stop and list the
713 possible root filesystems and ask the user which to use. This
714 requires that virt-v2v is run interactively.
715 --root first means to choose the first root device in the case of a
717 multi-boot operating system. Since this is a heuristic, it may
718 sometimes choose the wrong one.
719 You can also name a specific root device, eg. --root /dev/sda2
721 would mean to use the second partition on the first hard drive. If
722 the named root device does not exist or was not detected as a root
723 device, then virt-v2v will fail.
724 Note that there is a bug in grub which prevents it from
726 successfully booting a multiboot system if virtio is enabled. Grub
727 is only able to boot an operating system from the first virtio
728 disk. Specifically, /boot must be on the first virtio disk, and it
729 cannot chainload an OS which is not in the first virtio disk.
730 -v
732 --verbose
733 Enable verbose messages for debugging.
734 -V
736 --version
737 Display version number and exit.
738 --wrap
740 Wrap error, warning, and informative messages. This is the default
741 when the output is a tty. If the output of the program is
742 redirected to a file, wrapping is disabled unless you use this
743 option.
744 -x Enable tracing of libguestfs API calls.
746
748 Xen paravirtualized guests
749 Older versions of virt-v2v could turn a Xen paravirtualized (PV) guest
750 into a KVM guest by installing a new kernel. This version of virt-v2v
751 does not attempt to install any new kernels. Instead it will give you
752 an error if there are only Xen PV kernels available.
753 Therefore before conversion you should check that a regular kernel is
755 installed. For some older Linux distributions, this means installing a
756 kernel from the table below:
757 RHEL 3 (Does not apply, as there was no Xen PV kernel)
759 RHEL 4 i686 with > 10GB of RAM: install 'kernel-hugemem'
761 i686 SMP: install 'kernel-smp'
762 other i686: install 'kernel'
763 x86-64 SMP with > 8 CPUs: install 'kernel-largesmp'
764 x86-64 SMP: install 'kernel-smp'
765 other x86-64: install 'kernel'
766 RHEL 5 i686: install 'kernel-PAE'
768 x86-64: install 'kernel'
769 SLES 10 i586 with > 10GB of RAM: install 'kernel-bigsmp'
771 i586 SMP: install 'kernel-smp'
772 other i586: install 'kernel-default'
773 x86-64 SMP: install 'kernel-smp'
774 other x86-64: install 'kernel-default'
775 SLES 11+ i586: install 'kernel-pae'
777 x86-64: install 'kernel-default'
778 Windows (Does not apply, as there is no Xen PV Windows kernel)
780 Enabling virtio
782 "Virtio" is the name for a set of drivers which make disk (block
783 device), network and other guest operations work much faster on KVM.
784 Older versions of virt-v2v could install these drivers for certain
786 Linux guests. This version of virt-v2v does not attempt to install new
787 Linux kernels or drivers, but will warn you if they are not installed
788 already.
789 In order to enable virtio, and hence improve performance of the guest
791 after conversion, you should ensure that the minimum versions of
792 packages are installed before conversion, by consulting the table
793 below.
794 RHEL 3 No virtio drivers are available
796 RHEL 4 kernel >= 2.5.9-89.EL
798 lvm2 >= 2.02.42-5.el4
799 device-mapper >= 1.02.28-2.el4
800 selinux-policy-targeted >= 1.17.30-2.152.el4
801 policycoreutils >= 1.18.1-4.13
802 RHEL 5 kernel >= 2.6.18-128.el5
804 lvm2 >= 2.02.40-6.el5
805 selinux-policy-targeted >= 2.4.6-203.el5
806 RHEL 6+ All versions support virtio
808 Fedora All versions support virtio
810 SLES 11+ All versions support virtio
812 SLES 10 kernel >= 2.6.16.60-0.85.1
814 OpenSUSE 11+ All versions support virtio
816 OpenSUSE 10 kernel >= 2.6.25.5-1.1
818 Debian 6+ All versions support virtio
820 Ubuntu 10.04+ All versions support virtio
822 Windows Drivers are installed from the ISO or directory pointed
824 to by the "VIRTIO_WIN" environment variable if present.
825 If the "VIRTIO_WIN" environment variable is absent
826 (which is the recommended setting), then libosinfo is
827 consulted first, for driver files that are locally
828 available on the conversion host.
829 RHEL 4: SELinux relabel appears to hang forever
831 In RHEL ≤ 4.7 there was a bug which causes SELinux relabelling to
832 appear to hang forever at:
833 *** Warning -- SELinux relabel is required. ***
835 *** Disabling security enforcement. ***
836 *** Relabeling could take a very long time, ***
837 *** depending on file system size. ***
838 In reality it is waiting for you to press a key (but there is no visual
840 indication of this). You can either hit the "[Return]" key, at which
841 point the guest will finish relabelling and reboot, or you can install
842 policycoreutils ≥ 1.18.1-4.13 before starting the v2v conversion. See
843 also https://bugzilla.redhat.com/show_bug.cgi?id=244636
844 Debian and Ubuntu
846 "warning: could not determine a way to update the configuration of
847 Grub2"
848 Currently, virt-v2v has no way to set the default kernel in Debian and
850 Ubuntu guests using GRUB 2 as bootloader. This means that virt-v2v
851 will not change the default kernel used for booting, even in case it is
852 not the best kernel available on the guest. A recommended procedure
853 is, before using virt-v2v, to check that the boot kernel is the best
854 kernel available in the guest (for example by making sure the guest is
855 up-to-date).
856 "vsyscall attempted with vsyscall=none"
858 When run on a recent Debian host virt-v2v may fail to convert guests
860 which were created before 2013. In the debugging output you will see a
861 crash message similar to:
862 vsyscall attempted with vsyscall=none ip:...
864 segfault at ...
865 This is caused because Debian removed support for running old binaries
867 which used the legacy vsyscall page to call into the kernel.
868 You can work around this problem by running this command before running
870 virt-v2v:
871 export LIBGUESTFS_APPEND="vsyscall=emulate"
873 For more information, see https://bugzilla.redhat.com/1592061
875 Windows
877 System disk on a Dynamic Disk is not supported
878 If the Windows system disk (the drive containing "\windows") is located
880 on a Dynamic Disk then it cannot be converted. Data disks — that is,
881 disks which are part of the guest but do not contain parts of the
882 Windows operating system — may be Dynamic Disks.
883 See https://bugzilla.redhat.com/2140548.
885 Windows ≥ 8 Fast Startup is incompatible with virt-v2v
887 Guests which use the Windows ≥ 8 "Fast Startup" feature (or guests
889 which are hibernated) cannot be converted with virt-v2v. You will see
890 an error:
891 virt-v2v: error: unable to mount the disk image for writing. This has
893 probably happened because Windows Hibernation or Fast Restart is being
894 used in this guest. You have to disable this (in the guest) in order
895 to use virt-v2v.
896 As the message says, you need to boot the guest and disable the "Fast
898 Startup" feature (Control Panel → Power Options → Choose what the power
899 buttons do → Change settings that are currently unavailable → Turn on
900 fast startup), and shut down the guest, and then you will be able to
901 convert it.
902 For more information, see: "WINDOWS HIBERNATION AND WINDOWS 8 FAST
904 STARTUP" in guestfs(3).
905 Boot failure: 0x0000007B
907 This boot failure is caused by Windows being unable to find or load the
909 right disk driver (eg. viostor.sys). If you experience this error,
910 here are some things to check:
911 • First ensure that the guest boots on the source hypervisor before
913 conversion.
914 • Check you have the Windows virtio drivers available in
916 /usr/share/virtio-win, and that virt-v2v did not print any warning
917 about not being able to install virtio drivers.
918 On Red Hat Enterprise Linux 7, you will need to install the signed
920 drivers available in the "virtio-win" package. If you do not have
921 access to the signed drivers, then you will probably need to
922 disable driver signing in the boot menus.
923 • Check that you are presenting a virtio-blk interface (not virtio-
925 scsi and not ide) to the guest. On the qemu/KVM command line you
926 should see something similar to this:
927 ... -drive file=windows-sda,if=virtio ...
929 In libvirt XML, you should see:
931 <target dev='vda' bus='virtio'/>
933 • Check that Windows Group Policy does not prevent the driver from
935 being installed or used. Try deleting Windows Group Policy before
936 conversion.
937 • Check there is no anti-virus or other software which implements
939 Group Policy-like prohibitions on installing or using new drivers.
940 • Enable boot debugging and check the viostor.sys driver is being
942 loaded.
943 OpenStack and Windows reactivation
945 OpenStack does not offer stable device / PCI addresses to guests.
947 Every time it creates or starts a guest, it regenerates the libvirt XML
948 for that guest from scratch. The libvirt XML will have no <address>
949 fields. Libvirt will then assign addresses to devices, in a
950 predictable manner. Addresses may change if any of the following are
951 true:
952 • A new disk or network device has been added or removed from the
954 guest.
955 • The version of OpenStack or (possibly) libvirt has changed.
957 Because Windows does not like "hardware" changes of this kind, it may
959 trigger Windows reactivation.
960 This can also prevent booting with a 7B error [see previous section] if
962 the guest has group policy containing "Device Installation
963 Restrictions".
964 Support for SHA-2 certificates in Windows 7 and Windows Server 2008 R2
966 Later versions of the Windows virtio drivers are signed using SHA-2
968 certificates (instead of SHA-1). The original shipping Windows 7 and
969 Windows Server 2008 R2 did not understand SHA-2 certificates and so the
970 Windows virtio drivers will not install properly.
971 To fix this you must apply SHA-2 Code Signing Support from:
973 https://docs.microsoft.com/en-us/security-updates/SecurityAdvisories/2015/3033929
974 before converting the guest.
975 For further information see:
977 https://bugzilla.redhat.com/show_bug.cgi?id=1624878
978 Networks and bridges
980 Guests are usually connected to one or more networks, and when
981 converted to the target hypervisor you usually want to reconnect those
982 networks at the destination. The options --network, --bridge and --mac
983 allow you to do that.
984 If you are unsure of what networks and bridges are in use on the source
986 hypervisor, then you can examine the source metadata (libvirt XML,
987 vCenter information, etc.). Or you can run virt-v2v with the
988 --print-source option which causes virt-v2v to print out the
989 information it has about the guest on the source and then exit.
990 In the --print-source output you will see a section showing the guest’s
992 Network Interface Cards (NICs):
993 $ virt-v2v [-i ...] --print-source name
995 [...]
996 NICs:
997 Network "default" mac: 52:54:00:d0:cf:0e
998 Bridges are special classes of network devices which are attached to a
1000 named external network on the source hypervisor, for example:
1001 $ virt-v2v [-i ...] --print-source name
1003 [...]
1004 NICs:
1005 Bridge "br0"
1006 To map a specific source bridge to a target network, for example "br0"
1008 on the source to "ovirtmgmt" on the target, use:
1009 virt-v2v [...] --bridge br0:ovirtmgmt
1011 To map every bridge to a target network, use:
1013 virt-v2v [...] --bridge ovirtmgmt
1015 Fine-grained mapping of guest NICs
1017 The --mac option gives you more control over the mapping, letting you
1019 map single NICs to either networks or bridges on the target. For
1020 example a source guest with two NICs could map them individually to two
1021 networks called "mgmt" and "clientdata" like this:
1022 $ virt-v2v [...] \
1024 --mac 52:54:00:d0:cf:0e:network:mgmt \
1025 --mac 52:54:00:d0:cf:0f:network:clientdata
1026 Note that virt-v2v does not have the ability to change a guest’s MAC
1028 address. The MAC address is part of the guest metadata and must remain
1029 the same on source and target hypervisors. Most guests will use the
1030 MAC address to set up persistent associations between NICs and internal
1031 names (like "eth0"), with firewall settings, or even for other purposes
1032 like software licensing.
1033 Resource requirements
1035 Network
1036 The most important resource for virt-v2v appears to be network
1038 bandwidth. Virt-v2v should be able to copy guest data at gigabit
1039 ethernet speeds or greater.
1040 Ensure that the network connections between servers (conversion server,
1042 NFS server, vCenter, Xen) are as fast and as low latency as possible.
1043 Disk space
1045 Virt-v2v places potentially large temporary files in $VIRT_V2V_TMPDIR
1047 (usually /var/tmp, see also "ENVIRONMENT VARIBLES" below). Using tmpfs
1048 is a bad idea.
1049 For each guest disk, an overlay is stored temporarily. This stores the
1051 changes made during conversion, and is used as a cache. The overlays
1052 are not particularly large - tens or low hundreds of megabytes per disk
1053 is typical. In addition to the overlay(s), input and output methods
1054 may use disk space, as outlined in the table below.
1055 -i ova
1057 This temporarily places a full copy of the uncompressed source
1058 disks in $VIRT_V2V_TMPDIR (or /var/tmp).
1059 -o glance
1061 This temporarily places a full copy of the output disks in
1062 $VIRT_V2V_TMPDIR (or /var/tmp).
1063 -o local
1065 -o qemu
1066 You must ensure there is sufficient space in the output directory
1067 for the converted guest.
1068 See also "Minimum free space check in the host" below.
1070 VMware vCenter resources
1072 Copying from VMware vCenter is currently quite slow, but we believe
1074 this to be an issue with VMware. Ensuring the VMware ESXi hypervisor
1075 and vCenter are running on fast hardware with plenty of memory should
1076 alleviate this.
1077 Compute power and RAM
1079 Virt-v2v is not especially compute or RAM intensive. If you are
1081 running many parallel conversions, then you may consider allocating one
1082 CPU core and 2 GB of RAM per running instance.
1083 Virt-v2v can be run in a virtual machine.
1085 Trimming
1087 Virt-v2v attempts to optimize the speed of conversion by ignoring guest
1089 filesystem data which is not used. This would include unused
1090 filesystem blocks, blocks containing zeroes, and deleted files.
1091 To do this, virt-v2v issues a non-destructive fstrim(8) operation. As
1093 this happens to an overlay placed over the guest data, it does not
1094 affect the source in any way.
1095 If this fstrim operation fails, you will see a warning, but virt-v2v
1097 will continue anyway. It may run more slowly (in some cases much more
1098 slowly), because it is copying the unused parts of the disk.
1099 Unfortunately support for fstrim is not universal, and it also depends
1101 on specific details of the filesystem, partition alignment, and backing
1102 storage. As an example, NTFS filesystems cannot be fstrimmed if they
1103 occupy a partition which is not aligned to the underlying storage.
1104 That was the default on Windows before Vista. As another example, VFAT
1105 filesystems (used by UEFI guests) cannot be trimmed at all.
1106 fstrim support in the Linux kernel is improving gradually, so over time
1108 some of these restrictions will be lifted and virt-v2v will work
1109 faster.
1110 Post-conversion tasks
1112 Guest network configuration
1113 Virt-v2v cannot currently reconfigure a guest’s network configuration.
1115 If the converted guest is not connected to the same subnet as the
1116 source, its network configuration may have to be updated. See also
1117 virt-customize(1).
1118 Converting a Windows guest
1120 When converting a Windows guests, the conversion process is split into
1122 two stages:
1123 1. Offline conversion.
1125 2. First boot.
1127 The guest will be bootable after the offline conversion stage, but will
1129 not yet have all necessary drivers installed to work correctly. These
1130 will be installed automatically the first time the guest boots.
1131 N.B. Take care not to interrupt the automatic driver installation
1133 process when logging in to the guest for the first time, as this may
1134 prevent the guest from subsequently booting correctly.
1135 Free space for conversion
1137 Free space in the guest
1138 Virt-v2v checks there is sufficient free space in the guest filesystem
1140 to perform the conversion. Currently it checks:
1141 Linux root filesystem
1143 Minimum free space: 100 MB
1144 Linux /boot
1146 Minimum free space: 50 MB
1147 This is because we need to build a new initramfs for some
1149 Enterprise Linux conversions.
1150 Windows "C:" drive
1152 Minimum free space: 100 MB
1153 We may have to copy in many virtio drivers and guest agents.
1155 Any other mountable filesystem
1157 Minimum free space: 10 MB
1158 In addition to the actual free space, each filesystem is required to
1160 have at least 100 available inodes.
1161 Minimum free space check in the host
1163 You must have sufficient free space in the host directory used to store
1165 large temporary overlays. To find out which directory this is, use:
1166 $ df -h "`guestfish get-cachedir`"
1168 Filesystem Size Used Avail Use% Mounted on
1169 /dev/mapper/root 50G 40G 6.8G 86% /
1170 and look under the "Avail" column. Virt-v2v will refuse to do the
1172 conversion at all unless at least 1GB is available there. You can
1173 change the directory that virt-v2v uses by setting $VIRT_V2V_TMPDIR.
1174 See also "Resource requirements" above and "ENVIRONMENT VARIABLES"
1176 below.
1177 Running virt-v2v as root or non-root
1179 Nothing in virt-v2v inherently needs root access, and it will run just
1180 fine as a non-root user. However, certain external features may
1181 require either root or a special user:
1182 Mounting the Export Storage Domain
1184 When using -o rhv -os server:/esd virt-v2v has to have sufficient
1185 privileges to NFS mount the Export Storage Domain from "server".
1186 You can avoid needing root here by mounting it yourself before
1188 running virt-v2v, and passing -os /mountpoint instead, but first of
1189 all read the next section ...
1190 Writing to the Export Storage Domain as 36:36
1192 RHV-M cannot read files and directories from the Export Storage
1193 Domain unless they have UID:GID 36:36. You will see VM import
1194 problems if the UID:GID is not correct.
1195 When you run virt-v2v -o rhv as root, virt-v2v attempts to create
1197 files and directories with the correct ownership. If you run
1198 virt-v2v as non-root, it will probably still work, but you will
1199 need to manually change ownership after virt-v2v has finished.
1200 Writing to libvirt
1202 When using -o libvirt, you may need to run virt-v2v as root so that
1203 it can write to the libvirt system instance (ie. "qemu:///system")
1204 and to the default location for disk images (usually
1205 /var/lib/libvirt/images).
1206 You can avoid this by setting up libvirt connection authentication,
1208 see http://libvirt.org/auth.html. Alternatively, use -oc
1209 qemu:///session, which will write to your per-user libvirt
1210 instance.
1211 See also "Starting the libvirt system instance".
1213 Writing to Openstack
1215 Because of how Cinder volumes are presented as /dev block devices,
1216 using -o openstack normally requires that virt-v2v is run as root.
1217 Writing to Glance
1219 This does not need root (in fact it probably won’t work), but may
1220 require either a special user and/or for you to source a script
1221 that sets authentication environment variables. Consult the Glance
1222 documentation.
1223 Writing to block devices
1225 This normally requires root. See the next section.
1226 Writing to block devices
1228 Some output modes write to local files. In general these modes also
1229 let you write to block devices, but before you run virt-v2v you may
1230 have to arrange for symbolic links to the desired block devices in the
1231 output directory.
1232 For example if using -o local -os /dir then virt-v2v would normally
1234 create files called:
1235 /dir/name-sda # first disk
1237 /dir/name-sdb # second disk
1238 ...
1239 /dir/name.xml # metadata
1240 If you wish the disks to be written to block devices then you would
1242 need to create /dir/name-sda (etc) as symlinks to the block devices:
1243 # lvcreate -L 10G -n VolumeForDiskA VG
1245 # lvcreate -L 6G -n VolumeForDiskB VG
1246 # ln -sf /dev/VG/VolumeForDiskA /dir/name-sda
1247 # ln -sf /dev/VG/VolumeForDiskB /dir/name-sdb
1248 Note that you must precreate the correct number of block devices of the
1250 correct size. Typically -of raw has to be used too, but other formats
1251 such as qcow2 can be useful occasionally so virt-v2v does not force you
1252 to use raw on block devices.
1253 Minimal XML for -i libvirtxml option
1255 When using the -i libvirtxml option, you have to supply some libvirt
1256 XML. Writing this from scratch is hard, so the template below is
1257 helpful.
1258 Note this should only be used for testing and/or where you know what
1260 you're doing! If you have libvirt metadata for the guest, always use
1261 that instead.
1262 <domain type='kvm'>
1264 <name> NAME </name>
1265 <memory>1048576</memory>
1266 <vcpu>2</vcpu>
1267 <os>
1268 <type>hvm</type>
1269 <boot dev='hd'/>
1270 </os>
1271 <features>
1272 <acpi/>
1273 <apic/>
1274 <pae/>
1275 </features>
1276 <devices>
1277 <disk type='file' device='disk'>
1278 <driver name='qemu' type='raw'/>
1279 <source file='/path/to/disk/image'/>
1280 <target dev='hda' bus='ide'/>
1281 </disk>
1282 <interface type='network'>
1283 <mac address='52:54:00:01:02:03'/>
1284 <source network='default'/>
1285 <model type='rtl8139'/>
1286 </interface>
1287 </devices>
1288 </domain>
1289 Machine readable output
1291 The --machine-readable option can be used to make the output more
1292 machine friendly, which is useful when calling virt-v2v from other
1293 programs, GUIs etc.
1294 There are two ways to use this option.
1296 Firstly use the option on its own to query the capabilities of the
1298 virt-v2v binary. Typical output looks like this:
1299 $ virt-v2v --machine-readable
1301 virt-v2v
1302 libguestfs-rewrite
1303 colours-option
1304 vdsm-compat-option
1305 input:disk
1306 [...]
1307 output:local
1308 [...]
1309 convert:linux
1310 convert:windows
1311 A list of features is printed, one per line, and the program exits with
1313 status 0.
1314 The "input:" and "output:" features refer to -i and -o (input and
1316 output mode) options supported by this binary. The "convert:" features
1317 refer to guest types that this binary knows how to convert.
1318 Secondly use the option in conjunction with other options to make the
1320 regular program output more machine friendly.
1321 At the moment this means:
1323 1. Progress bar messages can be parsed from stdout by looking for this
1325 regular expression:
1326 ^[0-9]+/[0-9]+$
1328 2. The calling program should treat messages sent to stdout (except
1330 for progress bar messages) as status messages. They can be logged
1331 and/or displayed to the user.
1332 3. The calling program should treat messages sent to stderr as error
1334 messages. In addition, virt-v2v exits with a non-zero status code
1335 if there was a fatal error.
1336 Virt-v2v ≤ 0.9.1 did not support the --machine-readable option at all.
1338 The option was added when virt-v2v was rewritten in 2014.
1339 It is possible to specify a format string for controlling the output;
1341 see "ADVANCED MACHINE READABLE OUTPUT" in guestfs(3).
1342 Starting the libvirt system instance
1344 Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory
1345 Failed to connect socket to '/var/run/libvirt/virtqemud-sock-ro': Connection refused
1346 If you have just installed libvirt and virt-v2v, then you may see the
1348 errors above. This is caused by libvirt daemons that provide various
1349 services not running straight after installation. (This may depend on
1350 your distribution and vendor presets).
1351 To fix this on systemd-based distributions, do:
1353 systemctl isolate multi-user.target
1355 See also https://bugzilla.redhat.com/2182024.
1357
1359 /usr/share/virtio-win
1360 (Optional)
1361 If this directory is present, then virtio drivers for Windows
1363 guests will be found from this directory and installed in the guest
1364 during conversion.
1365
1367 "VIRT_V2V_TMPDIR"
1368 "LIBGUESTFS_CACHEDIR"
1369 Location of the temporary directory used for the potentially large
1370 temporary overlay file. If neither environment variable is set
1371 then /var/tmp is used.
1372 To reliably ensure large temporary files are cleaned up (for
1374 example in case virt-v2v crashes) you should create a randomly
1375 named directory under /var/tmp, set "VIRT_V2V_TMPDIR" to point to
1376 this directory, then when virt-v2v exits remove the directory.
1377 See the "Disk space" section above.
1379 "VIRT_TOOLS_DATA_DIR"
1381 This can point to the directory containing data files used for
1382 Windows conversion.
1383 Normally you do not need to set this. If not set, a compiled-in
1385 default will be used (something like /usr/share/virt-tools).
1386 This directory may contain the following files:
1388 rhsrvany.exe
1390 (Required when doing conversions of Windows guests)
1391 This is the RHSrvAny Windows binary, used to install a
1393 "firstboot" script in the guest during conversion of Windows
1394 guests.
1395 See also: "https://github.com/rwmjones/rhsrvany"
1397 pnp_wait.exe
1399 (Recommended when doing conversions of Windows guests)
1400 This tool waits for newly installed Windows devices to become
1402 available before trying to configure them, for example to set
1403 network configuration. It is part of the RHSrvAny project.
1404 pvvxsvc.exe
1406 This is a Windows binary shipped with SUSE VMDP, used to
1407 install a "firstboot" script in Windows guests. It is an
1408 alternative to RHSrvAny.
1409 "VIRTIO_WIN"
1411 This is an override for where virtio drivers for Windows are
1412 searched for. It can be a directory or point to virtio-win.iso (CD
1413 ROM image containing drivers).
1414 If unset, then we look for drivers via whichever of these methods
1416 succeeds first:
1417 "osinfo-db"
1419 Load osinfo data from the default paths, and attempt to find
1420 drivers via libosinfo lookup. This is the preferred method.
1421 /usr/share/virtio-win/virtio-win.iso
1423 The ISO containing virtio drivers for Windows.
1424 /usr/share/virtio-win
1426 The exploded tree of virtio drivers for Windows. This is
1427 usually incomplete, hence the least preferred method.
1428 See "Enabling virtio".
1430 For other environment variables, see "ENVIRONMENT VARIABLES" in
1432 guestfs(3).
1433
1435 engine-image-uploader(8)
1436 Variously called "engine-image-uploader", "ovirt-image-uploader" or
1437 "rhevm-image-uploader", this tool allows you to copy a guest from
1438 one oVirt or RHV Export Storage Domain to another. It only permits
1439 importing a guest that was previously exported from another
1440 oVirt/RHV instance.
1441 import-to-ovirt.pl
1443 This script can be used to import guests that already run on KVM to
1444 oVirt or RHV. For more information, see this blog posting by the
1445 author of virt-v2v:
1446 https://rwmj.wordpress.com/2015/09/18/importing-kvm-guests-to-ovirt-or-rhev/#content
1448
1450 virt-p2v(1), virt-v2v-inspector(1), virt-v2v-in-place(1),
1451 virt-customize(1), virt-df(1), virt-filesystems(1), virt-sparsify(1),
1452 virt-sysprep(1), guestfs(3), guestfish(1), qemu-img(1),
1453 engine-image-uploader(8), import-to-ovirt.pl, nbdkit(1),
1454 nbdkit-vddk-plugin(1), http://libguestfs.org/.
1455
1457 Matthew Booth
1458 Cédric Bosdonnat
1460 Laszlo Ersek
1462 Tomáš Golembiovský
1464 Shahar Havivi
1466 Richard W.M. Jones
1468 Roman Kagan
1470 Mike Latimer
1472 Nir Soffer
1474 Pino Toscano
1476 Xiaodai Wang
1478 Ming Xie
1480 Tingting Zheng
1482
1484 Copyright (C) 2009-2022 Red Hat Inc.
1485
1487 This program is free software; you can redistribute it and/or modify it
1488 under the terms of the GNU General Public License as published by the
1489 Free Software Foundation; either version 2 of the License, or (at your
1490 option) any later version.
1491 This program is distributed in the hope that it will be useful, but
1493 WITHOUT ANY WARRANTY; without even the implied warranty of
1494 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
1495 General Public License for more details.
1496 You should have received a copy of the GNU General Public License along
1498 with this program; if not, write to the Free Software Foundation, Inc.,
1499 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
1500
1502 To get a list of bugs against libguestfs, use this link:
1503 https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools
1504 To report a new bug against libguestfs, use this link:
1506 https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Virtualization+Tools
1507 When reporting a bug, please supply:
1509 • The version of libguestfs.
1511 • Where you got libguestfs (eg. which Linux distro, compiled from
1513 source, etc)
1514 • Describe the bug accurately and give a way to reproduce it.
1516 • Run libguestfs-test-tool(1) and paste the complete, unedited output
1518 into the bug report.
1519virt-v2v-2.3.7 2023-12-09 virt-v2v(1)