Description of problem: RHEV 3.6 Administration Guide 11.2.6. Adding a VMware Instance as a Virtual Machine Provider: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html-single/Administration_Guide/index.html#Adding_a_VMware_Instance_as_a_Virtual_Machine_Provider It would appear that RHEV-H isn't supported for this feature since it does not include the virt-v2v utility. If possible RHEV-H should maintain similiar features to a full RHEL host. Version-Release number of selected component (if applicable): Versions after 3.6 How reproducible: Deploy RHEV with only RHEV-H hypervisors. Steps to Reproduce: 1. Untested, as it is not currently supported. Actual results: After reviewing the documentation, and checking the hypervisors I do not believe this feature is available. It depends on the virt-v2v tool (/usr/bin/virt-v2v) which does not exist in the rhev-h image. Expected results: RHEV-H should include the virt-v2v tool to allow VMWare machines to be imported. Additional info:
I would qualify this as a bug. We couldn't include it in 7.1 duing original development phase, but nowadays it is available (also with fixes tracked in bug 1292096) which allows us to include it by default on RHEL as well as RHEV-H Raising priority for this as currently the situation is confusing. It is mentioned in documentation that you need to install v2v packages manually, but it's not obvious to see you didn't do that in UI - import looks like working ok and just fails the actual conversion later on.
PPC hosts are filtered out correctly since bug 1280264
Should this bug be on ovirt-engine if the dependency is needed on the host side? Shouldn't it be on RHEV-H?
(In reply to Eyal Edri from comment #4) > Should this bug be on ovirt-engine if the dependency is needed on the host > side? > Shouldn't it be on RHEV-H? it's tracking both sides. does it matter? if yes then we can clone it and split it
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
bug targeted against master, http://gerrit.ovirt.org/54866 merged -> MODIFIED to verify, just check that once Vdsm is installed, virt-v2v is installed too on the virtualization host.
Verified. ovirt-engine-4.0.2.6-0.1.el7ev
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-1743.html