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
62 Convert from VMware vCenter server to local libvirt
63 You have a VMware vCenter server called "vcenter.example.com", a
64 datacenter called "Datacenter", and an ESXi hypervisor called "esxi".
65 You want to convert a guest called "vmware_guest" to run locally under
66 libvirt.
67 virt-v2v -ic vpx://vcenter.example.com/Datacenter/esxi vmware_guest
69 In this case you will most likely have to run virt-v2v as "root", since
71 it needs to talk to the system libvirt daemon and copy the guest disks
72 to /var/lib/libvirt/images.
73 For more information see virt-v2v-input-vmware(1).
75 Convert from VMware to RHV/oVirt
77 This is the same as the previous example, except you want to send the
78 guest to a RHV Data Domain using the RHV REST API. Guest network
79 interface(s) are connected to the target network called "ovirtmgmt".
80 virt-v2v -ic vpx://vcenter.example.com/Datacenter/esxi vmware_guest \
82 -o rhv-upload -oc https://ovirt-engine.example.com/ovirt-engine/api \
83 -os ovirt-data -op /tmp/ovirt-admin-password -of raw \
84 -oo rhv-cafile=/tmp/ca.pem -oo rhv-direct \
85 --bridge ovirtmgmt
86 In this case the host running virt-v2v acts as a conversion server.
88 For more information see virt-v2v-output-rhv(1).
90 Convert from ESXi hypervisor over SSH to local libvirt
92 You have an ESXi hypervisor called "esxi.example.com" with SSH access
93 enabled. You want to convert from VMFS storage on that server to a
94 local file.
95 virt-v2v \
97 -i vmx -it ssh \
98 "ssh://root@esxi.example.com/vmfs/volumes/datastore1/guest/guest.vmx" \
99 -o local -os /var/tmp
100 The guest must not be running. Virt-v2v would not need to be run as
102 root in this case.
103 For more information about converting from VMX files see
105 virt-v2v-input-vmware(1).
106 Convert disk image to OpenStack
108 Given a disk image from another hypervisor that you want to convert to
109 run on OpenStack (only KVM-based OpenStack is supported), you can run
110 virt-v2v inside an OpenStack VM (called "v2v-vm" below), and do:
111 virt-v2v -i disk disk.img -o openstack -oo server-id=v2v-vm
113 See virt-v2v-output-openstack(1).
115 Convert disk image to disk image
117 Given a disk image from another hypervisor that you want to convert to
118 run on KVM, you have two options. The simplest way is to try:
119 virt-v2v -i disk disk.img -o local -os /var/tmp
121 where virt-v2v guesses everything about the input disk.img and (in this
123 case) writes the converted result to /var/tmp.
124 A more complex method is to write some libvirt XML describing the input
126 guest (if you can get the source hypervisor to provide you with libvirt
127 XML, then so much the better). You can then do:
128 virt-v2v -i libvirtxml guest-domain.xml -o local -os /var/tmp
130 Since guest-domain.xml contains the path(s) to the guest disk image(s)
132 you do not need to specify the name of the disk image on the command
133 line.
134 To convert a local disk image and immediately boot it in local qemu,
136 do:
137 virt-v2v -i disk disk.img -o qemu -os /var/tmp -oo qemu-boot
139
141 --help
142 Display help.
143 --bandwidth bps
145 --bandwidth-file filename
146 Some input methods are able to limit the network bandwidth they
147 will use statically or dynamically. In the first variant this sets
148 the bandwidth limit statically in bits per second. Formats like
149 "10M" may be used (meaning 10 megabits per second).
150 In the second variant the bandwidth is limited dynamically from the
152 content of the file (also in bits per second, in the same formats
153 supported by the first variant). You may use both parameters
154 together, meaning: first limit to a static rate, then you can
155 create the file while virt-v2v is running to adjust the rate
156 dynamically.
157 This is only supported for:
159 • input from Xen
161 • input from VMware VMX when using the SSH transport method
163 • input from VDDK
165 • -i libvirtxml when using HTTP or HTTPS disks
167 • input from VMware vCenter server
169 The options are silently ignored for other input methods.
171 -b ...
173 --bridge ...
174 See --network below.
175 --colors
177 --colours
178 Use ANSI colour sequences to colourize messages. This is the
179 default when the output is a tty. If the output of the program is
180 redirected to a file, ANSI colour sequences are disabled unless you
181 use this option.
182 --compressed
184 This is the same as -oo compressed.
185 --echo-keys
187 When prompting for keys and passphrases, virt-v2v normally turns
188 echoing off so you cannot see what you are typing. If you are not
189 worried about Tempest attacks and there is no one else in the room
190 you can specify this flag to see what you are typing.
191 Note this options only applies to keys and passphrases for
193 encrypted devices and partitions, not for passwords used to connect
194 to remote servers.
195 -i disk
197 Set the input method to disk.
198 In this mode you can read a virtual machine disk image with no
200 metadata. virt-v2v tries to guess the best default metadata. This
201 is usually adequate but you can get finer control (eg. of memory
202 and vCPUs) by using -i libvirtxml instead. Only guests that use a
203 single disk can be imported this way.
204 -i libvirt
206 Set the input method to libvirt. This is the default.
207 In this mode you have to specify a libvirt guest name or UUID on
209 the command line. You may also specify a libvirt connection URI
210 (see -ic).
211 -i libvirtxml
213 Set the input method to libvirtxml.
214 In this mode you have to pass a libvirt XML file on the command
216 line. This file is read in order to get metadata about the source
217 guest (such as its name, amount of memory), and also to locate the
218 input disks. See "Minimal XML for -i libvirtxml option" below.
219 -i local
221 This is the same as -i disk.
222 -i ova
224 Set the input method to ova.
225 In this mode you can read a VMware ova file. Virt-v2v will read
227 the ova manifest file and check the vmdk volumes for validity
228 (checksums) as well as analyzing the ovf file, and then convert the
229 guest. See virt-v2v-input-vmware(1).
230 -i vmx
232 Set the input method to vmx.
233 In this mode you can read a VMware vmx file directly or over SSH.
235 This is useful when VMware VMs are stored on an NFS server which
236 you can mount directly, or where you have access by SSH to an ESXi
237 hypervisor. See virt-v2v-input-vmware(1).
238 -ic libvirtURI
240 Specify a libvirt connection URI to use when reading the guest.
241 This is only used when -i libvirt.
242 Only local libvirt connections, VMware vCenter connections, or RHEL
244 5 Xen remote connections can be used. Other remote libvirt
245 connections will not work in general.
246 See also virt-v2v-input-vmware(1), virt-v2v-input-xen(1).
248 -if format
250 For -i disk only, this specifies the format of the input disk
251 image. For other input methods you should specify the input format
252 in the metadata.
253 --in-place
255 Do not create an output virtual machine in the target hypervisor.
256 Instead, adjust the guest OS in the source VM to run in the input
257 hypervisor.
258 This mode is meant for integration with other toolsets, which take
260 the responsibility of converting the VM configuration, providing
261 for rollback in case of errors, transforming the storage, etc.
262 See "In-place conversion" below.
264 Conflicts with all -o * options.
266 -io OPTION=VALUE
268 Set input option(s) related to the current input mode or transport.
269 To display short help on what options are available you can use:
270 virt-v2v -it vddk -io "?"
272 -io vddk-libdir=LIBDIR
274 Set the VDDK library directory. This directory should contain
275 subdirectories called include, lib64 etc., but do not include lib64
276 actually in the parameter.
277 In most cases this parameter is required when using the -it vddk
279 (VDDK) transport. See virt-v2v-input-vmware(1) for details.
280 -io vddk-thumbprint=xx:xx:xx:...
282 Set the thumbprint of the remote VMware server.
283 This parameter is required when using the -it vddk (VDDK)
285 transport. See virt-v2v-input-vmware(1) for details.
286 -io vddk-config=FILENAME
288 -io vddk-cookie=COOKIE
289 -io vddk-nfchostport=PORT
290 -io vddk-port=PORT
291 -io vddk-snapshot=SNAPSHOT-MOREF
292 -io vddk-transports=MODE:MODE:...
293 When using VDDK mode, these options are passed unmodified to the
294 nbdkit(1) VDDK plugin. Please refer to nbdkit-vddk-plugin(1). Do
295 not use these options unless you know what you are doing. These
296 are all optional.
297 -ip filename
299 Supply a file containing a password to be used when connecting to
300 the target hypervisor. If this is omitted then the input
301 hypervisor may ask for the password interactively. Note the file
302 should contain the whole password, without any trailing newline,
303 and for security the file should have mode 0600 so that others
304 cannot read it.
305 -it ssh
307 When using -i vmx, this enables the ssh transport. See
308 virt-v2v-input-vmware(1).
309 -it vddk
311 Use VMware VDDK as a transport to copy the input disks. See
312 virt-v2v-input-vmware(1). If you use this parameter then you may
313 need to use other -io vddk* options to specify how to connect
314 through VDDK.
315 --key SELECTOR
317 Specify a key for LUKS, to automatically open a LUKS device when
318 using the inspection. "ID" can be either the libguestfs device
319 name, or the UUID of the LUKS device.
320 --key "ID":key:KEY_STRING
322 Use the specified "KEY_STRING" as passphrase.
323 --key "ID":file:FILENAME
325 Read the passphrase from FILENAME.
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 json
393 Set the output method to json.
394 In this mode, the converted guest is written to a local directory
396 specified by -os /dir (the directory must exist), with a JSON file
397 containing the majority of the metadata that virt-v2v gathered
398 during the conversion.
399 See virt-v2v-output-local(1).
401 -o libvirt
403 Set the output method to libvirt. This is the default.
404 In this mode, the converted guest is created as a libvirt guest.
406 You may also specify a libvirt connection URI (see -oc).
407 See virt-v2v-output-local(1).
409 -o local
411 Set the output method to local.
412 In this mode, the converted guest is written to a local directory
414 specified by -os /dir (the directory must exist). The converted
415 guest’s disks are written as:
416 /dir/name-sda
418 /dir/name-sdb
419 [etc]
420 and a libvirt XML file is created containing guest metadata:
422 /dir/name.xml
424 where "name" is the guest name.
426 -o null
428 Set the output method to null.
429 The guest is converted and copied (unless you also specify
431 --no-copy), but the results are thrown away and no metadata is
432 written.
433 -o openstack
435 Set the output method to OpenStack. See
436 virt-v2v-output-openstack(1).
437 -o ovirt
439 This is the same as -o rhv.
440 -o ovirt-upload
442 This is the same as -o rhv-upload.
443 -o qemu
445 Set the output method to qemu.
446 This is similar to -o local, except that a shell script is written
448 which you can use to boot the guest in qemu. The converted disks
449 and shell script are written to the directory specified by -os.
450 When using this output mode, you can also specify the -oo qemu-boot
452 option which boots the guest under qemu immediately.
453 -o rhev
455 This is the same as -o rhv.
456 -o rhv
458 Set the output method to rhv.
459 The converted guest is written to a RHV Export Storage Domain. The
461 -os parameter must also be used to specify the location of the
462 Export Storage Domain. Note this does not actually import the
463 guest into RHV. You have to do that manually later using the UI.
464 See virt-v2v-output-rhv(1).
466 -o rhv-upload
468 Set the output method to rhv-upload.
469 The converted guest is written directly to a RHV Data Domain. This
471 is a faster method than -o rhv, but requires oVirt or RHV ≥ 4.2.
472 See virt-v2v-output-rhv(1).
474 -o vdsm
476 Set the output method to vdsm.
477 This mode is similar to -o rhv, but the full path to the data
479 domain must be given:
480 /rhv/data-center/<data-center-uuid>/<data-domain-uuid>. This mode
481 is only used when virt-v2v runs under VDSM control.
482 -oa sparse
484 -oa preallocated
485 Set the output file allocation mode. The default is "sparse".
486 -oc URI
488 Specify a connection URI to use when writing the converted guest.
489 For -o libvirt this is the libvirt URI. Only local libvirt
491 connections can be used. Remote libvirt connections will not work.
492 See virt-v2v-output-local(1) for further information.
493 -of format
495 When converting the guest, convert the disks to the given format.
496 If not specified, then the input format is used.
498 -on name
500 Rename the guest when converting it. If this option is not used
501 then the output name is the same as the input name.
502 -oo OPTION=VALUE
504 Set output option(s) related to the current output mode. To
505 display short help on what options are available you can use:
506 virt-v2v -o rhv-upload -oo "?"
508 -oo compressed
510 For outputs which support qcow2 format (-of qcow2), this writes a
511 compressed qcow2 file. It is the equivalent to the -c option of
512 qemu-img(1).
513 -oo guest-id="ID"
515 For -o openstack (virt-v2v-output-openstack(1)) only, set a guest
516 ID which is saved on each Cinder volume in the "virt_v2v_guest_id"
517 volume property.
518 -oo qemu-boot
520 When using -o qemu only, this boots the guest immediately after
521 virt-v2v finishes.
522 -oo verify-server-certificate
524 -oo verify-server-certificate="true|false"
525 For -o openstack (virt-v2v-output-openstack(1)) only, this can be
526 used to disable SSL certification validation when connecting to
527 OpenStack by specifying -oo verify-server-certificate=false.
528 -oo os-*=*
530 For -o openstack (virt-v2v-output-openstack(1)) only, set optional
531 OpenStack authentication. For example -oo os-username=NAME is
532 equivalent to "openstack --os-username=NAME".
533 -oo rhv-cafile=ca.pem
535 For -o rhv-upload (virt-v2v-output-rhv(1)) only, the ca.pem file
536 (Certificate Authority), copied from /etc/pki/ovirt-engine/ca.pem
537 on the oVirt engine.
538 -oo rhv-cluster="CLUSTERNAME"
540 For -o rhv-upload (virt-v2v-output-rhv(1)) only, set the RHV
541 Cluster Name. If not given it uses "Default".
542 -oo rhv-direct
544 For -o rhv-upload (virt-v2v-output-rhv(1)) only, if this option is
545 given then virt-v2v will attempt to directly upload the disk to the
546 oVirt node, otherwise it will proxy the upload through the oVirt
547 engine. Direct upload requires that you have network access to the
548 oVirt nodes. Non-direct upload is slightly slower but should work
549 in all situations.
550 -oo rhv-verifypeer
552 For -o rhv-upload (virt-v2v-output-rhv(1)) only, verify the
553 oVirt/RHV server’s identity by checking the server‘s certificate
554 against the Certificate Authority.
555 -oo server-id="NAME|UUID"
557 For -o openstack (virt-v2v-output-openstack(1)) only, set the name
558 of the conversion appliance where virt-v2v is running.
559 -oo vdsm-compat=0.10
561 -oo vdsm-compat=1.1
562 If -o vdsm and the output format is qcow2, then we add the qcow2
563 compat=0.10 option to the output file for compatibility with RHEL 6
564 (see https://bugzilla.redhat.com/1145582).
565 If -oo vdsm-compat=1.1 is used then modern qcow2 (compat=1.1) files
567 are generated instead.
568 Currently -oo vdsm-compat=0.10 is the default, but this will change
570 to -oo vdsm-compat=1.1 in a future version of virt-v2v (when we can
571 assume that everyone is using a modern version of qemu).
572 Note this option only affects -o vdsm output. All other output
574 modes (including -o rhv) generate modern qcow2 compat=1.1 files,
575 always.
576 If this option is available, then "vdsm-compat-option" will appear
578 in the --machine-readable output.
579 -oo vdsm-image-uuid=UUID
581 -oo vdsm-vol-uuid=UUID
582 -oo vdsm-vm-uuid=UUID
583 -oo vdsm-ovf-output=DIR
584 Normally the RHV output mode chooses random UUIDs for the target
585 guest. However VDSM needs to control the UUIDs and passes these
586 parameters when virt-v2v runs under VDSM control. The parameters
587 control:
588 • the image directory of each guest disk (-oo vdsm-image-uuid)
590 (this option is passed once for each guest disk)
591 • UUIDs for each guest disk (-oo vdsm-vol-uuid) (this option is
593 passed once for each guest disk)
594 • the OVF file name (-oo vdsm-vm-uuid).
596 • the OVF output directory (default current directory) (-oo vdsm-
598 ovf-output).
599 The format of UUIDs is: "12345678-1234-1234-1234-123456789abc"
601 (each hex digit can be "0-9" or "a-f"), conforming to OSF DCE 1.1.
602 These options can only be used with -o vdsm.
604 -oo vdsm-ovf-flavour=flavour
606 This option controls the format of the OVF generated at the end of
607 conversion. Currently there are two possible flavours:
608 rhvexp
610 The OVF format used in RHV export storage domain.
611 ovirt
613 The OVF format understood by oVirt REST API.
614 For backward compatibility the default is rhvexp, but this may
616 change in the future.
617 -op file
619 Supply a file containing a password to be used when connecting to
620 the target hypervisor. Note the file should contain the whole
621 password, without any trailing newline, and for security the file
622 should have mode 0600 so that others cannot read it.
623 -os storage
625 The location of the storage for the converted guest.
626 For -o libvirt, this is a libvirt directory pool (see
628 "virsh pool-list") or pool UUID.
629 For -o json, -o local and -o qemu, this is a directory name. The
631 directory must exist.
632 For -o rhv-upload, this is the name of the destination Storage
634 Domain.
635 For -o openstack, this is the optional Cinder volume type.
637 For -o rhv, this can be an NFS path of the Export Storage Domain of
639 the form "<host>:<path>", eg:
640 rhv-storage.example.com:/rhv/export
642 The NFS export must be mountable and writable by the user and host
644 running virt-v2v, since the virt-v2v program has to actually mount
645 it when it runs. So you probably have to run virt-v2v as "root".
646 Or: You can mount the Export Storage Domain yourself, and point -os
648 to the mountpoint. Note that virt-v2v will still need to write to
649 this remote directory, so virt-v2v will still need to run as
650 "root".
651 You will get an error if virt-v2v is unable to mount/write to the
653 Export Storage Domain.
654 --print-source
656 Print information about the source guest and stop. This option is
657 useful when you are setting up network and bridge maps. See
658 "Networks and bridges".
659 --qemu-boot
661 This is the same as -oo qemu-boot.
662 -q
664 --quiet
665 This disables progress bars and other unnecessary output.
666 --root ask
668 --root single
669 --root first
670 --root /dev/sdX
671 --root /dev/VG/LV
672 Choose the root filesystem to be converted.
673 In the case where the virtual machine is dual-boot or multi-boot,
675 or where the VM has other filesystems that look like operating
676 systems, this option can be used to select the root filesystem
677 (a.k.a. "C:" drive or /) of the operating system that is to be
678 converted. The Windows Recovery Console, certain attached DVD
679 drives, and bugs in libguestfs inspection heuristics, can make a
680 guest look like a multi-boot operating system.
681 The default in virt-v2v ≤ 0.7.1 was --root single, which causes
683 virt-v2v to die if a multi-boot operating system is found.
684 Since virt-v2v ≥ 0.7.2 the default is now --root ask: If the VM is
686 found to be multi-boot, then virt-v2v will stop and list the
687 possible root filesystems and ask the user which to use. This
688 requires that virt-v2v is run interactively.
689 --root first means to choose the first root device in the case of a
691 multi-boot operating system. Since this is a heuristic, it may
692 sometimes choose the wrong one.
693 You can also name a specific root device, eg. --root /dev/sda2
695 would mean to use the second partition on the first hard drive. If
696 the named root device does not exist or was not detected as a root
697 device, then virt-v2v will fail.
698 Note that there is a bug in grub which prevents it from
700 successfully booting a multiboot system if virtio is enabled. Grub
701 is only able to boot an operating system from the first virtio
702 disk. Specifically, /boot must be on the first virtio disk, and it
703 cannot chainload an OS which is not in the first virtio disk.
704 -v
706 --verbose
707 Enable verbose messages for debugging.
708 -V
710 --version
711 Display version number and exit.
712 -x Enable tracing of libguestfs API calls.
714
716 Xen paravirtualized guests
717 Older versions of virt-v2v could turn a Xen paravirtualized (PV) guest
718 into a KVM guest by installing a new kernel. This version of virt-v2v
719 does not attempt to install any new kernels. Instead it will give you
720 an error if there are only Xen PV kernels available.
721 Therefore before conversion you should check that a regular kernel is
723 installed. For some older Linux distributions, this means installing a
724 kernel from the table below:
725 RHEL 3 (Does not apply, as there was no Xen PV kernel)
727 RHEL 4 i686 with > 10GB of RAM: install 'kernel-hugemem'
729 i686 SMP: install 'kernel-smp'
730 other i686: install 'kernel'
731 x86-64 SMP with > 8 CPUs: install 'kernel-largesmp'
732 x86-64 SMP: install 'kernel-smp'
733 other x86-64: install 'kernel'
734 RHEL 5 i686: install 'kernel-PAE'
736 x86-64: install 'kernel'
737 SLES 10 i586 with > 10GB of RAM: install 'kernel-bigsmp'
739 i586 SMP: install 'kernel-smp'
740 other i586: install 'kernel-default'
741 x86-64 SMP: install 'kernel-smp'
742 other x86-64: install 'kernel-default'
743 SLES 11+ i586: install 'kernel-pae'
745 x86-64: install 'kernel-default'
746 Windows (Does not apply, as there is no Xen PV Windows kernel)
748 Enabling virtio
750 "Virtio" is the name for a set of drivers which make disk (block
751 device), network and other guest operations work much faster on KVM.
752 Older versions of virt-v2v could install these drivers for certain
754 Linux guests. This version of virt-v2v does not attempt to install new
755 Linux kernels or drivers, but will warn you if they are not installed
756 already.
757 In order to enable virtio, and hence improve performance of the guest
759 after conversion, you should ensure that the minimum versions of
760 packages are installed before conversion, by consulting the table
761 below.
762 RHEL 3 No virtio drivers are available
764 RHEL 4 kernel >= 2.5.9-89.EL
766 lvm2 >= 2.02.42-5.el4
767 device-mapper >= 1.02.28-2.el4
768 selinux-policy-targeted >= 1.17.30-2.152.el4
769 policycoreutils >= 1.18.1-4.13
770 RHEL 5 kernel >= 2.6.18-128.el5
772 lvm2 >= 2.02.40-6.el5
773 selinux-policy-targeted >= 2.4.6-203.el5
774 RHEL 6+ All versions support virtio
776 Fedora All versions support virtio
778 SLES 11+ All versions support virtio
780 SLES 10 kernel >= 2.6.16.60-0.85.1
782 OpenSUSE 11+ All versions support virtio
784 OpenSUSE 10 kernel >= 2.6.25.5-1.1
786 Debian 6+ All versions support virtio
788 Ubuntu 10.04+ All versions support virtio
790 Windows Drivers are installed from the ISO or directory pointed
792 to by "VIRTIO_WIN" environment variable if present
793 RHEL 4: SELinux relabel appears to hang forever
795 In RHEL ≤ 4.7 there was a bug which causes SELinux relabelling to
796 appear to hang forever at:
797 *** Warning -- SELinux relabel is required. ***
799 *** Disabling security enforcement. ***
800 *** Relabeling could take a very long time, ***
801 *** depending on file system size. ***
802 In reality it is waiting for you to press a key (but there is no visual
804 indication of this). You can either hit the "[Return]" key, at which
805 point the guest will finish relabelling and reboot, or you can install
806 policycoreutils ≥ 1.18.1-4.13 before starting the v2v conversion. See
807 also https://bugzilla.redhat.com/show_bug.cgi?id=244636
808 Debian and Ubuntu
810 "warning: could not determine a way to update the configuration of
811 Grub2"
812 Currently, virt-v2v has no way to set the default kernel in Debian and
814 Ubuntu guests using GRUB 2 as bootloader. This means that virt-v2v
815 will not change the default kernel used for booting, even in case it is
816 not the best kernel available on the guest. A recommended procedure
817 is, before using virt-v2v, to check that the boot kernel is the best
818 kernel available in the guest (for example by making sure the guest is
819 up-to-date).
820 "vsyscall attempted with vsyscall=none"
822 When run on a recent Debian host virt-v2v may fail to convert guests
824 which were created before 2013. In the debugging output you will see a
825 crash message similar to:
826 vsyscall attempted with vsyscall=none ip:...
828 segfault at ...
829 This is caused because Debian removed support for running old binaries
831 which used the legacy vsyscall page to call into the kernel.
832 You can work around this problem by running this command before running
834 virt-v2v:
835 export LIBGUESTFS_APPEND="vsyscall=emulate"
837 For more information, see https://bugzilla.redhat.com/1592061
839 Windows
841 Windows ≥ 8 Fast Startup is incompatible with virt-v2v
842 Guests which use the Windows ≥ 8 "Fast Startup" feature (or guests
844 which are hibernated) cannot be converted with virt-v2v. You will see
845 an error:
846 virt-v2v: error: unable to mount the disk image for writing. This has
848 probably happened because Windows Hibernation or Fast Restart is being
849 used in this guest. You have to disable this (in the guest) in order
850 to use virt-v2v.
851 As the message says, you need to boot the guest and disable the "Fast
853 Startup" feature (Control Panel → Power Options → Choose what the power
854 buttons do → Change settings that are currently unavailable → Turn on
855 fast startup), and shut down the guest, and then you will be able to
856 convert it.
857 For more information, see: "WINDOWS HIBERNATION AND WINDOWS 8 FAST
859 STARTUP" in guestfs(3).
860 Boot failure: 0x0000007B
862 This boot failure is caused by Windows being unable to find or load the
864 right disk driver (eg. viostor.sys). If you experience this error,
865 here are some things to check:
866 • First ensure that the guest boots on the source hypervisor before
868 conversion.
869 • Check you have the Windows virtio drivers available in
871 /usr/share/virtio-win, and that virt-v2v did not print any warning
872 about not being able to install virtio drivers.
873 On Red Hat Enterprise Linux 7, you will need to install the signed
875 drivers available in the "virtio-win" package. If you do not have
876 access to the signed drivers, then you will probably need to
877 disable driver signing in the boot menus.
878 • Check that you are presenting a virtio-blk interface (not virtio-
880 scsi and not ide) to the guest. On the qemu/KVM command line you
881 should see something similar to this:
882 ... -drive file=windows-sda,if=virtio ...
884 In libvirt XML, you should see:
886 <target dev='vda' bus='virtio'/>
888 • Check that Windows Group Policy does not prevent the driver from
890 being installed or used. Try deleting Windows Group Policy before
891 conversion.
892 • Check there is no anti-virus or other software which implements
894 Group Policy-like prohibitions on installing or using new drivers.
895 • Enable boot debugging and check the viostor.sys driver is being
897 loaded.
898 OpenStack and Windows reactivation
900 OpenStack does not offer stable device / PCI addresses to guests.
902 Every time it creates or starts a guest, it regenerates the libvirt XML
903 for that guest from scratch. The libvirt XML will have no <address>
904 fields. Libvirt will then assign addresses to devices, in a
905 predictable manner. Addresses may change if any of the following are
906 true:
907 • A new disk or network device has been added or removed from the
909 guest.
910 • The version of OpenStack or (possibly) libvirt has changed.
912 Because Windows does not like "hardware" changes of this kind, it may
914 trigger Windows reactivation.
915 This can also prevent booting with a 7B error [see previous section] if
917 the guest has group policy containing "Device Installation
918 Restrictions".
919 Support for SHA-2 certificates in Windows 7 and Windows Server 2008 R2
921 Later versions of the Windows virtio drivers are signed using SHA-2
923 certificates (instead of SHA-1). The original shipping Windows 7 and
924 Windows Server 2008 R2 did not understand SHA-2 certificates and so the
925 Windows virtio drivers will not install properly.
926 To fix this you must apply SHA-2 Code Signing Support from:
928 https://docs.microsoft.com/en-us/security-updates/SecurityAdvisories/2015/3033929
929 before converting the guest.
930 For further information see:
932 https://bugzilla.redhat.com/show_bug.cgi?id=1624878
933 Networks and bridges
935 Guests are usually connected to one or more networks, and when
936 converted to the target hypervisor you usually want to reconnect those
937 networks at the destination. The options --network, --bridge and --mac
938 allow you to do that.
939 If you are unsure of what networks and bridges are in use on the source
941 hypervisor, then you can examine the source metadata (libvirt XML,
942 vCenter information, etc.). Or you can run virt-v2v with the
943 --print-source option which causes virt-v2v to print out the
944 information it has about the guest on the source and then exit.
945 In the --print-source output you will see a section showing the guest’s
947 Network Interface Cards (NICs):
948 $ virt-v2v [-i ...] --print-source name
950 [...]
951 NICs:
952 Network "default" mac: 52:54:00:d0:cf:0e
953 Bridges are special classes of network devices which are attached to a
955 named external network on the source hypervisor, for example:
956 $ virt-v2v [-i ...] --print-source name
958 [...]
959 NICs:
960 Bridge "br0"
961 To map a specific source bridge to a target network, for example "br0"
963 on the source to "ovirtmgmt" on the target, use:
964 virt-v2v [...] --bridge br0:ovirtmgmt
966 To map every bridge to a target network, use:
968 virt-v2v [...] --bridge ovirtmgmt
970 Fine-grained mapping of guest NICs
972 The --mac option gives you more control over the mapping, letting you
974 map single NICs to either networks or bridges on the target. For
975 example a source guest with two NICs could map them individually to two
976 networks called "mgmt" and "clientdata" like this:
977 $ virt-v2v [...] \
979 --mac 52:54:00:d0:cf:0e:network:mgmt \
980 --mac 52:54:00:d0:cf:0f:network:clientdata
981 Note that virt-v2v does not have the ability to change a guest’s MAC
983 address. The MAC address is part of the guest metadata and must remain
984 the same on source and target hypervisors. Most guests will use the
985 MAC address to set up persistent associations between NICs and internal
986 names (like "eth0"), with firewall settings, or even for other purposes
987 like software licensing.
988 Resource requirements
990 Network
991 The most important resource for virt-v2v appears to be network
993 bandwidth. Virt-v2v should be able to copy guest data at gigabit
994 ethernet speeds or greater.
995 Ensure that the network connections between servers (conversion server,
997 NFS server, vCenter, Xen) are as fast and as low latency as possible.
998 Disk space
1000 Virt-v2v places potentially large temporary files in $VIRT_V2V_TMPDIR
1002 (usually /var/tmp, see also "ENVIRONMENT VARIBLES" below). Using tmpfs
1003 is a bad idea.
1004 For each guest disk, an overlay is stored temporarily. This stores the
1006 changes made during conversion, and is used as a cache. The overlays
1007 are not particularly large - tens or low hundreds of megabytes per disk
1008 is typical. In addition to the overlay(s), input and output methods
1009 may use disk space, as outlined in the table below.
1010 -i ova
1012 This temporarily places a full copy of the uncompressed source
1013 disks in $VIRT_V2V_TMPDIR (or /var/tmp).
1014 -o glance
1016 This temporarily places a full copy of the output disks in
1017 $VIRT_V2V_TMPDIR (or /var/tmp).
1018 -o local
1020 -o qemu
1021 You must ensure there is sufficient space in the output directory
1022 for the converted guest.
1023 See also "Minimum free space check in the host" below.
1025 VMware vCenter resources
1027 Copying from VMware vCenter is currently quite slow, but we believe
1029 this to be an issue with VMware. Ensuring the VMware ESXi hypervisor
1030 and vCenter are running on fast hardware with plenty of memory should
1031 alleviate this.
1032 Compute power and RAM
1034 Virt-v2v is not especially compute or RAM intensive. If you are
1036 running many parallel conversions, then you may consider allocating one
1037 CPU core and 2 GB of RAM per running instance.
1038 Virt-v2v can be run in a virtual machine.
1040 Trimming
1042 Virt-v2v attempts to optimize the speed of conversion by ignoring guest
1044 filesystem data which is not used. This would include unused
1045 filesystem blocks, blocks containing zeroes, and deleted files.
1046 To do this, virt-v2v issues a non-destructive fstrim(8) operation. As
1048 this happens to an overlay placed over the guest data, it does not
1049 affect the source in any way.
1050 If this fstrim operation fails, you will see a warning, but virt-v2v
1052 will continue anyway. It may run more slowly (in some cases much more
1053 slowly), because it is copying the unused parts of the disk.
1054 Unfortunately support for fstrim is not universal, and it also depends
1056 on specific details of the filesystem, partition alignment, and backing
1057 storage. As an example, NTFS filesystems cannot be fstrimmed if they
1058 occupy a partition which is not aligned to the underlying storage.
1059 That was the default on Windows before Vista. As another example, VFAT
1060 filesystems (used by UEFI guests) cannot be trimmed at all.
1061 fstrim support in the Linux kernel is improving gradually, so over time
1063 some of these restrictions will be lifted and virt-v2v will work
1064 faster.
1065 Post-conversion tasks
1067 Guest network configuration
1068 Virt-v2v cannot currently reconfigure a guest’s network configuration.
1070 If the converted guest is not connected to the same subnet as the
1071 source, its network configuration may have to be updated. See also
1072 virt-customize(1).
1073 Converting a Windows guest
1075 When converting a Windows guests, the conversion process is split into
1077 two stages:
1078 1. Offline conversion.
1080 2. First boot.
1082 The guest will be bootable after the offline conversion stage, but will
1084 not yet have all necessary drivers installed to work correctly. These
1085 will be installed automatically the first time the guest boots.
1086 N.B. Take care not to interrupt the automatic driver installation
1088 process when logging in to the guest for the first time, as this may
1089 prevent the guest from subsequently booting correctly.
1090 Free space for conversion
1092 Free space in the guest
1093 Virt-v2v checks there is sufficient free space in the guest filesystem
1095 to perform the conversion. Currently it checks:
1096 Linux root filesystem
1098 Minimum free space: 100 MB
1099 Linux /boot
1101 Minimum free space: 50 MB
1102 This is because we need to build a new initramfs for some
1104 Enterprise Linux conversions.
1105 Windows "C:" drive
1107 Minimum free space: 100 MB
1108 We may have to copy in many virtio drivers and guest agents.
1110 Any other mountable filesystem
1112 Minimum free space: 10 MB
1113 In addition to the actual free space, each filesystem is required to
1115 have at least 100 available inodes.
1116 Minimum free space check in the host
1118 You must have sufficient free space in the host directory used to store
1120 large temporary overlays (except in --in-place mode). To find out
1121 which directory this is, use:
1122 $ df -h "`guestfish get-cachedir`"
1124 Filesystem Size Used Avail Use% Mounted on
1125 /dev/mapper/root 50G 40G 6.8G 86% /
1126 and look under the "Avail" column. Virt-v2v will refuse to do the
1128 conversion at all unless at least 1GB is available there. You can
1129 change the directory that virt-v2v uses by setting $VIRT_V2V_TMPDIR.
1130 See also "Resource requirements" above and "ENVIRONMENT VARIABLES"
1132 below.
1133 Running virt-v2v as root or non-root
1135 Nothing in virt-v2v inherently needs root access, and it will run just
1136 fine as a non-root user. However, certain external features may
1137 require either root or a special user:
1138 Mounting the Export Storage Domain
1140 When using -o rhv -os server:/esd virt-v2v has to have sufficient
1141 privileges to NFS mount the Export Storage Domain from "server".
1142 You can avoid needing root here by mounting it yourself before
1144 running virt-v2v, and passing -os /mountpoint instead, but first of
1145 all read the next section ...
1146 Writing to the Export Storage Domain as 36:36
1148 RHV-M cannot read files and directories from the Export Storage
1149 Domain unless they have UID:GID 36:36. You will see VM import
1150 problems if the UID:GID is not correct.
1151 When you run virt-v2v -o rhv as root, virt-v2v attempts to create
1153 files and directories with the correct ownership. If you run
1154 virt-v2v as non-root, it will probably still work, but you will
1155 need to manually change ownership after virt-v2v has finished.
1156 Writing to libvirt
1158 When using -o libvirt, you may need to run virt-v2v as root so that
1159 it can write to the libvirt system instance (ie. "qemu:///system")
1160 and to the default location for disk images (usually
1161 /var/lib/libvirt/images).
1162 You can avoid this by setting up libvirt connection authentication,
1164 see http://libvirt.org/auth.html. Alternatively, use -oc
1165 qemu:///session, which will write to your per-user libvirt
1166 instance.
1167 Writing to Openstack
1169 Because of how Cinder volumes are presented as /dev block devices,
1170 using -o openstack normally requires that virt-v2v is run as root.
1171 Writing to Glance
1173 This does not need root (in fact it probably won’t work), but may
1174 require either a special user and/or for you to source a script
1175 that sets authentication environment variables. Consult the Glance
1176 documentation.
1177 Writing to block devices
1179 This normally requires root. See the next section.
1180 Writing to block devices
1182 Some output modes write to local files. In general these modes also
1183 let you write to block devices, but before you run virt-v2v you may
1184 have to arrange for symbolic links to the desired block devices in the
1185 output directory.
1186 For example if using -o local -os /dir then virt-v2v would normally
1188 create files called:
1189 /dir/name-sda # first disk
1191 /dir/name-sdb # second disk
1192 ...
1193 /dir/name.xml # metadata
1194 If you wish the disks to be written to block devices then you would
1196 need to create /dir/name-sda (etc) as symlinks to the block devices:
1197 # lvcreate -L 10G -n VolumeForDiskA VG
1199 # lvcreate -L 6G -n VolumeForDiskB VG
1200 # ln -sf /dev/VG/VolumeForDiskA /dir/name-sda
1201 # ln -sf /dev/VG/VolumeForDiskB /dir/name-sdb
1202 Note that you must precreate the correct number of block devices of the
1204 correct size. Typically -of raw has to be used too, but other formats
1205 such as qcow2 can be useful occasionally so virt-v2v does not force you
1206 to use raw on block devices.
1207 Minimal XML for -i libvirtxml option
1209 When using the -i libvirtxml option, you have to supply some libvirt
1210 XML. Writing this from scratch is hard, so the template below is
1211 helpful.
1212 Note this should only be used for testing and/or where you know what
1214 you're doing! If you have libvirt metadata for the guest, always use
1215 that instead.
1216 <domain type='kvm'>
1218 <name> NAME </name>
1219 <memory>1048576</memory>
1220 <vcpu>2</vcpu>
1221 <os>
1222 <type>hvm</type>
1223 <boot dev='hd'/>
1224 </os>
1225 <features>
1226 <acpi/>
1227 <apic/>
1228 <pae/>
1229 </features>
1230 <devices>
1231 <disk type='file' device='disk'>
1232 <driver name='qemu' type='raw'/>
1233 <source file='/path/to/disk/image'/>
1234 <target dev='hda' bus='ide'/>
1235 </disk>
1236 <interface type='network'>
1237 <mac address='52:54:00:01:02:03'/>
1238 <source network='default'/>
1239 <model type='rtl8139'/>
1240 </interface>
1241 </devices>
1242 </domain>
1243 In-place conversion
1245 It is also possible to use virt-v2v in scenarios where a foreign VM has
1246 already been imported into a KVM-based hypervisor, but still needs
1247 adjustments in the guest to make it run in the new virtual hardware.
1248 In that case it is assumed that a third-party tool has created the
1250 target VM in the supported KVM-based hypervisor based on the source VM
1251 configuration and contents, but using virtual devices more appropriate
1252 for KVM (e.g. virtio storage and network, etc.).
1253 Then, to make the guest OS boot and run in the changed environment, one
1255 can use:
1256 virt-v2v -ic qemu:///system converted_vm --in-place
1258 Virt-v2v will analyze the configuration of "converted_vm" in the
1260 "qemu:///system" libvirt instance, and apply various fixups to the
1261 guest OS configuration to make it match the VM configuration. This may
1262 include installing virtio drivers, configuring the bootloader, the
1263 mountpoints, the network interfaces, and so on.
1264 Should an error occur during the operation, virt-v2v exits with an
1266 error code leaving the VM in an undefined state.
1267 Machine readable output
1269 The --machine-readable option can be used to make the output more
1270 machine friendly, which is useful when calling virt-v2v from other
1271 programs, GUIs etc.
1272 There are two ways to use this option.
1274 Firstly use the option on its own to query the capabilities of the
1276 virt-v2v binary. Typical output looks like this:
1277 $ virt-v2v --machine-readable
1279 virt-v2v
1280 libguestfs-rewrite
1281 colours-option
1282 vdsm-compat-option
1283 input:disk
1284 [...]
1285 output:local
1286 [...]
1287 convert:linux
1288 convert:windows
1289 A list of features is printed, one per line, and the program exits with
1291 status 0.
1292 The "input:" and "output:" features refer to -i and -o (input and
1294 output mode) options supported by this binary. The "convert:" features
1295 refer to guest types that this binary knows how to convert.
1296 Secondly use the option in conjunction with other options to make the
1298 regular program output more machine friendly.
1299 At the moment this means:
1301 1. Progress bar messages can be parsed from stdout by looking for this
1303 regular expression:
1304 ^[0-9]+/[0-9]+$
1306 2. The calling program should treat messages sent to stdout (except
1308 for progress bar messages) as status messages. They can be logged
1309 and/or displayed to the user.
1310 3. The calling program should treat messages sent to stderr as error
1312 messages. In addition, virt-v2v exits with a non-zero status code
1313 if there was a fatal error.
1314 Virt-v2v ≤ 0.9.1 did not support the --machine-readable option at all.
1316 The option was added when virt-v2v was rewritten in 2014.
1317 It is possible to specify a format string for controlling the output;
1319 see "ADVANCED MACHINE READABLE OUTPUT" in guestfs(3).
1320
1322 /usr/share/virtio-win
1323 (Optional)
1324 If this directory is present, then virtio drivers for Windows
1326 guests will be found from this directory and installed in the guest
1327 during conversion.
1328
1330 "VIRT_V2V_TMPDIR"
1331 "LIBGUESTFS_CACHEDIR"
1332 Location of the temporary directory used for the potentially large
1333 temporary overlay file. If neither environment variable is set
1334 then /var/tmp is used.
1335 To reliably ensure large temporary files are cleaned up (for
1337 example in case virt-v2v crashes) you should create a randomly
1338 named directory under /var/tmp, set "VIRT_V2V_TMPDIR" to point to
1339 this directory, then when virt-v2v exits remove the directory.
1340 See the "Disk space" section above.
1342 "VIRT_TOOLS_DATA_DIR"
1344 This can point to the directory containing data files used for
1345 Windows conversion.
1346 Normally you do not need to set this. If not set, a compiled-in
1348 default will be used (something like /usr/share/virt-tools).
1349 This directory may contain the following files:
1351 rhsrvany.exe
1353 (Required when doing conversions of Windows guests)
1354 This is the RHSrvAny Windows binary, used to install a
1356 "firstboot" script in the guest during conversion of Windows
1357 guests.
1358 See also: "https://github.com/rwmjones/rhsrvany"
1360 pvvxsvc.exe
1362 This is a Windows binary shipped with SUSE VMDP, used to
1363 install a "firstboot" script in Windows guests. It is required
1364 if you intend to use the --firstboot or --firstboot-command
1365 options with Windows guests.
1366 "VIRTIO_WIN"
1368 This is where virtio drivers for Windows are searched for. It can
1369 be a directory or point to virtio-win.iso (CD ROM image containing
1370 drivers).
1371 If unset, then we look for drivers in whichever of these paths is
1373 found first:
1374 /usr/share/virtio-win/virtio-win.iso
1376 The ISO containing virtio drivers for Windows.
1377 /usr/share/virtio-win
1379 The exploded tree of virtio drivers for Windows. This is
1380 usually incomplete, hence the ISO is preferred.
1381 See "Enabling virtio".
1383 For other environment variables, see "ENVIRONMENT VARIABLES" in
1385 guestfs(3).
1386
1388 engine-image-uploader(8)
1389 Variously called "engine-image-uploader", "ovirt-image-uploader" or
1390 "rhevm-image-uploader", this tool allows you to copy a guest from
1391 one oVirt or RHV Export Storage Domain to another. It only permits
1392 importing a guest that was previously exported from another
1393 oVirt/RHV instance.
1394 import-to-ovirt.pl
1396 This script can be used to import guests that already run on KVM to
1397 oVirt or RHV. For more information, see this blog posting by the
1398 author of virt-v2v:
1399 https://rwmj.wordpress.com/2015/09/18/importing-kvm-guests-to-ovirt-or-rhev/#content
1401
1403 virt-p2v(1), virt-customize(1), virt-df(1), virt-filesystems(1),
1404 virt-sparsify(1), virt-sysprep(1), guestfs(3), guestfish(1),
1405 qemu-img(1), engine-image-uploader(8), import-to-ovirt.pl, nbdkit(1),
1406 nbdkit-vddk-plugin(1), http://libguestfs.org/.
1407
1409 Matthew Booth
1410 Cédric Bosdonnat
1412 Tomáš Golembiovský
1414 Shahar Havivi
1416 Roman Kagan
1418 Mike Latimer
1420 Nir Soffer
1422 Richard W.M. Jones
1424 Pino Toscano
1426 Tingting Zheng
1428
1430 Copyright (C) 2009-2020 Red Hat Inc.
1431
1433 This program is free software; you can redistribute it and/or modify it
1434 under the terms of the GNU General Public License as published by the
1435 Free Software Foundation; either version 2 of the License, or (at your
1436 option) any later version.
1437 This program is distributed in the hope that it will be useful, but
1439 WITHOUT ANY WARRANTY; without even the implied warranty of
1440 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
1441 General Public License for more details.
1442 You should have received a copy of the GNU General Public License along
1444 with this program; if not, write to the Free Software Foundation, Inc.,
1445 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
1446
1448 To get a list of bugs against libguestfs, use this link:
1449 https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools
1450 To report a new bug against libguestfs, use this link:
1452 https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Virtualization+Tools
1453 When reporting a bug, please supply:
1455 • The version of libguestfs.
1457 • Where you got libguestfs (eg. which Linux distro, compiled from
1459 source, etc)
1460 • Describe the bug accurately and give a way to reproduce it.
1462 • Run libguestfs-test-tool(1) and paste the complete, unedited output
1464 into the bug report.
1465virt-v2v-1.45.91 2021-11-23 virt-v2v(1)