On 7/30/20 10:14 AM, Steve Sistare wrote:
Provide the cprload QMP command. The VM is created from the file produced
by the cprsave command. Guest RAM is restored in-place from the shared
memory backend file, and guest block devices are used as is. The contents
of such devices must not be modified between the cprsave and cprload
operations. If the VM was running at cprsave time, then VM execution
resumes.
Is it always wise to unconditionally resume, or might this command need
an additional optional knob that says what state (paused or running) to
move into?
Syntax:
{'command':'cprload', 'data':{'file':'str'}}
Signed-off-by: Steve Sistare <steven.sist...@oracle.com>
Signed-off-by: Maran Wilson <maran.wil...@oracle.com>
---
+++ b/qapi/migration.json
@@ -1635,3 +1635,14 @@
##
{ 'command': 'cprsave', 'data': { 'file': 'str', 'mode': 'str' } }
+##
+# @cprload:
+#
+# Start virtual machine from checkpoint file that was created earlier using
+# the cprsave command.
+#
+# @file: name of checkpoint file
+#
+# Since 5.0
another 5.2 instance. I'll quit pointing it out for the rest of the series.
+##
+{ 'command': 'cprload', 'data': { 'file': 'str' } }
diff --git a/softmmu/vl.c b/softmmu/vl.c
index 660537a..8478778 100644
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
