sys-kernel/kata-guest-kernel
Linux kernel for Kata Containers guest VMs, built from Kata's config fragments
Screenshots
View
Download
BrowseChangeLog
commit ae787f1ab04e5e6847abbb73113a002e82345d16
Author: lucascouts <lucascs@protonmail.com>
Date: Sat Oct 10 23:44:06 2026 -0300
treewide: drop non-amd64 keywords from bentoo's own ebuilds
Applies the amd64-only baseline to the 132 ebuilds (126 packages) that
have no ::gentoo counterpart; the 375 mirror ebuilds keep upstream's
KEYWORDS.
- KEYWORDS: only ~amd64 (amd64 stays stable on gst-plugins-va and
librewolf-bin).
- SRC_URI: arm64?/x86?/... blocks removed from 36 ebuilds, plus the dead
`elif use arm64` branches that picked those distfiles.
- Manifest: 80 DIST lines nothing references any more, from 34 packages.
- Comments in ebuilds and .autoupdate/packages.toml that justified
~arm64 rewritten; no probe url or pattern changed.
- md5-cache regenerated for exactly the edited ebuilds.
librewolf and kata-* keep their per-arch logic on purpose: it mirrors
the Firefox/Kata build scripts and keeping it eases rebases.
Verified: pkgcheck per package shows no new finding vs master (14 fewer),
gentoo-parity.sh output identical to master, emerge -pv resolves.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
commit 9fd8474399c88f484d0bccd0263829baab81cca2
Author: lucascouts <lucascs@protonmail.com>
Date: Fri Oct 2 17:04:50 2026 -0300
add(app-containers/kata-containers-4.2.0, sys-kernel/kata-guest-kernel-6.18.35_p202, metadata/md5-cache/{app-containers/kata-containers-4.2.0, sys-kernel/kata-guest-kernel-6.18.35_p202}), mod(.autoupdate/packages.toml)
Kata Containers built entirely from source: runtime-rs, kata-ctl and the
in-guest kata-agent from the upstream vendor tarball, the guest kernel from
kernel.org plus Kata's config fragments and patches, and a guest initrd made
of the agent (as PID 1) and the libraries it links on this system instead of
upstream's Ubuntu rootfs. QEMU is the only configured hypervisor for now.
Verified with unprivileged builds and a manual KVM boot of the guest: the
agent comes up as PID 1 and starts its ttRPC server on vsock port 1024.
Not verified: a container run through containerd, which needs root.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Author: lucascouts <lucascs@protonmail.com>
Date: Sat Oct 10 23:44:06 2026 -0300
treewide: drop non-amd64 keywords from bentoo's own ebuilds
Applies the amd64-only baseline to the 132 ebuilds (126 packages) that
have no ::gentoo counterpart; the 375 mirror ebuilds keep upstream's
KEYWORDS.
- KEYWORDS: only ~amd64 (amd64 stays stable on gst-plugins-va and
librewolf-bin).
- SRC_URI: arm64?/x86?/... blocks removed from 36 ebuilds, plus the dead
`elif use arm64` branches that picked those distfiles.
- Manifest: 80 DIST lines nothing references any more, from 34 packages.
- Comments in ebuilds and .autoupdate/packages.toml that justified
~arm64 rewritten; no probe url or pattern changed.
- md5-cache regenerated for exactly the edited ebuilds.
librewolf and kata-* keep their per-arch logic on purpose: it mirrors
the Firefox/Kata build scripts and keeping it eases rebases.
Verified: pkgcheck per package shows no new finding vs master (14 fewer),
gentoo-parity.sh output identical to master, emerge -pv resolves.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
commit 9fd8474399c88f484d0bccd0263829baab81cca2
Author: lucascouts <lucascs@protonmail.com>
Date: Fri Oct 2 17:04:50 2026 -0300
add(app-containers/kata-containers-4.2.0, sys-kernel/kata-guest-kernel-6.18.35_p202, metadata/md5-cache/{app-containers/kata-containers-4.2.0, sys-kernel/kata-guest-kernel-6.18.35_p202}), mod(.autoupdate/packages.toml)
Kata Containers built entirely from source: runtime-rs, kata-ctl and the
in-guest kata-agent from the upstream vendor tarball, the guest kernel from
kernel.org plus Kata's config fragments and patches, and a guest initrd made
of the agent (as PID 1) and the libraries it links on this system instead of
upstream's Ubuntu rootfs. QEMU is the only configured hypervisor for now.
Verified with unprivileged builds and a manual KVM boot of the guest: the
agent comes up as PID 1 and starts its ttRPC server on vsock port 1024.
Not verified: a container run through containerd, which needs root.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>