|
| From: | Eric Blake |
| Subject: | Re: [Qemu-devel] [PULL 33/41] qmp/migration: new command migrate-recover |
| Date: | Wed, 9 May 2018 07:59:27 -0500 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 |
On 05/09/2018 06:23 AM, Juan Quintela wrote:
From: Peter Xu <address@hidden> The first allow-oob=true command. It's used on destination side when the postcopy migration is paused and ready for a recovery. After execution, a new migration channel will be established for postcopy to continue.
Right now, oob is still disabled by default. Where do we stand on re-enabling it after the last-minute disabling needed for a stable 2.12 release?
+++ b/qapi/migration.json
@@ -1191,3 +1191,23 @@
# Since: 2.9
##
{ 'command': 'xen-colo-do-checkpoint' }
+
+##
+# @migrate-recover:
+#
+# Provide a recovery migration stream URI.
+#
+# @uri: the URI to be used for the recovery of migration stream.
+#
+# Returns: nothing.
+#
+# Example:
+#
+# -> { "execute": "migrate-recover",
+# "arguments": { "uri": "tcp:192.168.1.200:12345" } }
+# <- { "return": {} }
+#
+# Since: 2.12
This needs to be amended to 2.13 (same followup as other issues mentioned elsewhere in the series)
+##
+{ 'command': 'migrate-recover', 'data': { 'uri': 'str' },
+ 'allow-oob': true }
-- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
| [Prev in Thread] | Current Thread | [Next in Thread] |