Peter Xu <[email protected]> writes: > 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]> > 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..48856078db 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, resume one paused postcopy migration, using the new
Scratch "one" unless there can be more than one. > +# URI/channels specified to replace the old/broken channels. The user > +# should make sure the migration is in "postcopy-paused" state before > +# the resume request. Default "off". (since 3.0) > # > # Features: > # What happens when migration is not in state "postcopy-paused"? Remind me, how can migration get into and out of this state?
