This pulls https://github.com/flatcar/bootengine/pull/113 to fix a
kernel boot warning being printed for three modules that are loaded
explicitly.
Signed-off-by: Kai Lueke <kailuke@microsoft.com>
This is consistent with other sysexts. Note that the sysext must be
enabled at boot time for this to happen, otherwise you need to call
`systemd-tmpfiles --create` and `systemctl daemon-reload` first.
Signed-off-by: James Le Cuirot <jlecuirot@microsoft.com>
This pulls in https://github.com/flatcar/init/pull/136 to prevent the
default network setup to conflict with TUN/TAP device configuration
from other tools.
Signed-off-by: Kai Lueke <kailuke@microsoft.com>
The Intel microcode wasn't applied anymore after it was reworked to be
in the initrd instead of being built-in as part of the kernel image.
This was due to how the kernel build system can't handle combined
initrds and skip the early cpio when compressing. The AMD microcode was
still built-in as part of the kernel image.
Let the kernel build system pick up the Intel microcode by installing it
to the firmware directory. Disable the inclusion of microcode in the
initrd. Also, we can drop the preservation of the early cpio when
generating the minimal initrd.
Signed-off-by: Kai Lueke <kailuke@microsoft.com>
When the virtio graphic mode instead of qemu's bochs was used, the
interactive console did not show up because fbdev emulation recently
got disabled.
Reenable fbdev emulation and also add the "simple" and QXL FB DRM
driver to make TTM_HELPER available for the out-of-tree nvidia driver
(which is needed when fbdev emulation is enabled).
Fixes https://github.com/flatcar/Flatcar/issues/1834
Signed-off-by: Kai Lueke <kailuke@microsoft.com>
This change ingests a new baselayout version that fixes a UID / GID
mis-alignment with the "messagebus" user / group.
See https://github.com/flatcar/baselayout/pull/36.
Signed-off-by: Thilo Fromm <thilofromm@microsoft.com>
Co-authored-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
The microcode was accidentally dropped from Flatcar a while back because
Gentoo started telling Dracut to not include it when USE=-initramfs.
Flatcar disabled that flag because the microcode is installed to /boot.
This is only done under the board root though, not in the final image,
so there's no harm in enabling it.
That Dracut setting also affected the AMD microcode, which is part of
coreos-firmware, so this fixes that too.
Signed-off-by: James Le Cuirot <jlecuirot@microsoft.com>
I couldn't take it anymore! The launcher script could not handle paths
outside the script's own directory, and it was driving me crazy. Now
only the default values are relative to the script's directory. Given
paths are relative to the current directory and absolute paths work as
you would expect.
Signed-off-by: James Le Cuirot <jlecuirot@microsoft.com>
This change removes the legacy_boot flag from the EFI system partition.
We already have a BIOS boot partition which should offer compatibility with
legacy bios systems.
Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>
docs: Add entrance to the changelog about the fix
Update changelog/changes/2025-01-15-qemu-startup-script-comma-fix.md
Co-authored-by: Mathieu Tortuyaux <mathieu.tortuyaux@gmail.com>
This change updates coreos-cloudinit to the latest flatcar-master commit.
This change disables user-configdrive.service on OpenStack,
as coreos-cloudinit.service already runs on OpenStack when the system is
not configured via ignition.
Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>
The Flatcar extension images built with build_sysext created directories
in the overlay in a way that masked contents from other layers.
Instead of fixing the way we create directories, make use of
postprocessing to avoid any similar problems show up again in the
future.
This pulls in https://github.com/flatcar/update_engine/pull/38
with two workarounds to read out proxy env vars from the service unit
and to read out the XML response from the journal logs, because the XML
passing and the passing of proxy env vars is not present in old clients.
CloudSigma uses a serial port to transfer metadata into a running
instance. Because the service was overwritten with the configuration
"restart" it was possible that the previous instance got interrupted.
This left the serial connection in an non-deterministic state as the
next user would get output from the previous request. The service in
general was not needed as the cloud oem is already set to cloudsigma.
