[BUG] Private-client preparation rejects counted grant destinations #5

Closed
opened 2026-09-25 11:07:58 +02:00 by erikinkinen · 0 comments
Owner

Summary

Private realm-client preparation still requires Launchd's legacy fixed install-grant destination in Loaderd's transport intake, payload handler and success-reply encoder. Launchd's counted client producer instead reserves a distinct caller-local column, retires its received executable-directory scope, and requests the returned install grant at that exact original destination. The producer and consumer disagree before the first client can be staged.

The first configured-client VM on the corrected mediator-fixture graph reaches all preceding admission, guarded-preparation and private-startup markers, then returns INTERNAL for the first PREPARE_REALM_CLIENT. The source mismatch is directly visible; a focused actual-code reproduction and corrected native run are required before claiming complete root-cause closure.

Reproduction

Use signed Integration 9451847f and its complete original catalog, then run:

bash scripts/run-scenario.sh tests/scenarios/appliance-disk-image-realm-clients-positive.toml components.toml

The original guest deadline is 120 seconds and the serial-progress deadline is 45 seconds. The first local execution fails; no unchanged retry or deadline adjustment was used.

Expected and actual behavior

The authenticated private client operation must retain the original explicit caller-local grant destination through intake, materialization and the single install-grant MOVE reply. The existing source endpoint, exact SEND receipt, supervisor, full realm/mediator relation and original cleanup owners remain mandatory. Legacy ordinary-child and mediator destinations must retain their existing contracts; there is no ordinary-launch fallback or additional grant.

Actual serial output reaches all three preceding verified markers, then reports:

ERIX_EXSH:REALM_ADMISSION:FAILED request=00000022 kind=0000000b first=000006d7 second=00000005

Request 34, opcode 0x6d7, is the first private-client preparation and returns INTERNAL (5). No client has started, and no configured-client success marker or full guest build is established. The original bounded runner ends with status 1.

Environment and identity

  • Integration: 9451847fbff64d10a0d56dd673e8a238110d7ac1.
  • Exsh: f36b1f51f138f4c5c56fcac45a881731d0471c81.
  • Loaderd: e0562cdc6a52b518ea7fe34341a49f57caa9b1d8.
  • Launchd: 0b0788b5530ce7607097eee97babe22e71d8c1b9.
  • Original 76-repository graph, release x86_64 appliance, one CPU; explicit two-realm/four-client policy with 576 plan bytes and existing shell routes only.

Evidence and prior checks

Native configured-client acceptance — 25 September 2026: the exact signed Integration 7a42fa26 graph passes the configured-client, preparation and startup VMs with all original markers, deadlines and cleanup gates. The configured witness seals two isolated realms, observes six successful byte-client exits across three realm instances, checks independent retirement, rejects stale client selectors and reuses a Launchd realm record with a new generation. This proves the native configure/seal/publish/mediated-I/O criterion; full Procd managed-row/final CPU reclamation, supervisor loss and resource ceilings remain separate requirements.

Launchd 372ab70e retains only the required result-carrier GRANT and preserves RECV-only client copies plus complete setup retirement. All six strict 497-test configurations and original CI179/180 pass. Loaderd 5bcf522c retains the counted grant destination; four strict 145-test configurations and original CI107/108 pass. The original red tests, failed native runs and admitted host TCG diagnostic remain preserved. Docs 6a1a9686 passes the full 2,655-page manual and 45 tests locally and in original CI1085/1086; four complete CI logs total 824,660 bytes and final warnings are zero.

The configuration carrier defect, counted grant defect and configured-client stall are resolved by this component and native evidence. The Exsh fixture report retains its pending release compiler/frame validation despite the three native passes. Complete Integration CI1801/1802 is still queued. Whole-fleet authority/source/effect/frame acceptance, final accounting/profiler observation, rebuilding the external Rust/LLVM/runtime toolchain inside EriX and both full EriX guest-build generations remain open.

Original prerequisite Integration CI1793/1794 each passes 490/491 scenarios; Rust and Markdown pass, and six complete logs total 27,432,406 bytes with zero warnings. CI1794 retains the ext4 quota timeout. CI1793 instead exposes a distinct one-shot replay QMP connection loss, recorded using the canonical bug template and phase label. No original workflow was rerun, and no deadline or authority check was relaxed.

Only the existing native-witness sub-item gains credit: 15.42% weighted progress, 413/873 sub-items. Whole acceptance remains 3.86%, 17/460 parents.

The configured-client VM stalls after the same three inherited markers and a private process exit with status 5. Its original failure retains 109 artifacts and 56,130 serial bytes, zero image-warning candidates and no process-owner cleanup failure. Integration issue 92 preserves that observation. An admitted host TCG counter run against the identical guest disk reproduces the stall under the original 120/45-second bounds. Its complete capture contains 100,639 translations and 74,009 code groups. The top 100 groups cover 85.32% of the 65,912,963,324 translated-instruction upper bound; uniquely matching Kernel mapping-batch code accounts for 38.67% of that total. This is a performance investigation candidate, without a measured speedup, timing attribution or accepted native result. Shared code, addresses and process identity remain separate evidence questions.

Exact retained executable-region comparison with original symbol-bearing artifacts narrows the failure to Posixd configuration progress and its native exit; the exit block uniquely matches Posixd across all 68 packaged executables/shared objects. The source mismatch is confirmed independently: Launchd retains only RECV on its configuration receiver, while native COMPLETE requires carrier GRANT for capability-bearing client replies. Enforcing that actual gate in the maintained complete-record pull fixture fails the original implementation. Launchd issue 10 tracks the correction and original red control. The local correction retains exactly RECV | GRANT only for counted-client replies, preserves readiness-only RECV, mediator SEND-only routes and RECV-only client copies, and retains complete receiver disposal before seal/cancellation. Full component validation is running; corrected native client execution remains required.

Both original Docs CI1083/1084 pass, with 45 document tests and the 2,653-page manual. All four complete logs total 824,211 bytes; normal early-pass references converge to zero final warnings. Original Integration runs remain running or queued, without unchanged reruns. No canonical checklist credit is added: configured native clients, managed-row reuse, complete authority/frame closure, profiling improvements and both full guest-build requirements remain open.

Legacy destinations, exact source/rights/caller/relation checks, native empty-slot and capacity enforcement, and acknowledged disposal remain required.

Signed Docs ee08bab6 documents the contract. All 45 document tests pass, the full 2,653-page manual builds without final warnings, all 491,233 word bounds pass and three affected/adjacent pages are visually reviewed. Its original CI1083/1084 is under observation.

Signed Integration 04bff04f adopts those two original image sources. Both catalog policies, all 76 original signatures and complete transitive closure pass. The Cargo catalog contains neither changed component and remains unchanged. All helper, Rust, profiler and CI source bytes retain their previous validation; fresh formatting, source policy and Markdown pass. Original CI1799/1800 is queued. Fresh configured-client and older preparation/startup VM execution on this successor remains required by Loaderd issue 5; the previous two prerequisite passes and subsequent client failure remain retained.

Original Exsh CI281/282 now have complete failure logs: unit suites pass 507/478/1 and all 355 frame-checker controls pass, but both runtime profiles reach 256 functions with 101 unresolved observations and both all-feature profiles reach 286 with 68 unresolved observations. All four logs total 322,830 bytes with zero warning candidates. Exsh frame issue 4 and compiler issue 9 remain open. No unchanged CI was restarted and no acceptance bound was relaxed. These repairs add no checklist credit; native configured-client acceptance, managed-row reuse, profiling, complete authority closure and both full guest-build requirements remain open.

Guarded preparation uses the actual Posixd root with its required immutable layout, and actual private mediators reach readiness and retire independently.

The configured-client VM now passes all three inherited markers, then its first PREPARE_REALM_CLIENT request 34 (opcode 0x6d7) returns INTERNAL (5). The original failed run retains 109 artifacts and 56,226 serial bytes, with zero build-warning candidates and no process-owner cleanup failure. Loaderd issue 5 records the separate defect: the counted Launchd client producer selects its own grant column, while Loaderd's intake, handler and reply retain legacy fixed destination 645. Two independent actual-code tests reproduce intake refusal and reply redirection. A correction must preserve the exact original client destination while retaining legacy destination, source receipt, actual caller, relation and cleanup gates.

The mediator-fixture correction is demonstrated in both prerequisite VMs; Exsh issue 10 remains linked to full configured-client validation. No client execution, configuration/seal/byte-I/O acceptance, managed-row reuse, profiler observation or full guest build is claimed. Original Exsh CI281/282 is running, and original Integration CI1797/1798 is queued; earlier original Integration cohorts remain under observation. Exsh compiler/frame gates remain open, and no unchanged CI was restarted. These repairs add no canonical checklist credit.

Launchd's realm_client_loader.rs uses the original counted row's destination. Loaderd's prepare_transport.rs and prepare.rs still compare it with fixed slot 645, and prepare_response.rs always returns the grant to that fixed slot. Existing Loaderd client fixtures also select 645, so they do not exercise the actual counted producer destination. The intake rejection yields an untyped refusal, consistent with Launchd's strict typed-reply validation reporting INTERNAL; this source explanation does not claim instruction-level guest tracing.

On the same signed graph, the separate preparation-only and older two-mediator startup VMs pass all original markers and ordinary shell exit. The configured-client failure retains 109 artifacts and 56,226 serial bytes. All three image builds have zero warning candidates and no process-owner cleanup failure. The earlier mediator-fixture regression and both of its original failures remain retained.

Tracking

Loaderd feature work, Launchd feature work, Integration PR12, and phase completion.

  • Preserve the first native failure and both passing prerequisite VMs.
  • Reproduce the real counted destination against Loaderd's maintained intake and reply code.
  • Preserve the exact client destination end to end while retaining original authority, legacy destination and cleanup controls.
  • Pass strict component validation, original CI observation and corrected native client execution with unchanged guest gates.
## Summary Private realm-client preparation still requires Launchd's legacy fixed install-grant destination in Loaderd's transport intake, payload handler and success-reply encoder. Launchd's counted client producer instead reserves a distinct caller-local column, retires its received executable-directory scope, and requests the returned install grant at that exact original destination. The producer and consumer disagree before the first client can be staged. The first configured-client VM on the corrected mediator-fixture graph reaches all preceding admission, guarded-preparation and private-startup markers, then returns INTERNAL for the first PREPARE_REALM_CLIENT. The source mismatch is directly visible; a focused actual-code reproduction and corrected native run are required before claiming complete root-cause closure. ## Reproduction Use signed [Integration 9451847f](https://git.erikinkinen.fi/erix/integration/commit/9451847fbff64d10a0d56dd673e8a238110d7ac1) and its complete original catalog, then run: ```sh bash scripts/run-scenario.sh tests/scenarios/appliance-disk-image-realm-clients-positive.toml components.toml ``` The original guest deadline is 120 seconds and the serial-progress deadline is 45 seconds. The first local execution fails; no unchanged retry or deadline adjustment was used. ## Expected and actual behavior The authenticated private client operation must retain the original explicit caller-local grant destination through intake, materialization and the single install-grant MOVE reply. The existing source endpoint, exact SEND receipt, supervisor, full realm/mediator relation and original cleanup owners remain mandatory. Legacy ordinary-child and mediator destinations must retain their existing contracts; there is no ordinary-launch fallback or additional grant. Actual serial output reaches all three preceding verified markers, then reports: ```text ERIX_EXSH:REALM_ADMISSION:FAILED request=00000022 kind=0000000b first=000006d7 second=00000005 ``` Request 34, opcode 0x6d7, is the first private-client preparation and returns INTERNAL (5). No client has started, and no configured-client success marker or full guest build is established. The original bounded runner ends with status 1. ## Environment and identity - Integration: `9451847fbff64d10a0d56dd673e8a238110d7ac1`. - Exsh: `f36b1f51f138f4c5c56fcac45a881731d0471c81`. - Loaderd: `e0562cdc6a52b518ea7fe34341a49f57caa9b1d8`. - Launchd: `0b0788b5530ce7607097eee97babe22e71d8c1b9`. - Original 76-repository graph, release x86_64 appliance, one CPU; explicit two-realm/four-client policy with 576 plan bytes and existing shell routes only. ## Evidence and prior checks Native configured-client acceptance — 25 September 2026: the exact signed [Integration 7a42fa26](https://git.erikinkinen.fi/erix/integration/commit/7a42fa2663bda878edcf59de01d972dd20c58ec7) graph passes the configured-client, preparation and startup VMs with all original markers, deadlines and cleanup gates. The configured witness seals two isolated realms, observes six successful byte-client exits across three realm instances, checks independent retirement, rejects stale client selectors and reuses a Launchd realm record with a new generation. This proves the native configure/seal/publish/mediated-I/O criterion; full Procd managed-row/final CPU reclamation, supervisor loss and resource ceilings remain separate requirements. [Launchd 372ab70e](https://git.erikinkinen.fi/erix/launchd/commit/372ab70ea2ea1133a9bc3edb2cb621f9679b075d) retains only the required result-carrier GRANT and preserves RECV-only client copies plus complete setup retirement. All six strict 497-test configurations and original CI179/180 pass. [Loaderd 5bcf522c](https://git.erikinkinen.fi/erix/loaderd/commit/5bcf522cfec873fa29ffe1b91bde1bf67e9f5ba2) retains the counted grant destination; four strict 145-test configurations and original CI107/108 pass. The original red tests, failed native runs and admitted host TCG diagnostic remain preserved. [Docs 6a1a9686](https://git.erikinkinen.fi/erix/docs/commit/6a1a96869736030727d0366c3e7622993dded7ff) passes the full 2,655-page manual and 45 tests locally and in original CI1085/1086; four complete CI logs total 824,660 bytes and final warnings are zero. The [configuration carrier defect](https://git.erikinkinen.fi/erix/launchd/issues/10), [counted grant defect](https://git.erikinkinen.fi/erix/loaderd/issues/5) and [configured-client stall](https://git.erikinkinen.fi/erix/integration/issues/92) are resolved by this component and native evidence. The [Exsh fixture report](https://git.erikinkinen.fi/erix/exsh/issues/10) retains its pending release compiler/frame validation despite the three native passes. Complete Integration CI1801/1802 is still queued. Whole-fleet authority/source/effect/frame acceptance, final accounting/profiler observation, rebuilding the external Rust/LLVM/runtime toolchain inside EriX and both full EriX guest-build generations remain open. Original prerequisite Integration CI1793/1794 each passes 490/491 scenarios; Rust and Markdown pass, and six complete logs total 27,432,406 bytes with zero warnings. CI1794 retains the [ext4 quota timeout](https://git.erikinkinen.fi/erix/integration/issues/18). CI1793 instead exposes a distinct [one-shot replay QMP connection loss](https://git.erikinkinen.fi/erix/integration/issues/93), recorded using the canonical bug template and phase label. No original workflow was rerun, and no deadline or authority check was relaxed. Only the existing native-witness sub-item gains credit: **15.42% weighted progress**, 413/873 sub-items. Whole acceptance remains **3.86%, 17/460 parents**. The configured-client VM stalls after the same three inherited markers and a private process exit with status 5. Its original failure retains 109 artifacts and 56,130 serial bytes, zero image-warning candidates and no process-owner cleanup failure. [Integration issue 92](https://git.erikinkinen.fi/erix/integration/issues/92) preserves that observation. An admitted host TCG counter run against the identical guest disk reproduces the stall under the original 120/45-second bounds. Its complete capture contains 100,639 translations and 74,009 code groups. The top 100 groups cover 85.32% of the 65,912,963,324 translated-instruction upper bound; uniquely matching Kernel mapping-batch code accounts for 38.67% of that total. This is a performance investigation candidate, without a measured speedup, timing attribution or accepted native result. Shared code, addresses and process identity remain separate evidence questions. Exact retained executable-region comparison with original symbol-bearing artifacts narrows the failure to Posixd configuration progress and its native exit; the exit block uniquely matches Posixd across all 68 packaged executables/shared objects. The source mismatch is confirmed independently: Launchd retains only RECV on its configuration receiver, while native COMPLETE requires carrier GRANT for capability-bearing client replies. Enforcing that actual gate in the maintained complete-record pull fixture fails the original implementation. [Launchd issue 10](https://git.erikinkinen.fi/erix/launchd/issues/10) tracks the correction and original red control. The local correction retains exactly RECV | GRANT only for counted-client replies, preserves readiness-only RECV, mediator SEND-only routes and RECV-only client copies, and retains complete receiver disposal before seal/cancellation. Full component validation is running; corrected native client execution remains required. Both original Docs CI1083/1084 pass, with 45 document tests and the 2,653-page manual. All four complete logs total 824,211 bytes; normal early-pass references converge to zero final warnings. Original Integration runs remain running or queued, without unchanged reruns. No canonical checklist credit is added: configured native clients, managed-row reuse, complete authority/frame closure, profiling improvements and both full guest-build requirements remain open. Legacy destinations, exact source/rights/caller/relation checks, native empty-slot and capacity enforcement, and acknowledged disposal remain required. Signed [Docs ee08bab6](https://git.erikinkinen.fi/erix/docs/commit/ee08bab65e29dd6c3c3781f1b361070a99d7325b) documents the contract. All 45 document tests pass, the full 2,653-page manual builds without final warnings, all 491,233 word bounds pass and three affected/adjacent pages are visually reviewed. Its original CI1083/1084 is under observation. Signed [Integration 04bff04f](https://git.erikinkinen.fi/erix/integration/commit/04bff04f4328676ba8205f7ac2b0df64213698a0) adopts those two original image sources. Both catalog policies, all 76 original signatures and complete transitive closure pass. The Cargo catalog contains neither changed component and remains unchanged. All helper, Rust, profiler and CI source bytes retain their previous validation; fresh formatting, source policy and Markdown pass. Original CI1799/1800 is queued. Fresh configured-client and older preparation/startup VM execution on this successor remains required by [Loaderd issue 5](https://git.erikinkinen.fi/erix/loaderd/issues/5); the previous two prerequisite passes and subsequent client failure remain retained. Original Exsh CI281/282 now have complete failure logs: unit suites pass 507/478/1 and all 355 frame-checker controls pass, but both runtime profiles reach 256 functions with 101 unresolved observations and both all-feature profiles reach 286 with 68 unresolved observations. All four logs total 322,830 bytes with zero warning candidates. [Exsh frame issue 4](https://git.erikinkinen.fi/erix/exsh/issues/4) and [compiler issue 9](https://git.erikinkinen.fi/erix/exsh/issues/9) remain open. No unchanged CI was restarted and no acceptance bound was relaxed. These repairs add no checklist credit; native configured-client acceptance, managed-row reuse, profiling, complete authority closure and both full guest-build requirements remain open. Guarded preparation uses the actual Posixd root with its required immutable layout, and actual private mediators reach readiness and retire independently. The configured-client VM now passes all three inherited markers, then its first PREPARE_REALM_CLIENT request 34 (opcode 0x6d7) returns INTERNAL (5). The original failed run retains 109 artifacts and 56,226 serial bytes, with zero build-warning candidates and no process-owner cleanup failure. [Loaderd issue 5](https://git.erikinkinen.fi/erix/loaderd/issues/5) records the separate defect: the counted Launchd client producer selects its own grant column, while Loaderd's intake, handler and reply retain legacy fixed destination 645. Two independent actual-code tests reproduce intake refusal and reply redirection. A correction must preserve the exact original client destination while retaining legacy destination, source receipt, actual caller, relation and cleanup gates. The mediator-fixture correction is demonstrated in both prerequisite VMs; [Exsh issue 10](https://git.erikinkinen.fi/erix/exsh/issues/10) remains linked to full configured-client validation. No client execution, configuration/seal/byte-I/O acceptance, managed-row reuse, profiler observation or full guest build is claimed. Original Exsh CI281/282 is running, and original Integration CI1797/1798 is queued; earlier original Integration cohorts remain under observation. Exsh compiler/frame gates remain open, and no unchanged CI was restarted. These repairs add no canonical checklist credit. Launchd's `realm_client_loader.rs` uses the original counted row's destination. Loaderd's `prepare_transport.rs` and `prepare.rs` still compare it with fixed slot 645, and `prepare_response.rs` always returns the grant to that fixed slot. Existing Loaderd client fixtures also select 645, so they do not exercise the actual counted producer destination. The intake rejection yields an untyped refusal, consistent with Launchd's strict typed-reply validation reporting INTERNAL; this source explanation does not claim instruction-level guest tracing. On the same signed graph, the separate preparation-only and older two-mediator startup VMs pass all original markers and ordinary shell exit. The configured-client failure retains 109 artifacts and 56,226 serial bytes. All three image builds have zero warning candidates and no process-owner cleanup failure. The earlier [mediator-fixture regression](https://git.erikinkinen.fi/erix/exsh/issues/10) and both of its original failures remain retained. ## Tracking [Loaderd feature work](https://git.erikinkinen.fi/erix/loaderd/issues/1), [Launchd feature work](https://git.erikinkinen.fi/erix/launchd/issues/1), [Integration PR12](https://git.erikinkinen.fi/erix/integration/pulls/12), and [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65). - [x] Preserve the first native failure and both passing prerequisite VMs. - [x] Reproduce the real counted destination against Loaderd's maintained intake and reply code. - [x] Preserve the exact client destination end to end while retaining original authority, legacy destination and cleanup controls. - [x] Pass strict component validation, original CI observation and corrected native client execution with unchanged guest gates.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:01 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/loaderd#5
No description provided.