From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>, qemu-devel@nongnu.org
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [PATCH] migration: failover: emit a warning when the card is not fully unplugged
Date: Thu, 1 Jul 2021 18:11:36 +0200 [thread overview]
Message-ID: <241d8a85-428f-1abf-fe32-38a88f73bfc7@redhat.com> (raw)
In-Reply-To: <20210701131458.112036-1-lvivier@redhat.com>
On 7/1/21 3:14 PM, Laurent Vivier wrote:
> When the migration fails or is canceled we wait the end of the unplug
> operation to be able to plug it back. But if the unplug operation
> is never finished we stop to wait and QEMU emits a warning to inform
> the user.
>
> Based-on: 20210629155007.629086-1-lvivier@redhat.com
FYI this ^ tag ...
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
... goes here ;)
> migration/migration.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/migration/migration.c b/migration/migration.c
> index 3b06d43a7f42..e065c62e5189 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -3689,6 +3689,10 @@ static void qemu_savevm_wait_unplug(MigrationState *s, int old_state,
> while (timeout-- && qemu_savevm_state_guest_unplug_pending()) {
> qemu_sem_timedwait(&s->wait_unplug_sem, 250);
> }
> + if (qemu_savevm_state_guest_unplug_pending()) {
> + warn_report("migration: partially unplugged device on "
> + "failure");
> + }
> }
>
> migrate_set_state(&s->state, MIGRATION_STATUS_WAIT_UNPLUG, new_state);
>
next prev parent reply other threads:[~2021-07-01 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 13:14 [PATCH] migration: failover: emit a warning when the card is not fully unplugged Laurent Vivier
2021-07-01 16:11 ` Philippe Mathieu-Daudé [this message]
2021-07-01 17:59 ` Juan Quintela
2021-07-13 10:58 ` Dr. David Alan Gilbert
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=241d8a85-428f-1abf-fe32-38a88f73bfc7@redhat.com \
--to=philmd@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).