`multipass stop` command

Errors or typos? Topics missing? Hard to read? Let us know or open an issue on GitHub.

The multipass stop command without any argument will stop the primary instance. You can also pass one or more instance names or the --all option to stop more instances at the same time. Only Running instances can be stopped. Stopped instances can be started again with multipass start.

The --force option (available starting from Multipass version 1.14) can be used to stop the instance when it is in a non-responsive, unknown or suspended state. It can also be used with the --all option to stop all instances forcefully.

$ multipass stop --help
Usage: multipass stop [options] [<name> ...]
Stop the named instances. Exits with return code 0 
if successful.

  -h, --help         Displays help on commandline options
  -v, --verbose      Increase logging verbosity. Repeat the 'v' in the short
                     option for more detail. Maximum verbosity is obtained with
                     4 (or more) v's, i.e. -vvvv.
  --all              Stop all instances
  -t, --time <time>  Time from now, in minutes, to delay shutdown of the
  -c, --cancel       Cancel a pending delayed shutdown
  --force            Force the instance to shut down immediately. Warning: This
                     could potentially corrupt a running instance, so use with

  name               Names of instances to stop. If omitted, and without the
                     --all option, 'primary' will be assumed.

@saviq, let me know if the quality of the post above is sufficient enough for the documentation to be improved. I’ll proceed asap for the other topics I can create.

Due to the lack of response I’m dropping out of this effort.
I suggest choosing another working model for this project’s documentation, since what is mentioned in this thread does not seem to happen.
Just look at the fact that the missing commands as of Dec '19 are still not on the documentation webpage as of Sept '21.

Hi @rosuvladimir, sorry about that, I completely missed your reply ping above!

I’ve tweaked it a bit and now have hooked it up to our docs: