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 Note this options only applies to keys and passphrases for
342 encrypted devices and partitions, not for passwords used to connect
343 to remote servers.
344 --mac aa:bb:cc:dd:ee:ff:network:out
346 --mac aa:bb:cc:dd:ee:ff:bridge:out
347 Map source NIC MAC address to a network or bridge.
348 See "Networks and bridges" below.
350 --mac aa:bb:cc:dd:ee:ff:ip:ipaddr[,gw[,len[,ns,ns,...]]]
352 Force a particular interface (controlled by its MAC address) to
353 have a static IP address after boot.
354 The fields in the parameter are: "ipaddr" is the IP address. "gw"
356 is the optional gateway IP address. "len" is the subnet mask
357 length (an integer). The final parameters are zero or more
358 nameserver IP addresses.
359 This option can be supplied zero or more times.
361 You only need to use this option for certain broken guests such as
363 Windows which are unable to preserve MAC to static IP address
364 mappings automatically. You don't need to use it if Windows is
365 using DHCP. It is currently ignored for Linux guests since they do
366 not have this problem.
367 --machine-readable
369 --machine-readable=format
370 This option is used to make the output more machine friendly when
371 being parsed by other programs. See "Machine readable output"
372 below.
373 -n in:out
375 -n out
376 --network in:out
377 --network out
378 -b in:out
379 -b out
380 --bridge in:out
381 --bridge out
382 Map network (or bridge) called "in" to network (or bridge) called
383 "out". If no "in:" prefix is given, all other networks (or
384 bridges) are mapped to "out".
385 See "Networks and bridges" below.
387 --no-copy
389 Don’t copy the disks. Instead, conversion is performed (and thrown
390 away), and metadata is written, but no disks are created. See also
391 discussion of -o null below.
392 This is useful in two cases: Either you want to test if conversion
394 is likely to succeed, without the long copying process. Or you are
395 only interested in looking at the metadata.
396 This option is not compatible with -o libvirt since it would create
398 a faulty guest (one with no disks).
399 This option is not compatible with -o glance for technical reasons.
401 -o disk
403 This is the same as -o local.
404 -o glance
406 This is a legacy option. You should probably use -o openstack
407 instead.
408 Set the output method to OpenStack Glance. In this mode the
410 converted guest is uploaded to Glance. See
411 virt-v2v-output-openstack(1).
412 -o json
414 Set the output method to json.
415 In this mode, the converted guest is written to a local directory
417 specified by -os /dir (the directory must exist), with a JSON file
418 containing the majority of the metadata that virt-v2v gathered
419 during the conversion.
420 See virt-v2v-output-local(1).
422 -o libvirt
424 Set the output method to libvirt. This is the default.
425 In this mode, the converted guest is created as a libvirt guest.
427 You may also specify a libvirt connection URI (see -oc).
428 See virt-v2v-output-local(1).
430 -o local
432 Set the output method to local.
433 In this mode, the converted guest is written to a local directory
435 specified by -os /dir (the directory must exist). The converted
436 guest’s disks are written as:
437 /dir/name-sda
439 /dir/name-sdb
440 [etc]
441 and a libvirt XML file is created containing guest metadata:
443 /dir/name.xml
445 where "name" is the guest name.
447 -o null
449 Set the output method to null.
450 The guest is converted and copied (unless you also specify
452 --no-copy), but the results are thrown away and no metadata is
453 written.
454 -o openstack
456 Set the output method to OpenStack. See
457 virt-v2v-output-openstack(1).
458 -o ovirt
460 This is the same as -o rhv.
461 -o ovirt-upload
463 This is the same as -o rhv-upload.
464 -o qemu
466 Set the output method to qemu.
467 This is similar to -o local, except that a shell script is written
469 which you can use to boot the guest in qemu. The converted disks
470 and shell script are written to the directory specified by -os.
471 When using this output mode, you can also specify the --qemu-boot
473 option which boots the guest under qemu immediately.
474 -o rhev
476 This is the same as -o rhv.
477 -o rhv
479 Set the output method to rhv.
480 The converted guest is written to a RHV Export Storage Domain. The
482 -os parameter must also be used to specify the location of the
483 Export Storage Domain. Note this does not actually import the
484 guest into RHV. You have to do that manually later using the UI.
485 See virt-v2v-output-rhv(1).
487 -o rhv-upload
489 Set the output method to rhv-upload.
490 The converted guest is written directly to a RHV Data Domain. This
492 is a faster method than -o rhv, but requires oVirt or RHV ≥ 4.2.
493 See virt-v2v-output-rhv(1).
495 -o vdsm
497 Set the output method to vdsm.
498 This mode is similar to -o rhv, but the full path to the data
500 domain must be given:
501 /rhv/data-center/<data-center-uuid>/<data-domain-uuid>. This mode
502 is only used when virt-v2v runs under VDSM control.
503 -oa sparse
505 -oa preallocated
506 Set the output file allocation mode. The default is "sparse".
507 -oc URI
509 Specify a connection URI to use when writing the converted guest.
510 For -o libvirt this is the libvirt URI. Only local libvirt
512 connections can be used. Remote libvirt connections will not work.
513 See virt-v2v-output-local(1) for further information.
514 -of format
516 When converting the guest, convert the disks to the given format.
517 If not specified, then the input format is used.
519 -on name
521 Rename the guest when converting it. If this option is not used
522 then the output name is the same as the input name.
523 -oo OPTION=VALUE
525 Set output option(s) related to the current output mode. To
526 display short help on what options are available you can use:
527 virt-v2v -o rhv-upload -oo "?"
529 -oo guest-id="ID"
531 For -o openstack (virt-v2v-output-openstack(1)) only, set a guest
532 ID which is saved on each Cinder volume in the "virt_v2v_guest_id"
533 volume property.
534 -oo verify-server-certificate
536 -oo verify-server-certificate="true|false"
537 For -o openstack (virt-v2v-output-openstack(1)) only, this can be
538 used to disable SSL certification validation when connecting to
539 OpenStack by specifying -oo verify-server-certificate=false.
540 -oo os-*=*
542 For -o openstack (virt-v2v-output-openstack(1)) only, set optional
543 OpenStack authentication. For example -oo os-username=NAME is
544 equivalent to "openstack --os-username=NAME".
545 -oo rhv-cafile=ca.pem
547 For -o rhv-upload (virt-v2v-output-rhv(1)) only, the ca.pem file
548 (Certificate Authority), copied from /etc/pki/ovirt-engine/ca.pem
549 on the oVirt engine.
550 -oo rhv-cluster="CLUSTERNAME"
552 For -o rhv-upload (virt-v2v-output-rhv(1)) only, set the RHV
553 Cluster Name. If not given it uses "Default".
554 -oo rhv-direct
556 For -o rhv-upload (virt-v2v-output-rhv(1)) only, if this option is
557 given then virt-v2v will attempt to directly upload the disk to the
558 oVirt node, otherwise it will proxy the upload through the oVirt
559 engine. Direct upload requires that you have network access to the
560 oVirt nodes. Non-direct upload is slightly slower but should work
561 in all situations.
562 -oo rhv-verifypeer
564 For -o rhv-upload (virt-v2v-output-rhv(1)) only, verify the
565 oVirt/RHV server’s identity by checking the server‘s certificate
566 against the Certificate Authority.
567 -oo server-id="NAME|UUID"
569 For -o openstack (virt-v2v-output-openstack(1)) only, set the name
570 of the conversion appliance where virt-v2v is running.
571 -oo vdsm-compat=0.10
573 -oo vdsm-compat=1.1
574 If -o vdsm and the output format is qcow2, then we add the qcow2
575 compat=0.10 option to the output file for compatibility with RHEL 6
576 (see https://bugzilla.redhat.com/1145582).
577 If -oo vdsm-compat=1.1 is used then modern qcow2 (compat=1.1) files
579 are generated instead.
580 Currently -oo vdsm-compat=0.10 is the default, but this will change
582 to -oo vdsm-compat=1.1 in a future version of virt-v2v (when we can
583 assume that everyone is using a modern version of qemu).
584 Note this option only affects -o vdsm output. All other output
586 modes (including -o rhv) generate modern qcow2 compat=1.1 files,
587 always.
588 If this option is available, then "vdsm-compat-option" will appear
590 in the --machine-readable output.
591 -oo vdsm-image-uuid=UUID
593 -oo vdsm-vol-uuid=UUID
594 -oo vdsm-vm-uuid=UUID
595 -oo vdsm-ovf-output=DIR
596 Normally the RHV output mode chooses random UUIDs for the target
597 guest. However VDSM needs to control the UUIDs and passes these
598 parameters when virt-v2v runs under VDSM control. The parameters
599 control:
600 · the image directory of each guest disk (-oo vdsm-image-uuid)
602 (this option is passed once for each guest disk)
603 · UUIDs for each guest disk (-oo vdsm-vol-uuid) (this option is
605 passed once for each guest disk)
606 · the OVF file name (-oo vdsm-vm-uuid).
608 · the OVF output directory (default current directory) (-oo vdsm-
610 ovf-output).
611 The format of UUIDs is: "12345678-1234-1234-1234-123456789abc"
613 (each hex digit can be "0-9" or "a-f"), conforming to OSF DCE 1.1.
614 These options can only be used with -o vdsm.
616 -oo vdsm-ovf-flavour=flavour
618 This option controls the format of the OVF generated at the end of
619 conversion. Currently there are two possible flavours:
620 rhvexp
622 The OVF format used in RHV export storage domain.
623 ovirt
625 The OVF format understood by oVirt REST API.
626 For backward compatibility the default is rhvexp, but this may
628 change in the future.
629 -op file
631 Supply a file containing a password to be used when connecting to
632 the target hypervisor. Note the file should contain the whole
633 password, without any trailing newline, and for security the file
634 should have mode 0600 so that others cannot read it.
635 -os storage
637 The location of the storage for the converted guest.
638 For -o libvirt, this is a libvirt directory pool (see
640 "virsh pool-list") or pool UUID.
641 For -o json, -o local and -o qemu, this is a directory name. The
643 directory must exist.
644 For -o rhv-upload, this is the name of the destination Storage
646 Domain.
647 For -o openstack, this is the optional Cinder volume type.
649 For -o rhv, this can be an NFS path of the Export Storage Domain of
651 the form "<host>:<path>", eg:
652 rhv-storage.example.com:/rhv/export
654 The NFS export must be mountable and writable by the user and host
656 running virt-v2v, since the virt-v2v program has to actually mount
657 it when it runs. So you probably have to run virt-v2v as "root".
658 Or: You can mount the Export Storage Domain yourself, and point -os
660 to the mountpoint. Note that virt-v2v will still need to write to
661 this remote directory, so virt-v2v will still need to run as
662 "root".
663 You will get an error if virt-v2v is unable to mount/write to the
665 Export Storage Domain.
666 --print-estimate
668 Print the estimated size of the data which will be copied from the
669 source disk(s) and stop. One number (the size in bytes) is printed
670 per disk, and a total:
671 $ virt-v2v --print-estimate
673 ...
674 disk 1: 100000
675 disk 2: 200000
676 total: 300000
677 With the --machine-readable option you get JSON output which can be
679 directed into a file or elsewhere:
680 $ virt-v2v --print-estimate --machine-readable=file:estimates
682 ...
683 $ cat estimates
684 {
685 "disks": [ 100000, 200000 ],
686 "total": 300000
687 }
688 When using this option you must specify an output mode. This is
690 because virt-v2v has to perform the conversion in order to print
691 the estimate, and the conversion depends on the output mode. Using
692 -o null should be safe for most purposes.
693 When this option is used along with --machine-readable you can
695 direct the output to an alternate file.
696 --print-source
698 Print information about the source guest and stop. This option is
699 useful when you are setting up network and bridge maps. See
700 "Networks and bridges".
701 --qemu-boot
703 When using -o qemu only, this boots the guest immediately after
704 virt-v2v finishes.
705 -q
707 --quiet
708 This disables progress bars and other unnecessary output.
709 --root ask
711 --root single
712 --root first
713 --root /dev/sdX
714 --root /dev/VG/LV
715 Choose the root filesystem to be converted.
716 In the case where the virtual machine is dual-boot or multi-boot,
718 or where the VM has other filesystems that look like operating
719 systems, this option can be used to select the root filesystem
720 (a.k.a. "C:" drive or /) of the operating system that is to be
721 converted. The Windows Recovery Console, certain attached DVD
722 drives, and bugs in libguestfs inspection heuristics, can make a
723 guest look like a multi-boot operating system.
724 The default in virt-v2v ≤ 0.7.1 was --root single, which causes
726 virt-v2v to die if a multi-boot operating system is found.
727 Since virt-v2v ≥ 0.7.2 the default is now --root ask: If the VM is
729 found to be multi-boot, then virt-v2v will stop and list the
730 possible root filesystems and ask the user which to use. This
731 requires that virt-v2v is run interactively.
732 --root first means to choose the first root device in the case of a
734 multi-boot operating system. Since this is a heuristic, it may
735 sometimes choose the wrong one.
736 You can also name a specific root device, eg. --root /dev/sda2
738 would mean to use the second partition on the first hard drive. If
739 the named root device does not exist or was not detected as a root
740 device, then virt-v2v will fail.
741 Note that there is a bug in grub which prevents it from
743 successfully booting a multiboot system if virtio is enabled. Grub
744 is only able to boot an operating system from the first virtio
745 disk. Specifically, /boot must be on the first virtio disk, and it
746 cannot chainload an OS which is not in the first virtio disk.
747 -v
749 --verbose
750 Enable verbose messages for debugging.
751 -V
753 --version
754 Display version number and exit.
755 -x Enable tracing of libguestfs API calls.
757
759 Xen paravirtualized guests
760 Older versions of virt-v2v could turn a Xen paravirtualized (PV) guest
761 into a KVM guest by installing a new kernel. This version of virt-v2v
762 does not attempt to install any new kernels. Instead it will give you
763 an error if there are only Xen PV kernels available.
764 Therefore before conversion you should check that a regular kernel is
766 installed. For some older Linux distributions, this means installing a
767 kernel from the table below:
768 RHEL 3 (Does not apply, as there was no Xen PV kernel)
770 RHEL 4 i686 with > 10GB of RAM: install 'kernel-hugemem'
772 i686 SMP: install 'kernel-smp'
773 other i686: install 'kernel'
774 x86-64 SMP with > 8 CPUs: install 'kernel-largesmp'
775 x86-64 SMP: install 'kernel-smp'
776 other x86-64: install 'kernel'
777 RHEL 5 i686: install 'kernel-PAE'
779 x86-64: install 'kernel'
780 SLES 10 i586 with > 10GB of RAM: install 'kernel-bigsmp'
782 i586 SMP: install 'kernel-smp'
783 other i586: install 'kernel-default'
784 x86-64 SMP: install 'kernel-smp'
785 other x86-64: install 'kernel-default'
786 SLES 11+ i586: install 'kernel-pae'
788 x86-64: install 'kernel-default'
789 Windows (Does not apply, as there is no Xen PV Windows kernel)
791 Enabling virtio
793 "Virtio" is the name for a set of drivers which make disk (block
794 device), network and other guest operations work much faster on KVM.
795 Older versions of virt-v2v could install these drivers for certain
797 Linux guests. This version of virt-v2v does not attempt to install new
798 Linux kernels or drivers, but will warn you if they are not installed
799 already.
800 In order to enable virtio, and hence improve performance of the guest
802 after conversion, you should ensure that the minimum versions of
803 packages are installed before conversion, by consulting the table
804 below.
805 RHEL 3 No virtio drivers are available
807 RHEL 4 kernel >= 2.5.9-89.EL
809 lvm2 >= 2.02.42-5.el4
810 device-mapper >= 1.02.28-2.el4
811 selinux-policy-targeted >= 1.17.30-2.152.el4
812 policycoreutils >= 1.18.1-4.13
813 RHEL 5 kernel >= 2.6.18-128.el5
815 lvm2 >= 2.02.40-6.el5
816 selinux-policy-targeted >= 2.4.6-203.el5
817 RHEL 6+ All versions support virtio
819 Fedora All versions support virtio
821 SLES 11+ All versions support virtio
823 SLES 10 kernel >= 2.6.16.60-0.85.1
825 OpenSUSE 11+ All versions support virtio
827 OpenSUSE 10 kernel >= 2.6.25.5-1.1
829 Debian 6+ All versions support virtio
831 Ubuntu 10.04+ All versions support virtio
833 Windows Drivers are installed from the ISO or directory pointed
835 to by "VIRTIO_WIN" environment variable if present
836 RHEL 4: SELinux relabel appears to hang forever
838 In RHEL ≤ 4.7 there was a bug which causes SELinux relabelling to
839 appear to hang forever at:
840 *** Warning -- SELinux relabel is required. ***
842 *** Disabling security enforcement. ***
843 *** Relabeling could take a very long time, ***
844 *** depending on file system size. ***
845 In reality it is waiting for you to press a key (but there is no visual
847 indication of this). You can either hit the "[Return]" key, at which
848 point the guest will finish relabelling and reboot, or you can install
849 policycoreutils ≥ 1.18.1-4.13 before starting the v2v conversion. See
850 also https://bugzilla.redhat.com/show_bug.cgi?id=244636
851 Debian and Ubuntu
853 "warning: could not determine a way to update the configuration of
854 Grub2"
855 Currently, virt-v2v has no way to set the default kernel in Debian and
857 Ubuntu guests using GRUB 2 as bootloader. This means that virt-v2v
858 will not change the default kernel used for booting, even in case it is
859 not the best kernel available on the guest. A recommended procedure
860 is, before using virt-v2v, to check that the boot kernel is the best
861 kernel available in the guest (for example by making sure the guest is
862 up-to-date).
863 "vsyscall attempted with vsyscall=none"
865 When run on a recent Debian host virt-v2v may fail to convert guests
867 which were created before 2013. In the debugging output you will see a
868 crash message similar to:
869 vsyscall attempted with vsyscall=none ip:...
871 segfault at ...
872 This is caused because Debian removed support for running old binaries
874 which used the legacy vsyscall page to call into the kernel.
875 You can work around this problem by running this command before running
877 virt-v2v:
878 export LIBGUESTFS_APPEND="vsyscall=emulate"
880 For more information, see https://bugzilla.redhat.com/1592061
882 Windows
884 Windows ≥ 8 Fast Startup is incompatible with virt-v2v
885 Guests which use the Windows ≥ 8 "Fast Startup" feature (or guests
887 which are hibernated) cannot be converted with virt-v2v. You will see
888 an error:
889 virt-v2v: error: unable to mount the disk image for writing. This has
891 probably happened because Windows Hibernation or Fast Restart is being
892 used in this guest. You have to disable this (in the guest) in order
893 to use virt-v2v.
894 As the message says, you need to boot the guest and disable the "Fast
896 Startup" feature (Control Panel → Power Options → Choose what the power
897 buttons do → Change settings that are currently unavailable → Turn on
898 fast startup), and shut down the guest, and then you will be able to
899 convert it.
900 For more information, see: "WINDOWS HIBERNATION AND WINDOWS 8 FAST
902 STARTUP" in guestfs(3).
903 Boot failure: 0x0000007B
905 This boot failure is caused by Windows being unable to find or load the
907 right disk driver (eg. viostor.sys). If you experience this error,
908 here are some things to check:
909 · First ensure that the guest boots on the source hypervisor before
911 conversion.
912 · Check you have the Windows virtio drivers available in
914 /usr/share/virtio-win, and that virt-v2v did not print any warning
915 about not being able to install virtio drivers.
916 On Red Hat Enterprise Linux 7, you will need to install the signed
918 drivers available in the "virtio-win" package. If you do not have
919 access to the signed drivers, then you will probably need to
920 disable driver signing in the boot menus.
921 · Check that you are presenting a virtio-blk interface (not virtio-
923 scsi and not ide) to the guest. On the qemu/KVM command line you
924 should see something similar to this:
925 ... -drive file=windows-sda,if=virtio ...
927 In libvirt XML, you should see:
929 <target dev='vda' bus='virtio'/>
931 · Check that Windows Group Policy does not prevent the driver from
933 being installed or used. Try deleting Windows Group Policy before
934 conversion.
935 · Check there is no anti-virus or other software which implements
937 Group Policy-like prohibitions on installing or using new drivers.
938 · Enable boot debugging and check the viostor.sys driver is being
940 loaded.
941 OpenStack and Windows reactivation
943 OpenStack does not offer stable device / PCI addresses to guests.
945 Every time it creates or starts a guest, it regenerates the libvirt XML
946 for that guest from scratch. The libvirt XML will have no <address>
947 fields. Libvirt will then assign addresses to devices, in a
948 predictable manner. Addresses may change if any of the following are
949 true:
950 · A new disk or network device has been added or removed from the
952 guest.
953 · The version of OpenStack or (possibly) libvirt has changed.
955 Because Windows does not like "hardware" changes of this kind, it may
957 trigger Windows reactivation.
958 This can also prevent booting with a 7B error [see previous section] if
960 the guest has group policy containing "Device Installation
961 Restrictions".
962 Support for SHA-2 certificates in Windows 7 and Windows Server 2008 R2
964 Later versions of the Windows virtio drivers are signed using SHA-2
966 certificates (instead of SHA-1). The original shipping Windows 7 and
967 Windows Server 2008 R2 did not understand SHA-2 certificates and so the
968 Windows virtio drivers will not install properly.
969 To fix this you must apply SHA-2 Code Signing Support from:
971 https://docs.microsoft.com/en-us/security-updates/SecurityAdvisories/2015/3033929
972 before converting the guest.
973 For further information see:
975 https://bugzilla.redhat.com/show_bug.cgi?id=1624878
976 Networks and bridges
978 Guests are usually connected to one or more networks, and when
979 converted to the target hypervisor you usually want to reconnect those
980 networks at the destination. The options --network, --bridge and --mac
981 allow you to do that.
982 If you are unsure of what networks and bridges are in use on the source
984 hypervisor, then you can examine the source metadata (libvirt XML,
985 vCenter information, etc.). Or you can run virt-v2v with the
986 --print-source option which causes virt-v2v to print out the
987 information it has about the guest on the source and then exit.
988 In the --print-source output you will see a section showing the guest’s
990 Network Interface Cards (NICs):
991 $ virt-v2v [-i ...] --print-source name
993 [...]
994 NICs:
995 Network "default" mac: 52:54:00:d0:cf:0e
996 Bridges are special classes of network devices which are attached to a
998 named external network on the source hypervisor, for example:
999 $ virt-v2v [-i ...] --print-source name
1001 [...]
1002 NICs:
1003 Bridge "br0"
1004 To map a specific source bridge to a target network, for example "br0"
1006 on the source to "ovirtmgmt" on the target, use:
1007 virt-v2v [...] --bridge br0:ovirtmgmt
1009 To map every bridge to a target network, use:
1011 virt-v2v [...] --bridge ovirtmgmt
1013 Fine-grained mapping of guest NICs
1015 The --mac option gives you more control over the mapping, letting you
1017 map single NICs to either networks or bridges on the target. For
1018 example a source guest with two NICs could map them individually to two
1019 networks called "mgmt" and "clientdata" like this:
1020 $ virt-v2v [...] \
1022 --mac 52:54:00:d0:cf:0e:network:mgmt \
1023 --mac 52:54:00:d0:cf:0f:network:clientdata
1024 Note that virt-v2v does not have the ability to change a guest’s MAC
1026 address. The MAC address is part of the guest metadata and must remain
1027 the same on source and target hypervisors. Most guests will use the
1028 MAC address to set up persistent associations between NICs and internal
1029 names (like "eth0"), with firewall settings, or even for other purposes
1030 like software licensing.
1031 Resource requirements
1033 Network
1034 The most important resource for virt-v2v appears to be network
1036 bandwidth. Virt-v2v should be able to copy guest data at gigabit
1037 ethernet speeds or greater.
1038 Ensure that the network connections between servers (conversion server,
1040 NFS server, vCenter, Xen) are as fast and as low latency as possible.
1041 Disk space
1043 Virt-v2v places potentially large temporary files in
1045 $LIBGUESTFS_CACHEDIR (which is /var/tmp if you don't set it). Using
1046 tmpfs is a bad idea.
1047 For each guest disk, an overlay is stored temporarily. This stores the
1049 changes made during conversion, and is used as a cache. The overlays
1050 are not particularly large - tens or low hundreds of megabytes per disk
1051 is typical. In addition to the overlay(s), input and output methods
1052 may use disk space, as outlined in the table below.
1053 -i ova
1055 This temporarily places a full copy of the uncompressed source
1056 disks in $LIBGUESTFS_CACHEDIR (or /var/tmp).
1057 -o glance
1059 This temporarily places a full copy of the output disks in
1060 $LIBGUESTFS_CACHEDIR (or /var/tmp).
1061 -o local
1063 -o qemu
1064 You must ensure there is sufficient space in the output directory
1065 for the converted guest.
1066 See also "Minimum free space check in the host" below.
1068 VMware vCenter resources
1070 Copying from VMware vCenter is currently quite slow, but we believe
1072 this to be an issue with VMware. Ensuring the VMware ESXi hypervisor
1073 and vCenter are running on fast hardware with plenty of memory should
1074 alleviate this.
1075 Compute power and RAM
1077 Virt-v2v is not especially compute or RAM intensive. If you are
1079 running many parallel conversions, then you may consider allocating one
1080 CPU core and 2 GB of RAM per running instance.
1081 Virt-v2v can be run in a virtual machine.
1083 Trimming
1085 Virt-v2v attempts to optimize the speed of conversion by ignoring guest
1087 filesystem data which is not used. This would include unused
1088 filesystem blocks, blocks containing zeroes, and deleted files.
1089 To do this, virt-v2v issues a non-destructive fstrim(8) operation. As
1091 this happens to an overlay placed over the guest data, it does not
1092 affect the source in any way.
1093 If this fstrim operation fails, you will see a warning, but virt-v2v
1095 will continue anyway. It may run more slowly (in some cases much more
1096 slowly), because it is copying the unused parts of the disk.
1097 Unfortunately support for fstrim is not universal, and it also depends
1099 on specific details of the filesystem, partition alignment, and backing
1100 storage. As an example, NTFS filesystems cannot be fstrimmed if they
1101 occupy a partition which is not aligned to the underlying storage.
1102 That was the default on Windows before Vista. As another example, VFAT
1103 filesystems (used by UEFI guests) cannot be trimmed at all.
1104 fstrim support in the Linux kernel is improving gradually, so over time
1106 some of these restrictions will be lifted and virt-v2v will work
1107 faster.
1108 Post-conversion tasks
1110 Guest network configuration
1111 Virt-v2v cannot currently reconfigure a guest’s network configuration.
1113 If the converted guest is not connected to the same subnet as the
1114 source, its network configuration may have to be updated. See also
1115 virt-customize(1).
1116 Converting a Windows guest
1118 When converting a Windows guests, the conversion process is split into
1120 two stages:
1121 1. Offline conversion.
1123 2. First boot.
1125 The guest will be bootable after the offline conversion stage, but will
1127 not yet have all necessary drivers installed to work correctly. These
1128 will be installed automatically the first time the guest boots.
1129 N.B. Take care not to interrupt the automatic driver installation
1131 process when logging in to the guest for the first time, as this may
1132 prevent the guest from subsequently booting correctly.
1133 Free space for conversion
1135 Free space in the guest
1136 Virt-v2v checks there is sufficient free space in the guest filesystem
1138 to perform the conversion. Currently it checks:
1139 Linux root filesystem or Windows "C:" drive
1141 Minimum free space: 20 MB
1142 Linux /boot
1144 Minimum free space: 50 MB
1145 This is because we need to build a new initramfs for some
1147 Enterprise Linux conversions.
1148 Any other mountable filesystem
1150 Minimum free space: 10 MB
1151 In addition to the actual free space, each filesystem is required to
1153 have at least 100 available inodes.
1154 Minimum free space check in the host
1156 You must have sufficient free space in the host directory used to store
1158 temporary overlays (except in --in-place mode). To find out which
1159 directory this is, use:
1160 $ df -h "`guestfish get-cachedir`"
1162 Filesystem Size Used Avail Use% Mounted on
1163 /dev/mapper/root 50G 40G 6.8G 86% /
1164 and look under the "Avail" column. Virt-v2v will refuse to do the
1166 conversion at all unless at least 1GB is available there.
1167 See also "Resource requirements" above.
1169 Running virt-v2v as root or non-root
1171 Nothing in virt-v2v inherently needs root access, and it will run just
1172 fine as a non-root user. However, certain external features may
1173 require either root or a special user:
1174 Mounting the Export Storage Domain
1176 When using -o rhv -os server:/esd virt-v2v has to have sufficient
1177 privileges to NFS mount the Export Storage Domain from "server".
1178 You can avoid needing root here by mounting it yourself before
1180 running virt-v2v, and passing -os /mountpoint instead, but first of
1181 all read the next section ...
1182 Writing to the Export Storage Domain as 36:36
1184 RHV-M cannot read files and directories from the Export Storage
1185 Domain unless they have UID:GID 36:36. You will see VM import
1186 problems if the UID:GID is not correct.
1187 When you run virt-v2v -o rhv as root, virt-v2v attempts to create
1189 files and directories with the correct ownership. If you run
1190 virt-v2v as non-root, it will probably still work, but you will
1191 need to manually change ownership after virt-v2v has finished.
1192 Writing to libvirt
1194 When using -o libvirt, you may need to run virt-v2v as root so that
1195 it can write to the libvirt system instance (ie. "qemu:///system")
1196 and to the default location for disk images (usually
1197 /var/lib/libvirt/images).
1198 You can avoid this by setting up libvirt connection authentication,
1200 see http://libvirt.org/auth.html. Alternatively, use -oc
1201 qemu:///session, which will write to your per-user libvirt
1202 instance.
1203 Writing to Openstack
1205 Because of how Cinder volumes are presented as /dev block devices,
1206 using -o openstack normally requires that virt-v2v is run as root.
1207 Writing to Glance
1209 This does not need root (in fact it probably won’t work), but may
1210 require either a special user and/or for you to source a script
1211 that sets authentication environment variables. Consult the Glance
1212 documentation.
1213 Minimal XML for -i libvirtxml option
1215 When using the -i libvirtxml option, you have to supply some libvirt
1216 XML. Writing this from scratch is hard, so the template below is
1217 helpful.
1218 Note this should only be used for testing and/or where you know what
1220 you're doing! If you have libvirt metadata for the guest, always use
1221 that instead.
1222 <domain type='kvm'>
1224 <name> NAME </name>
1225 <memory>1048576</memory>
1226 <vcpu>2</vcpu>
1227 <os>
1228 <type>hvm</type>
1229 <boot dev='hd'/>
1230 </os>
1231 <features>
1232 <acpi/>
1233 <apic/>
1234 <pae/>
1235 </features>
1236 <devices>
1237 <disk type='file' device='disk'>
1238 <driver name='qemu' type='raw'/>
1239 <source file='/path/to/disk/image'/>
1240 <target dev='hda' bus='ide'/>
1241 </disk>
1242 <interface type='network'>
1243 <mac address='52:54:00:01:02:03'/>
1244 <source network='default'/>
1245 <model type='rtl8139'/>
1246 </interface>
1247 </devices>
1248 </domain>
1249 In-place conversion
1251 It is also possible to use virt-v2v in scenarios where a foreign VM has
1252 already been imported into a KVM-based hypervisor, but still needs
1253 adjustments in the guest to make it run in the new virtual hardware.
1254 In that case it is assumed that a third-party tool has created the
1256 target VM in the supported KVM-based hypervisor based on the source VM
1257 configuration and contents, but using virtual devices more appropriate
1258 for KVM (e.g. virtio storage and network, etc.).
1259 Then, to make the guest OS boot and run in the changed environment, one
1261 can use:
1262 virt-v2v -ic qemu:///system converted_vm --in-place
1264 Virt-v2v will analyze the configuration of "converted_vm" in the
1266 "qemu:///system" libvirt instance, and apply various fixups to the
1267 guest OS configuration to make it match the VM configuration. This may
1268 include installing virtio drivers, configuring the bootloader, the
1269 mountpoints, the network interfaces, and so on.
1270 Should an error occur during the operation, virt-v2v exits with an
1272 error code leaving the VM in an undefined state.
1273 Machine readable output
1275 The --machine-readable option can be used to make the output more
1276 machine friendly, which is useful when calling virt-v2v from other
1277 programs, GUIs etc.
1278 There are two ways to use this option.
1280 Firstly use the option on its own to query the capabilities of the
1282 virt-v2v binary. Typical output looks like this:
1283 $ virt-v2v --machine-readable
1285 virt-v2v
1286 libguestfs-rewrite
1287 colours-option
1288 vdsm-compat-option
1289 input:disk
1290 [...]
1291 output:local
1292 [...]
1293 convert:linux
1294 convert:windows
1295 A list of features is printed, one per line, and the program exits with
1297 status 0.
1298 The "input:" and "output:" features refer to -i and -o (input and
1300 output mode) options supported by this binary. The "convert:" features
1301 refer to guest types that this binary knows how to convert.
1302 Secondly use the option in conjunction with other options to make the
1304 regular program output more machine friendly.
1305 At the moment this means:
1307 1. Progress bar messages can be parsed from stdout by looking for this
1309 regular expression:
1310 ^[0-9]+/[0-9]+$
1312 2. The calling program should treat messages sent to stdout (except
1314 for progress bar messages) as status messages. They can be logged
1315 and/or displayed to the user.
1316 3. The calling program should treat messages sent to stderr as error
1318 messages. In addition, virt-v2v exits with a non-zero status code
1319 if there was a fatal error.
1320 Virt-v2v ≤ 0.9.1 did not support the --machine-readable option at all.
1322 The option was added when virt-v2v was rewritten in 2014.
1323 It is possible to specify a format string for controlling the output;
1325 see "ADVANCED MACHINE READABLE OUTPUT" in guestfs(3).
1326
1328 /usr/share/virtio-win
1329 (Optional)
1330 If this directory is present, then virtio drivers for Windows
1332 guests will be found from this directory and installed in the guest
1333 during conversion.
1334
1336 "LIBGUESTFS_CACHEDIR"
1337 Location of the temporary directory used for the potentially large
1338 temporary overlay file. If not set, /var/tmp is used.
1339 See the "Disk space" section above.
1341 "VIRT_TOOLS_DATA_DIR"
1343 This can point to the directory containing data files used for
1344 Windows conversion.
1345 Normally you do not need to set this. If not set, a compiled-in
1347 default will be used (something like /usr/share/virt-tools).
1348 This directory may contain the following files:
1350 rhsrvany.exe
1352 (Required when doing conversions of Windows guests)
1353 This is the RHSrvAny Windows binary, used to install a
1355 "firstboot" script in the guest during conversion of Windows
1356 guests.
1357 See also: "https://github.com/rwmjones/rhsrvany"
1359 pvvxsvc.exe
1361 This is a Windows binary shipped with SUSE VMDP, used to
1362 install a "firstboot" script in Windows guests. It is required
1363 if you intend to use the --firstboot or --firstboot-command
1364 options with Windows guests.
1365 rhev-apt.exe
1367 (Optional)
1368 The RHV Application Provisioning Tool (RHEV APT). If this file
1370 is present, then RHEV APT will be installed in the Windows
1371 guest during conversion. This tool is a guest agent which
1372 ensures that the virtio drivers remain up to date when the
1373 guest is running on Red Hat Virtualization (RHV).
1374 This file comes from Red Hat Virtualization (RHV), and is not
1376 distributed with virt-v2v.
1377 "VIRTIO_WIN"
1379 This is where virtio drivers for Windows are searched for. It can
1380 be a directory or point to virtio-win.iso (CD ROM image containing
1381 drivers).
1382 If unset, then we look for drivers in whichever of these paths is
1384 found first:
1385 /usr/share/virtio-win/virtio-win.iso
1387 The ISO containing virtio drivers for Windows.
1388 /usr/share/virtio-win
1390 The exploded tree of virtio drivers for Windows. This is
1391 usually incomplete, hence the ISO is preferred.
1392 See "Enabling virtio".
1394 For other environment variables, see "ENVIRONMENT VARIABLES" in
1396 guestfs(3).
1397
1399 virt-v2v-copy-to-local(1)
1400 There are some special cases where virt-v2v cannot directly access
1401 the remote hypervisor. In that case you have to use
1402 virt-v2v-copy-to-local(1) to make a local copy of the guest first,
1403 followed by running "virt-v2v -i libvirtxml" to perform the
1404 conversion.
1405 engine-image-uploader(8)
1407 Variously called "engine-image-uploader", "ovirt-image-uploader" or
1408 "rhevm-image-uploader", this tool allows you to copy a guest from
1409 one oVirt or RHV Export Storage Domain to another. It only permits
1410 importing a guest that was previously exported from another
1411 oVirt/RHV instance.
1412 import-to-ovirt.pl
1414 This script can be used to import guests that already run on KVM to
1415 oVirt or RHV. For more information, see this blog posting by the
1416 author of virt-v2v:
1417 https://rwmj.wordpress.com/2015/09/18/importing-kvm-guests-to-ovirt-or-rhev/#content
1419
1421 virt-p2v(1), virt-customize(1), virt-df(1), virt-filesystems(1),
1422 virt-sparsify(1), virt-sysprep(1), guestfs(3), guestfish(1),
1423 qemu-img(1), virt-v2v-copy-to-local(1), virt-v2v-test-harness(1),
1424 engine-image-uploader(8), import-to-ovirt.pl, nbdkit(1),
1425 nbdkit-vddk-plugin(1), http://libguestfs.org/.
1426
1428 Matthew Booth
1429 Cédric Bosdonnat
1431 Tomáš Golembiovský
1433 Shahar Havivi
1435 Roman Kagan
1437 Mike Latimer
1439 Nir Soffer
1441 Richard W.M. Jones
1443 Pino Toscano
1445 Tingting Zheng
1447
1449 Copyright (C) 2009-2020 Red Hat Inc.
1450
1452 This program is free software; you can redistribute it and/or modify it
1453 under the terms of the GNU General Public License as published by the
1454 Free Software Foundation; either version 2 of the License, or (at your
1455 option) any later version.
1456 This program is distributed in the hope that it will be useful, but
1458 WITHOUT ANY WARRANTY; without even the implied warranty of
1459 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
1460 General Public License for more details.
1461 You should have received a copy of the GNU General Public License along
1463 with this program; if not, write to the Free Software Foundation, Inc.,
1464 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
1465
1467 To get a list of bugs against libguestfs, use this link:
1468 https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools
1469 To report a new bug against libguestfs, use this link:
1471 https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Virtualization+Tools
1472 When reporting a bug, please supply:
1474 · The version of libguestfs.
1476 · Where you got libguestfs (eg. which Linux distro, compiled from
1478 source, etc)
1479 · Describe the bug accurately and give a way to reproduce it.
1481 · Run libguestfs-test-tool(1) and paste the complete, unedited output
1483 into the bug report.
1484virt-v2v-1.42.0 2020-04-16 virt-v2v(1)