You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#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.
Activity