Bug 985163 - Install does not allow bootloader configuration
Install does not allow bootloader configuration
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Anaconda Maintenance Team
Release Test Team
Depends On:
  Show dependency treegraph
Reported: 2013-07-16 21:37 EDT by Alex Williamson
Modified: 2013-12-11 11:29 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-12-11 11:29:01 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alex Williamson 2013-07-16 21:37:34 EDT
Description of problem:
I boot multiple installations from a single disk.  RHEL5 allows configuration of where the bootloader is installed (MBR vs partition).  RHEL6 allows configuration of where the bootloader is installed.  RHEL7 don't care, RHEL7 overwrites the MBR.

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

How reproducible:

Steps to Reproduce:
1. Attempt to install RHEL7 and finish with the MBR intact

Actual results:
RHEL7 now owns the MBR

Expected results:
No regression from RHEL5 and RHEL6 which allow partition installation.

Additional info:
Comment 2 David Cantrell 2013-12-11 11:29:01 EST
The RHEL-7 installer allows you to select the whole disk that you want the boot loader installed on.  You can also choose to not install a boot loader.  The link in the lower left corner of the INSTALLATION DESTINATION screen called "Full disk summary and bootloader..." allows you to pick an alternate disk or not install a boot loader at all.

More advanced boot loader configuration settings are available via kickstart.

Note You need to log in before you can comment on or make changes to this bug.