PR#915: Replaced part biosboot and part /boot by reqpart --add-boot to cover different requirements by differen archs - fedora-kickstarts

fedora-kickstarts

#915 Replaced part biosboot and part /boot by reqpart --add-boot to cover different requirements by differen archs

Merged 2 years ago by kevin. Opened 2 years ago by pboy.

pboy/fedora-kickstarts main into main

Removed some unnecessary commented out instructions.

Peter Boy • 2 years ago

3d653e5

Replaced part biosboot and part /boot by reqpart --add-boot to cover different requirements by differen archs

Peter Boy • 2 years ago

6777f93

fedora-server-vm-full.ks

file modified

+8 -8

		`@@ -1,11 +1,11 @@`
		`- # fedora-server-vm-full.ks (rel. 1.0)`
		`+ # fedora-server-vm-full.ks (rel. 1.01)`
		`# Kickstart file to build a Fedora Server Edition VM disk image.`
		`# The image aims to resemble as close as technically possible the`
		`# full features of a Fedora Server Edition in a virtual machine.`
		`#`
		`- # The image uses GPT partition type as of default in Fedora 37`
		`+ # The image uses GPT partition type as of default in Fedora 37.`
		`#`
		`- # At first boot it opens a test based basic configuration screen.`
		`+ # At first boot it opens a text mode basic configuration screen.`
		`#`
		`# This kickstart file is designed to be used with ImageFactory (in Koji).`
		`#`
		`@@ -13,7 +13,6 @@`
		`# various additional helpers and configuration files.`
		`# See Fedora Server Edition user documentation tutorial.`

		`-`
		`# Use text mode install`
		`text`

		`@@ -46,7 +45,6 @@`


		`# System services`
		`- # message: error enabling initial-setup, initial-setup does not exist`
		`services --enabled="sshd,NetworkManager,chronyd,initial-setup"`

		`# Run the Setup Agent on first boot`
		`@@ -55,14 +53,13 @@`
		`# Partition Information. Use GPT by default (since Fedora 37)`
		`# Resemble the Partitioning used for Fedora Server Install media`
		`clearpart --all --initlabel --disklabel=gpt`
		`- part biosboot --size=1 --fstype=biosboot`
		`- part /boot --size=1000 --fstype=xfs --label=boot`
		`+ reqpart --add-boot`
		`part pv.007 --size=4000 --grow`
		`volgroup sysvg pv.007`
		`logvol / --vgname=sysvg --size=4000 --grow --maxsize=16000 --fstype=xfs --name=root --label=sysroot`


		`- # Include URLs for network installation dynamically, dependent from Fedora release`
		`+ # Include URLs for network installation dynamically, dependent on Fedora release`
		`# and imagefactory runtime environment`
		`%include fedora-repo.ks`

		`@@ -79,6 +76,9 @@`
		`@headless-management`
		`@standard`
		`@networkmanager-submodules`
		`+ # container management is an optional install item on disk media.`
		`+ # Install options not available with VMs. So we don't include it`
		`+ # despite trying to resemble a DVD installation as close as possible.`
		`##@container-management`
		`@domain-client`
		`@guest-agents`

pboy commented 2 years ago

Fedora Server VM built for x86_64 but failed for aarch64 and ppc64. According to the error message, arch specific partitions were missed (efi and PReP).

Replaced 'part biosboot' and 'part /boot' by 'reqpart --boot' to let Anaconda create the required partitions in front of ROOT.

ngompa commented 2 years ago

You can just pre-create all of them in one go, like so:

# Configure for gpt with bios+uefi
clearpart --all --initlabel --disklabel=gpt
part prepboot  --size=4    --fstype=prepboot
part biosboot  --size=1    --fstype=biosboot
part /boot/efi --size=100  --fstype=efi

pbrobinson commented on line 12 of fedora-server-vm-full.ks 2 years ago

Is this required when it can be derived from the git repo logs?

pbrobinson commented on line 24 of fedora-server-vm-full.ks 2 years ago

Don't comment it out, just remove it

pboy commented 2 years ago

You can just pre-create all of them in one go, like so:

```

Configure for gpt with bios+uefi

clearpart --all --initlabel --disklabel=gpt
part prepboot --size=4 --fstype=prepboot
part biosboot --size=1 --fstype=biosboot
part /boot/efi --size=100 --fstype=efi
```

I tried that in a previous version, exactly as I found it in cloud-base. But it didn't build because it couldn't determine the proper partition to boot from (according to the error message). So I postponed it to the next version to get time to figure out why it doesn't work.