From: Juan Quintela <quintela@redhat.com>
To: Tejus GK <tejus.gk@nutanix.com>
Cc: qemu-devel@nongnu.org, peterx@redhat.com, leobras@redhat.com,
berrange@redhat.com, shivam.kumar1@nutanix.com
Subject: Re: [RFC v3 1/2] migration: Update error description whenever migration fails
Date: Thu, 18 May 2023 13:50:04 +0200 [thread overview]
Message-ID: <87o7mhdfkj.fsf@secure.mitica> (raw)
In-Reply-To: <20230518062308.90631-2-tejus.gk@nutanix.com> (Tejus GK's message of "Thu, 18 May 2023 06:23:07 +0000")
Tejus GK <tejus.gk@nutanix.com> wrote:
> There are places in migration.c where the migration is marked failed with
> MIGRATION_STATUS_FAILED, but the failure reason is never updated. Hence
> libvirt doesn't know why the migration failed when it queries for it.
>
> Signed-off-by: Tejus GK <tejus.gk@nutanix.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
> ---
> migration/migration.c | 23 ++++++++++++-----------
> 1 file changed, 12 insertions(+), 11 deletions(-)
>
> diff --git a/migration/migration.c b/migration/migration.c
> index 00d8ba8da0..864150d01d 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -1683,15 +1683,11 @@ void qmp_migrate(const char *uri, bool has_blk, bool blk,
> } else if (strstart(uri, "fd:", &p)) {
> fd_start_outgoing_migration(s, p, &local_err);
> } else {
> - if (!(has_resume && resume)) {
> - yank_unregister_instance(MIGRATION_YANK_INSTANCE);
> - }
> - error_setg(errp, QERR_INVALID_PARAMETER_VALUE, "uri",
> + error_setg(&local_err, QERR_INVALID_PARAMETER_VALUE, "uri",
> "a valid migration protocol");
> migrate_set_state(&s->state, MIGRATION_STATUS_SETUP,
> MIGRATION_STATUS_FAILED);
> block_cleanup_parameters();
> - return;
If you have to respin, please split the removal of the yan_unregister()
and return in one patch, and let of this patch the error bits.
> }
>
> if (local_err) {
> @@ -2073,7 +2069,7 @@ migration_wait_main_channel(MigrationState *ms)
> * Switch from normal iteration to postcopy
> * Returns non-0 on error
> */
> -static int postcopy_start(MigrationState *ms)
> +static int postcopy_start(MigrationState *ms, Error **errp)
> {
> int ret;
> QIOChannelBuffer *bioc;
> @@ -2183,7 +2179,7 @@ static int postcopy_start(MigrationState *ms)
> */
> ret = qemu_file_get_error(ms->to_dst_file);
> if (ret) {
> - error_report("postcopy_start: Migration stream errored (pre package)");
> + error_setg(errp, "postcopy_start: Migration stream errored (pre package)");
> goto fail_closefb;
> }
>
> @@ -2220,7 +2216,7 @@ static int postcopy_start(MigrationState *ms)
>
> ret = qemu_file_get_error(ms->to_dst_file);
> if (ret) {
> - error_report("postcopy_start: Migration stream errored");
> + error_setg(errp, "postcopy_start: Migration stream errored");
> migrate_set_state(&ms->state, MIGRATION_STATUS_POSTCOPY_ACTIVE,
> MIGRATION_STATUS_FAILED);
> }
> @@ -2741,6 +2737,7 @@ typedef enum {
> static MigIterateState migration_iteration_run(MigrationState *s)
> {
> uint64_t must_precopy, can_postcopy;
> + Error *local_err = NULL;
> bool in_postcopy = s->state == MIGRATION_STATUS_POSTCOPY_ACTIVE;
>
> qemu_savevm_state_pending_estimate(&must_precopy, &can_postcopy);
> @@ -2763,8 +2760,9 @@ static MigIterateState migration_iteration_run(MigrationState *s)
> /* Still a significant amount to transfer */
> if (!in_postcopy && must_precopy <= s->threshold_size &&
> qatomic_read(&s->start_postcopy)) {
> - if (postcopy_start(s)) {
> - error_report("%s: postcopy failed to start", __func__);
> + if (postcopy_start(s, &local_err)) {
> + migrate_set_error(s, local_err);
> + error_report_err(local_err);
Not your fault.
But the interface of migrate_set_error() is a mess. It is followed
sometimes from error_report_err() another from error_free() and another
by ...
next prev parent reply other threads:[~2023-05-18 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 6:23 [RFC v3 0/2] migration: Update error description whenever migration fails Tejus GK
2023-05-18 6:23 ` [RFC v3 1/2] " Tejus GK
2023-05-18 11:50 ` Juan Quintela [this message]
2023-05-18 12:24 ` Daniel P. Berrangé
2023-05-18 6:23 ` [RFC v3 2/2] " Tejus GK
2023-05-18 11:52 ` Juan Quintela
2023-05-18 14:24 ` Tejus GK
2023-05-18 11:53 ` [RFC v3 0/2] " Juan Quintela
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=87o7mhdfkj.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=berrange@redhat.com \
--cc=leobras@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shivam.kumar1@nutanix.com \
--cc=tejus.gk@nutanix.com \
/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.