The integration test build also encrypts /boot which requires
grub to open the LUKS pool using cryptomount. grub does not support
the argonID salted password hashes. Thus the integration test
description configures pbkdf2 instead
The archlinux integration test used a custom iso boot
template which still contained the terminal_setup variable.
This commit fixed the template to use the new terminal_input
and terminal_output variables
We were relying on the repos being parsed from the kiwi description but this can
cause problems and gives us less flexibility when it comes to fixing repository
setup issues.
This fixes https://github.com/OSInside/kiwi/issues/2335
The grub terminal setup is divided into the setting for the output
and the input console. For both settings different parameters exists.
So far kiwi did not differentiate between the two parts of the
console setup and that could lead to a wrong setting if only one
value is provided in kiwi's console= attribute which lead to the
grub setting, GRUB_TERMINAL=value. If value is set to e.g gfxterm
grub takes this for both input and output and it's obviously
wrong for the input. To make this less error prune the kiwi code
changes with this commit to set GRUB_TERMINAL_INPUT and
GRUB_TERMINAL_OUTPUT rather than GRUB_TERMINAL and also runs sanity
checks on the provided values if they are applicable. The information
for setting up the console in the schema stays untouched though.
That's because it's used for all bootloaders and also because grub
supports multiple values for the console in/out setting in one
GRUB_TERMINAL variable even though kiwi does no longer use it.
To make this clear for the users also the documentation for the
console attribute setup has been updated. If we want to wish two
distinct attributes for input and output console settings a schema
change and also differentiation between bootloaders is needed and
that I only see for the kiwi-10 branch if at all. This Fixes#2419
kernel-install does a lot more then making the kernel available
to the ESP. It calls dracut, it creates loader entries and all
that is unexpected and also breaks the boot because the way
dracut is called in the image build case where host != target
leads to broken results. This commit refactors the systemd-boot
support in kiwi to prevent the use of kernel-install
Create proper EFI FAT image via bootctl to be used as
alt loader in xorriso. This allows to boot the ISO
via EFI e.g kvm -bios /usr/share/qemu/ovmf-x86_64.bin -cdrom file.iso
Please note, hybrid boot is done via grub's hybrid MBR and
as systemd-boot does not provide one, hybrid boot is out
of scope yet. This Fixes#2281
Community repository is no longer needed for the test image. OBS does
not pull any package from this repository and in Arch linux there is not
the concept of empty repositories, so the build fails in an OBS context
if this repository is included within the build stack.
Signed-off-by: David Cassany <dcassany@suse.com>
The subvolumes must be mounted below the root of the
filesystem tree such that the sync mechanism correctly
shuffles the data to the correct volumes.
This Fixes#2356
In case of btrfs and if btrfs_set_default_volume is explicitly
switched off, we create the correct rootflags= kernel cmdline
entry to tell the system about the root volume for booting
When using btrfs with the proposed layout for testing the
delivered grub bios module for the Fedora system used to build
the integration test (FC37) is not capable to find the grub
config file. A manual call for configfile in the grub shell
fixes this with the existing kiwi created grub early-boot
script. However, it is expected that the delivered grub image
works and kiwi only creates its own one if no distro delivered
grub image was found. To make the integration test functional
for both BIOS and EFI the simple solution is to use an extra
not btrfs based boot partition. This still allows to test
the desired btrfs layout in terms of volumes and sub-volumes
and does not break on any of the boot methods.
Use dnf5 for rawhide. It's hard to differentiate between old and
new dnf version on Fedora Rawhide. Thus let's make the move to
dnf5. Since microdnf is also wrapped into dnf5 the integration
test for microdnf got renamed to dnf5
