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.
The removal of files in the overlay present in the lowerdir creates
whiteout entries that mask the lowerdir entries. For those files that
have a tmpfile rule for creation, a reboot would cause the file to be
created in the upperdir, meaning this file is not updated from the
lowerdir when it changes. In addition we have filtered out some tmpfile
rules that caused upcopies (symlinks and directories) which meant that
removing the /etc/resolv.conf symlink didn't bring it back after reboot.
To make files from the lowerdir show up if they have a tmpfile rule that
normally would recreate them we keep a list of whiteout entries that we
clean up on boot. This also prevents freezing files because
systemd-tmpfiles does not need to recreate them in the upperdir.
