Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Detail is in the man pages, but the new/changed features are:
* -op and -osd command line options continue to be supported, but are
deprecated in favour of -os. There is no deprecation warning when
they're used.
* -of command line option allows specification of the file format which
will be used for target storage: raw or qcow2. This allows, e.g. a guest
with raw storage to convert to qcow2 storage and vice versa.
* -oa command line option allows the allocation policy of the target
storage to be specified: sparse or preallocated. This can be used to
convert between sparse and preallocated. Underlying this change, sparse
volumes are now supported.
* The config file can now contain target 'profiles' which specify a
target's storage location, output format and allocation policy. This
allows the user to specify --profile <foo> rather than -os <a> -op <b>
-oa <oc>. See man virt-v2v.conf for details.
* We support Windows XP again, as long as the latest virtio-win package
is installed.
* We support conversion of Windows guests to libvirt targets, not just
RHEV targets.