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.

=== RFE Request ==

1. Who is the customer behind the request?

Account Name : Csn Ag
Customer segment : 3
Compliance Score: 640

* Customer would like to convert virtual machine running on Microsoft HyperV to RHEV.

2 What is the nature and description of the request?

Currently virt-v2v tool supports only xen, kvm and vmware virtual machines migration/conversion . customer requesting support of Hyper-V guests conversion. (Hyper -V to RHEV )
----------------
Ability to feed virt-v2v with the CIFS path to an arbitrary Hyper-V virtual machine image and its configuration file and automatic outputting to a RHEV-configured export storage.
-------------------

3. Why does the customer need this? (List the business requirements here)
To migrate Hyper-V guests to RHEV.

4. Is there already an existing RFE upstream or in Red Hat bugzilla? No.

5. It meets RHEL Inclusion criteria

6. List of affected packages : virt-v2v

*customer also commented why this is important.
-----------------
I think this would help to increase the acceptance of RHEV being a serious competitor to other (established) virtualisation solutions and reduce impediments to deploy RHEV.
-----------------------

Thank you for submitting this issue for consideration in Red Hat Enterprise
Linux. Red Hat will consider this request in a future release of Red Hat
Enterprise Linux, version 7, and does not have plans to make it available in earlier versions of Red Hat Enterprise Linux, as you requested.

virt-v2v will not be included in RHEL 7.

virt-v2v will not be included in RHEL 7.

Sorry, but didn´t get the answer. virt-v2v will be not included in RHEL 7, so we need to use RHEL 6. Only RHEL 5 and 6 will have that rpm available? If that´s the case, is going to be developed or is going to be depracated, as I understood from the answer?

Hi Jaime,
As far as I know, the new version virt-v2v will be included in RHEL7.1, it will not be depracated.
REHL5 and RHEL6 rpm are our former release. Of course you could get the upstream version in fedora.
Currently, this is no plan for new feature for virt-v2v, at lease in RHEL6.6 and RHEL7.0(not include).
Any virt-v2v related issues, you could ask for rjones who is virt-v2v developer now.

Lei