On Wed, Jul 2, 2025 at 4:04 AM Markus Armbruster <arm...@redhat.com> wrote: > > John Snow <js...@redhat.com> writes: > > > Signed-off-by: John Snow <js...@redhat.com> > > --- > > qapi/migration.json | 62 ++++++++++++++++++++++----------------------- > > 1 file changed, 31 insertions(+), 31 deletions(-) > > > > diff --git a/qapi/migration.json b/qapi/migration.json > > index d7c5047462e..fec6479a23e 100644 > > --- a/qapi/migration.json > > +++ b/qapi/migration.json > > [...] > > > @@ -646,10 +646,10 @@ > > # memory-backend-epc is not supported. The VM must be started > > # with the '-machine aux-ram-share=on' option. > > # > > -# When using -incoming defer, you must issue the migrate command > > +# When using -incoming defer, you must issue the `migrate` command > > # to old QEMU before issuing any monitor commands to new QEMU. > > # However, new QEMU does not open and read the migration stream > > -# until you issue the migrate incoming command. > > +# until you issue the `migrate` incoming command. > > I suspect this should be `migrate-incoming`. > > > # > > # (since 10.0) > > ## > > [...] > > > @@ -1733,8 +1733,8 @@ > > # list connected to a destination interface endpoint. > > # > > # @exit-on-error: Exit on incoming migration failure. Default true. > > -# When set to false, the failure triggers a MIGRATION event, and > > -# error details could be retrieved with query-migrate. > > +# When set to false, the failure triggers a :qapi:event:`MIGRATION` > > When and why do we need :qapi:event:?
/home/jsnow/src/qemu/qapi/migration.json:1737: WARNING: more than one target found for 'any' cross-reference 'MIGRATION': could be :std:ref:`Migration framework` or :qapi:event:`QMP:migration.MIGRATION` [ref.any] > > > +# event, and error details could be retrieved with `query-migrate`. > > # (since 9.1) > > # > > # Since: 2.3 > > [...] >
