All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: peterx@redhat.com,  farosas@suse.de,  eblake@redhat.com,
	pbonzini@redhat.com,  qemu-devel@nongnu.org,
	 yc-core@yandex-team.ru
Subject: Re: [PATCH v3 4/4] qapi: introduce exit-on-error parameter for migrate-incoming
Date: Fri, 26 Apr 2024 07:17:28 +0200	[thread overview]
Message-ID: <87frv81z4n.fsf@pond.sub.org> (raw)
In-Reply-To: <20240425181551.1465739-5-vsementsov@yandex-team.ru> (Vladimir Sementsov-Ogievskiy's message of "Thu, 25 Apr 2024 21:15:51 +0300")

Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru> writes:

> Now we do set MIGRATION_FAILED state, but don't give a chance to
> orchestrator to query migration state and get the error.
>
> Let's provide a possibility for QMP-based orchestrators to get an error
> like with outgoing migration.
>
> For hmp_migrate_incoming(), let's enable the new behavior: HMP is not
> and ABI, it's mostly intended to use by developer and it makes sense
> not to stop the process.
>
> For x-exit-preconfig, let's keep the old behavior:
>  - it's called from init(), so here we want to keep current behavior by
>    default
>  - it does exit on error by itself as well
> So, if we want to change the behavior of x-exit-preconfig, it should be
> another patch.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>

[...]

> diff --git a/qapi/migration.json b/qapi/migration.json
> index 8c65b90328..9de8b98d0b 100644
> --- a/qapi/migration.json
> +++ b/qapi/migration.json
> @@ -1837,6 +1837,10 @@
>  # @channels: list of migration stream channels with each stream in the
>  #     list connected to a destination interface endpoint.
>  #
> +# @exit-on-error: Do exit on incoming migration failure.  Default true.

Scratch "Do"?

> +#     When set to false, the error is reported by MIGRATION event and

Comma before "and", please.

Suggest "the failure triggers a MIGRATION event".

> +#     error could be retrieved by query-migrate command.  (since 9.1)

"error details could be retrieved with query-migrate", perhaps?

> +#
>  # Since: 2.3
>  #
>  # Notes:
> @@ -1889,7 +1893,8 @@
>  ##
>  { 'command': 'migrate-incoming',
>               'data': {'*uri': 'str',
> -                      '*channels': [ 'MigrationChannel' ] } }
> +                      '*channels': [ 'MigrationChannel' ],
> +                      '*exit-on-error': 'bool' } }
>  
>  ##
>  # @xen-save-devices-state:

QAPI schema
Acked-by: Markus Armbruster <armbru@redhat.com>

[...]



      parent reply	other threads:[~2024-04-26  5:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 18:15 [PATCH v3 0/4] migration: do not exit on incoming failure Vladimir Sementsov-Ogievskiy
2024-04-25 18:15 ` [PATCH v3 1/4] migration: move trace-point from migrate_fd_error to migrate_set_error Vladimir Sementsov-Ogievskiy
2024-04-25 20:03   ` Fabiano Rosas
2024-04-25 18:15 ` [PATCH v3 2/4] migration: process_incoming_migration_co(): complete cleanup on failure Vladimir Sementsov-Ogievskiy
2024-04-25 20:03   ` Fabiano Rosas
2024-04-25 18:15 ` [PATCH v3 3/4] migration: process_incoming_migration_co(): rework error reporting Vladimir Sementsov-Ogievskiy
2024-04-25 20:21   ` Fabiano Rosas
2024-04-25 18:15 ` [PATCH v3 4/4] qapi: introduce exit-on-error parameter for migrate-incoming Vladimir Sementsov-Ogievskiy
2024-04-25 20:30   ` Fabiano Rosas
2024-04-29  7:45     ` Vladimir Sementsov-Ogievskiy
2024-04-29 13:06       ` Fabiano Rosas
2024-04-29 15:03         ` Vladimir Sementsov-Ogievskiy
2024-04-26  5:17   ` Markus Armbruster [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87frv81z4n.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=farosas@suse.de \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@yandex-team.ru \
    --cc=yc-core@yandex-team.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.