1virt-v2v(1) Virtualization Support virt-v2v(1)
2
6 virt-v2v - Convert a guest to use KVM
7
9 virt-v2v [-i mode] [other -i* options]
10 [-o mode] [other -o* options]
11 [guest|filename]
12
14 Virt-v2v converts a single guest from a foreign hypervisor to run on
15 KVM. It can read Linux and Windows guests running on VMware, Xen,
16 Hyper-V and some other hypervisors, and convert them to KVM managed by
17 libvirt, OpenStack, oVirt, Red Hat Virtualisation (RHV) or several
18 other targets. It can modify the guest to make it bootable on KVM and
19 install virtio drivers so it will run quickly.
20 There is also a companion front-end called virt-p2v(1) which comes as
22 an ISO, CD or PXE image that can be booted on physical machines to
23 virtualize those machines (physical to virtual, or p2v).
24 To estimate the disk space needed before conversion, see
26 virt-v2v-inspector(1).
27 For in-place conversion, there is a separate tool called
29 virt-v2v-in-place(1).
30 Input and Output
32 You normally run virt-v2v with several -i* options controlling the
33 input mode and also several -o* options controlling the output mode.
34 In this sense, "input" refers to the source foreign hypervisor such as
35 VMware, and "output" refers to the target KVM-based management system
36 such as oVirt or OpenStack.
37 The input and output sides of virt-v2v are separate and unrelated.
39 Virt-v2v can read from any input and write to any output. Therefore
40 these sides of virt-v2v are documented separately in this manual.
41 Virt-v2v normally copies from the input to the output, called "copying
43 mode". In this case the source guest is always left unchanged. In-
44 place conversions may be done using virt-v2v-in-place(1).
45 Other virt-v2v topics
47 virt-v2v-support(1) — Supported hypervisors, virtualization management
48 systems, guests.
49 virt-v2v-input-vmware(1) — Input from VMware.
51 virt-v2v-input-xen(1) — Input from Xen.
53 virt-v2v-output-local(1) — Output to local files or local libvirt.
55 virt-v2v-output-rhv(1) — Output to oVirt or RHV.
57 virt-v2v-output-openstack(1) — Output to OpenStack.
59 virt-v2v-release-notes-1.42(1) — Release notes for 1.42 release.
61 virt-v2v-release-notes-2.0(1) — Release notes for 2.0 release.
63 virt-v2v-release-notes-2.2(1) — Release notes for 2.2 release.
65
67 Convert from VMware vCenter server to local libvirt
68 You have a VMware vCenter server called "vcenter.example.com", a
69 datacenter called "Datacenter", and an ESXi hypervisor called "esxi".
70 You want to convert a guest called "vmware_guest" to run locally under
71 libvirt.
72 virt-v2v -ic vpx://vcenter.example.com/Datacenter/esxi vmware_guest
74 In this case you will most likely have to run virt-v2v as "root", since
76 it needs to talk to the system libvirt daemon and copy the guest disks
77 to /var/lib/libvirt/images.
78 For more information see virt-v2v-input-vmware(1).
80 Convert from VMware to RHV/oVirt
82 This is the same as the previous example, except you want to send the
83 guest to a RHV Data Domain using the RHV REST API. Guest network
84 interface(s) are connected to the target network called "ovirtmgmt".
85 virt-v2v -ic vpx://vcenter.example.com/Datacenter/esxi vmware_guest \
87 -o rhv-upload -oc https://ovirt-engine.example.com/ovirt-engine/api \
88 -os ovirt-data -op /tmp/ovirt-admin-password -of raw \
89 -oo rhv-cafile=/tmp/ca.pem --bridge ovirtmgmt
90 In this case the host running virt-v2v acts as a conversion server.
92 For more information see virt-v2v-output-rhv(1).
94 Convert from ESXi hypervisor over SSH to local libvirt
96 You have an ESXi hypervisor called "esxi.example.com" with SSH access
97 enabled. You want to convert from VMFS storage on that server to a
98 local file.
99 virt-v2v \
101 -i vmx -it ssh \
102 "ssh://root@esxi.example.com/vmfs/volumes/datastore1/guest/guest.vmx" \
103 -o local -os /var/tmp
104 The guest must not be running. Virt-v2v would not need to be run as
106 root in this case.
107 For more information about converting from VMX files see
109 virt-v2v-input-vmware(1).
110 Convert disk image to OpenStack
112 Given a disk image from another hypervisor that you want to convert to
113 run on OpenStack (only KVM-based OpenStack is supported), you can run
114 virt-v2v inside an OpenStack VM (called "v2v-vm" below), and do:
115 virt-v2v -i disk disk.img -o openstack -oo server-id=v2v-vm
117 See virt-v2v-output-openstack(1).
119 Convert disk image to disk image
121 Given a disk image from another hypervisor that you want to convert to
122 run on KVM, you have two options. The simplest way is to try:
123 virt-v2v -i disk disk.img -o local -os /var/tmp
125 where virt-v2v guesses everything about the input disk.img and (in this
127 case) writes the converted result to /var/tmp.
128 A more complex method is to write some libvirt XML describing the input
130 guest (if you can get the source hypervisor to provide you with libvirt
131 XML, then so much the better). You can then do:
132 virt-v2v -i libvirtxml guest-domain.xml -o local -os /var/tmp
134 Since guest-domain.xml contains the path(s) to the guest disk image(s)
136 you do not need to specify the name of the disk image on the command
137 line.
138 To convert a local disk image and immediately boot it in local qemu,
140 do:
141 virt-v2v -i disk disk.img -o qemu -os /var/tmp -oo qemu-boot
143
145 --help
146 Display help.
147 --bandwidth bps
149 --bandwidth-file filename
150 Some input methods are able to limit the network bandwidth they
151 will use statically or dynamically. In the first variant this sets
152 the bandwidth limit statically in bits per second. Formats like
153 "10M" may be used (meaning 10 megabits per second).
154 In the second variant the bandwidth is limited dynamically from the
156 content of the file (also in bits per second, in the same formats
157 supported by the first variant). You may use both parameters
158 together, meaning: first limit to a static rate, then you can
159 create the file while virt-v2v is running to adjust the rate
160 dynamically.
161 This is only supported for:
163 • input from Xen
165 • input from VMware VMX when using the SSH transport method
167 • input from VDDK
169 • -i libvirtxml when using HTTP or HTTPS disks
171 • input from VMware vCenter server
173 The options are silently ignored for other input methods.
175 -b ...
177 --bridge ...
178 See --network below.
179 --colors
181 --colours
182 Use ANSI colour sequences to colourize messages. This is the
183 default when the output is a tty. If the output of the program is
184 redirected to a file, ANSI colour sequences are disabled unless you
185 use this option.
186 --compressed
188 This is the same as -oo compressed.
189 --echo-keys
191 When prompting for keys and passphrases, virt-v2v normally turns
192 echoing off so you cannot see what you are typing. If you are not
193 worried about Tempest attacks and there is no one else in the room
194 you can specify this flag to see what you are typing.
195 Note this options only applies to keys and passphrases for
197 encrypted devices and partitions, not for passwords used to connect
198 to remote servers.
199 -i disk
201 Set the input method to disk.
202 In this mode you can read a virtual machine disk image with no
204 metadata. virt-v2v tries to guess the best default metadata. This
205 is usually adequate but you can get finer control (eg. of memory
206 and vCPUs) by using -i libvirtxml instead. Only guests that use a
207 single disk can be imported this way.
208 -i libvirt
210 Set the input method to libvirt. This is the default.
211 In this mode you have to specify a libvirt guest name or UUID on
213 the command line. You may also specify a libvirt connection URI
214 (see -ic).
215 -i libvirtxml
217 Set the input method to libvirtxml.
218 In this mode you have to pass a libvirt XML file on the command
220 line. This file is read in order to get metadata about the source
221 guest (such as its name, amount of memory), and also to locate the
222 input disks. See "Minimal XML for -i libvirtxml option" below.
223 -i local
225 This is the same as -i disk.
226 -i ova
228 Set the input method to ova.
229 In this mode you can read a VMware ova file. Virt-v2v will read
231 the ova manifest file and check the vmdk volumes for validity
232 (checksums) as well as analyzing the ovf file, and then convert the
233 guest. See virt-v2v-input-vmware(1).
234 -i vmx
236 Set the input method to vmx.
237 In this mode you can read a VMware vmx file directly or over SSH.
239 This is useful when VMware VMs are stored on an NFS server which
240 you can mount directly, or where you have access by SSH to an ESXi
241 hypervisor. See virt-v2v-input-vmware(1).
242 -ic libvirtURI
244 Specify a libvirt connection URI to use when reading the guest.
245 This is only used when -i libvirt.
246 Only local libvirt connections, VMware vCenter connections, or RHEL
248 5 Xen remote connections can be used. Other remote libvirt
249 connections will not work in general.
250 See also virt-v2v-input-vmware(1), virt-v2v-input-xen(1).
252 -if format
254 For -i disk only, this specifies the format of the input disk
255 image. For other input methods you should specify the input format
256 in the metadata.
257 -io OPTION=VALUE
259 Set input option(s) related to the current input mode or transport.
260 To display short help on what options are available you can use:
261 virt-v2v -it vddk -io "?"
263 -io vddk-libdir=LIBDIR
265 Set the VDDK library directory. This directory should contain
266 subdirectories called include, lib64 etc., but do not include lib64
267 actually in the parameter.
268 In most cases this parameter is required when using the -it vddk
270 (VDDK) transport. See virt-v2v-input-vmware(1) for details.
271 -io vddk-thumbprint=xx:xx:xx:...
273 Set the thumbprint of the remote VMware server.
274 This parameter is required when using the -it vddk (VDDK)
276 transport. See virt-v2v-input-vmware(1) for details.
277 -io vddk-config=FILENAME
279 -io vddk-cookie=COOKIE
280 -io vddk-nfchostport=PORT
281 -io vddk-port=PORT
282 -io vddk-snapshot=SNAPSHOT-MOREF
283 -io vddk-transports=MODE:MODE:...
284 When using VDDK mode, these options are passed unmodified to the
285 nbdkit(1) VDDK plugin. Please refer to nbdkit-vddk-plugin(1). Do
286 not use these options unless you know what you are doing. These
287 are all optional.
288 -ip filename
290 Supply a file containing a password to be used when connecting to
291 the target hypervisor. If this is omitted then the input
292 hypervisor may ask for the password interactively. Note the file
293 should contain the whole password, without any trailing newline,
294 and for security the file should have mode 0600 so that others
295 cannot read it.
296 -it ssh
298 When using -i vmx, this enables the ssh transport. See
299 virt-v2v-input-vmware(1).
300 -it vddk
302 Use VMware VDDK as a transport to copy the input disks. See
303 virt-v2v-input-vmware(1). If you use this parameter then you may
304 need to use other -io vddk* options to specify how to connect
305 through VDDK.
306 --key SELECTOR
308 Specify a key for LUKS, to automatically open a LUKS device when
309 using the inspection. "ID" can be either the libguestfs device
310 name, or the UUID of the LUKS device.
311 --key "ID":key:KEY_STRING
313 Use the specified "KEY_STRING" as passphrase.
314 --key "ID":file:FILENAME
316 Read the passphrase from FILENAME.
317 --key "ID":clevis
319 Attempt passphrase-less unlocking for "ID" with Clevis, over
320 the network. Please refer to "ENCRYPTED DISKS" in guestfs(3)
321 for more information on network-bound disk encryption (NBDE).
322 Note that if any such option is present on the command line,
324 QEMU user networking will be automatically enabled for the
325 libguestfs appliance.
326 --keys-from-stdin
328 Read key or passphrase parameters from stdin. The default is to
329 try to read passphrases from the user by opening /dev/tty.
330 If there are multiple encrypted devices then you may need to supply
332 multiple keys on stdin, one per line.
333 Note --keys-from-stdin only applies to keys and passphrases for
335 encrypted devices and partitions, not for passwords used to connect
336 to remote servers.
337 --mac aa:bb:cc:dd:ee:ff:network:out
339 --mac aa:bb:cc:dd:ee:ff:bridge:out
340 Map source NIC MAC address to a network or bridge.
341 See "Networks and bridges" below.
343 --mac aa:bb:cc:dd:ee:ff:ip:ipaddr[,gw[,len[,ns,ns,...]]]
345 Force a particular interface (controlled by its MAC address) to
346 have a static IP address after boot.
347 The fields in the parameter are: "ipaddr" is the IP address. "gw"
349 is the optional gateway IP address. "len" is the subnet mask
350 length (an integer). The final parameters are zero or more
351 nameserver IP addresses.
352 This option can be supplied zero or more times.
354 You only need to use this option for certain broken guests such as
356 Windows which are unable to preserve MAC to static IP address
357 mappings automatically. You don't need to use it if Windows is
358 using DHCP. It is currently ignored for Linux guests since they do
359 not have this problem.
360 --machine-readable
362 --machine-readable=format
363 This option is used to make the output more machine friendly when
364 being parsed by other programs. See "Machine readable output"
365 below.
366 -n in:out
368 -n out
369 --network in:out
370 --network out
371 -b in:out
372 -b out
373 --bridge in:out
374 --bridge out
375 Map network (or bridge) called "in" to network (or bridge) called
376 "out". If no "in:" prefix is given, all other networks (or
377 bridges) are mapped to "out".
378 See "Networks and bridges" below.
380 -o disk
382 This is the same as -o local.
383 -o glance
385 This is a legacy option. You should probably use -o openstack
386 instead.
387 Set the output method to OpenStack Glance. In this mode the
389 converted guest is uploaded to Glance. See
390 virt-v2v-output-openstack(1).
391 -o kubevirt
393 Set the output method to kubevirt. Note the way this mode works is
394 experimental and will change in future.
395 In this mode, the converted guest is written to a local directory
397 specified by -os /dir (the directory must exist). The converted
398 guest’s disks are written to:
399 /dir/name-sda
401 /dir/name-sdb
402 [etc]
403 and guest metadata is created in the associated YAML file:
405 /dir/name.yaml
407 where "name" is the guest name.
409 -o libvirt
411 Set the output method to libvirt. This is the default.
412 In this mode, the converted guest is created as a libvirt guest.
414 You may also specify a libvirt connection URI (see -oc).
415 See virt-v2v-output-local(1).
417 -o local
419 Set the output method to local.
420 In this mode, the converted guest is written to a local directory
422 specified by -os /dir (the directory must exist). The converted
423 guest’s disks are written as:
424 /dir/name-sda
426 /dir/name-sdb
427 [etc]
428 and a libvirt XML file is created containing guest metadata:
430 /dir/name.xml
432 where "name" is the guest name.
434 -o null
436 Set the output method to null.
437 The guest is converted and copied but the results are thrown away
439 and no metadata is written.
440 -o openstack
442 Set the output method to OpenStack. See
443 virt-v2v-output-openstack(1).
444 -o ovirt
446 This is the same as -o rhv.
447 -o ovirt-upload
449 This is the same as -o rhv-upload.
450 -o qemu
452 Set the output method to qemu.
453 This is similar to -o local, except that a shell script is written
455 which you can use to boot the guest in qemu. The converted disks
456 and shell script are written to the directory specified by -os.
457 When using this output mode, you can also specify the -oo qemu-boot
459 option which boots the guest under qemu immediately.
460 -o rhev
462 This is the same as -o rhv.
463 -o rhv
465 Set the output method to rhv.
466 The converted guest is written to a RHV Export Storage Domain. The
468 -os parameter must also be used to specify the location of the
469 Export Storage Domain. Note this does not actually import the
470 guest into RHV. You have to do that manually later using the UI.
471 See virt-v2v-output-rhv(1).
473 -o rhv-upload
475 Set the output method to rhv-upload.
476 The converted guest is written directly to a RHV Data Domain. This
478 is a faster method than -o rhv, but requires oVirt or RHV ≥ 4.2.
479 See virt-v2v-output-rhv(1).
481 -o vdsm
483 Set the output method to vdsm.
484 This mode is similar to -o rhv, but the full path to the data
486 domain must be given:
487 /rhv/data-center/<data-center-uuid>/<data-domain-uuid>. This mode
488 is only used when virt-v2v runs under VDSM control.
489 -oa sparse
491 -oa preallocated
492 Set the output file allocation mode. The default is "sparse".
493 -oc URI
495 Specify a connection URI to use when writing the converted guest.
496 For -o libvirt this is the libvirt URI. Only local libvirt
498 connections can be used. Remote libvirt connections will not work.
499 See virt-v2v-output-local(1) for further information.
500 -of format
502 When converting the guest, convert the disks to the given format.
503 If not specified, then the input format is used.
505 -on name
507 Rename the guest when converting it. If this option is not used
508 then the output name is the same as the input name.
509 -oo OPTION=VALUE
511 Set output option(s) related to the current output mode. To
512 display short help on what options are available you can use:
513 virt-v2v -o rhv-upload -oo "?"
515 -oo compressed
517 For outputs which support qcow2 format (-of qcow2), this writes a
518 compressed qcow2 file. It is the equivalent to the -c option of
519 qemu-img(1).
520 -oo guest-id="ID"
522 For -o openstack (virt-v2v-output-openstack(1)) only, set a guest
523 ID which is saved on each Cinder volume in the "virt_v2v_guest_id"
524 volume property.
525 -oo qemu-boot
527 When using -o qemu only, this boots the guest immediately after
528 virt-v2v finishes.
529 -oo verify-server-certificate
531 -oo verify-server-certificate="true|false"
532 For -o openstack (virt-v2v-output-openstack(1)) only, this can be
533 used to disable SSL certification validation when connecting to
534 OpenStack by specifying -oo verify-server-certificate=false.
535 -oo os-*=*
537 For -o openstack (virt-v2v-output-openstack(1)) only, set optional
538 OpenStack authentication. For example -oo os-username=NAME is
539 equivalent to "openstack --os-username=NAME".
540 -oo rhv-cafile=ca.pem
542 For -o rhv-upload (virt-v2v-output-rhv(1)) only, the ca.pem file
543 (Certificate Authority), copied from /etc/pki/ovirt-engine/ca.pem
544 on the oVirt engine.
545 -oo rhv-cluster="CLUSTERNAME"
547 For -o rhv-upload (virt-v2v-output-rhv(1)) only, set the RHV
548 Cluster Name. If not given it uses "Default".
549 -oo rhv-proxy
551 For -o rhv-upload (virt-v2v-output-rhv(1)) only, proxy the upload
552 through oVirt Engine. This is slower than uploading directly to
553 the oVirt node but may be necessary if you do not have direct
554 network access to the nodes.
555 -oo rhv-verifypeer
557 For -o rhv-upload (virt-v2v-output-rhv(1)) only, verify the
558 oVirt/RHV server’s identity by checking the server‘s certificate
559 against the Certificate Authority.
560 -oo server-id="NAME|UUID"
562 For -o openstack (virt-v2v-output-openstack(1)) only, set the name
563 of the conversion appliance where virt-v2v is running.
564 -oo vdsm-compat=0.10
566 -oo vdsm-compat=1.1
567 If -o vdsm and the output format is qcow2, then we add the qcow2
568 compat=0.10 option to the output file for compatibility with RHEL 6
569 (see https://bugzilla.redhat.com/1145582).
570 If -oo vdsm-compat=1.1 is used then modern qcow2 (compat=1.1) files
572 are generated instead.
573 Currently -oo vdsm-compat=0.10 is the default, but this will change
575 to -oo vdsm-compat=1.1 in a future version of virt-v2v (when we can
576 assume that everyone is using a modern version of qemu).
577 Note this option only affects -o vdsm output. All other output
579 modes (including -o rhv) generate modern qcow2 compat=1.1 files,
580 always.
581 If this option is available, then "vdsm-compat-option" will appear
583 in the --machine-readable output.
584 -oo vdsm-image-uuid=UUID
586 -oo vdsm-vol-uuid=UUID
587 -oo vdsm-vm-uuid=UUID
588 -oo vdsm-ovf-output=DIR
589 Normally the RHV output mode chooses random UUIDs for the target
590 guest. However VDSM needs to control the UUIDs and passes these
591 parameters when virt-v2v runs under VDSM control. The parameters
592 control:
593 • the image directory of each guest disk (-oo vdsm-image-uuid)
595 (this option is passed once for each guest disk)
596 • UUIDs for each guest disk (-oo vdsm-vol-uuid) (this option is
598 passed once for each guest disk)
599 • the OVF file name (-oo vdsm-vm-uuid).
601 • the OVF output directory (default current directory) (-oo vdsm-
603 ovf-output).
604 The format of UUIDs is: "12345678-1234-1234-1234-123456789abc"
606 (each hex digit can be "0-9" or "a-f"), conforming to OSF DCE 1.1.
607 These options can only be used with -o vdsm.
609 -oo vdsm-ovf-flavour=flavour
611 This option controls the format of the OVF generated at the end of
612 conversion. Currently there are two possible flavours:
613 rhvexp
615 The OVF format used in RHV export storage domain.
616 ovirt
618 The OVF format understood by oVirt REST API.
619 For backward compatibility the default is rhvexp, but this may
621 change in the future.
622 -op file
624 Supply a file containing a password to be used when connecting to
625 the target hypervisor. Note the file should contain the whole
626 password, without any trailing newline, and for security the file
627 should have mode 0600 so that others cannot read it.
628 -os storage
630 The location of the storage for the converted guest.
631 For -o libvirt, this is a libvirt directory pool (see
633 "virsh pool-list") or pool UUID.
634 For -o local and -o qemu, this is a directory name. The directory
636 must exist.
637 For -o rhv-upload, this is the name of the destination Storage
639 Domain.
640 For -o openstack, this is the optional Cinder volume type.
642 For -o rhv, this can be an NFS path of the Export Storage Domain of
644 the form "<host>:<path>", eg:
645 rhv-storage.example.com:/rhv/export
647 The NFS export must be mountable and writable by the user and host
649 running virt-v2v, since the virt-v2v program has to actually mount
650 it when it runs. So you probably have to run virt-v2v as "root".
651 Or: You can mount the Export Storage Domain yourself, and point -os
653 to the mountpoint. Note that virt-v2v will still need to write to
654 this remote directory, so virt-v2v will still need to run as
655 "root".
656 You will get an error if virt-v2v is unable to mount/write to the
658 Export Storage Domain.
659 --print-source
661 Print information about the source guest and stop. This option is
662 useful when you are setting up network and bridge maps. See
663 "Networks and bridges".
664 --qemu-boot
666 This is the same as -oo qemu-boot.
667 -q
669 --quiet
670 This disables progress bars and other unnecessary output.
671 --root ask
673 --root single
674 --root first
675 --root /dev/sdX
676 --root /dev/VG/LV
677 Choose the root filesystem to be converted.
678 In the case where the virtual machine is dual-boot or multi-boot,
680 or where the VM has other filesystems that look like operating
681 systems, this option can be used to select the root filesystem
682 (a.k.a. "C:" drive or /) of the operating system that is to be
683 converted. The Windows Recovery Console, certain attached DVD
684 drives, and bugs in libguestfs inspection heuristics, can make a
685 guest look like a multi-boot operating system.
686 The default in virt-v2v ≤ 0.7.1 was --root single, which causes
688 virt-v2v to die if a multi-boot operating system is found.
689 Since virt-v2v ≥ 0.7.2 the default is now --root ask: If the VM is
691 found to be multi-boot, then virt-v2v will stop and list the
692 possible root filesystems and ask the user which to use. This
693 requires that virt-v2v is run interactively.
694 --root first means to choose the first root device in the case of a
696 multi-boot operating system. Since this is a heuristic, it may
697 sometimes choose the wrong one.
698 You can also name a specific root device, eg. --root /dev/sda2
700 would mean to use the second partition on the first hard drive. If
701 the named root device does not exist or was not detected as a root
702 device, then virt-v2v will fail.
703 Note that there is a bug in grub which prevents it from
705 successfully booting a multiboot system if virtio is enabled. Grub
706 is only able to boot an operating system from the first virtio
707 disk. Specifically, /boot must be on the first virtio disk, and it
708 cannot chainload an OS which is not in the first virtio disk.
709 -v
711 --verbose
712 Enable verbose messages for debugging.
713 -V
715 --version
716 Display version number and exit.
717 --wrap
719 Wrap error, warning, and informative messages. This is the default
720 when the output is a tty. If the output of the program is
721 redirected to a file, wrapping is disabled unless you use this
722 option.
723 -x Enable tracing of libguestfs API calls.
725
727 Xen paravirtualized guests
728 Older versions of virt-v2v could turn a Xen paravirtualized (PV) guest
729 into a KVM guest by installing a new kernel. This version of virt-v2v
730 does not attempt to install any new kernels. Instead it will give you
731 an error if there are only Xen PV kernels available.
732 Therefore before conversion you should check that a regular kernel is
734 installed. For some older Linux distributions, this means installing a
735 kernel from the table below:
736 RHEL 3 (Does not apply, as there was no Xen PV kernel)
738 RHEL 4 i686 with > 10GB of RAM: install 'kernel-hugemem'
740 i686 SMP: install 'kernel-smp'
741 other i686: install 'kernel'
742 x86-64 SMP with > 8 CPUs: install 'kernel-largesmp'
743 x86-64 SMP: install 'kernel-smp'
744 other x86-64: install 'kernel'
745 RHEL 5 i686: install 'kernel-PAE'
747 x86-64: install 'kernel'
748 SLES 10 i586 with > 10GB of RAM: install 'kernel-bigsmp'
750 i586 SMP: install 'kernel-smp'
751 other i586: install 'kernel-default'
752 x86-64 SMP: install 'kernel-smp'
753 other x86-64: install 'kernel-default'
754 SLES 11+ i586: install 'kernel-pae'
756 x86-64: install 'kernel-default'
757 Windows (Does not apply, as there is no Xen PV Windows kernel)
759 Enabling virtio
761 "Virtio" is the name for a set of drivers which make disk (block
762 device), network and other guest operations work much faster on KVM.
763 Older versions of virt-v2v could install these drivers for certain
765 Linux guests. This version of virt-v2v does not attempt to install new
766 Linux kernels or drivers, but will warn you if they are not installed
767 already.
768 In order to enable virtio, and hence improve performance of the guest
770 after conversion, you should ensure that the minimum versions of
771 packages are installed before conversion, by consulting the table
772 below.
773 RHEL 3 No virtio drivers are available
775 RHEL 4 kernel >= 2.5.9-89.EL
777 lvm2 >= 2.02.42-5.el4
778 device-mapper >= 1.02.28-2.el4
779 selinux-policy-targeted >= 1.17.30-2.152.el4
780 policycoreutils >= 1.18.1-4.13
781 RHEL 5 kernel >= 2.6.18-128.el5
783 lvm2 >= 2.02.40-6.el5
784 selinux-policy-targeted >= 2.4.6-203.el5
785 RHEL 6+ All versions support virtio
787 Fedora All versions support virtio
789 SLES 11+ All versions support virtio
791 SLES 10 kernel >= 2.6.16.60-0.85.1
793 OpenSUSE 11+ All versions support virtio
795 OpenSUSE 10 kernel >= 2.6.25.5-1.1
797 Debian 6+ All versions support virtio
799 Ubuntu 10.04+ All versions support virtio
801 Windows Drivers are installed from the ISO or directory pointed
803 to by the "VIRTIO_WIN" environment variable if present.
804 If the "VIRTIO_WIN" environment variable is absent
805 (which is the recommended setting), then libosinfo is
806 consulted first, for driver files that are locally
807 available on the conversion host.
808 RHEL 4: SELinux relabel appears to hang forever
810 In RHEL ≤ 4.7 there was a bug which causes SELinux relabelling to
811 appear to hang forever at:
812 *** Warning -- SELinux relabel is required. ***
814 *** Disabling security enforcement. ***
815 *** Relabeling could take a very long time, ***
816 *** depending on file system size. ***
817 In reality it is waiting for you to press a key (but there is no visual
819 indication of this). You can either hit the "[Return]" key, at which
820 point the guest will finish relabelling and reboot, or you can install
821 policycoreutils ≥ 1.18.1-4.13 before starting the v2v conversion. See
822 also https://bugzilla.redhat.com/show_bug.cgi?id=244636
823 Debian and Ubuntu
825 "warning: could not determine a way to update the configuration of
826 Grub2"
827 Currently, virt-v2v has no way to set the default kernel in Debian and
829 Ubuntu guests using GRUB 2 as bootloader. This means that virt-v2v
830 will not change the default kernel used for booting, even in case it is
831 not the best kernel available on the guest. A recommended procedure
832 is, before using virt-v2v, to check that the boot kernel is the best
833 kernel available in the guest (for example by making sure the guest is
834 up-to-date).
835 "vsyscall attempted with vsyscall=none"
837 When run on a recent Debian host virt-v2v may fail to convert guests
839 which were created before 2013. In the debugging output you will see a
840 crash message similar to:
841 vsyscall attempted with vsyscall=none ip:...
843 segfault at ...
844 This is caused because Debian removed support for running old binaries
846 which used the legacy vsyscall page to call into the kernel.
847 You can work around this problem by running this command before running
849 virt-v2v:
850 export LIBGUESTFS_APPEND="vsyscall=emulate"
852 For more information, see https://bugzilla.redhat.com/1592061
854 Windows
856 System disk on a Dynamic Disk is not supported
857 If the Windows system disk (the drive containing "\windows") is located
859 on a Dynamic Disk then it cannot be converted. Data disks — that is,
860 disks which are part of the guest but do not contain parts of the
861 Windows operating system — may be Dynamic Disks.
862 See https://bugzilla.redhat.com/2140548.
864 Windows ≥ 8 Fast Startup is incompatible with virt-v2v
866 Guests which use the Windows ≥ 8 "Fast Startup" feature (or guests
868 which are hibernated) cannot be converted with virt-v2v. You will see
869 an error:
870 virt-v2v: error: unable to mount the disk image for writing. This has
872 probably happened because Windows Hibernation or Fast Restart is being
873 used in this guest. You have to disable this (in the guest) in order
874 to use virt-v2v.
875 As the message says, you need to boot the guest and disable the "Fast
877 Startup" feature (Control Panel → Power Options → Choose what the power
878 buttons do → Change settings that are currently unavailable → Turn on
879 fast startup), and shut down the guest, and then you will be able to
880 convert it.
881 For more information, see: "WINDOWS HIBERNATION AND WINDOWS 8 FAST
883 STARTUP" in guestfs(3).
884 Boot failure: 0x0000007B
886 This boot failure is caused by Windows being unable to find or load the
888 right disk driver (eg. viostor.sys). If you experience this error,
889 here are some things to check:
890 • First ensure that the guest boots on the source hypervisor before
892 conversion.
893 • Check you have the Windows virtio drivers available in
895 /usr/share/virtio-win, and that virt-v2v did not print any warning
896 about not being able to install virtio drivers.
897 On Red Hat Enterprise Linux 7, you will need to install the signed
899 drivers available in the "virtio-win" package. If you do not have
900 access to the signed drivers, then you will probably need to
901 disable driver signing in the boot menus.
902 • Check that you are presenting a virtio-blk interface (not virtio-
904 scsi and not ide) to the guest. On the qemu/KVM command line you
905 should see something similar to this:
906 ... -drive file=windows-sda,if=virtio ...
908 In libvirt XML, you should see:
910 <target dev='vda' bus='virtio'/>
912 • Check that Windows Group Policy does not prevent the driver from
914 being installed or used. Try deleting Windows Group Policy before
915 conversion.
916 • Check there is no anti-virus or other software which implements
918 Group Policy-like prohibitions on installing or using new drivers.
919 • Enable boot debugging and check the viostor.sys driver is being
921 loaded.
922 OpenStack and Windows reactivation
924 OpenStack does not offer stable device / PCI addresses to guests.
926 Every time it creates or starts a guest, it regenerates the libvirt XML
927 for that guest from scratch. The libvirt XML will have no <address>
928 fields. Libvirt will then assign addresses to devices, in a
929 predictable manner. Addresses may change if any of the following are
930 true:
931 • A new disk or network device has been added or removed from the
933 guest.
934 • The version of OpenStack or (possibly) libvirt has changed.
936 Because Windows does not like "hardware" changes of this kind, it may
938 trigger Windows reactivation.
939 This can also prevent booting with a 7B error [see previous section] if
941 the guest has group policy containing "Device Installation
942 Restrictions".
943 Support for SHA-2 certificates in Windows 7 and Windows Server 2008 R2
945 Later versions of the Windows virtio drivers are signed using SHA-2
947 certificates (instead of SHA-1). The original shipping Windows 7 and
948 Windows Server 2008 R2 did not understand SHA-2 certificates and so the
949 Windows virtio drivers will not install properly.
950 To fix this you must apply SHA-2 Code Signing Support from:
952 https://docs.microsoft.com/en-us/security-updates/SecurityAdvisories/2015/3033929
953 before converting the guest.
954 For further information see:
956 https://bugzilla.redhat.com/show_bug.cgi?id=1624878
957 Networks and bridges
959 Guests are usually connected to one or more networks, and when
960 converted to the target hypervisor you usually want to reconnect those
961 networks at the destination. The options --network, --bridge and --mac
962 allow you to do that.
963 If you are unsure of what networks and bridges are in use on the source
965 hypervisor, then you can examine the source metadata (libvirt XML,
966 vCenter information, etc.). Or you can run virt-v2v with the
967 --print-source option which causes virt-v2v to print out the
968 information it has about the guest on the source and then exit.
969 In the --print-source output you will see a section showing the guest’s
971 Network Interface Cards (NICs):
972 $ virt-v2v [-i ...] --print-source name
974 [...]
975 NICs:
976 Network "default" mac: 52:54:00:d0:cf:0e
977 Bridges are special classes of network devices which are attached to a
979 named external network on the source hypervisor, for example:
980 $ virt-v2v [-i ...] --print-source name
982 [...]
983 NICs:
984 Bridge "br0"
985 To map a specific source bridge to a target network, for example "br0"
987 on the source to "ovirtmgmt" on the target, use:
988 virt-v2v [...] --bridge br0:ovirtmgmt
990 To map every bridge to a target network, use:
992 virt-v2v [...] --bridge ovirtmgmt
994 Fine-grained mapping of guest NICs
996 The --mac option gives you more control over the mapping, letting you
998 map single NICs to either networks or bridges on the target. For
999 example a source guest with two NICs could map them individually to two
1000 networks called "mgmt" and "clientdata" like this:
1001 $ virt-v2v [...] \
1003 --mac 52:54:00:d0:cf:0e:network:mgmt \
1004 --mac 52:54:00:d0:cf:0f:network:clientdata
1005 Note that virt-v2v does not have the ability to change a guest’s MAC
1007 address. The MAC address is part of the guest metadata and must remain
1008 the same on source and target hypervisors. Most guests will use the
1009 MAC address to set up persistent associations between NICs and internal
1010 names (like "eth0"), with firewall settings, or even for other purposes
1011 like software licensing.
1012 Resource requirements
1014 Network
1015 The most important resource for virt-v2v appears to be network
1017 bandwidth. Virt-v2v should be able to copy guest data at gigabit
1018 ethernet speeds or greater.
1019 Ensure that the network connections between servers (conversion server,
1021 NFS server, vCenter, Xen) are as fast and as low latency as possible.
1022 Disk space
1024 Virt-v2v places potentially large temporary files in $VIRT_V2V_TMPDIR
1026 (usually /var/tmp, see also "ENVIRONMENT VARIBLES" below). Using tmpfs
1027 is a bad idea.
1028 For each guest disk, an overlay is stored temporarily. This stores the
1030 changes made during conversion, and is used as a cache. The overlays
1031 are not particularly large - tens or low hundreds of megabytes per disk
1032 is typical. In addition to the overlay(s), input and output methods
1033 may use disk space, as outlined in the table below.
1034 -i ova
1036 This temporarily places a full copy of the uncompressed source
1037 disks in $VIRT_V2V_TMPDIR (or /var/tmp).
1038 -o glance
1040 This temporarily places a full copy of the output disks in
1041 $VIRT_V2V_TMPDIR (or /var/tmp).
1042 -o local
1044 -o qemu
1045 You must ensure there is sufficient space in the output directory
1046 for the converted guest.
1047 See also "Minimum free space check in the host" below.
1049 VMware vCenter resources
1051 Copying from VMware vCenter is currently quite slow, but we believe
1053 this to be an issue with VMware. Ensuring the VMware ESXi hypervisor
1054 and vCenter are running on fast hardware with plenty of memory should
1055 alleviate this.
1056 Compute power and RAM
1058 Virt-v2v is not especially compute or RAM intensive. If you are
1060 running many parallel conversions, then you may consider allocating one
1061 CPU core and 2 GB of RAM per running instance.
1062 Virt-v2v can be run in a virtual machine.
1064 Trimming
1066 Virt-v2v attempts to optimize the speed of conversion by ignoring guest
1068 filesystem data which is not used. This would include unused
1069 filesystem blocks, blocks containing zeroes, and deleted files.
1070 To do this, virt-v2v issues a non-destructive fstrim(8) operation. As
1072 this happens to an overlay placed over the guest data, it does not
1073 affect the source in any way.
1074 If this fstrim operation fails, you will see a warning, but virt-v2v
1076 will continue anyway. It may run more slowly (in some cases much more
1077 slowly), because it is copying the unused parts of the disk.
1078 Unfortunately support for fstrim is not universal, and it also depends
1080 on specific details of the filesystem, partition alignment, and backing
1081 storage. As an example, NTFS filesystems cannot be fstrimmed if they
1082 occupy a partition which is not aligned to the underlying storage.
1083 That was the default on Windows before Vista. As another example, VFAT
1084 filesystems (used by UEFI guests) cannot be trimmed at all.
1085 fstrim support in the Linux kernel is improving gradually, so over time
1087 some of these restrictions will be lifted and virt-v2v will work
1088 faster.
1089 Post-conversion tasks
1091 Guest network configuration
1092 Virt-v2v cannot currently reconfigure a guest’s network configuration.
1094 If the converted guest is not connected to the same subnet as the
1095 source, its network configuration may have to be updated. See also
1096 virt-customize(1).
1097 Converting a Windows guest
1099 When converting a Windows guests, the conversion process is split into
1101 two stages:
1102 1. Offline conversion.
1104 2. First boot.
1106 The guest will be bootable after the offline conversion stage, but will
1108 not yet have all necessary drivers installed to work correctly. These
1109 will be installed automatically the first time the guest boots.
1110 N.B. Take care not to interrupt the automatic driver installation
1112 process when logging in to the guest for the first time, as this may
1113 prevent the guest from subsequently booting correctly.
1114 Free space for conversion
1116 Free space in the guest
1117 Virt-v2v checks there is sufficient free space in the guest filesystem
1119 to perform the conversion. Currently it checks:
1120 Linux root filesystem
1122 Minimum free space: 100 MB
1123 Linux /boot
1125 Minimum free space: 50 MB
1126 This is because we need to build a new initramfs for some
1128 Enterprise Linux conversions.
1129 Windows "C:" drive
1131 Minimum free space: 100 MB
1132 We may have to copy in many virtio drivers and guest agents.
1134 Any other mountable filesystem
1136 Minimum free space: 10 MB
1137 In addition to the actual free space, each filesystem is required to
1139 have at least 100 available inodes.
1140 Minimum free space check in the host
1142 You must have sufficient free space in the host directory used to store
1144 large temporary overlays. To find out which directory this is, use:
1145 $ df -h "`guestfish get-cachedir`"
1147 Filesystem Size Used Avail Use% Mounted on
1148 /dev/mapper/root 50G 40G 6.8G 86% /
1149 and look under the "Avail" column. Virt-v2v will refuse to do the
1151 conversion at all unless at least 1GB is available there. You can
1152 change the directory that virt-v2v uses by setting $VIRT_V2V_TMPDIR.
1153 See also "Resource requirements" above and "ENVIRONMENT VARIABLES"
1155 below.
1156 Running virt-v2v as root or non-root
1158 Nothing in virt-v2v inherently needs root access, and it will run just
1159 fine as a non-root user. However, certain external features may
1160 require either root or a special user:
1161 Mounting the Export Storage Domain
1163 When using -o rhv -os server:/esd virt-v2v has to have sufficient
1164 privileges to NFS mount the Export Storage Domain from "server".
1165 You can avoid needing root here by mounting it yourself before
1167 running virt-v2v, and passing -os /mountpoint instead, but first of
1168 all read the next section ...
1169 Writing to the Export Storage Domain as 36:36
1171 RHV-M cannot read files and directories from the Export Storage
1172 Domain unless they have UID:GID 36:36. You will see VM import
1173 problems if the UID:GID is not correct.
1174 When you run virt-v2v -o rhv as root, virt-v2v attempts to create
1176 files and directories with the correct ownership. If you run
1177 virt-v2v as non-root, it will probably still work, but you will
1178 need to manually change ownership after virt-v2v has finished.
1179 Writing to libvirt
1181 When using -o libvirt, you may need to run virt-v2v as root so that
1182 it can write to the libvirt system instance (ie. "qemu:///system")
1183 and to the default location for disk images (usually
1184 /var/lib/libvirt/images).
1185 You can avoid this by setting up libvirt connection authentication,
1187 see http://libvirt.org/auth.html. Alternatively, use -oc
1188 qemu:///session, which will write to your per-user libvirt
1189 instance.
1190 Writing to Openstack
1192 Because of how Cinder volumes are presented as /dev block devices,
1193 using -o openstack normally requires that virt-v2v is run as root.
1194 Writing to Glance
1196 This does not need root (in fact it probably won’t work), but may
1197 require either a special user and/or for you to source a script
1198 that sets authentication environment variables. Consult the Glance
1199 documentation.
1200 Writing to block devices
1202 This normally requires root. See the next section.
1203 Writing to block devices
1205 Some output modes write to local files. In general these modes also
1206 let you write to block devices, but before you run virt-v2v you may
1207 have to arrange for symbolic links to the desired block devices in the
1208 output directory.
1209 For example if using -o local -os /dir then virt-v2v would normally
1211 create files called:
1212 /dir/name-sda # first disk
1214 /dir/name-sdb # second disk
1215 ...
1216 /dir/name.xml # metadata
1217 If you wish the disks to be written to block devices then you would
1219 need to create /dir/name-sda (etc) as symlinks to the block devices:
1220 # lvcreate -L 10G -n VolumeForDiskA VG
1222 # lvcreate -L 6G -n VolumeForDiskB VG
1223 # ln -sf /dev/VG/VolumeForDiskA /dir/name-sda
1224 # ln -sf /dev/VG/VolumeForDiskB /dir/name-sdb
1225 Note that you must precreate the correct number of block devices of the
1227 correct size. Typically -of raw has to be used too, but other formats
1228 such as qcow2 can be useful occasionally so virt-v2v does not force you
1229 to use raw on block devices.
1230 Minimal XML for -i libvirtxml option
1232 When using the -i libvirtxml option, you have to supply some libvirt
1233 XML. Writing this from scratch is hard, so the template below is
1234 helpful.
1235 Note this should only be used for testing and/or where you know what
1237 you're doing! If you have libvirt metadata for the guest, always use
1238 that instead.
1239 <domain type='kvm'>
1241 <name> NAME </name>
1242 <memory>1048576</memory>
1243 <vcpu>2</vcpu>
1244 <os>
1245 <type>hvm</type>
1246 <boot dev='hd'/>
1247 </os>
1248 <features>
1249 <acpi/>
1250 <apic/>
1251 <pae/>
1252 </features>
1253 <devices>
1254 <disk type='file' device='disk'>
1255 <driver name='qemu' type='raw'/>
1256 <source file='/path/to/disk/image'/>
1257 <target dev='hda' bus='ide'/>
1258 </disk>
1259 <interface type='network'>
1260 <mac address='52:54:00:01:02:03'/>
1261 <source network='default'/>
1262 <model type='rtl8139'/>
1263 </interface>
1264 </devices>
1265 </domain>
1266 Machine readable output
1268 The --machine-readable option can be used to make the output more
1269 machine friendly, which is useful when calling virt-v2v from other
1270 programs, GUIs etc.
1271 There are two ways to use this option.
1273 Firstly use the option on its own to query the capabilities of the
1275 virt-v2v binary. Typical output looks like this:
1276 $ virt-v2v --machine-readable
1278 virt-v2v
1279 libguestfs-rewrite
1280 colours-option
1281 vdsm-compat-option
1282 input:disk
1283 [...]
1284 output:local
1285 [...]
1286 convert:linux
1287 convert:windows
1288 A list of features is printed, one per line, and the program exits with
1290 status 0.
1291 The "input:" and "output:" features refer to -i and -o (input and
1293 output mode) options supported by this binary. The "convert:" features
1294 refer to guest types that this binary knows how to convert.
1295 Secondly use the option in conjunction with other options to make the
1297 regular program output more machine friendly.
1298 At the moment this means:
1300 1. Progress bar messages can be parsed from stdout by looking for this
1302 regular expression:
1303 ^[0-9]+/[0-9]+$
1305 2. The calling program should treat messages sent to stdout (except
1307 for progress bar messages) as status messages. They can be logged
1308 and/or displayed to the user.
1309 3. The calling program should treat messages sent to stderr as error
1311 messages. In addition, virt-v2v exits with a non-zero status code
1312 if there was a fatal error.
1313 Virt-v2v ≤ 0.9.1 did not support the --machine-readable option at all.
1315 The option was added when virt-v2v was rewritten in 2014.
1316 It is possible to specify a format string for controlling the output;
1318 see "ADVANCED MACHINE READABLE OUTPUT" in guestfs(3).
1319
1321 /usr/share/virtio-win
1322 (Optional)
1323 If this directory is present, then virtio drivers for Windows
1325 guests will be found from this directory and installed in the guest
1326 during conversion.
1327
1329 "VIRT_V2V_TMPDIR"
1330 "LIBGUESTFS_CACHEDIR"
1331 Location of the temporary directory used for the potentially large
1332 temporary overlay file. If neither environment variable is set
1333 then /var/tmp is used.
1334 To reliably ensure large temporary files are cleaned up (for
1336 example in case virt-v2v crashes) you should create a randomly
1337 named directory under /var/tmp, set "VIRT_V2V_TMPDIR" to point to
1338 this directory, then when virt-v2v exits remove the directory.
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 pnp_wait.exe
1361 (Recommended when doing conversions of Windows guests)
1362 This tool waits for newly installed Windows devices to become
1364 available before trying to configure them, for example to set
1365 network configuration. It is part of the RHSrvAny project.
1366 pvvxsvc.exe
1368 This is a Windows binary shipped with SUSE VMDP, used to
1369 install a "firstboot" script in Windows guests. It is an
1370 alternative to RHSrvAny.
1371 "VIRTIO_WIN"
1373 This is an override for where virtio drivers for Windows are
1374 searched for. It can be a directory or point to virtio-win.iso (CD
1375 ROM image containing drivers).
1376 If unset, then we look for drivers via whichever of these methods
1378 succeeds first:
1379 "osinfo-db"
1381 Load osinfo data from the default paths, and attempt to find
1382 drivers via libosinfo lookup. This is the preferred method.
1383 /usr/share/virtio-win/virtio-win.iso
1385 The ISO containing virtio drivers for Windows.
1386 /usr/share/virtio-win
1388 The exploded tree of virtio drivers for Windows. This is
1389 usually incomplete, hence the least preferred method.
1390 See "Enabling virtio".
1392 For other environment variables, see "ENVIRONMENT VARIABLES" in
1394 guestfs(3).
1395
1397 engine-image-uploader(8)
1398 Variously called "engine-image-uploader", "ovirt-image-uploader" or
1399 "rhevm-image-uploader", this tool allows you to copy a guest from
1400 one oVirt or RHV Export Storage Domain to another. It only permits
1401 importing a guest that was previously exported from another
1402 oVirt/RHV instance.
1403 import-to-ovirt.pl
1405 This script can be used to import guests that already run on KVM to
1406 oVirt or RHV. For more information, see this blog posting by the
1407 author of virt-v2v:
1408 https://rwmj.wordpress.com/2015/09/18/importing-kvm-guests-to-ovirt-or-rhev/#content
1410
1412 virt-p2v(1), virt-v2v-inspector(1), virt-v2v-in-place(1),
1413 virt-customize(1), virt-df(1), virt-filesystems(1), virt-sparsify(1),
1414 virt-sysprep(1), guestfs(3), guestfish(1), qemu-img(1),
1415 engine-image-uploader(8), import-to-ovirt.pl, nbdkit(1),
1416 nbdkit-vddk-plugin(1), http://libguestfs.org/.
1417
1419 Matthew Booth
1420 Cédric Bosdonnat
1422 Laszlo Ersek
1424 Tomáš Golembiovský
1426 Shahar Havivi
1428 Richard W.M. Jones
1430 Roman Kagan
1432 Mike Latimer
1434 Nir Soffer
1436 Pino Toscano
1438 Xiaodai Wang
1440 Ming Xie
1442 Tingting Zheng
1444
1446 Copyright (C) 2009-2022 Red Hat Inc.
1447
1449 This program is free software; you can redistribute it and/or modify it
1450 under the terms of the GNU General Public License as published by the
1451 Free Software Foundation; either version 2 of the License, or (at your
1452 option) any later version.
1453 This program is distributed in the hope that it will be useful, but
1455 WITHOUT ANY WARRANTY; without even the implied warranty of
1456 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
1457 General Public License for more details.
1458 You should have received a copy of the GNU General Public License along
1460 with this program; if not, write to the Free Software Foundation, Inc.,
1461 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
1462
1464 To get a list of bugs against libguestfs, use this link:
1465 https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools
1466 To report a new bug against libguestfs, use this link:
1468 https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Virtualization+Tools
1469 When reporting a bug, please supply:
1471 • The version of libguestfs.
1473 • Where you got libguestfs (eg. which Linux distro, compiled from
1475 source, etc)
1476 • Describe the bug accurately and give a way to reproduce it.
1478 • Run libguestfs-test-tool(1) and paste the complete, unedited output
1480 into the bug report.
1481virt-v2v-2.2.0 2023-01-10 virt-v2v(1)