Repository navigation
Conversation
This was referenced Oct 25, 2026
zibi-pplx
force-pushed
the
pr936
branch
2 times, most recently
from
October 25, 2026 17:04
f0741bf to
ce84ec6
Compare
This was referenced Oct 26, 2026
zibi-pplx
force-pushed
the
pr936
branch
3 times, most recently
from
October 26, 2026 17:25
e2a0335 to
ab9066c
Compare
zibi-pplx
force-pushed
the
pr936
branch
3 times, most recently
from
October 26, 2026 23:46
6899fde to
ef3910a
Compare
zibi-pplx
force-pushed
the
pr936
branch
2 times, most recently
from
October 27, 2026 05:59
a449b3d to
8aaa2ed
Compare
## Summary Add a static x86-64 Cloud Hypervisor build from a checksum-pinned v54.0 source archive. Correct VFIO Landlock rules to resolve the PCI device's iommu_group link and allow read access only to that device subtree. Export the binary checksum, source/patch identity and upstream licenses. The result requires a separate catalog identity; this change neither replaces the upstream pin nor changes runtime selection. ## Validation Built the exported artifact and ran a CUDA calculation through VFIO with Landlock enabled, an unprivileged VMM, a minimal chroot, and PID/mount namespaces. The stock v54.0 binary refused the same Landlock device configuration before the correction. A host-file control-API probe remained confined to the chroot. ## Severity and risk The upstream path bug prevents VFIO launch with Landlock. Deployment risk is low because this adds a build recipe only; artifact publication, qualification and admission remain separate. ## 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 and validated the change 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
Add a static x86-64 Cloud Hypervisor build from a checksum-pinned v54.0 source archive. Correct VFIO Landlock rules to resolve the PCI device's iommu_group link and allow read access only to that device subtree.
Export the binary checksum, source/patch identity and upstream licenses. The result requires a separate catalog identity; this change neither replaces the upstream pin nor changes runtime selection.
Validation
Built the exported artifact and ran a CUDA calculation through VFIO with Landlock enabled, an unprivileged VMM, a minimal chroot, and PID/mount namespaces. The stock v54.0 binary refused the same Landlock device configuration before the correction. A host-file control-API probe remained confined to the chroot.
Severity and risk
The upstream path bug prevents VFIO launch with Landlock. Deployment risk is low because this adds a build recipe only; artifact publication, qualification and admission remain separate.
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 and validated the change and drafted this description.
Stack created with Sapling. Best reviewed with ReviewStack.
Base: #960, the separate Cloud Hypervisor CPU execution stack.