Skip to content

Prove bounded Linux sealed read leases at the VMM #5422

Open

Description

@auser

Scope

Build and test one bounded x86_64 Linux immutable read-lease provider under the reviewed TrustedSnapshotService owner API. Governing program #5415, architecture #5413 and typed API issue #5419. The first supported fixture may use page-budgeted sealed memfds; fs-verity for larger rootfs files requires its own independently validated provider before selection, not a silent fallback.

Acceptance

  • Publish exact authenticated kernel/rootfs/runtime bytes under a reservation; enforce seal refusal, RAM/FD/parent quota and generation identity. A read lease owns held descriptors; mutation, stale handle, pathname replacement, incompatible closure and budget exhaustion refuse without claiming warm readiness.
  • Keep the provider choice fixed at publication and preserve owner crash/restart cleanup semantics. Do not use chmod, reflink, a mutable sidecar or an unverified /proc/self/fd pathname as authority.
  • On a named x86_64 KVM/Firecracker host, witness sealed object identity through the scoped launcher and VMM open, not only a direct-VMM test; negative tests cover changed path, seal failure, descriptor reuse, exhaustion and cleanup failure. Measure staging/publication apart from launch.

Context and validation

Read landed preview ADR-059 and merged #5407, crates/mvm-runtime/src/trusted_snapshot_service.rs, crates/mvm-fs/src/trusted_snapshot.rs and existing Firecracker descriptor handoff. The PR-only arm64 sealed-memfd probe is feasibility evidence, not claim-time custody. Run focused filesystem/runtime tests, cargo clippy --workspace -- -D warnings, just check::gated when Linux-gated tests/types change, cargo run -p xtask -- check-all; record exact host/backend live evidence separately. Unsupported platforms continue refusing warm claims.

Depends on: #5419 typed owner API implemented. Independent of: build-lock and producer tracks. Warm VMM-lifetime claim integration depends on this live provider witness.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions