You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: