diff options
| author | Craig Jennings <c@cjennings.net> | 2024-04-07 13:41:34 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2024-04-07 13:41:34 -0500 |
| commit | 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 (patch) | |
| tree | f1190704f78f04a2b0b4c977d20fe96a828377f1 /devdocs/vagrant/cli%2Fsuspend.html | |
new repository
Diffstat (limited to 'devdocs/vagrant/cli%2Fsuspend.html')
| -rw-r--r-- | devdocs/vagrant/cli%2Fsuspend.html | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/devdocs/vagrant/cli%2Fsuspend.html b/devdocs/vagrant/cli%2Fsuspend.html new file mode 100644 index 00000000..2bbb0642 --- /dev/null +++ b/devdocs/vagrant/cli%2Fsuspend.html @@ -0,0 +1,6 @@ +<h1 id="suspend"> Suspend </h1> <p><strong>Command: <code>vagrant suspend [name|id]</code></strong></p> <p>This suspends the guest machine Vagrant is managing, rather than fully <a href="halt">shutting it down</a> or <a href="destroy">destroying it</a>.</p> <p>A suspend effectively saves the <em>exact point-in-time state</em> of the machine, so that when you <a href="resume">resume</a> it later, it begins running immediately from that point, rather than doing a full boot.</p> <p>This generally requires extra disk space to store all the contents of the RAM within your guest machine, but the machine no longer consumes the RAM of your host machine or CPU cycles while it is suspended.</p><div class="_attribution"> + <p class="_attribution-p"> + © 2010–2018 Mitchell Hashimoto<br>Licensed under the MPL 2.0 License.<br> + <a href="https://www.vagrantup.com/docs/cli/suspend.html" class="_attribution-link">https://www.vagrantup.com/docs/cli/suspend.html</a> + </p> +</div> |