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.

Description of problem:
Currently two-phase conversion in virt-v2v-wrapper relies on an unsupported parameter `--debug-overlays` in conjunction with `--no-copy` even though that is heavily dependent on internal implementation of the conversion.

What we need to do is to be able to leverage all the greatness of virt-v2v but without copying the disks as that part will already be prepared.

This bugzilla is not a request for a specific solution, but rather a feature request for the above scenario to be accessible in a supportable fashion.

Eventual plan to fix this is:
https://listman.redhat.com/archives/libguestfs/2020-November/msg00022.html

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Ridiculous process.

We decided after consulting with QE to move this feature to RHEL 9.1.

Rich - reassigning to you directly. If the bz is targeted to a release (or with devel_ack+), there should be a developer assigned and not in the backlog (e.g. virt-maint).

If it can be in the backlog for some future release planning, the feel free to remove the ITR and reassign to virt-maint.

I'm closing this because we will create a new cleaner and
clearer bug to track the new feature.

*** This bug has been marked as a duplicate of bug 2011713 ***