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.
=Comment: #0=================================================
Emily J. Ratliff <emilyr.com> - 2008-09-24 13:53 EDT
1. Feature Overview:
Feature Id: [201719]
a. Name of Feature: Reipl support
b. Feature Description
The Linux kernel already has support for a feature called Reipl. We want to enable the installer to
use Reipl. What Reipl does is instruct the 390 where to boot next. This is different than a boot
loader since the 390 does not support a default boot location. Also, this tool can be used by a
system administrator during other times. If they want to shutdown the machine and reboot from a
different partition. There are documentation hits on this as well. Versions of hardware/software:
- LPAR on machine older than z9
- LPAR on z9 or newer (required to reipl from FCP)
- z/VM 5.2 or older
- z/VM 5.4 or later (required to reipl from FCP)
2. Feature Details:
Sponsor: LTC
Architectures:
s390 native
s390 compat
s390x
Arch Specificity: Purely Arch Specific Code
Affects Installer: Yes
Delivery Mechanism: Backport
Category: Installation
Request Type: Installer - Enhancement from IBM
d. Upstream Acceptance: Accepted
Sponsor Priority 2
f. Severity: Medium
IBM Confidential: no
Code Contribution: IBM code
g. Component Version Target: The reipl code is included in the Linux mainline kernel and the distro
kernels that this feature has been targeted for. The installer does not have an associated upstream
project, so IBM will provide code directly.
3. Business Case
Avoid customer frustration on installation by rebooting automatically instead of manually between
install phase 1 and 2.
4. Primary contact at Red Hat:
John Jarvis
jjarvis
5. Primary contacts at Partner:
Project Management Contact:
Sarah Wright, sarahw.com, 503-578-5145
Technical contact(s):
Mark Hamzy, hamzy.com
IBM Manager:
Jeffrey Heroux, heroux.com
This has been checked into rawhide.
commit d00ef216099104c03c400f56fb21e19089df4a7d
Author: Mark Hamzy <hamzy.com>
Date: Mon Feb 16 14:19:35 2009 -0600
reIPL support for s390
Signed-off-by: David Cantrell <dcantrell>
I can confirm this is working in z/VM 5.4 for both DASD and FCP LUN.
Tested on tree RHEL6.0-20100603.1 with anaconda-13.21.50-2.el6
Moving to VERIFIED
Comment 9releng-rhel@redhat.com
2010-07-02 20:39:50 UTC
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.