Anaconda developers,
I wish to enhance our RHEL7 ks.cfg file to support either UEFI boot or legacy BIOS on UEFI boot. This build will be supported on recent server models only, whose system firmware supports both these boot methods.
I have done both BIOS and UEFI kickstarts. (Fedora 20).
My preference would be a single partitioning scheme for both. That is, I'd add inst.gpt to the boot flags. Like this:
KERNEL /boot/ol/7.0/x86_64/vmlinuz
APPEND initrd=/boot/ol/7.0/x86_64/initrd.img inst.stage2=hd:LABEL=MINIBOOT:/stage2/squashfs.img inst.ks=hd:LABEL=MINIBOOT:/ks.cfg inst.gpt
^^^^^^^^
And then I'd create a biosboot partition and a efi partition.
If I understand the kickstart syntax:
My ks.cfg would look like this:
bootloader --location=mbr
part biosboot --size 1 --fstype="biosboot"
part /boot --fstype="xfs" --size=300
part /boot/efi --fstype="efi" --size=300 --fsoptions="umask=0077,shortname=winnt"
My bootloader is std RHEL7.0 grub2.
Here's my questions.
1. Anaconda will put usual grub2 stuff under /boot/grub2/*?
grub.cfg, grubenv, etc?
2. After reboot with BIOS mode, will grub2 expect my vmlinuz/initrd images under /boot?
3. Anaconda will put usual grub2 stuff under /boot/efi ?
4. After reboot with UEFI mode, will grub2 expect my vmlinuz/initrd images under /boot/efi?
5. If I go w/ this auto-dual-boot method, as I add new kernels, how do I keep /boot/grub2/* and /boot/efi/* in sync? will dracut do that for me automatically?
Alternatively, it's be OK to have a common partitioning scheme (to make it easy to flip between boot methods). And documentation to my engineers on how to flip between boot methods.
Is there a way in my syslinux.cfg to pass an arg to my boot kernel? So that in my ks.cfg %pre section I parse /proc/cmdline to determine whether I'm booted UEFI or BIOS? Or is there an easier way for my ks.cfg %pre section to determine whether it's booted BIOS or UEFI?
Spike
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
