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 virt-v2v --in-place
14 [-i mode] [other -i* options]
15 [guest|filename]
16
18 Virt-v2v converts a single guest from a foreign hypervisor to run on
19 KVM. It can read Linux and Windows guests running on VMware, Xen,
20 Hyper-V and some other hypervisors, and convert them to KVM managed by
21 libvirt, OpenStack, oVirt, Red Hat Virtualisation (RHV) or several
22 other targets. It can modify the guest to make it bootable on KVM and
23 install virtio drivers so it will run quickly.
24 There is also a companion front-end called virt-p2v(1) which comes as
26 an ISO, CD or PXE image that can be booted on physical machines to
27 virtualize those machines (physical to virtual, or p2v).
28 Input and Output
30 You normally run virt-v2v with several -i* options controlling the
31 input mode and also several -o* options controlling the output mode.
32 In this sense, "input" refers to the source foreign hypervisor such as
33 VMware, and "output" refers to the target KVM-based management system
34 such as oVirt or OpenStack.
35 The input and output sides of virt-v2v are separate and unrelated.
37 Virt-v2v can read from any input and write to any output. Therefore
38 these sides of virt-v2v are documented separately in this manual.
39 Virt-v2v normally copies from the input to the output, called "copying
41 mode". In this case the source guest is always left unchanged. In-
42 place conversion (--in-place) only uses the -i* options and modifies
43 the source guest in-place. (See "In-place conversion" below.)
44 Other virt-v2v topics
46 virt-v2v-support(1) — Supported hypervisors, virtualization management
47 systems, guests.
48 virt-v2v-input-vmware(1) — Input from VMware.
50 virt-v2v-input-xen(1) — Input from Xen.
52 virt-v2v-output-local(1) — Output to local files or local libvirt.
54 virt-v2v-output-rhv(1) — Output to oVirt or RHV.
56 virt-v2v-output-openstack(1) — Output to OpenStack.
58 virt-v2v-release-notes-1.42(1) — Release notes for this release.
60 virt-v2v-copy-to-local(1) — Deprecated tool to handle Xen guests using
62 host block device storage.
63
65 Convert from VMware vCenter server to local libvirt
66 You have a VMware vCenter server called "vcenter.example.com", a
67 datacenter called "Datacenter", and an ESXi hypervisor called "esxi".
68 You want to convert a guest called "vmware_guest" to run locally under
69 libvirt.
70 virt-v2v -ic vpx://vcenter.example.com/Datacenter/esxi vmware_guest
72 In this case you will most likely have to run virt-v2v as "root", since
74 it needs to talk to the system libvirt daemon and copy the guest disks
75 to /var/lib/libvirt/images.
76 For more information see virt-v2v-input-vmware(1).
78 Convert from VMware to RHV/oVirt
80 This is the same as the previous example, except you want to send the
81 guest to a RHV Data Domain using the RHV REST API. Guest network
82 interface(s) are connected to the target network called "ovirtmgmt".
83 virt-v2v -ic vpx://vcenter.example.com/Datacenter/esxi vmware_guest \
85 -o rhv-upload -oc https://ovirt-engine.example.com/ovirt-engine/api \
86 -os ovirt-data -op /tmp/ovirt-admin-password -of raw \
87 -oo rhv-cafile=/tmp/ca.pem -oo rhv-direct \
88 --bridge ovirtmgmt
89 In this case the host running virt-v2v acts as a conversion server.
91 For more information see virt-v2v-output-rhv(1).
93 Convert from ESXi hypervisor over SSH to local libvirt
95 You have an ESXi hypervisor called "esxi.example.com" with SSH access
96 enabled. You want to convert from VMFS storage on that server to a
97 local file.
98 virt-v2v \
100 -i vmx -it ssh \
101 "ssh://root@esxi.example.com/vmfs/volumes/datastore1/guest/guest.vmx" \
102 -o local -os /var/tmp
103 The guest must not be running. Virt-v2v would not need to be run as
105 root in this case.
106 For more information about converting from VMX files see
108 virt-v2v-input-vmware(1).
109 Convert disk image to OpenStack
111 Given a disk image from another hypervisor that you want to convert to
112 run on OpenStack (only KVM-based OpenStack is supported), you can run
113 virt-v2v inside an OpenStack VM (called "v2v-vm" below), and do:
114 virt-v2v -i disk disk.img -o openstack -oo server-id=v2v-vm
116 See virt-v2v-output-openstack(1).
118 Convert disk image to disk image
120 Given a disk image from another hypervisor that you want to convert to
121 run on KVM, you have two options. The simplest way is to try:
122 virt-v2v -i disk disk.img -o local -os /var/tmp
124 where virt-v2v guesses everything about the input disk.img and (in this
126 case) writes the converted result to /var/tmp.
127 A more complex method is to write some libvirt XML describing the input
129 guest (if you can get the source hypervisor to provide you with libvirt
130 XML, then so much the better). You can then do:
131 virt-v2v -i libvirtxml guest-domain.xml -o local -os /var/tmp
133 Since guest-domain.xml contains the path(s) to the guest disk image(s)
135 you do not need to specify the name of the disk image on the command
136 line.
137 To convert a local disk image and immediately boot it in local qemu,
139 do:
140 virt-v2v -i disk disk.img -o qemu -os /var/tmp --qemu-boot
142
144 --help
145 Display help.
146 --bandwidth bps
148 --bandwidth-file filename
149 Some input methods are able to limit the network bandwidth they
150 will use statically or dynamically. In the first variant this sets
151 the bandwidth limit statically in bits per second. Formats like
152 "10M" may be used (meaning 10 megabits per second).
153 In the second variant the bandwidth is limited dynamically from the
155 content of the file (also in bits per second, in the same formats
156 supported by the first variant). You may use both parameters
157 together, meaning: first limit to a static rate, then you can
158 create the file while virt-v2v is running to adjust the rate
159 dynamically.
160 This is only supported for:
162 • input from Xen
164 • input from VMware VMX when using the SSH transport method
166 • input from VDDK
168 • -i libvirtxml when using HTTP or HTTPS disks
170 • input from VMware vCenter server
172 The options are silently ignored for other input methods.
174 -b ...
176 --bridge ...
177 See --network below.
178 --colors
180 --colours
181 Use ANSI colour sequences to colourize messages. This is the
182 default when the output is a tty. If the output of the program is
183 redirected to a file, ANSI colour sequences are disabled unless you
184 use this option.
185 --compressed
187 Write a compressed output file. This is only allowed if the output
188 format is qcow2 (see -of below), and is equivalent to the -c option
189 of qemu-img(1).
190 --debug-overlays
192 Save the overlay file(s) created during conversion. This option is
193 only used for debugging virt-v2v and may be removed in a future
194 version.
195 --echo-keys
197 When prompting for keys and passphrases, virt-v2v normally turns
198 echoing off so you cannot see what you are typing. If you are not
199 worried about Tempest attacks and there is no one else in the room
200 you can specify this flag to see what you are typing.
201 Note this options only applies to keys and passphrases for
203 encrypted devices and partitions, not for passwords used to connect
204 to remote servers.
205 -i disk
207 Set the input method to disk.
208 In this mode you can read a virtual machine disk image with no
210 metadata. virt-v2v tries to guess the best default metadata. This
211 is usually adequate but you can get finer control (eg. of memory
212 and vCPUs) by using -i libvirtxml instead. Only guests that use a
213 single disk can be imported this way.
214 -i libvirt
216 Set the input method to libvirt. This is the default.
217 In this mode you have to specify a libvirt guest name or UUID on
219 the command line. You may also specify a libvirt connection URI
220 (see -ic).
221 -i libvirtxml
223 Set the input method to libvirtxml.
224 In this mode you have to pass a libvirt XML file on the command
226 line. This file is read in order to get metadata about the source
227 guest (such as its name, amount of memory), and also to locate the
228 input disks. See "Minimal XML for -i libvirtxml option" below.
229 -i local
231 This is the same as -i disk.
232 -i ova
234 Set the input method to ova.
235 In this mode you can read a VMware ova file. Virt-v2v will read
237 the ova manifest file and check the vmdk volumes for validity
238 (checksums) as well as analyzing the ovf file, and then convert the
239 guest. See virt-v2v-input-vmware(1).
240 -i vmx
242 Set the input method to vmx.
243 In this mode you can read a VMware vmx file directly or over SSH.
245 This is useful when VMware VMs are stored on an NFS server which
246 you can mount directly, or where you have access by SSH to an ESXi
247 hypervisor. See virt-v2v-input-vmware(1).
248 -ic libvirtURI
250 Specify a libvirt connection URI to use when reading the guest.
251 This is only used when -i libvirt.
252 Only local libvirt connections, VMware vCenter connections, or RHEL
254 5 Xen remote connections can be used. Other remote libvirt
255 connections will not work in general.
256 See also virt-v2v-input-vmware(1), virt-v2v-input-xen(1).
258 -if format
260 For -i disk only, this specifies the format of the input disk
261 image. For other input methods you should specify the input format
262 in the metadata.
263 --in-place
265 Do not create an output virtual machine in the target hypervisor.
266 Instead, adjust the guest OS in the source VM to run in the input
267 hypervisor.
268 This mode is meant for integration with other toolsets, which take
270 the responsibility of converting the VM configuration, providing
271 for rollback in case of errors, transforming the storage, etc.
272 See "In-place conversion" below.
274 Conflicts with all -o * options.
276 -io OPTION=VALUE
278 Set input option(s) related to the current input mode or transport.
279 To display short help on what options are available you can use:
280 virt-v2v -it vddk -io "?"
282 -io vddk-libdir=LIBDIR
284 Set the VDDK library directory. This directory should contain
285 subdirectories called include, lib64 etc., but do not include lib64
286 actually in the parameter.
287 In most cases this parameter is required when using the -it vddk
289 (VDDK) transport. See virt-v2v-input-vmware(1) for details.
290 -io vddk-thumbprint=xx:xx:xx:...
292 Set the thumbprint of the remote VMware server.
293 This parameter is required when using the -it vddk (VDDK)
295 transport. See virt-v2v-input-vmware(1) for details.
296 -io vddk-config=FILENAME
298 -io vddk-cookie=COOKIE
299 -io vddk-nfchostport=PORT
300 -io vddk-port=PORT
301 -io vddk-snapshot=SNAPSHOT-MOREF
302 -io vddk-transports=MODE:MODE:...
303 When using VDDK mode, these options are passed unmodified to the
304 nbdkit(1) VDDK plugin. Please refer to nbdkit-vddk-plugin(1). Do
305 not use these options unless you know what you are doing. These
306 are all optional.
307 -ip filename
309 Supply a file containing a password to be used when connecting to
310 the target hypervisor. If this is omitted then the input
311 hypervisor may ask for the password interactively. Note the file
312 should contain the whole password, without any trailing newline,
313 and for security the file should have mode 0600 so that others
314 cannot read it.
315 -it ssh
317 When using -i vmx, this enables the ssh transport. See
318 virt-v2v-input-vmware(1).
319 -it vddk
321 Use VMware VDDK as a transport to copy the input disks. See
322 virt-v2v-input-vmware(1). If you use this parameter then you may
323 need to use other -io vddk* options to specify how to connect
324 through VDDK.
325 --key SELECTOR
327 Specify a key for LUKS, to automatically open a LUKS device when
328 using the inspection. "ID" can be either the libguestfs device
329 name, or the UUID of the LUKS device.
330 --key "ID":key:KEY_STRING
332 Use the specified "KEY_STRING" as passphrase.
333 --key "ID":file:FILENAME
335 Read the passphrase from FILENAME.
336 --keys-from-stdin
338 Read key or passphrase parameters from stdin. The default is to
339 try to read passphrases from the user by opening /dev/tty.
340 If there are multiple encrypted devices then you may need to supply
342 multiple keys on stdin, one per line.
343 Note --keys-from-stdin only applies to keys and passphrases for
345 encrypted devices and partitions, not for passwords used to connect
346 to remote servers.
347 --mac aa:bb:cc:dd:ee:ff:network:out
349 --mac aa:bb:cc:dd:ee:ff:bridge:out
350 Map source NIC MAC address to a network or bridge.
351 See "Networks and bridges" below.
353 --mac aa:bb:cc:dd:ee:ff:ip:ipaddr[,gw[,len[,ns,ns,...]]]
355 Force a particular interface (controlled by its MAC address) to
356 have a static IP address after boot.
357 The fields in the parameter are: "ipaddr" is the IP address. "gw"
359 is the optional gateway IP address. "len" is the subnet mask
360 length (an integer). The final parameters are zero or more
361 nameserver IP addresses.
362 This option can be supplied zero or more times.
364 You only need to use this option for certain broken guests such as
366 Windows which are unable to preserve MAC to static IP address
367 mappings automatically. You don't need to use it if Windows is
368 using DHCP. It is currently ignored for Linux guests since they do
369 not have this problem.
370 --machine-readable
372 --machine-readable=format
373 This option is used to make the output more machine friendly when
374 being parsed by other programs. See "Machine readable output"
375 below.
376 -n in:out
378 -n out
379 --network in:out
380 --network out
381 -b in:out
382 -b out
383 --bridge in:out
384 --bridge out
385 Map network (or bridge) called "in" to network (or bridge) called
386 "out". If no "in:" prefix is given, all other networks (or
387 bridges) are mapped to "out".
388 See "Networks and bridges" below.
390 --no-copy
392 Don’t copy the disks. Instead, conversion is performed (and thrown
393 away), and metadata is written, but no disks are created. See also
394 discussion of -o null below.
395 This is useful in two cases: Either you want to test if conversion
397 is likely to succeed, without the long copying process. Or you are
398 only interested in looking at the metadata.
399 This option is not compatible with -o libvirt since it would create
401 a faulty guest (one with no disks).
402 This option is not compatible with -o glance for technical reasons.
404 -o disk
406 This is the same as -o local.
407 -o glance
409 This is a legacy option. You should probably use -o openstack
410 instead.
411 Set the output method to OpenStack Glance. In this mode the
413 converted guest is uploaded to Glance. See
414 virt-v2v-output-openstack(1).
415 -o json
417 Set the output method to json.
418 In this mode, the converted guest is written to a local directory
420 specified by -os /dir (the directory must exist), with a JSON file
421 containing the majority of the metadata that virt-v2v gathered
422 during the conversion.
423 See virt-v2v-output-local(1).
425 -o libvirt
427 Set the output method to libvirt. This is the default.
428 In this mode, the converted guest is created as a libvirt guest.
430 You may also specify a libvirt connection URI (see -oc).
431 See virt-v2v-output-local(1).
433 -o local
435 Set the output method to local.
436 In this mode, the converted guest is written to a local directory
438 specified by -os /dir (the directory must exist). The converted
439 guest’s disks are written as:
440 /dir/name-sda
442 /dir/name-sdb
443 [etc]
444 and a libvirt XML file is created containing guest metadata:
446 /dir/name.xml
448 where "name" is the guest name.
450 -o null
452 Set the output method to null.
453 The guest is converted and copied (unless you also specify
455 --no-copy), but the results are thrown away and no metadata is
456 written.
457 -o openstack
459 Set the output method to OpenStack. See
460 virt-v2v-output-openstack(1).
461 -o ovirt
463 This is the same as -o rhv.
464 -o ovirt-upload
466 This is the same as -o rhv-upload.
467 -o qemu
469 Set the output method to qemu.
470 This is similar to -o local, except that a shell script is written
472 which you can use to boot the guest in qemu. The converted disks
473 and shell script are written to the directory specified by -os.
474 When using this output mode, you can also specify the --qemu-boot
476 option which boots the guest under qemu immediately.
477 -o rhev
479 This is the same as -o rhv.
480 -o rhv
482 Set the output method to rhv.
483 The converted guest is written to a RHV Export Storage Domain. The
485 -os parameter must also be used to specify the location of the
486 Export Storage Domain. Note this does not actually import the
487 guest into RHV. You have to do that manually later using the UI.
488 See virt-v2v-output-rhv(1).
490 -o rhv-upload
492 Set the output method to rhv-upload.
493 The converted guest is written directly to a RHV Data Domain. This
495 is a faster method than -o rhv, but requires oVirt or RHV ≥ 4.2.
496 See virt-v2v-output-rhv(1).
498 -o vdsm
500 Set the output method to vdsm.
501 This mode is similar to -o rhv, but the full path to the data
503 domain must be given:
504 /rhv/data-center/<data-center-uuid>/<data-domain-uuid>. This mode
505 is only used when virt-v2v runs under VDSM control.
506 -oa sparse
508 -oa preallocated
509 Set the output file allocation mode. The default is "sparse".
510 -oc URI
512 Specify a connection URI to use when writing the converted guest.
513 For -o libvirt this is the libvirt URI. Only local libvirt
515 connections can be used. Remote libvirt connections will not work.
516 See virt-v2v-output-local(1) for further information.
517 -of format
519 When converting the guest, convert the disks to the given format.
520 If not specified, then the input format is used.
522 -on name
524 Rename the guest when converting it. If this option is not used
525 then the output name is the same as the input name.
526 -oo OPTION=VALUE
528 Set output option(s) related to the current output mode. To
529 display short help on what options are available you can use:
530 virt-v2v -o rhv-upload -oo "?"
532 -oo guest-id="ID"
534 For -o openstack (virt-v2v-output-openstack(1)) only, set a guest
535 ID which is saved on each Cinder volume in the "virt_v2v_guest_id"
536 volume property.
537 -oo verify-server-certificate
539 -oo verify-server-certificate="true|false"
540 For -o openstack (virt-v2v-output-openstack(1)) only, this can be
541 used to disable SSL certification validation when connecting to
542 OpenStack by specifying -oo verify-server-certificate=false.
543 -oo os-*=*
545 For -o openstack (virt-v2v-output-openstack(1)) only, set optional
546 OpenStack authentication. For example -oo os-username=NAME is
547 equivalent to "openstack --os-username=NAME".
548 -oo rhv-cafile=ca.pem
550 For -o rhv-upload (virt-v2v-output-rhv(1)) only, the ca.pem file
551 (Certificate Authority), copied from /etc/pki/ovirt-engine/ca.pem
552 on the oVirt engine.
553 -oo rhv-cluster="CLUSTERNAME"
555 For -o rhv-upload (virt-v2v-output-rhv(1)) only, set the RHV
556 Cluster Name. If not given it uses "Default".
557 -oo rhv-direct
559 For -o rhv-upload (virt-v2v-output-rhv(1)) only, if this option is
560 given then virt-v2v will attempt to directly upload the disk to the
561 oVirt node, otherwise it will proxy the upload through the oVirt
562 engine. Direct upload requires that you have network access to the
563 oVirt nodes. Non-direct upload is slightly slower but should work
564 in all situations.
565 -oo rhv-verifypeer
567 For -o rhv-upload (virt-v2v-output-rhv(1)) only, verify the
568 oVirt/RHV server’s identity by checking the server‘s certificate
569 against the Certificate Authority.
570 -oo server-id="NAME|UUID"
572 For -o openstack (virt-v2v-output-openstack(1)) only, set the name
573 of the conversion appliance where virt-v2v is running.
574 -oo vdsm-compat=0.10
576 -oo vdsm-compat=1.1
577 If -o vdsm and the output format is qcow2, then we add the qcow2
578 compat=0.10 option to the output file for compatibility with RHEL 6
579 (see https://bugzilla.redhat.com/1145582).
580 If -oo vdsm-compat=1.1 is used then modern qcow2 (compat=1.1) files
582 are generated instead.
583 Currently -oo vdsm-compat=0.10 is the default, but this will change
585 to -oo vdsm-compat=1.1 in a future version of virt-v2v (when we can
586 assume that everyone is using a modern version of qemu).
587 Note this option only affects -o vdsm output. All other output
589 modes (including -o rhv) generate modern qcow2 compat=1.1 files,
590 always.
591 If this option is available, then "vdsm-compat-option" will appear
593 in the --machine-readable output.
594 -oo vdsm-image-uuid=UUID
596 -oo vdsm-vol-uuid=UUID
597 -oo vdsm-vm-uuid=UUID
598 -oo vdsm-ovf-output=DIR
599 Normally the RHV output mode chooses random UUIDs for the target
600 guest. However VDSM needs to control the UUIDs and passes these
601 parameters when virt-v2v runs under VDSM control. The parameters
602 control:
603 • the image directory of each guest disk (-oo vdsm-image-uuid)
605 (this option is passed once for each guest disk)
606 • UUIDs for each guest disk (-oo vdsm-vol-uuid) (this option is
608 passed once for each guest disk)
609 • the OVF file name (-oo vdsm-vm-uuid).
611 • the OVF output directory (default current directory) (-oo vdsm-
613 ovf-output).
614 The format of UUIDs is: "12345678-1234-1234-1234-123456789abc"
616 (each hex digit can be "0-9" or "a-f"), conforming to OSF DCE 1.1.
617 These options can only be used with -o vdsm.
619 -oo vdsm-ovf-flavour=flavour
621 This option controls the format of the OVF generated at the end of
622 conversion. Currently there are two possible flavours:
623 rhvexp
625 The OVF format used in RHV export storage domain.
626 ovirt
628 The OVF format understood by oVirt REST API.
629 For backward compatibility the default is rhvexp, but this may
631 change in the future.
632 -op file
634 Supply a file containing a password to be used when connecting to
635 the target hypervisor. Note the file should contain the whole
636 password, without any trailing newline, and for security the file
637 should have mode 0600 so that others cannot read it.
638 -os storage
640 The location of the storage for the converted guest.
641 For -o libvirt, this is a libvirt directory pool (see
643 "virsh pool-list") or pool UUID.
644 For -o json, -o local and -o qemu, this is a directory name. The
646 directory must exist.
647 For -o rhv-upload, this is the name of the destination Storage
649 Domain.
650 For -o openstack, this is the optional Cinder volume type.
652 For -o rhv, this can be an NFS path of the Export Storage Domain of
654 the form "<host>:<path>", eg:
655 rhv-storage.example.com:/rhv/export
657 The NFS export must be mountable and writable by the user and host
659 running virt-v2v, since the virt-v2v program has to actually mount
660 it when it runs. So you probably have to run virt-v2v as "root".
661 Or: You can mount the Export Storage Domain yourself, and point -os
663 to the mountpoint. Note that virt-v2v will still need to write to
664 this remote directory, so virt-v2v will still need to run as
665 "root".
666 You will get an error if virt-v2v is unable to mount/write to the
668 Export Storage Domain.
669 --print-estimate
671 Print the estimated size of the data which will be copied from the
672 source disk(s) and stop. One number (the size in bytes) is printed
673 per disk, and a total:
674 $ virt-v2v --print-estimate
676 ...
677 disk 1: 100000
678 disk 2: 200000
679 total: 300000
680 With the --machine-readable option you get JSON output which can be
682 directed into a file or elsewhere:
683 $ virt-v2v --print-estimate --machine-readable=file:estimates
685 ...
686 $ cat estimates
687 {
688 "disks": [ 100000, 200000 ],
689 "total": 300000
690 }
691 When using this option you must specify an output mode. This is
693 because virt-v2v has to perform the conversion in order to print
694 the estimate, and the conversion depends on the output mode. Using
695 -o null should be safe for most purposes.
696 When this option is used along with --machine-readable you can
698 direct the output to an alternate file.
699 --print-source
701 Print information about the source guest and stop. This option is
702 useful when you are setting up network and bridge maps. See
703 "Networks and bridges".
704 --qemu-boot
706 When using -o qemu only, this boots the guest immediately after
707 virt-v2v finishes.
708 -q
710 --quiet
711 This disables progress bars and other unnecessary output.
712 --root ask
714 --root single
715 --root first
716 --root /dev/sdX
717 --root /dev/VG/LV
718 Choose the root filesystem to be converted.
719 In the case where the virtual machine is dual-boot or multi-boot,
721 or where the VM has other filesystems that look like operating
722 systems, this option can be used to select the root filesystem
723 (a.k.a. "C:" drive or /) of the operating system that is to be
724 converted. The Windows Recovery Console, certain attached DVD
725 drives, and bugs in libguestfs inspection heuristics, can make a
726 guest look like a multi-boot operating system.
727 The default in virt-v2v ≤ 0.7.1 was --root single, which causes
729 virt-v2v to die if a multi-boot operating system is found.
730 Since virt-v2v ≥ 0.7.2 the default is now --root ask: If the VM is
732 found to be multi-boot, then virt-v2v will stop and list the
733 possible root filesystems and ask the user which to use. This
734 requires that virt-v2v is run interactively.
735 --root first means to choose the first root device in the case of a
737 multi-boot operating system. Since this is a heuristic, it may
738 sometimes choose the wrong one.
739 You can also name a specific root device, eg. --root /dev/sda2
741 would mean to use the second partition on the first hard drive. If
742 the named root device does not exist or was not detected as a root
743 device, then virt-v2v will fail.
744 Note that there is a bug in grub which prevents it from
746 successfully booting a multiboot system if virtio is enabled. Grub
747 is only able to boot an operating system from the first virtio
748 disk. Specifically, /boot must be on the first virtio disk, and it
749 cannot chainload an OS which is not in the first virtio disk.
750 -v
752 --verbose
753 Enable verbose messages for debugging.
754 -V
756 --version
757 Display version number and exit.
758 -x Enable tracing of libguestfs API calls.
760
762 Xen paravirtualized guests
763 Older versions of virt-v2v could turn a Xen paravirtualized (PV) guest
764 into a KVM guest by installing a new kernel. This version of virt-v2v
765 does not attempt to install any new kernels. Instead it will give you
766 an error if there are only Xen PV kernels available.
767 Therefore before conversion you should check that a regular kernel is
769 installed. For some older Linux distributions, this means installing a
770 kernel from the table below:
771 RHEL 3 (Does not apply, as there was no Xen PV kernel)
773 RHEL 4 i686 with > 10GB of RAM: install 'kernel-hugemem'
775 i686 SMP: install 'kernel-smp'
776 other i686: install 'kernel'
777 x86-64 SMP with > 8 CPUs: install 'kernel-largesmp'
778 x86-64 SMP: install 'kernel-smp'
779 other x86-64: install 'kernel'
780 RHEL 5 i686: install 'kernel-PAE'
782 x86-64: install 'kernel'
783 SLES 10 i586 with > 10GB of RAM: install 'kernel-bigsmp'
785 i586 SMP: install 'kernel-smp'
786 other i586: install 'kernel-default'
787 x86-64 SMP: install 'kernel-smp'
788 other x86-64: install 'kernel-default'
789 SLES 11+ i586: install 'kernel-pae'
791 x86-64: install 'kernel-default'
792 Windows (Does not apply, as there is no Xen PV Windows kernel)
794 Enabling virtio
796 "Virtio" is the name for a set of drivers which make disk (block
797 device), network and other guest operations work much faster on KVM.
798 Older versions of virt-v2v could install these drivers for certain
800 Linux guests. This version of virt-v2v does not attempt to install new
801 Linux kernels or drivers, but will warn you if they are not installed
802 already.
803 In order to enable virtio, and hence improve performance of the guest
805 after conversion, you should ensure that the minimum versions of
806 packages are installed before conversion, by consulting the table
807 below.
808 RHEL 3 No virtio drivers are available
810 RHEL 4 kernel >= 2.5.9-89.EL
812 lvm2 >= 2.02.42-5.el4
813 device-mapper >= 1.02.28-2.el4
814 selinux-policy-targeted >= 1.17.30-2.152.el4
815 policycoreutils >= 1.18.1-4.13
816 RHEL 5 kernel >= 2.6.18-128.el5
818 lvm2 >= 2.02.40-6.el5
819 selinux-policy-targeted >= 2.4.6-203.el5
820 RHEL 6+ All versions support virtio
822 Fedora All versions support virtio
824 SLES 11+ All versions support virtio
826 SLES 10 kernel >= 2.6.16.60-0.85.1
828 OpenSUSE 11+ All versions support virtio
830 OpenSUSE 10 kernel >= 2.6.25.5-1.1
832 Debian 6+ All versions support virtio
834 Ubuntu 10.04+ All versions support virtio
836 Windows Drivers are installed from the ISO or directory pointed
838 to by "VIRTIO_WIN" environment variable if present
839 RHEL 4: SELinux relabel appears to hang forever
841 In RHEL ≤ 4.7 there was a bug which causes SELinux relabelling to
842 appear to hang forever at:
843 *** Warning -- SELinux relabel is required. ***
845 *** Disabling security enforcement. ***
846 *** Relabeling could take a very long time, ***
847 *** depending on file system size. ***
848 In reality it is waiting for you to press a key (but there is no visual
850 indication of this). You can either hit the "[Return]" key, at which
851 point the guest will finish relabelling and reboot, or you can install
852 policycoreutils ≥ 1.18.1-4.13 before starting the v2v conversion. See
853 also https://bugzilla.redhat.com/show_bug.cgi?id=244636
854 Debian and Ubuntu
856 "warning: could not determine a way to update the configuration of
857 Grub2"
858 Currently, virt-v2v has no way to set the default kernel in Debian and
860 Ubuntu guests using GRUB 2 as bootloader. This means that virt-v2v
861 will not change the default kernel used for booting, even in case it is
862 not the best kernel available on the guest. A recommended procedure
863 is, before using virt-v2v, to check that the boot kernel is the best
864 kernel available in the guest (for example by making sure the guest is
865 up-to-date).
866 "vsyscall attempted with vsyscall=none"
868 When run on a recent Debian host virt-v2v may fail to convert guests
870 which were created before 2013. In the debugging output you will see a
871 crash message similar to:
872 vsyscall attempted with vsyscall=none ip:...
874 segfault at ...
875 This is caused because Debian removed support for running old binaries
877 which used the legacy vsyscall page to call into the kernel.
878 You can work around this problem by running this command before running
880 virt-v2v:
881 export LIBGUESTFS_APPEND="vsyscall=emulate"
883 For more information, see https://bugzilla.redhat.com/1592061
885 Windows
887 Windows ≥ 8 Fast Startup is incompatible with virt-v2v
888 Guests which use the Windows ≥ 8 "Fast Startup" feature (or guests
890 which are hibernated) cannot be converted with virt-v2v. You will see
891 an error:
892 virt-v2v: error: unable to mount the disk image for writing. This has
894 probably happened because Windows Hibernation or Fast Restart is being
895 used in this guest. You have to disable this (in the guest) in order
896 to use virt-v2v.
897 As the message says, you need to boot the guest and disable the "Fast
899 Startup" feature (Control Panel → Power Options → Choose what the power
900 buttons do → Change settings that are currently unavailable → Turn on
901 fast startup), and shut down the guest, and then you will be able to
902 convert it.
903 For more information, see: "WINDOWS HIBERNATION AND WINDOWS 8 FAST
905 STARTUP" in guestfs(3).
906 Boot failure: 0x0000007B
908 This boot failure is caused by Windows being unable to find or load the
910 right disk driver (eg. viostor.sys). If you experience this error,
911 here are some things to check:
912 • First ensure that the guest boots on the source hypervisor before
914 conversion.
915 • Check you have the Windows virtio drivers available in
917 /usr/share/virtio-win, and that virt-v2v did not print any warning
918 about not being able to install virtio drivers.
919 On Red Hat Enterprise Linux 7, you will need to install the signed
921 drivers available in the "virtio-win" package. If you do not have
922 access to the signed drivers, then you will probably need to
923 disable driver signing in the boot menus.
924 • Check that you are presenting a virtio-blk interface (not virtio-
926 scsi and not ide) to the guest. On the qemu/KVM command line you
927 should see something similar to this:
928 ... -drive file=windows-sda,if=virtio ...
930 In libvirt XML, you should see:
932 <target dev='vda' bus='virtio'/>
934 • Check that Windows Group Policy does not prevent the driver from
936 being installed or used. Try deleting Windows Group Policy before
937 conversion.
938 • Check there is no anti-virus or other software which implements
940 Group Policy-like prohibitions on installing or using new drivers.
941 • Enable boot debugging and check the viostor.sys driver is being
943 loaded.
944 OpenStack and Windows reactivation
946 OpenStack does not offer stable device / PCI addresses to guests.
948 Every time it creates or starts a guest, it regenerates the libvirt XML
949 for that guest from scratch. The libvirt XML will have no <address>
950 fields. Libvirt will then assign addresses to devices, in a
951 predictable manner. Addresses may change if any of the following are
952 true:
953 • A new disk or network device has been added or removed from the
955 guest.
956 • The version of OpenStack or (possibly) libvirt has changed.
958 Because Windows does not like "hardware" changes of this kind, it may
960 trigger Windows reactivation.
961 This can also prevent booting with a 7B error [see previous section] if
963 the guest has group policy containing "Device Installation
964 Restrictions".
965 Support for SHA-2 certificates in Windows 7 and Windows Server 2008 R2
967 Later versions of the Windows virtio drivers are signed using SHA-2
969 certificates (instead of SHA-1). The original shipping Windows 7 and
970 Windows Server 2008 R2 did not understand SHA-2 certificates and so the
971 Windows virtio drivers will not install properly.
972 To fix this you must apply SHA-2 Code Signing Support from:
974 https://docs.microsoft.com/en-us/security-updates/SecurityAdvisories/2015/3033929
975 before converting the guest.
976 For further information see:
978 https://bugzilla.redhat.com/show_bug.cgi?id=1624878
979 Networks and bridges
981 Guests are usually connected to one or more networks, and when
982 converted to the target hypervisor you usually want to reconnect those
983 networks at the destination. The options --network, --bridge and --mac
984 allow you to do that.
985 If you are unsure of what networks and bridges are in use on the source
987 hypervisor, then you can examine the source metadata (libvirt XML,
988 vCenter information, etc.). Or you can run virt-v2v with the
989 --print-source option which causes virt-v2v to print out the
990 information it has about the guest on the source and then exit.
991 In the --print-source output you will see a section showing the guest’s
993 Network Interface Cards (NICs):
994 $ virt-v2v [-i ...] --print-source name
996 [...]
997 NICs:
998 Network "default" mac: 52:54:00:d0:cf:0e
999 Bridges are special classes of network devices which are attached to a
1001 named external network on the source hypervisor, for example:
1002 $ virt-v2v [-i ...] --print-source name
1004 [...]
1005 NICs:
1006 Bridge "br0"
1007 To map a specific source bridge to a target network, for example "br0"
1009 on the source to "ovirtmgmt" on the target, use:
1010 virt-v2v [...] --bridge br0:ovirtmgmt
1012 To map every bridge to a target network, use:
1014 virt-v2v [...] --bridge ovirtmgmt
1016 Fine-grained mapping of guest NICs
1018 The --mac option gives you more control over the mapping, letting you
1020 map single NICs to either networks or bridges on the target. For
1021 example a source guest with two NICs could map them individually to two
1022 networks called "mgmt" and "clientdata" like this:
1023 $ virt-v2v [...] \
1025 --mac 52:54:00:d0:cf:0e:network:mgmt \
1026 --mac 52:54:00:d0:cf:0f:network:clientdata
1027 Note that virt-v2v does not have the ability to change a guest’s MAC
1029 address. The MAC address is part of the guest metadata and must remain
1030 the same on source and target hypervisors. Most guests will use the
1031 MAC address to set up persistent associations between NICs and internal
1032 names (like "eth0"), with firewall settings, or even for other purposes
1033 like software licensing.
1034 Resource requirements
1036 Network
1037 The most important resource for virt-v2v appears to be network
1039 bandwidth. Virt-v2v should be able to copy guest data at gigabit
1040 ethernet speeds or greater.
1041 Ensure that the network connections between servers (conversion server,
1043 NFS server, vCenter, Xen) are as fast and as low latency as possible.
1044 Disk space
1046 Virt-v2v places potentially large temporary files in $VIRT_V2V_TMPDIR
1048 (usually /var/tmp, see also "ENVIRONMENT VARIBLES" below). Using tmpfs
1049 is a bad idea.
1050 For each guest disk, an overlay is stored temporarily. This stores the
1052 changes made during conversion, and is used as a cache. The overlays
1053 are not particularly large - tens or low hundreds of megabytes per disk
1054 is typical. In addition to the overlay(s), input and output methods
1055 may use disk space, as outlined in the table below.
1056 -i ova
1058 This temporarily places a full copy of the uncompressed source
1059 disks in $VIRT_V2V_TMPDIR (or /var/tmp).
1060 -o glance
1062 This temporarily places a full copy of the output disks in
1063 $VIRT_V2V_TMPDIR (or /var/tmp).
1064 -o local
1066 -o qemu
1067 You must ensure there is sufficient space in the output directory
1068 for the converted guest.
1069 See also "Minimum free space check in the host" below.
1071 VMware vCenter resources
1073 Copying from VMware vCenter is currently quite slow, but we believe
1075 this to be an issue with VMware. Ensuring the VMware ESXi hypervisor
1076 and vCenter are running on fast hardware with plenty of memory should
1077 alleviate this.
1078 Compute power and RAM
1080 Virt-v2v is not especially compute or RAM intensive. If you are
1082 running many parallel conversions, then you may consider allocating one
1083 CPU core and 2 GB of RAM per running instance.
1084 Virt-v2v can be run in a virtual machine.
1086 Trimming
1088 Virt-v2v attempts to optimize the speed of conversion by ignoring guest
1090 filesystem data which is not used. This would include unused
1091 filesystem blocks, blocks containing zeroes, and deleted files.
1092 To do this, virt-v2v issues a non-destructive fstrim(8) operation. As
1094 this happens to an overlay placed over the guest data, it does not
1095 affect the source in any way.
1096 If this fstrim operation fails, you will see a warning, but virt-v2v
1098 will continue anyway. It may run more slowly (in some cases much more
1099 slowly), because it is copying the unused parts of the disk.
1100 Unfortunately support for fstrim is not universal, and it also depends
1102 on specific details of the filesystem, partition alignment, and backing
1103 storage. As an example, NTFS filesystems cannot be fstrimmed if they
1104 occupy a partition which is not aligned to the underlying storage.
1105 That was the default on Windows before Vista. As another example, VFAT
1106 filesystems (used by UEFI guests) cannot be trimmed at all.
1107 fstrim support in the Linux kernel is improving gradually, so over time
1109 some of these restrictions will be lifted and virt-v2v will work
1110 faster.
1111 Post-conversion tasks
1113 Guest network configuration
1114 Virt-v2v cannot currently reconfigure a guest’s network configuration.
1116 If the converted guest is not connected to the same subnet as the
1117 source, its network configuration may have to be updated. See also
1118 virt-customize(1).
1119 Converting a Windows guest
1121 When converting a Windows guests, the conversion process is split into
1123 two stages:
1124 1. Offline conversion.
1126 2. First boot.
1128 The guest will be bootable after the offline conversion stage, but will
1130 not yet have all necessary drivers installed to work correctly. These
1131 will be installed automatically the first time the guest boots.
1132 N.B. Take care not to interrupt the automatic driver installation
1134 process when logging in to the guest for the first time, as this may
1135 prevent the guest from subsequently booting correctly.
1136 Free space for conversion
1138 Free space in the guest
1139 Virt-v2v checks there is sufficient free space in the guest filesystem
1141 to perform the conversion. Currently it checks:
1142 Linux root filesystem
1144 Minimum free space: 20 MB
1145 Linux /boot
1147 Minimum free space: 50 MB
1148 This is because we need to build a new initramfs for some
1150 Enterprise Linux conversions.
1151 Windows "C:" drive
1153 Minimum free space: 100 MB
1154 We may have to copy in many virtio drivers and guest agents.
1156 Any other mountable filesystem
1158 Minimum free space: 10 MB
1159 In addition to the actual free space, each filesystem is required to
1161 have at least 100 available inodes.
1162 Minimum free space check in the host
1164 You must have sufficient free space in the host directory used to store
1166 large temporary overlays (except in --in-place mode). To find out
1167 which directory this is, use:
1168 $ df -h "`guestfish get-cachedir`"
1170 Filesystem Size Used Avail Use% Mounted on
1171 /dev/mapper/root 50G 40G 6.8G 86% /
1172 and look under the "Avail" column. Virt-v2v will refuse to do the
1174 conversion at all unless at least 1GB is available there. You can
1175 change the directory that virt-v2v uses by setting $VIRT_V2V_TMPDIR.
1176 See also "Resource requirements" above and "ENVIRONMENT VARIABLES"
1178 below.
1179 Running virt-v2v as root or non-root
1181 Nothing in virt-v2v inherently needs root access, and it will run just
1182 fine as a non-root user. However, certain external features may
1183 require either root or a special user:
1184 Mounting the Export Storage Domain
1186 When using -o rhv -os server:/esd virt-v2v has to have sufficient
1187 privileges to NFS mount the Export Storage Domain from "server".
1188 You can avoid needing root here by mounting it yourself before
1190 running virt-v2v, and passing -os /mountpoint instead, but first of
1191 all read the next section ...
1192 Writing to the Export Storage Domain as 36:36
1194 RHV-M cannot read files and directories from the Export Storage
1195 Domain unless they have UID:GID 36:36. You will see VM import
1196 problems if the UID:GID is not correct.
1197 When you run virt-v2v -o rhv as root, virt-v2v attempts to create
1199 files and directories with the correct ownership. If you run
1200 virt-v2v as non-root, it will probably still work, but you will
1201 need to manually change ownership after virt-v2v has finished.
1202 Writing to libvirt
1204 When using -o libvirt, you may need to run virt-v2v as root so that
1205 it can write to the libvirt system instance (ie. "qemu:///system")
1206 and to the default location for disk images (usually
1207 /var/lib/libvirt/images).
1208 You can avoid this by setting up libvirt connection authentication,
1210 see http://libvirt.org/auth.html. Alternatively, use -oc
1211 qemu:///session, which will write to your per-user libvirt
1212 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 In-place conversion
1291 It is also possible to use virt-v2v in scenarios where a foreign VM has
1292 already been imported into a KVM-based hypervisor, but still needs
1293 adjustments in the guest to make it run in the new virtual hardware.
1294 In that case it is assumed that a third-party tool has created the
1296 target VM in the supported KVM-based hypervisor based on the source VM
1297 configuration and contents, but using virtual devices more appropriate
1298 for KVM (e.g. virtio storage and network, etc.).
1299 Then, to make the guest OS boot and run in the changed environment, one
1301 can use:
1302 virt-v2v -ic qemu:///system converted_vm --in-place
1304 Virt-v2v will analyze the configuration of "converted_vm" in the
1306 "qemu:///system" libvirt instance, and apply various fixups to the
1307 guest OS configuration to make it match the VM configuration. This may
1308 include installing virtio drivers, configuring the bootloader, the
1309 mountpoints, the network interfaces, and so on.
1310 Should an error occur during the operation, virt-v2v exits with an
1312 error code leaving the VM in an undefined state.
1313 Machine readable output
1315 The --machine-readable option can be used to make the output more
1316 machine friendly, which is useful when calling virt-v2v from other
1317 programs, GUIs etc.
1318 There are two ways to use this option.
1320 Firstly use the option on its own to query the capabilities of the
1322 virt-v2v binary. Typical output looks like this:
1323 $ virt-v2v --machine-readable
1325 virt-v2v
1326 libguestfs-rewrite
1327 colours-option
1328 vdsm-compat-option
1329 input:disk
1330 [...]
1331 output:local
1332 [...]
1333 convert:linux
1334 convert:windows
1335 A list of features is printed, one per line, and the program exits with
1337 status 0.
1338 The "input:" and "output:" features refer to -i and -o (input and
1340 output mode) options supported by this binary. The "convert:" features
1341 refer to guest types that this binary knows how to convert.
1342 Secondly use the option in conjunction with other options to make the
1344 regular program output more machine friendly.
1345 At the moment this means:
1347 1. Progress bar messages can be parsed from stdout by looking for this
1349 regular expression:
1350 ^[0-9]+/[0-9]+$
1352 2. The calling program should treat messages sent to stdout (except
1354 for progress bar messages) as status messages. They can be logged
1355 and/or displayed to the user.
1356 3. The calling program should treat messages sent to stderr as error
1358 messages. In addition, virt-v2v exits with a non-zero status code
1359 if there was a fatal error.
1360 Virt-v2v ≤ 0.9.1 did not support the --machine-readable option at all.
1362 The option was added when virt-v2v was rewritten in 2014.
1363 It is possible to specify a format string for controlling the output;
1365 see "ADVANCED MACHINE READABLE OUTPUT" in guestfs(3).
1366
1368 /usr/share/virtio-win
1369 (Optional)
1370 If this directory is present, then virtio drivers for Windows
1372 guests will be found from this directory and installed in the guest
1373 during conversion.
1374
1376 "VIRT_V2V_TMPDIR"
1377 "LIBGUESTFS_CACHEDIR"
1378 Location of the temporary directory used for the potentially large
1379 temporary overlay file. If neither environment variable is set
1380 then /var/tmp is used.
1381 To reliably ensure large temporary files are cleaned up (for
1383 example in case virt-v2v crashes) you should create a randomly
1384 named directory under /var/tmp, set "VIRT_V2V_TMPDIR" to point to
1385 this directory, then when virt-v2v exits remove the directory.
1386 See the "Disk space" section above.
1388 "VIRT_TOOLS_DATA_DIR"
1390 This can point to the directory containing data files used for
1391 Windows conversion.
1392 Normally you do not need to set this. If not set, a compiled-in
1394 default will be used (something like /usr/share/virt-tools).
1395 This directory may contain the following files:
1397 rhsrvany.exe
1399 (Required when doing conversions of Windows guests)
1400 This is the RHSrvAny Windows binary, used to install a
1402 "firstboot" script in the guest during conversion of Windows
1403 guests.
1404 See also: "https://github.com/rwmjones/rhsrvany"
1406 pvvxsvc.exe
1408 This is a Windows binary shipped with SUSE VMDP, used to
1409 install a "firstboot" script in Windows guests. It is required
1410 if you intend to use the --firstboot or --firstboot-command
1411 options with Windows guests.
1412 rhev-apt.exe
1414 (Optional)
1415 The RHV Application Provisioning Tool (RHEV APT). If this file
1417 is present, then RHEV APT will be installed in the Windows
1418 guest during conversion. This tool is a guest agent which
1419 ensures that the virtio drivers remain up to date when the
1420 guest is running on Red Hat Virtualization (RHV).
1421 This file comes from Red Hat Virtualization (RHV), and is not
1423 distributed with virt-v2v.
1424 "VIRTIO_WIN"
1426 This is where virtio drivers for Windows are searched for. It can
1427 be a directory or point to virtio-win.iso (CD ROM image containing
1428 drivers).
1429 If unset, then we look for drivers in whichever of these paths is
1431 found first:
1432 /usr/share/virtio-win/virtio-win.iso
1434 The ISO containing virtio drivers for Windows.
1435 /usr/share/virtio-win
1437 The exploded tree of virtio drivers for Windows. This is
1438 usually incomplete, hence the ISO is preferred.
1439 See "Enabling virtio".
1441 For other environment variables, see "ENVIRONMENT VARIABLES" in
1443 guestfs(3).
1444
1446 virt-v2v-copy-to-local(1)
1447 There are some special cases where virt-v2v cannot directly access
1448 the remote hypervisor. In that case you have to use
1449 virt-v2v-copy-to-local(1) to make a local copy of the guest first,
1450 followed by running "virt-v2v -i libvirtxml" to perform the
1451 conversion.
1452 engine-image-uploader(8)
1454 Variously called "engine-image-uploader", "ovirt-image-uploader" or
1455 "rhevm-image-uploader", this tool allows you to copy a guest from
1456 one oVirt or RHV Export Storage Domain to another. It only permits
1457 importing a guest that was previously exported from another
1458 oVirt/RHV instance.
1459 import-to-ovirt.pl
1461 This script can be used to import guests that already run on KVM to
1462 oVirt or RHV. For more information, see this blog posting by the
1463 author of virt-v2v:
1464 https://rwmj.wordpress.com/2015/09/18/importing-kvm-guests-to-ovirt-or-rhev/#content
1466
1468 virt-p2v(1), virt-customize(1), virt-df(1), virt-filesystems(1),
1469 virt-sparsify(1), virt-sysprep(1), guestfs(3), guestfish(1),
1470 qemu-img(1), virt-v2v-copy-to-local(1), virt-v2v-test-harness(1),
1471 engine-image-uploader(8), import-to-ovirt.pl, nbdkit(1),
1472 nbdkit-vddk-plugin(1), http://libguestfs.org/.
1473
1475 Matthew Booth
1476 Cédric Bosdonnat
1478 Tomáš Golembiovský
1480 Shahar Havivi
1482 Roman Kagan
1484 Mike Latimer
1486 Nir Soffer
1488 Richard W.M. Jones
1490 Pino Toscano
1492 Tingting Zheng
1494
1496 Copyright (C) 2009-2020 Red Hat Inc.
1497
1499 This program is free software; you can redistribute it and/or modify it
1500 under the terms of the GNU General Public License as published by the
1501 Free Software Foundation; either version 2 of the License, or (at your
1502 option) any later version.
1503 This program is distributed in the hope that it will be useful, but
1505 WITHOUT ANY WARRANTY; without even the implied warranty of
1506 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
1507 General Public License for more details.
1508 You should have received a copy of the GNU General Public License along
1510 with this program; if not, write to the Free Software Foundation, Inc.,
1511 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
1512
1514 To get a list of bugs against libguestfs, use this link:
1515 https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools
1516 To report a new bug against libguestfs, use this link:
1518 https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Virtualization+Tools
1519 When reporting a bug, please supply:
1521 • The version of libguestfs.
1523 • Where you got libguestfs (eg. which Linux distro, compiled from
1525 source, etc)
1526 • Describe the bug accurately and give a way to reproduce it.
1528 • Run libguestfs-test-tool(1) and paste the complete, unedited output
1530 into the bug report.
1531virt-v2v-1.44.0 2021-04-30 virt-v2v(1)