From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Fei Li <fli@suse.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com, peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH RFC 0/2] Fix migration issues
Date: Thu, 25 Oct 2018 13:55:02 +0100 [thread overview]
Message-ID: <20181025125501.GA5912@work-vm> (raw)
In-Reply-To: <20181022110854.10284-1-fli@suse.com>
* Fei Li (fli@suse.com) wrote:
> Hi,
> these two patches are to fix live migration issues. The first is
> about multifd, and the second is to fix some error handling.
>
> But I have a question about using multifd migration.
> In our current code, when multifd is used during migration, if there
> is an error before the destination receives all new channels (I mean
> multifd_recv_new_channel(ioc)), the destination does not exit but
> keeps waiting (Hang in recvmsg() in qio_channel_socket_readv) until
> the source exits.
>
> My question is about the state of the destination host if fails during
> this period. I did a test, after applying [1/2] patch, if
> multifd_new_send_channel_async() fails, the destination host hangs for
> a while then later pops up a window saying
> "'QEMU (...) [stopped]' is not responding.
> You may choose to wait a short while for it to continue or force
> the application to quit entirely."
> But after closing the window by clicking, the qemu on the dest still
> hangs there until I exclusively kill the qemu on the source.
That sounds like the main thread is blocked for some reason? But I don't
normally use the window setup; if you try with -nographic and can see
the HMP (or a QMP) monitor, can you see if the monitor still responds?
If it doesn't then try and get a backtrace.
The monitor really shouldn't block, so it would be interesting to see.
Dave
> The source host keeps running as expected, but I guess the hang
> phenonmenon in the dest is not right.
> Would someone kindly give some suggestions on this? Thanks a lot.
>
>
> Fei Li (2):
> migration: fix the multifd code
> migration: fix some error handling
>
> migration/migration.c | 5 +----
> migration/postcopy-ram.c | 3 +++
> migration/ram.c | 33 +++++++++++++++++++++++----------
> migration/ram.h | 2 +-
> 4 files changed, 28 insertions(+), 15 deletions(-)
>
> --
> 2.13.7
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-10-25 12:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 11:08 [Qemu-devel] [PATCH RFC 0/2] Fix migration issues Fei Li
2018-10-22 11:08 ` [Qemu-devel] [PATCH RFC 1/2] migration: fix the multifd code Fei Li
2018-10-22 11:08 ` [Qemu-devel] [PATCH RFC 2/2] migration: fix some error handling Fei Li
2018-10-24 21:27 ` [Qemu-devel] [PATCH RFC 0/2] Fix migration issues Peter Xu
2018-10-25 9:04 ` Fei Li
2018-10-25 12:58 ` Peter Xu
2018-10-26 13:10 ` Fei Li
2018-10-26 13:35 ` Peter Xu
2018-10-26 15:24 ` Dr. David Alan Gilbert
2018-10-29 7:15 ` Fei Li
2018-10-25 12:55 ` Dr. David Alan Gilbert [this message]
2018-10-26 12:59 ` Fei Li
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=20181025125501.GA5912@work-vm \
--to=dgilbert@redhat.com \
--cc=fli@suse.com \
--cc=peterx@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 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.