After switching the disk layout for the cloud image to gpt + btrfs (for https://fedoraproject.org/wiki/Changes/FedoraCloudHybridBoot) the image creation is broken on ppc64le. The root cause is that there is no "PReP" partition that's mandatory on "pseries"-class systems (like VMs).
see e.g. https://koji.fedoraproject.org/koji/taskinfo?taskID=74491564
Would overwriting the bios boot partition with a PreP partition work here? If so, what else do I need for POWER? And what about s390x, which is also built in that task?
Metadata Update from @ngompa: - Issue tagged with: IBM
Metadata Update from @ngompa: - Issue tagged with: OpenStack
Might be able to pick up a tip or two from https://github.com/coreos/coreos-assembler/blob/main/src/create_disk.sh#L113-L154
It won't directly apply, but might be able to glean something from it.
The struggle is real here: I can't use %ifarch or similar with the declarative aspects of kickstart...
%ifarch
yes, I believe swapping biosboot with PReP would work
re s390x - interestingly it has no problem with the new layout, but the bootloader is block number oriented, so it's sufficient to have /boot somewhere
I haven't tried, but can't we add the PReP partition to the existing ones? I guess it defaults to 4MB or such ...
Metadata Update from @davdunc: - Issue tagged with: meeting
can't you use reqpart?
reqpart
https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#reqpart
It doesn't let you set both BIOS+EFI with GPT for x86 architectures. If it did, I would have used that originally...
just thinking loud, not even
clearpart --all --initlabel --disklabel=gpt reqpart # to create the EFI stuff part biosboot --size=1 --fstype=biosboot ...
would work, if the VM is EFI-based?
other option would be to open an RFE against pykickstart/blivet/...
# Partition clearing information clearpart --all --initlabel --disklabel=gpt # Disk partitioning information part prepboot --fstype="prepboot" --size=4 part biosboot --fstype="biosboot" --size=1 part /boot/efi --fstype="efi" --size=100 part /boot --fstype="ext4" --size=500 --label=boot part btrfs.007 --fstype="btrfs" --grow --size=2000 btrfs none --label=fedora btrfs.007 btrfs /home --subvol --name=home LABEL=fedora btrfs / --subvol --name=root LABEL=fedora
gave me a working VM on ppc64le
We should do that. I'd love to simplify this...
I've sent an email to the Anaconda devel mailing list about this: https://listman.redhat.com/archives/anaconda-devel-list/2021-August/msg00000.html
Could any one try the workaround with prepboot added to the list of all possible boot partitions on x86? I believe it could be a workaround until there is a proper fix. We need a solution for ppc64le before F-35 GA ...
prepboot
I can add it to our kickstart and see if it helps. 1MB of wasted space isn't a huge deal even if it sucks balls...
thanks, it's 4MB, but still shouldn't hurt
Fixes proposed:
Metadata Update from @ngompa: - Issue assigned to ngompa
This seems to be fixed now with our workaround: https://koji.fedoraproject.org/koji/taskinfo?taskID=75458981
Metadata Update from @ngompa: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.