From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org, quintela@redhat.com, stefanha@redhat.com,
christian.ehrhardt@canonical.com
Cc: peterx@redhat.com, lvivier@redhat.com
Subject: Re: [Qemu-devel] [PATCH] migration: Report when bdrv_inactivate_all fails
Date: Wed, 6 Sep 2017 14:26:24 +0100 [thread overview]
Message-ID: <20170906132624.GA8457@work-vm> (raw)
In-Reply-To: <20170822170212.27347-1-dgilbert@redhat.com>
* Dr. David Alan Gilbert (git) (dgilbert@redhat.com) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>
> If the bdrv_inactivate_all fails near the end of the migration,
> the migration will fail and often the only diagnostics in the log
> are an I/O error which you can't distinguish from an error on
> the socket connection.
>
> Add an error so we know when it's actually a block problem.
>
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Queued for migration.
> ---
> migration/savevm.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/migration/savevm.c b/migration/savevm.c
> index fdd15fa0a7..7a55023d1a 100644
> --- a/migration/savevm.c
> +++ b/migration/savevm.c
> @@ -1157,6 +1157,8 @@ int qemu_savevm_state_complete_precopy(QEMUFile *f, bool iterable_only,
> * bdrv_invalidate_cache_all() on the other end won't fail. */
> ret = bdrv_inactivate_all();
> if (ret) {
> + error_report("%s: bdrv_inactivate_all() failed (%d)",
> + __func__, ret);
> qemu_file_set_error(f, ret);
> return ret;
> }
> --
> 2.13.5
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2017-09-06 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 17:02 [Qemu-devel] [PATCH] migration: Report when bdrv_inactivate_all fails Dr. David Alan Gilbert (git)
2017-08-23 2:13 ` Peter Xu
2017-08-23 14:42 ` Stefan Hajnoczi
2017-09-06 13:26 ` Dr. David Alan Gilbert [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=20170906132624.GA8457@work-vm \
--to=dgilbert@redhat.com \
--cc=christian.ehrhardt@canonical.com \
--cc=lvivier@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.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).