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.
Descriptionmxie@redhat.com
2017-10-31 11:02:48 UTC
Description of problem:
Physical machine can't boot into virt-p2v client when machine's BIOS is on UEFI mode
Version-Release number of selected component (if applicable):
virt-p2v-1.36.10-1.el7.iso
How reproducible:
100%
Steps to Reproduce:
1.Mount the virt-p2v iso to virtual media of physical machine via remote console
2.Set UEFI mode for machine at BIOS
3.Boot the machine into virt-p2v iso file but failed
Actual results:
As above description
Expected results:
Physical machine can boot into virt-p2v client when BIOS is on UEFI mode
Additional info:
Comment 2Richard W.M. Jones
2017-11-07 10:41:25 UTC
Does it give any error?
Also is CSM (the BIOS compatibility mode of UEFI) enabled in the firmware
settings?
(In reply to Richard W.M. Jones from comment #2)
> Does it give any error?
>
> Also is CSM (the BIOS compatibility mode of UEFI) enabled in the firmware
> settings?
No,will not pop up any error, as screenshot1 shows, machine's BIOS is on UEFI mode,at boot menu interface, select "iLO virtual ..." to boot (virt-p2v iso file has been mounted via iLO), but machine will return to screenshot2
Also could reproduce this problem using guest, create a uefi guest in virt-manager and connect virt-p2v iso file to CDROM. then boot guest into CDROM but console will keep at screenshot3 forever
I'm seeing a similar failure, I have a physical system that does not support CSM, it's pure UEFI, the RHEL7.6 virt-p2v ISO (SHA-256 Checksum: d437f5768fe3cdb992f53861ced9438a4680d5a161eaed89aa6885d60212501b) is not recognized as bootable. A Fedora 30 ISO boots well on the system.
Comment 8Jaroslav Suchanek
2019-12-04 15:30:28 UTC
This bug will be addressed in next major release.
Comment 12RHEL Program Management
2021-01-08 07:24:50 UTC
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.
Comment 13Richard W.M. Jones
2021-01-08 10:54:32 UTC
I apologise for the actions of the "stale" bug process above. This bug
is not stale, and I am reopening it. All bugs are important.
Comment 16RHEL Program Management
2021-07-31 07:27:14 UTC
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.
Comment 17Richard W.M. Jones
2021-07-31 07:46:08 UTC
My apologies, this bug was closed by a broken process that we
do not have any control over. Reopening.
Comment 18Richard W.M. Jones
2022-01-07 14:32:59 UTC
Let's fix this in RHEL 9. Since there is a bug already for that
I'm making this bug a duplicate of the newer one.
*** This bug has been marked as a duplicate of bug 2038105 ***