Repository navigation
feat(enforcement): bind registered VM disk observations - #933
Merged
Merged
Conversation
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 installed owner previously matched a VM's realized identity while accepting changed attached files. New administrative registrations now bind the offline disk/DVD topology, volume/file IDs and defined file metadata in a strict version-two record. The read-only service retains ancestor/file handles without write/delete sharing, rechecks attachments and metadata, and permanently refuses an observed replacement, change, outage or running VM. Upgrade preserves the original binding; legacy version-one and unconfigured records retain their read-only compatibility path.
Storage acquisition runs under the original installed owner before routing releases the fixed main controller. A fresh authenticated request consumes the fixed read-only inventory observation once and creates a terminal completion fence. That fence binds to the same owner, retains the live caller/token/Job/pinned installation under the original supervisor deadline, and exposes no further dispatch or renewal. The two-second request age remains enforced at dispatch. Native topology reads fence VM identity/Off state and file holds through publication. Fixed numeric failure checkpoints are retained on the original private channel.
Validation on
78562125: all five required CI contexts passed in run 38294119952. The final focused Windows suites passed 116 registration/lifetime/lease tests and 28 caller tests, including real write/delete refusal, replacement, hard links, open writers, cleanup, a 2200-ms preparation followed by fresh admission, and aged dispatch refusal with retained live-peer completion. Seven production helpers compiled. Windows11 run 38294111598, attempt 3, passed the host, registered VM and guest corpora: inspection count 1 before/after upgrade, 55 mutation denials, rollback/partial/uninstall controls, VM Off/removal and closed owned media cleanup. All 42 compiled native input hashes were verified; four raw-byte differences are strictly explained by hosted CRLF checkout normalization. Earlier guest-readiness and HTTP-control deadline failures remain recorded. The local full source-control batch was stopped after observing an owned suspended verifier; its result is incomplete. Hosted source-control preflight passed on the successful attempt.This adds an offline attachment observation. It does not establish image-content provenance, VHD parent-chain or storage ACL sealing, network/namespace containment, production lifecycle dispatch, guest transport or complete E1/E2/E3/A1 acceptance. Launch remains unavailable.