Repository navigation
feat(minvmd): extend per-VM gvproxy to full PTask switch with vsock shuttle (DM1/DM3/DM4) #497
Description
Task
repo: gominimal/minimal
spec: docs/specs/03-spec-networking/03-spec-networking.md
requirements: R1.4, R1.5, R1.8
files in scope:
- crates/minvmd/src/vm.rs — remove "no network device in v0.1" comment; add
network_mode: NetworkModetoVmConfig; extend gvproxy child to serve as shared per-PTask switch - crates/minvmd/src/net.rs (new) —
spawn_gvproxy, per-PTask vsock shuttle setup,VmEgressPolicystub aligned with Unit 2 types; structured tracing events (R1.8) - crates/minvmd/src/lifecycle.rs — reuse
StartingGuardRAII pattern for gvproxy child supervision
proof artifacts: - Test:
cargo test -p minvmdpasses withVmConfig.network_mode: NetworkModefield present — demonstrates DM1/DM3/DM4 type structure compiles. Fails on base (field absent). - [Deferred to Networking switch hardening: subnet validation, exit-channel semantics, attached_count, tokio::fs (minvmd+minimald) #526] Test:
cargo test -p minvmd -- --include-ignored(hardware,#[ignore]by default, gated onMINVMD_INTEGRATION_TESTenv var): starts a libkrun VM with anOwnIpPTask and asserts the PTask's netns is assigned an IP from the switch subnet via vsock shuttle — demonstrates DM1 switch attachment. This proof depends on the vsock fd-pass attachment mechanism, which is not delivered by the PR that closes this task; it is re-scoped to Networking switch hardening: subnet validation, exit-channel semantics, attached_count, tokio::fs (minvmd+minimald) #526 along with the relay/attachment plumbing (see Proof re-scope below).
verification: - cargo test -p minvmd
- cargo fmt && cargo test -- --include-ignored
- cargo clippy --allow-dirty --fix --all-targets -- -D warnings
depends on: - blocked by feat(sandbox2,minimald-rpc,sessions): introduce trimodal NetworkMode enum and vendor gvproxy source #495
Related to Unit 1: gvproxy switch and PTask network modes (UC1, UC6) #492
Proof re-scope (2026-06-22)
The PR closing this task (#522) delivers the gvproxy switch supervisor (spawn / async teardown / unexpected-exit watchdog) and the in-memory IP allocator, verified by Proof 1 (cargo test -p minvmd, covered by consumer CI cargo nextest run --workspace).
Proof 2 — the #[ignore] DM1 vsock IP-assignment test — depends on the per-PTask vsock fd-pass + TAP/relay attachment mechanism, which is deferred to #526. The test and its CI gate (ci-linux-kvm.yml DM1 step) land there, not here. This task's delivered/verified contract is therefore Proof 1 only; Proof 2 is tracked and verified under #526.
Generated by sdd-triage-materialize for issue #478 · ◷
Activity
gominimal-aw-bot commentedon Jun 21, 2026
/execute
norrietaylor commentedon Jun 22, 2026
/execute
feat(minvmd): extend per-VM gvproxy to full PTask switch with vsock s…
gominimal-aw-bot commentedon Jun 22, 2026
Pull request created: #522
ci(kvm): add gated DM1 vsock-shuttle proof step (U1-T3 #497)
fix(minvmd): make gvproxy switch teardown async and detect exit
norrietaylor commentedon Jun 22, 2026
Re-scoped the declared proofs: Proof 2 (the
#[ignore]DM1 vsock IP-assignment test) is deferred to #526 along with the vsock fd-pass + TAP/relay attachment it depends on. #522 (closing this task) delivers the switch supervisor + IP allocator, verified by Proof 1 via consumer CI. This closes the declared-vs-delivered gap that sdd-validate flagged on #522.