Repository navigation
Exercise the published boot contract in QEMU - #642
Merged
Merged
Conversation
This was referenced Nov 2, 2026
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.
The existing disk launchers use a test-only dinit graph. Add
test/qemu/packaged-boot-smoketo install published boot packages into a fresh system profile, activate their defaults and service primitives through Mere, and boot their/sbin/initwithout replacing production services.Separate disposable disks cover serial authentication and power-off, reboot with persistent data, and required-mount failure followed by menu-selected authenticated recovery. A test service checks mount availability during shutdown, and read-only filesystem checks bracket each scenario. Record package/trust inputs and support replay while keeping guest execution offline.
Document host requirements, disposable account fixtures, invocation, replay, and the boundary between these boot checks and the remaining lifecycle/bootloader work. The existing guest-profile preparation remains the default.
Part of #634 and #633.