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.

Bug 2222696

Summary: RFE: virt-drivers should be able to detect the bootloader of rhel guest image on s390x
Product: Red Hat Enterprise Linux 9 Reporter: YongkuiGuo <yoguo>
Component: guestfs-toolsAssignee: Virtualization Maintenance <virt-maint>
Status: CLOSED MIGRATED QA Contact: YongkuiGuo <yoguo>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 9.3CC: lersek, qzhang, rjones, virt-maint, ymao, yoguo
Target Milestone: rcKeywords: FutureFeature, MigratedToJIRA, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-22 17:22:21 UTC Type: Story
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
the whole log of virt-drivers none

Description YongkuiGuo 2023-07-13 13:36:54 UTC 
Created attachment 1975600 [details]
the whole log of virt-drivers

Description of problem:
virt-drivers fails to detect the bootloader when handling the rhel guest image on s390x env.

# virt-drivers -v -x -a rhel-guest-image-9.3-20230713.0.s390x.qcow2
virt-drivers: error: no bootloader detected

If reporting bugs, run virt-drivers with debugging enabled and include the
complete output:

  virt-drivers -v -x [...]



Version-Release number of selected component (if applicable):
guestfs-tools-1.50.1-3.el9.s390x
libguestfs-1.50.1-6.el9.s390x
kernel-5.14.0-333.el9.s390x
qemu-kvm-8.0.0-6.el9.s390x
libvirt-9.3.0-2.el9.s390x


How reproducible:
100%


Steps:

1. Download the latest rhel guest image on s390x
# wget https://download.eng.bos.redhat.com/rhel-9/nightly/RHEL-9/RHEL-9.3.0-20230713.0/compose/BaseOS/s390x/images/rhel-guest-image-9.3-20230713.0.s390x.qcow2
2. Run the virt-drivers command


Actual results:
As above

Expected results:
virt-drivers works fine just like on x86_64/aarch64 env.
Comment 1 Richard W.M. Jones 2023-07-13 13:59:48 UTC 
Turning this into an RFE since:

* s390x uses a bootloader called zipl (https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/chap-post-installation-configuration-s390)

* virt-v2v never supported s390x so we have never had a reason before to add this bootloader

Therefore this is a new feature for virt-drivers (which uses the virt-v2v code)
Comment 3 RHEL Program Management 2023-09-22 17:19:40 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 4 RHEL Program Management 2023-09-22 17:22:21 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.