feat(runtime): fill MicroVMRuntime lifecycle methods (RIG-2493) - #719
Open
rigel-mintaka wants to merge 1 commit into
Open
Conversation
This was referenced Aug 28, 2026
|
Compass engineering docs preview: https://compass-runner-rig-2493-u4-m.compass-eng-docs.pages.dev Deployed from |
rigel-mintaka
force-pushed
the
compass-runner/rig-2493-u4-microvm-lifecycle
branch
2 times, most recently
from
August 28, 2026 07:15
c4480be to
56eed91
Compare
rigel-mintaka
force-pushed
the
compass-runner/rig-2493-u3-host-exec
branch
from
August 28, 2026 10:09
869399a to
81856f8
Compare
rigel-mintaka
force-pushed
the
compass-runner/rig-2493-u4-microvm-lifecycle
branch
from
August 28, 2026 10:11
56eed91 to
b95a89a
Compare
U4 of the frozen microVM Runner V2b plan (docs/designs/infra/runtime/compass-elastic-session-runtime/microvm-v2b-guest-supervisor-exec.md, Plan U4 / (c)/(d)/(e)). Fills the eight typed-error MicroVMRuntime stubs behind their frozen ContainerRuntime signatures against the V2a boot harness + the U3 GuestExec layer.
### Socket-path budget (CI fix, folded)
`e2eConfig` built its runroot with `t.TempDir()`, whose path embeds the test-function name. Under the 39-char `TestMicroVMExecStreamingKillSignalsExit` the widest per-session socket path — `<RunRoot>/microvm/<32-hex id>/virtiofsd.sock`, a 56-byte tail — reached 114 bytes, over the 107-byte Linux AF_UNIX `sun_path` cap, so virtiofsd's `bind(2)` failed EINVAL, the socket never appeared, and the boot timed out (`… did not appear within 10s`). `TestMicroVMLifecycleEndToEnd` (28-char name, 103 bytes) fit and booted. Production runroots are short and startup-budget-checked (`run.go` validateRuntimeDir); this is a pure harness artifact. Fix: `e2eConfig` uses a short `os.MkdirTemp("", "cvm")` runroot (cleaned via `t.Cleanup`), keeping the worst-case path well under the cap.
Refs RIG-2493
Co-authored-by: Matt Wilkinson <matt@rigel.build>
rigel-mintaka
force-pushed
the
compass-runner/rig-2493-u3-host-exec
branch
from
August 28, 2026 11:09
81856f8 to
417292b
Compare
rigel-mintaka
force-pushed
the
compass-runner/rig-2493-u4-microvm-lifecycle
branch
from
August 28, 2026 11:11
b95a89a to
9f07047
Compare
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.
This PR is part of a stack containing 5 PRs:
mainU4 of the frozen microVM Runner V2b plan (docs/designs/infra/runtime/compass-elastic-session-runtime/microvm-v2b-guest-supervisor-exec.md, Plan U4 / (c)/(d)/(e)). Fills the eight typed-error MicroVMRuntime stubs behind their frozen ContainerRuntime signatures against the V2a boot harness + the U3 GuestExec layer.
Refs RIG-2493
Co-authored-by: Matt Wilkinson matt@rigel.build