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:

Output modes -o local and -o libvirt (and -o qemu upstream, but not
in RHEL) depend on UEFI firmware being installed in the host when
converting EFI guests.  See the following upstream code:

  https://github.com/libguestfs/libguestfs/blob/c6d8d68a4643794128c1d617bc83fc22438cc7c5/v2v/output_libvirt.ml#L143-L153
  https://github.com/libguestfs/libguestfs/blob/c6d8d68a4643794128c1d617bc83fc22438cc7c5/v2v/create_libvirt_xml.ml#L38

However virt-v2v does not depend on OVMF, and so conversions
fail with:

  virt-v2v: error: cannot find firmware for UEFI guests.
  You probably need to install OVMF, or AAVMF (if using aarch64)

The reason that we didn't depend on OVMF/AAVMF previously was
because it was not available in the base RHEL channel for RHEL < 7.3.

However that will apparently change in RHEL 7.4:

  https://bugzilla.redhat.com/show_bug.cgi?id=1329559#c31

And so we'll be able to have something like this:

%package virt-v2v
...
%ifarch x86_64
Requires: OVMF
%endif
%ifarch aarch64
Requires: AAVMF
%endif

Version-Release number of selected component (if applicable):

libguestfs 1.36

Steps to Reproduce:

rpm -qR virt-v2v | grep -i vmf

On x86_64, it should print "OVMF-..." and on aarch64 it should print
"AAVMF-...".  On other architectures there is no UEFI virtual firmware.

We should also check that virt-v2v remains installable without requiring
any supplementary RHEL channels.

Verify the bug with below builds:
virt-v2v-1.36.2-2.el7.x86_64
libguestfs-1.36.2-2.el7.x86_64

Steps:
1:Make sure OVMF and virt-v2v installed,then run below command:
# rpm -qR virt-v2v | grep -i vmf
OVMF

2:Make sure no OVMF and virt-v2v package removed, then re-install virt-v2v .
# yum install virt-v2v
******************
Resolving Dependencies
--> Running transaction check
---> Package virt-v2v.x86_64 1:1.36.2-2.el7 will be installed
--> Processing Dependency: OVMF for package: 1:virt-v2v-1.36.2-2.el7.x86_64
--> Running transaction check
---> Package OVMF.noarch 0:20170228-1.gitc325e41585e3.el7 will be installed
--> Finished Dependency Resolution
*****************

Results:I think virt-v2v is  depending on OVMF in this version build.
So , I think we could move this to VERIFIED.

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://access.redhat.com/errata/RHBA-2017:2023