microvm: bump kata assets to 4.1.0 - #1708
Open
Huy Pham (hdp617) wants to merge 2 commits into
Open
Huy Pham (hdp617) wants to merge 2 commits into
Huy Pham (hdp617) wants to merge 2 commits into
Conversation
Contributor
Author
2 tasks
Today, `ateom` fetches the `kata-config` asset (configuration-clh.toml) to read only 3 values `default_memory`, `default_vcpus` and `kernel_params`. The first 2 are redundant because (1) the values never change and (2) ateom has the same defaults. Only `kernel_params` is relevant for the `kata-agent`; its value also changed once in the Kata project history. `ateom` now owns all three values, which also allows us to tune them specifically for Substrate.
Huy Pham (hdp617)
force-pushed
the
kata-4.1.0
branch
from
September 17, 2026 22:07
bce28a1 to
7b84ca9
Compare
Bowei Du (bowei)
added
kind/cleanup
Kata 4.1.0 bundles virtiofsd v1.14.0, the first release carrying the vhost-0.16 / vhost-user-backend-0.22 snapshot-restore fix that Cloud Hypervisor's restore handshake needs. Kata bundled v1.13.3 through 4.0.0, which hangs that handshake, so assemble.sh sourced virtiofsd separately: an upstream prebuilt zip on amd64, and a cargo build from the release tag on arm64. Both paths now go away. virtiofsd comes out of kata-static alongside the kernel and rootfs, so assembling assets on arm64 no longer needs rust or the libcap-ng / libseccomp build deps, and the GitLab upload URL that only resolves in its unauthenticated project-id form is no longer pinned. Because the arm64 binary is downloaded rather than built, its bytes are reproducible and its sha256 can be committed like every other asset. That retires the deploy-time injection in install-microvm-deps.sh, which existed only because a locally built binary varies per toolchain; applying the SandboxConfig now substitutes nothing but the bucket name. The guest kernel is unchanged at v6.18.35, and the vendored kata-agent protos stay byte-identical between 3.31.0 and 4.1.0, so neither needs a re-vendor. Cloud Hypervisor stays at v53.0: kata pins v51.1, so the separately sourced CH binary is untouched by this bump. Verified by running assemble.sh for arm64 on a KVM-capable Linux host, which reproduced the four committed shas and reported virtiofsd 1.14.0. On amd64 the kata-bundled binary is byte-identical to the upstream prebuilt pinned before this change.
Huy Pham (hdp617)
force-pushed
the
kata-4.1.0
branch
from
September 18, 2026 19:01
7b84ca9 to
9e8f42e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #1704, which removes kata-config.
Kata 4.1.0 bundles virtiofsd 1.14.0 (required by Substrate). This simplifies the dev process on arm64 because it removes the need to build virtiofsd from source.
Verified on an arm64 KVM host (Lima + kind).
Fixes #1695