Skip to content

Add HVF policy rollover parity #5393

Open

Description

@auser

Parent and dependency

#5386. Follow #5391 and the first live Firecracker cutover slice. HVF is an explicit second target, not an optional afterthought.

Outcome

The same committed-policy and host-interface cutover contract works for HVF on supported macOS hardware. Put backend-specific prepare/fence/stop under existing backend contracts, not a second CLI coordinator; remain NIC-less and keep its tier-specific claims unchanged.

Acceptance

  • Prepare an isolated HVF replacement with the candidate policy, complete signed admission and applicable readiness, and fence old effects before sole-owner handoff.
  • Recover/typed-refuse interrupted or failed handoffs; no two active owners for one policy epoch, mailbox, endpoint or host route.
  • Test candidate failure, missing enforcement, in-flight effects, policy/source tamper, stale epoch, quota exhaustion, cleanup/stop failure; witness a real macOS HVF lifecycle on supported hardware.
  • Measure admission-inclusive readiness and cutover downtime separately; do not claim zero downtime without evidence.
  • Update backend matrix/docs with observed status; leave parent/all-backend work open until the remaining targets pass.
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