oxidecomputer / oxidecomputer/omicron
Stopping VMMs mid-migration seems buggy, a little unexplored
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
https://github.com/oxidecomputer/omicron/issues/8755 has a lot more context, in particular:
https://github.com/oxidecomputer/omicron/issues/8755#issuecomment-5332927871
and
https://github.com/oxidecomputer/omicron/issues/8755#issuecomment-5333712500
In summary:
- Migrating instances can be stopped
- We don't actually try to tell the target to stop
- It's not clear to us propolis-server is doing the right thing when this happens - we may need Nexus to actually tell both VMMs to stop in this scenario.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with issue #8755 and the two linked comments for the migration-stop context. Trace how Nexus and propolis-server handle stopping a migrating instance, including whether the target VMM is told to stop. Done means the intended behavior for both VMMs is defined and verified in the relevant migration-stop flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100