qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 2/2] migration: Update error description whenever migration fails
Date: Thu, 18 May 2023 13:52:47 +0200	[thread overview]
Message-ID: <87ilcpdfg0.fsf@secure.mitica> (raw)
In-Reply-To: <20230518062308.90631-3-tejus.gk@nutanix.com> (Tejus GK's message of "Thu, 18 May 2023 06:23:08 +0000")

Tejus GK <tejus.gk@nutanix.com> wrote:
> There are places outside of migration.c which eventually leads to a
> migration failure, 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>


If you have to respin:

> @@ -1456,6 +1460,7 @@ int qemu_savevm_state_complete_precopy_non_iterable(QEMUFile *f,
>      int vmdesc_len;
>      SaveStateEntry *se;
>      int ret;
> +    Error *local_err = NULL;

You can declare this:

>      QTAILQ_FOREACH(se, &savevm_state.handlers, entry) {
>          if (se->vmsd && se->vmsd->early_setup) {
> @@ -1475,8 +1480,10 @@ int qemu_savevm_state_complete_precopy_non_iterable(QEMUFile *f,
>           * bdrv_activate_all() on the other end won't fail. */
>          ret = bdrv_inactivate_all();
>          if (ret) {

here

> -            error_report("%s: bdrv_inactivate_all() failed (%d)",
> -                         __func__, ret);



  reply	other threads:[~2023-05-18 11:53 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
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 [this message]
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=87ilcpdfg0.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).