From: Juan Quintela <quintela@redhat.com>
To: Li Zhang <lizhang@suse.de>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com, cfontana@suse.de
Subject: Re: [PATCH 2/2] migration: Set the socket backlog number to reduce the chance of live migration failure
Date: Fri, 26 Nov 2021 17:32:59 +0100 [thread overview]
Message-ID: <87ilweg9ms.fsf@secure.mitica> (raw)
In-Reply-To: <20211126153154.25424-3-lizhang@suse.de> (Li Zhang's message of "Fri, 26 Nov 2021 16:31:54 +0100")
Li Zhang <lizhang@suse.de> wrote:
> When creating the guest on destination with -incoming ip:port in QEMU command line,
> the source code that sets the backlog number as the same as multifd channels doesn't
> get called. So the number of backlog is always 1. It's very easy to cause live migration
> failure, so a bigger number is preferred to reduce the chance of the failure.
>
> Signed-off-by: Li Zhang <lizhang@suse.de>
> ---
> migration/socket.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/migration/socket.c b/migration/socket.c
> index 05705a32d8..398d4c10fa 100644
> --- a/migration/socket.c
> +++ b/migration/socket.c
> @@ -152,7 +152,7 @@ socket_start_incoming_migration_internal(SocketAddress *saddr,
> QIONetListener *listener = qio_net_listener_new();
> MigrationIncomingState *mis = migration_incoming_get_current();
> size_t i;
> - int num = 1;
> + int num = 16;
>
> qio_net_listener_set_name(listener, "migration-socket-listener");
Here, the right answer is to use -incoming defer.
Later, Juan.
next prev parent reply other threads:[~2021-11-26 16:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 15:31 [PATCH 0/2] migration: multifd live migration improvement Li Zhang
2021-11-26 15:31 ` [PATCH 1/2] multifd: use qemu_sem_timedwait in multifd_recv_thread to avoid waiting forever Li Zhang
2021-11-26 15:49 ` Daniel P. Berrangé
2021-11-26 16:44 ` Li Zhang
2021-11-26 16:51 ` Daniel P. Berrangé
2021-11-26 17:00 ` Li Zhang
2021-11-26 17:13 ` Daniel P. Berrangé
2021-11-26 17:44 ` Li Zhang
2021-11-29 11:20 ` Dr. David Alan Gilbert
2021-11-29 13:37 ` Li Zhang
2021-11-29 14:50 ` Dr. David Alan Gilbert
2021-11-29 15:34 ` Li Zhang
2021-12-01 12:11 ` Li Zhang
2021-12-01 12:22 ` Daniel P. Berrangé
2021-12-01 13:42 ` Li Zhang
2021-12-01 14:09 ` Daniel P. Berrangé
2021-12-01 14:15 ` Li Zhang
2021-11-29 14:58 ` Daniel P. Berrangé
2021-11-29 15:49 ` Dr. David Alan Gilbert
2021-12-06 9:28 ` Li Zhang
2021-11-26 16:33 ` Juan Quintela
2021-11-26 16:56 ` Li Zhang
2021-11-26 15:31 ` [PATCH 2/2] migration: Set the socket backlog number to reduce the chance of live migration failure Li Zhang
2021-11-26 16:32 ` Juan Quintela [this message]
2021-11-26 16:44 ` Li Zhang
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=87ilweg9ms.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=cfontana@suse.de \
--cc=dgilbert@redhat.com \
--cc=lizhang@suse.de \
--cc=qemu-devel@nongnu.org \
/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).