[pve-devel] [PATCH docs v2 1/1] add chapter about hibernation and vmstate storage selection

Dominik Csapak d.csapak at proxmox.com
Mon Dec 9 15:27:01 CET 2019

and reference it also in the snapshot chapter

Signed-off-by: Dominik Csapak <d.csapak at proxmox.com>
new in v2
 qm.adoc | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/qm.adoc b/qm.adoc
index b13f0f4..f0d63af 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -1193,6 +1193,28 @@ It will be called during various phases of the guests lifetime.
 For an example and documentation see the example script under
+You can suspend a VM to disk with the GUI option `Hibernate` or with
+ qm suspend ID --todisk
+That means that the current content of the memory will be saved onto disk
+and the VM gets stopped. On the next start, the memory content will be
+loaded and the VM can continue where it was left off.
+.State storage selection
+If no target storage for the memory is given, it will be automatically
+chosen, the first of:
+1. The storage `vmstatestorage` from the VM config.
+2. The first shared storage from any VM disk.
+3. The first non-shared storage from any VM disk.
+4. The storage `local` as a fallback.
 Managing Virtual Machines with `qm`
@@ -1302,6 +1324,10 @@ There are a few snapshot related properties like `parent` and
 relationship between snapshots. `snaptime` is the snapshot creation
 time stamp (Unix epoch).
+You can optionally save the memory of a running VM with the option `vmstate`.
+For details about how the target storage gets chosen for the VM state, see
+xref:qm_vmstatestorage[State storage selection] in the chapter

More information about the pve-devel mailing list