Jeremi Piotrowski

Old sources likely gone from mirrors, let me see if this is something that can be revived.

@chewi: if we're switching to catalyst4 then it would be a good idea to switch for amd64 sdk first, validate that everything is still correct and then go for arm64....

I've pushed two sdk container images: ghcr.io/jepio/flatcar-sdk-arm64/flatcar-sdk-arm64:3941.0.0-2024-05-29-1223 ghcr.io/jepio/flatcar-sdk-arm64/flatcar-sdk-tarball:3941.0.0-2024-05-29-1223 arm64, there is no usecase for it and it's not something anyone has thought of doing in the oss world.

This is the tracking issue, we keep it open until the PR lands.

There was a bug 2 years back which changed how ansible reports this (https://github.com/ansible/ansible/issues/77537), so I think ansible users will have needed to learn how to handle both (image-builder does)....

You'll have to make systemd-modules-load.service run after the sysext service (via dropins), and enable all the zfs services/targets manually. And then you'll probably also need to add a dependency between...

I configure the top-level cmake project like this and it lets me build on Linux against system libraries without vcpkg: ``` AZURE_SDK_DISABLE_AUTO_VCPKG=1 cmake -GNinja -DDISABLE_AZURE_CORE_OPENTELEMETRY=1 -DBUILD_WINDOWS_UWP=1 .. ``` This effectively...

There was no change in Flatcar to explain it, so we don't know what to do about it. The best guess is that an update to `open-vm-tools` changed how this...

Which version worked?

amd-pstate will be added, thanks for catching this. Any reason you think CONFIG_HZ=1000 is bad? We also have CONFIG_NO_HZ_IDLE.