Repository navigation
Add a QEMU guest namespace test harness - #636
Merged
Merged
Conversation
9 tasks done
Boot a disposable Linux guest with explicit kernel and static BusyBox inputs to check user/group ID mapping, mount and PID namespaces, private procfs, and tmpfs access. Keep the POSIX shell harness under test/qemu with usage instructions, bounded execution, serial diagnostics, and cleanup. This establishes a developer test environment without requiring host KVM or mount privileges. Mere build and dinit scenarios remain follow-up work under #635; this does not define the distro's boot or installation interface. Part of #635.
jhuntwork
force-pushed
the
qemu-guest-harness
branch
from
November 1, 2026 02:24
1ca11af to
dbd6db9
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
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.
Boot a disposable Linux guest with explicit kernel and static BusyBox inputs to check user/group ID mapping, mount and PID namespaces, private procfs, and tmpfs access. Keep the POSIX shell harness under test/qemu with usage instructions, bounded execution, serial diagnostics, and cleanup.
This establishes a developer test environment without requiring host KVM or mount privileges. Mere build and dinit scenarios remain follow-up work under #635; this does not define the distro's boot or installation interface.
Part of #635.