oxidecomputer / oxidecomputer/propolis
want stop requests to inform the guest OS so that it can try to shut down gracefully
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
Today, asking a running Propolis to stop does not assert any signals into the guest (like a virtual power button press) that give the guest OS a chance to run its own shutdown logic. It would be nice if Propolis did assert such a signal, with a timeout (preferably configurable, at least through the TOML/command line, if not by the HTTP API) after which it will proceed down its existing, non-graceful instance-stop path.
Contributor guide
No contributing guide indexed for this repository
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 by tracing Propolis's existing non-graceful instance-stop path and identify where a guest shutdown signal could be asserted. Then inspect the TOML and command-line configuration entry points for a configurable timeout; done means the signal is attempted before the existing stop path and the timeout fallback is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100