[RHEL 7.2 - PATCH] Disable GRUB os_prober on POWER (#1193281)
by Robert Marshall
The GRUB2 os_prober utility searches for other Linux installations
and the output to the grub config file is parsed incorrectly by
petitboot. This disables the os_prober script on the following
POWER based machine/platform combinations.
CHRP/pSeries
CHRP IBM/pSeries
pSeries/pSeries
Maple/pSeries,
Cell/pSeries
Momentum/pSeries
PowerNV/pSeries
Resolves: rhbz#1193281
---
pyanaconda/bootloader.py | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/pyanaconda/bootloader.py b/pyanaconda/bootloader.py
index 510ab07..877a975 100644
--- a/pyanaconda/bootloader.py
+++ b/pyanaconda/bootloader.py
@@ -2067,6 +2067,12 @@ class IPSeriesGRUB2(GRUB2):
defaults = open(defaults_file, "a+")
# The terminfo's X and Y size, and output location could change in the future
defaults.write("GRUB_TERMINFO=\"terminfo -g 80x24 console\"\n")
+ # Disable OS Prober on pSeries systems
+ # TODO: This will disable across all POWER platforms. Need to get
+ # into blivet and rework how it segments the POWER systems
+ # to allow for differentiation between PowerNV and
+ # PowerVM / POWER on qemu/kvm
+ defaults.write("GRUB_DISABLE_OS_PROBER=true\n")
defaults.close()
--
1.8.3.1
8 years, 11 months
Updated: [rhinstaller/anaconda/pulls/181 master] dracut: fix boot with inst.ks and no inst.{repo,stage2} (#1238987)
by dashea
Okay so: commit 4883b96 moved fetch-kickstart-net.sh from the online
hook into initqueue (or initqueue/settled) to fix inst.ks.sendmac.
So when you boot with inst.ks=[URL], the order goes:
1. Network comes up
2. Run `online` hook
* Schedule kickstart fetch in initqueue
* Other online tasks from boot args (e.g. updates)
3. Run `initqueue`
* fetch + run kickstart
* add `anaconda-netroot.sh` (etc.) to `online` hook
* `udevadm trigger` disk devices
* `udevadm trigger` net devices
The problem is, triggering network devices is *not* sufficient to re-run
the `online` hook - this only happens when the NIC actually gets
_configured_, not when the device is triggered.
The fix is pretty straightforward: re-run the `online` hook for active
NICs after we run the kickstart, in order to pick up any new tasks that
the kickstart might have scheduled.
Resolves: RHBZ#1238987
--
To view this pull request on github, visit https://github.com/rhinstaller/anaconda/pull/181
8 years, 11 months
Updated: [rhinstaller/anaconda/pulls/182 master] Driverdisk refactor
by dashea
Okay, here it is - the big refactor of driver-updates. `README.dd` still needs to be updated, but the code is all here. It also adds a suite of unit tests for `driver-updates` and a kickstart test for the `driverdisk` command.
Other than some minor text changes the overall behavior should be the same, except for one thing: we no longer attempt to unload running modules. (This is, I think, outside the scope of what problems the driver-updates stuff is designed to solve. `modprobe.blacklist` can handle the rare cases where a driver-updates disk needs to replace an existing module.)
Resolves: RHBZ#1084197
Resolves: RHBZ#1164131
--
To view this pull request on github, visit https://github.com/rhinstaller/anaconda/pull/182
8 years, 11 months