Repository navigation
gce-linux-detonation: the detonation kernel, bootable on a Compute Engine host - #1553
Closed
bryan-minimal wants to merge 1 commit into
Closed
bryan-minimal wants to merge 1 commit into
bryan-minimal wants to merge 1 commit into
Conversation
…gine host virtio-linux-detonation has virtio drivers only and cannot boot a C4 or C4A instance (NVMe disks, gVNIC). This is the same source and version with the same BPF-LSM, BTF and tracing settings, plus what such a host needs: UEFI, NVMe, gVNIC, ext4, nftables, cgroups, the vTPM, AppArmor. The build fails when an observability setting differs from the config virtio-linux-detonation ships, when a host symbol does not resolve to built in, or when anything is left as a module. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Contributor
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
|
Member
Author
|
Closing at Bryan's call: we will not carry our own host kernel. For the record, the build stopped after 160 s at this PR's own comparison, not in the kernel build: |
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
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.
Why
The Package Build Log's sensor was written for the detonation kernel (
virtio-linux-detonation). The build hosts run it on the stock Ubuntu kernel instead, whose BPF settings we do not choose.virtio-linux-detonationcannot boot those hosts: it is a microVM guest kernel with virtio drivers only, and C4 / C4A instances present NVMe disks and a gVNIC network card.Running each build inside a microVM on the detonation kernel is the real answer and waits for the build-box work. Until then this gives the hosts a kernel we build, with those settings exactly.
What
A new package,
gce-linux-detonation: the same kernel source and version (6.18.63) asvirtio-linux-detonation, withbuild.sh;/proc/config.gz.Everything is built in. There are no modules; the image is the whole kernel.
Checks in the build
The build fails when:
virtio-linux-detonationships (that package is a build dependency for this), or the kernel version differs;=y(unknown on this arch or version, or a dependency unmet:olddefconfigdrops those silently);=m.Not done
-gcpconfig, which I do not have. Expect the first boot to find something missing./usr/share/virtio-linux-detonation/config.🤖 Generated with Claude Code