Skip to content

fix(vmm): reap VM launcher children on SvStop - #858

Merged
kvinwang merged 3 commits into
masterfrom
codex/fix-vmm-svstop-child-reaping
Aug 3, 2026
Merged

fix(vmm): reap VM launcher children on SvStop#858
kvinwang merged 3 commits into
masterfrom
codex/fix-vmm-svstop-child-reaping

Conversation

@kvinwang

@kvinwang kvinwang commented Jul 31, 2026

Copy link
Copy Markdown
Collaborator

Problem

SvStop stopped VM services without reaping their launcher child processes. Repeated stop/start operations could leave zombies and stale launcher state even though VMM reported the VM stopped.

Root cause and fix

Wait for and reap launcher children as part of SvStop, preserving the launcher exit result instead of orphaning the process.

Implementation

The branch records the following focused implementation work:

  • fix(vmm): reap VM launcher children on SvStop
  • fix(vmm): keep SvStop unknown IDs rejected

Changed paths:

  • dstack/supervisor/src/process.rs
  • dstack/vmm/src/app.rs
  • dstack/vmm/src/main_service.rs

Scope

This PR addresses one logical vmm finding. It intentionally excludes the acceptance-test infrastructure from #841 and unrelated product fixes from #840.

Dependency and merge order

This PR is based directly on master and does not require another split product PR to merge first.

Verification

  • git diff --check origin/master..origin/codex/fix-vmm-svstop-child-reaping: passed.
  • The declared base was verified as an ancestor of the PR head.
  • Focused compile/check verification was run for the changed component where applicable; non-Rust packaging or configuration changes were reviewed against their exact branch delta.

Copilot AI review requested due to automatic review settings July 31, 2026 02:43

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

Overwriting Exited(code)/Error states with Stopped on SvStop masked
crash diagnostics in sv_list and clobbered the exit timestamp the wait
task had recorded. Narrow the normalization to Exited(0) so an explicit
stop still reads as stopped while non-zero exit codes and error states
stay visible.
@kvinwang
kvinwang merged commit a7b393b into master Aug 3, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants