On 11/3/25 22:06, Peter Xu wrote:
It wasn't obvious how the resume flag should be used when staring at the
QAPI doc. Enrich it to be crystal clear.
Reported-by: Markus Armbruster <[email protected]>
Reviewed-by: Markus Armbruster <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
[peterx: amended wordings, per markus]
Signed-off-by: Peter Xu <[email protected]>
---
qapi/migration.json | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/qapi/migration.json b/qapi/migration.json
index be0f3fcc12..c7a6737cc1 100644
--- a/qapi/migration.json
+++ b/qapi/migration.json
@@ -1732,7 +1732,10 @@
# @detach: this argument exists only for compatibility reasons and is
# ignored by QEMU
#
-# @resume: resume one paused migration, default "off". (since 3.0)
+# @resume: when set, use the new uri/channels specified to resume paused
+# postcopy migration. This flag should only be used if the previous
+# postcopy migration was interrupted. The command will fail unless
+# migration is in "postcopy-paused" state. (default: false, since 3.0)
#
# Features:
#
Grr. I interrupted myself last night and didn't complete all my pre-merge testing, so
this has been merged with a regression:
/home/rth/qemu/bld-pub/pyvenv/bin/python3 /home/rth/qemu/publish/scripts/qapi-gen.py -o
qapi -b ../publish/qapi/qapi-schema.json
In file included from ../publish/qapi/qapi-schema.json:53:
../publish/qapi/migration.json:1750:1: documentation line longer than 70
characters
r~
