Repository navigation
Conversation
This was referenced Oct 25, 2026
This was referenced Oct 25, 2026
This was referenced Oct 26, 2026
zibi-pplx
force-pushed
the
pr937
branch
4 times, most recently
from
October 26, 2026 15:41
99adfd2 to
f9117cd
Compare
zibi-pplx
force-pushed
the
pr937
branch
3 times, most recently
from
October 26, 2026 23:46
cc6dd28 to
f6cc525
Compare
## Summary Build the Linux kernel, NVIDIA compute modules and embedded GSP firmware as one pinned boot bundle. Sign modules with a per-build key held on tmpfs and discarded after signing; keep the kernel's signature enforcement and disabled module unloading, FUSE and vsock loopback. Templates install matching compute userspace without receiving a GPU. Keep the distribution-signed build as qualification tooling, distinct from the source-built bundle. Neither build installs or approves an execution environment. ## Validation - Preserve certified Firecracker upgrade edges while leaving the signed GPU boot entry without unqualified upgrade targets. The rebased runtime-core suite and Linux all-target check passed. The source-built bundle booted through Cloud Hypervisor and completed a checked CUDA computation, stop/start and deletion in a dedicated development test. Bash syntax checks passed. Kernel and module builds were performed during implementation; they were not repeated for this commit rearrangement. ## Severity and risk New boot tooling; existing Firecracker images and selection remain unchanged. Build keys intentionally produce distinct immutable artifacts. GPU device-node initialization currently requires driver initialization from root; automatic unprivileged first use is not validated. These artifacts do not qualify sanitization or cross-tenant reuse. ## Stack GPU execution, after the CPU-only Cloud Hypervisor group. #962 is the first PR in this group and supplies the SQLite schema before #945 and the device consumers. Requirements, artifact delivery, fenced ownership, operator visibility and GPU smoke coverage follow. Device-bearing requests remain standalone-only. The scrub candidate in #950 is unqualified; this stack does not claim production-safe tenant reuse. AI assistance: Codex implemented the changes, ran validation and drafted this description.
This branch has not been deployed
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.
Summary
Build the Linux kernel, NVIDIA compute modules and embedded GSP firmware as one pinned boot bundle. Sign modules with a per-build key held on tmpfs and discarded after signing; keep the kernel's signature enforcement and disabled module unloading, FUSE and vsock loopback. Templates install matching compute userspace without receiving a GPU.
Keep the distribution-signed build as qualification tooling, distinct from the source-built bundle. Neither build installs or approves an execution environment.
Validation
The source-built bundle booted through Cloud Hypervisor and completed a checked CUDA computation, stop/start and deletion in a dedicated development test. Bash syntax checks passed. Kernel and module builds were performed during implementation; they were not repeated for this commit rearrangement.
Severity and risk
New boot tooling; existing Firecracker images and selection remain unchanged. Build keys intentionally produce distinct immutable artifacts. GPU device-node initialization currently requires driver initialization from root; automatic unprivileged first use is not validated. These artifacts do not qualify sanitization or cross-tenant reuse.
Stack
GPU execution, after the CPU-only Cloud Hypervisor group. #962 is the first PR in this group and supplies the SQLite schema before #945 and the device consumers. Requirements, artifact delivery, fenced ownership, operator visibility and GPU smoke coverage follow. Device-bearing requests remain standalone-only. The scrub candidate in #950 is unqualified; this stack does not claim production-safe tenant reuse.
AI assistance: Codex implemented the changes, ran validation and drafted this description.
Stack created with Sapling. Best reviewed with ReviewStack.
Base: #960, the separate Cloud Hypervisor CPU execution stack.