test(installer): verify GPT backups after abrupt VM loss - #121
Merged
Merged
Conversation
…t-vm-interruption-20260923 # Conflicts: # packages/os/linux/installer/ISSUES.md # packages/os/linux/installer/README.md
lalalune
marked this pull request as ready for review
September 23, 2026 12:06
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
1 participant
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.
Existing artifact persistence qualification kills the writer process while the guest kernel remains alive. Add a local KVM qualification that kills the exact disposable QEMU process at each of four persistence checkpoints and boots the same overlay with a fresh kernel. The native reader must return either the exact artifact or no usable output; the directory-synced checkpoint must recover successfully.
The runner accepts only a completed prepared qualification, checks native source/binary and artifact bindings, preserves the prepared image as unchanged backing storage, and retains per-boot seed/log hashes and QEMU commands. It attaches only disposable image files and disables guest networking.
Validation: complete local 512-byte and 4096-byte artifact lanes (16 final guest boots total), independent inspection of retained log/seed hashes and fresh-kernel/ext4-recovery logs, rejection of incomplete prepared source evidence before VM creation, Python compilation,
bun install, andbun run verify. In both lanes the created/written-but-unsynced artifacts were absent after reboot (ENOENT, zero usable bytes); file-synced and directory-synced artifacts were recovered byte-for-byte.This models abrupt guest/kernel and QEMU process loss. Host caches and physical storage remain powered, so it does not prove physical power-loss safety or complete installer backend integration. Related to #20; does not close it.