RFC 0002: Add cubesandbox provider (lifecycle-capable, Cloud Hypervisor microVM) - #136
Open
JackWeiw wants to merge 1 commit into
Open
RFC 0002: Add cubesandbox provider (lifecycle-capable, Cloud Hypervisor microVM)#136JackWeiw wants to merge 1 commit into
JackWeiw wants to merge 1 commit into
Conversation
…ervisor microVM) Draft RFC 0002 proposes a new env_provider backend driven by the native cubesandbox SDK (Cloud Hypervisor / KVM microVM, Tencent Cloud). It implements LifecycleCapable/EphemeralCapable/SnapshotSizeCapable so all three replay modes (exec_only/lifecycle/trajectory) work with --provider cubesandbox, mirroring aenv on a different VMM. Host-level vm_monitor (cube-hypervisor type) and real snapshot-size attribution are deferred follow-ons; the contract and kernel stay untouched except two one-line registrations.
This was referenced Sep 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Draft RFC 0002 for a new
cubesandboxprovider undersrc/env_provider/— the second lifecycle-capable backend alongsideaenv, driven by the nativecubesandboxPython SDK (Cloud Hypervisor / KVM microVM, Tencent Cloud).Implements all three replay Protocols (
LifecycleCapablepause/resume with memory snapshot,EphemeralCapablecreate_one/kill_one,SnapshotSizeCapable), so every replay mode (exec_only/lifecycle/trajectory) works with--provider cubesandbox, on a different VMM than aenv/e2b (Firecracker).BaseSandboxManagerstructure. (Alternatives B/C in the RFC.)vm_monitor(cube-hypervisortype), real VM-id parsing, NUMA binding, realsnapshot_sizesattribution — documented follow-ons.BaseSandboxManager,ReadyCheckerunchanged except two one-line registrations (_build_provider+ CLI--providerchoices).Snapshot-size / CubeCoW-path / VMM-process-name questions stay Unresolved (CubeSandbox not yet deployed — verified at implementation time).
Full design, drawbacks, alternatives, and open questions in
docs/rfcs/0002-cubesandbox-provider.md.Status
Draft — open for discussion per
docs/rfcs/README.md. On acceptance the file keeps0002and status flips to Active (index row added).Stacked implementation PRs will follow on top of this branch.