[BUG] Empty configuration CLAIM aborts private realm startup #5

Open
opened 2026-09-24 20:00:10 +02:00 by erikinkinen · 0 comments
Owner

Summary

Private realm startup treats the Kernel's normal empty configuration-queue result as a permanent failure. Kernel CLAIM returns NOT_FOUND with delivery owner zero when no invocation is queued; Launchd recognizes only RETRY with owner zero as idle. It records NativeStatus(3), retires its retained owners, and can return a typed public START refusal.

The changed-image native scenario reaches the actual Posixd PREPARE successfully, then receives NOT_FOUND for START. The source defect matches that result. The guest does not emit an internal bootstrap-stage trace, so this report does not claim direct observation of the precise failing instruction.

Reproduction

At Integration fa857c0964774def6777142afeb7a3c16440abee and Launchd eb2a1eedabe66e01ab0eb8c630d2f06ecb67b68d, run the original selected native scenario:

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

The smaller deterministic trigger is a registered, currently empty configuration receiver during Provision, Start or Ready. Return the actual native empty CLAIM pair (IPC_RESULT_NOT_FOUND, 0) before the next ContextProbe/Ready delivery, including the normal interval after completing ContextProbe while the producer retires its caller. The original host fixture instead supplied only (IPC_RESULT_RETRY, 0) for idle intake.

Expected and actual behavior

A zero-owner empty CLAIM must preserve the retained bootstrap and allow independent producer/configuration progress. Every nonzero returned delivery must remain owned even if its status is erroneous. Other failures must remain failures; no additional authority or wire change is needed.

The original native receipt contains:

ERIX_EXSH:REALM_ADMISSION:VERIFIED
ERIX_EXSH:REALM_PREPARATION:VERIFIED
ERIX_EXSH:REALM_ADMISSION:FAILED request=00000013 kind=0000000b first=000006d4 second=00000003

Request 0x13, operation 0x6D4 (START), receives a valid typed rejection with NOT_FOUND (3). The startup marker is absent. Exsh's endpoint 0x520 exits 0xE5; that status is not evidence of a Launchd process-event exit. Rootd later exits 0xDC. The scenario returns 1, and its unchanged 45-second progress watchdog terminates QEMU. No native readiness or retirement acceptance is established.

Environment and identity

  • Integration fa857c0964774def6777142afeb7a3c16440abee; Launchd eb2a1eedabe66e01ab0eb8c630d2f06ecb67b68d; Procd d04311abff67e7355bd92bb2e48fb6161e0ec674; Posixd 809647d60544c4c6121868c99133f30d054965c9; Kernel 5e285aa91a1423523b2a094d4ce0449ada39b16c.
  • Release native x86-64 QEMU/OVMF image, development runtime configuration, one virtual CPU, Rust 1.97.1. Original hard limit: 120 seconds; progress watchdog: 45 seconds.
  • Retained post-VM disk SHA-256: 95c48dc71a5d7fd0f1282d33e68f86ed2997d5be529f518f50e53efa2d6baf0d. The runner uses a writable disk; this digest does not assert equality with preboot bytes.
  • Serial log: 56,013 bytes, SHA-256 803bd99106573710f28ffb2d2a994f22c8d24fb29910447e5cc643c8ed498aef. Image construction recorded no warnings.
  • Existing scoped executable preparation and explicitly guarded configuration route only; no ordinary launch sidecar, global fallback or extra client grant. Last known working revision is unestablished.

Evidence and prior checks

Kernel queued lookup returns NOT_FOUND for an empty registered queue. Server CLAIM propagates it; wire rejection returns a zero owner.

Launchd configuration intake accepts only RETRY/zero as idle. Bounded progress retains the failure and starts cleanup; the public result mapping preserves native status 3. Procd's existing owned receiver already treats zero-owner RETRY or NOT_FOUND as idle.

The original failed run and complete serial evidence remain retained. No unchanged-image retry or timeout relaxation was used. The source correction and strict validation described below are complete. Changed-source native validation remains pending.

Signed correction cf6d4a70d5423dca65bbab5e8092fd374184c4ed treats only zero-owner NOT_FOUND or RETRY as idle. The native-faithful fixture now defaults to NOT_FOUND; regression controls cover both empty statuses and preserve erroneous nonzero owners. All 12 focused startup controls pass. The complete default, all-feature and runtime-feature development/release matrix passes 329 library and 67 runtime tests in each of six configurations, with formatting, strict host/native Clippy, warning-denied native builds, host/native rustdoc and documentation/dependency checks reporting zero warnings.

Both original exact-head CI runs, 153 and 154, passed. Their complete Rust and Markdown logs were reviewed with no warning or failure candidates. Integration 8f9b7d752c4769e3017aa4116ad0a542f54f488b selects the signed correction. Actual changed-image startup, readiness and independent retirement remain pending; this issue remains open.

Tracking

Launchd lifecycle audit, Launchd PR 2, Posixd realm lifecycle, Integration validation, and Phase 6 completion. The previous private preparation defect is a separate failure now passed by this receipt; the WAIT decoder defect is not assigned as this START failure's cause.

  • Reproduce zero-owner native NOT_FOUND with a regression control against the failing source, including normal empty intervals between bootstrap messages.
  • Treat only zero-owner NOT_FOUND or RETRY as idle, preserving all nonzero handle custody and other errors.
  • Complete formatting, strict Clippy, unit tests and warning-denied host/native build and documentation checks.
  • Pass the unchanged actual Posixd startup/readiness/independent-retirement scenario after adopting the correction before closing native acceptance.

Baseline regression reproduced against unchanged production: cargo test --locked --offline --all-targets empty_configuration_claims_preserve_private_start_progress -- --nocapture returns 101 with one failing control. The native-faithful empty-queue result produces public START result 3 instead of successful progress. This is host reproduction evidence, not a corrected matrix or native acceptance. Original failure output and source identity remain retained.

## Summary Private realm startup treats the Kernel's normal empty configuration-queue result as a permanent failure. Kernel CLAIM returns `NOT_FOUND` with delivery owner zero when no invocation is queued; Launchd recognizes only `RETRY` with owner zero as idle. It records `NativeStatus(3)`, retires its retained owners, and can return a typed public START refusal. The changed-image native scenario reaches the actual Posixd PREPARE successfully, then receives `NOT_FOUND` for START. The source defect matches that result. The guest does not emit an internal bootstrap-stage trace, so this report does not claim direct observation of the precise failing instruction. ## Reproduction At Integration `fa857c0964774def6777142afeb7a3c16440abee` and Launchd `eb2a1eedabe66e01ab0eb8c630d2f06ecb67b68d`, run the original selected native scenario: ```sh bash scripts/run-scenario.sh tests/scenarios/appliance-disk-image-realm-startup-positive.toml components.toml ``` The smaller deterministic trigger is a registered, currently empty configuration receiver during Provision, Start or Ready. Return the actual native empty CLAIM pair `(IPC_RESULT_NOT_FOUND, 0)` before the next ContextProbe/Ready delivery, including the normal interval after completing ContextProbe while the producer retires its caller. The original host fixture instead supplied only `(IPC_RESULT_RETRY, 0)` for idle intake. ## Expected and actual behavior A zero-owner empty CLAIM must preserve the retained bootstrap and allow independent producer/configuration progress. Every nonzero returned delivery must remain owned even if its status is erroneous. Other failures must remain failures; no additional authority or wire change is needed. The original native receipt contains: ```text ERIX_EXSH:REALM_ADMISSION:VERIFIED ERIX_EXSH:REALM_PREPARATION:VERIFIED ERIX_EXSH:REALM_ADMISSION:FAILED request=00000013 kind=0000000b first=000006d4 second=00000003 ``` Request `0x13`, operation `0x6D4` (START), receives a valid typed rejection with `NOT_FOUND` (`3`). The startup marker is absent. Exsh's endpoint `0x520` exits `0xE5`; that status is not evidence of a Launchd process-event exit. Rootd later exits `0xDC`. The scenario returns 1, and its unchanged 45-second progress watchdog terminates QEMU. No native readiness or retirement acceptance is established. ## Environment and identity - Integration `fa857c0964774def6777142afeb7a3c16440abee`; Launchd `eb2a1eedabe66e01ab0eb8c630d2f06ecb67b68d`; Procd `d04311abff67e7355bd92bb2e48fb6161e0ec674`; Posixd `809647d60544c4c6121868c99133f30d054965c9`; Kernel `5e285aa91a1423523b2a094d4ce0449ada39b16c`. - Release native x86-64 QEMU/OVMF image, development runtime configuration, one virtual CPU, Rust 1.97.1. Original hard limit: 120 seconds; progress watchdog: 45 seconds. - Retained post-VM disk SHA-256: `95c48dc71a5d7fd0f1282d33e68f86ed2997d5be529f518f50e53efa2d6baf0d`. The runner uses a writable disk; this digest does not assert equality with preboot bytes. - Serial log: 56,013 bytes, SHA-256 `803bd99106573710f28ffb2d2a994f22c8d24fb29910447e5cc643c8ed498aef`. Image construction recorded no warnings. - Existing scoped executable preparation and explicitly guarded configuration route only; no ordinary launch sidecar, global fallback or extra client grant. Last known working revision is unestablished. ## Evidence and prior checks [Kernel queued lookup](https://git.erikinkinen.fi/erix/kernel/src/commit/5e285aa91a1423523b2a094d4ce0449ada39b16c/src/kobj/endpoint/invocation/table.rs#L145) returns `NOT_FOUND` for an empty registered queue. [Server CLAIM](https://git.erikinkinen.fi/erix/kernel/src/commit/5e285aa91a1423523b2a094d4ce0449ada39b16c/src/kobj/endpoint/invocation/server.rs#L24) propagates it; [wire rejection](https://git.erikinkinen.fi/erix/kernel/src/commit/5e285aa91a1423523b2a094d4ce0449ada39b16c/src/kobj/endpoint/invocation/wire.rs#L103) returns a zero owner. [Launchd configuration intake](https://git.erikinkinen.fi/erix/launchd/src/commit/eb2a1eedabe66e01ab0eb8c630d2f06ecb67b68d/src/realm_start_server.rs#L31) accepts only `RETRY`/zero as idle. [Bounded progress](https://git.erikinkinen.fi/erix/launchd/src/commit/eb2a1eedabe66e01ab0eb8c630d2f06ecb67b68d/src/realm_start_progress.rs#L27) retains the failure and starts cleanup; the [public result mapping](https://git.erikinkinen.fi/erix/launchd/src/commit/eb2a1eedabe66e01ab0eb8c630d2f06ecb67b68d/src/runtime/realm_reply.rs#L117) preserves native status 3. Procd's existing owned receiver already treats zero-owner `RETRY` or `NOT_FOUND` as idle. The original failed run and complete serial evidence remain retained. No unchanged-image retry or timeout relaxation was used. The source correction and strict validation described below are complete. Changed-source native validation remains pending. Signed correction [cf6d4a70d5423dca65bbab5e8092fd374184c4ed](https://git.erikinkinen.fi/erix/launchd/commit/cf6d4a70d5423dca65bbab5e8092fd374184c4ed) treats only zero-owner `NOT_FOUND` or `RETRY` as idle. The native-faithful fixture now defaults to `NOT_FOUND`; regression controls cover both empty statuses and preserve erroneous nonzero owners. All 12 focused startup controls pass. The complete default, all-feature and runtime-feature development/release matrix passes 329 library and 67 runtime tests in each of six configurations, with formatting, strict host/native Clippy, warning-denied native builds, host/native rustdoc and documentation/dependency checks reporting zero warnings. Both original exact-head CI runs, [153](https://git.erikinkinen.fi/erix/launchd/actions/runs/153) and [154](https://git.erikinkinen.fi/erix/launchd/actions/runs/154), passed. Their complete Rust and Markdown logs were reviewed with no warning or failure candidates. Integration [8f9b7d752c4769e3017aa4116ad0a542f54f488b](https://git.erikinkinen.fi/erix/integration/commit/8f9b7d752c4769e3017aa4116ad0a542f54f488b) selects the signed correction. Actual changed-image startup, readiness and independent retirement remain pending; this issue remains open. ## Tracking [Launchd lifecycle audit](https://git.erikinkinen.fi/erix/launchd/issues/1), [Launchd PR 2](https://git.erikinkinen.fi/erix/launchd/pulls/2), [Posixd realm lifecycle](https://git.erikinkinen.fi/erix/posixd/issues/1), [Integration validation](https://git.erikinkinen.fi/erix/integration/issues/3), and [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). The previous [private preparation defect](https://git.erikinkinen.fi/erix/launchd/issues/4) is a separate failure now passed by this receipt; the [WAIT decoder defect](https://git.erikinkinen.fi/erix/launchd/issues/3) is not assigned as this START failure's cause. - [x] Reproduce zero-owner native `NOT_FOUND` with a regression control against the failing source, including normal empty intervals between bootstrap messages. - [x] Treat only zero-owner `NOT_FOUND` or `RETRY` as idle, preserving all nonzero handle custody and other errors. - [x] Complete formatting, strict Clippy, unit tests and warning-denied host/native build and documentation checks. - [ ] Pass the unchanged actual Posixd startup/readiness/independent-retirement scenario after adopting the correction before closing native acceptance. Baseline regression reproduced against unchanged production: `cargo test --locked --offline --all-targets empty_configuration_claims_preserve_private_start_progress -- --nocapture` returns 101 with one failing control. The native-faithful empty-queue result produces public START result 3 instead of successful progress. This is host reproduction evidence, not a corrected matrix or native acceptance. Original failure output and source identity remain retained.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:31 +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/launchd#5
No description provided.