From: Paolo Bonzini <pbonzini@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: "quintela@redhat.com" <quintela@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
yanghongyang <yanghongyang@huawei.com>,
Huangzhichao <huangzhichao@huawei.com>
Subject: Re: [Qemu-devel] [Bug?] BQL about live migration
Date: Fri, 3 Mar 2017 13:48:16 +0100 [thread overview]
Message-ID: <10d66d73-a269-acb4-bc3d-2250793cba8e@redhat.com> (raw)
In-Reply-To: <20170303120054.GB2439@work-vm>
On 03/03/2017 13:00, Dr. David Alan Gilbert wrote:
> Ouch that's pretty nasty; I remember Paolo explaining to me a while ago that
> their were times when run_on_cpu would have to drop the BQL and I worried about it,
> but this is the 1st time I've seen an error due to it.
>
> Do you know what the migration state was at that point? Was it MIGRATION_STATUS_CANCELLING?
> I'm thinking perhaps we should stop 'cont' from continuing while migration is in
> MIGRATION_STATUS_CANCELLING. Do we send an event when we hit CANCELLED - so that
> perhaps libvirt could avoid sending the 'cont' until then?
No, there's no event, though I thought libvirt would poll until
"query-migrate" returns the cancelled state. Of course that is a small
consolation, because a segfault is unacceptable.
One possibility is to suspend the monitor in qmp_migrate_cancel and
resume it (with add_migration_state_change_notifier) when we hit the
CANCELLED state. I'm not sure what the latency would be between the end
of migrate_fd_cancel and finally reaching CANCELLED.
Paolo
next prev parent reply other threads:[~2017-03-03 12:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 9:29 [Qemu-devel] [Bug?] BQL about live migration Gonglei (Arei)
2017-03-03 10:42 ` Fam Zheng
2017-03-06 2:07 ` yanghongyang
2017-03-03 12:00 ` Dr. David Alan Gilbert
2017-03-03 12:48 ` Paolo Bonzini [this message]
2017-03-03 13:11 ` Dr. David Alan Gilbert
2017-03-03 13:14 ` Paolo Bonzini
2017-03-03 13:26 ` Dr. David Alan Gilbert
2017-03-03 13:33 ` Paolo Bonzini
2017-03-03 14:15 ` Yang Hongyang
2017-03-03 15:03 ` Dr. David Alan Gilbert
2017-03-03 13:57 ` Yang Hongyang
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=10d66d73-a269-acb4-bc3d-2250793cba8e@redhat.com \
--to=pbonzini@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=dgilbert@redhat.com \
--cc=huangzhichao@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=yanghongyang@huawei.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).