All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jay Zhou <jianjay.zhou@huawei.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: pbonzini@redhat.com, rkrcmar@redhat.com, qemu-devel@nongnu.org,
	quintela@redhat.com, armbru@redhat.com, arei.gonglei@huawei.com,
	zhang.zhanghailiang@huawei.com, wangxinxin.wang@huawei.com,
	weidong.huang@huawei.com, aarcange@redhat.com,
	jdenemar@redhat.com
Subject: Re: [Qemu-devel] [PATCH] migration: optimize the downtime
Date: Mon, 31 Jul 2017 15:04:27 +0800	[thread overview]
Message-ID: <597ED67B.4000904@huawei.com> (raw)
In-Reply-To: <20170725103426.GC2099@work-vm>

Hi Dave,

On 2017/7/25 18:34, Dr. David Alan Gilbert wrote:
>> After checking the codes of the newest libvirt, I think it is the same
>> in the qemuMigrationWaitForCompletion function, which is used to poll
>> qemu every 50ms.
>
> Checking with Jiri Denemark (added to cc), newer libvirt should use
> events when available - but that polling code is there to cope with
> older qemu's.  So with a newer qemu, i think it should spot the
> COMPLETED event.
>

I do tests on the newest libvirt(v3.6.0) + newest qemu(v2.9.90,
v2.10.0-rc0-29-ga588c49-dirty). The log added indicates that the source
side libvirt spots the COMPLETE event after the cleanup of the source side
qemu, i.e. 300ms still exists.

BTW, I'm not very familiar with libvirt, if there is something special to
configure or I'm missing something, please let me know.

Thanks,
Jay

  reply	other threads:[~2017-07-31  7:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20  3:49 [Qemu-devel] [PATCH] migration: optimize the downtime Jay Zhou
2017-07-20  4:23 ` no-reply
2017-07-21  9:49 ` Dr. David Alan Gilbert
2017-07-21 12:23   ` Jay Zhou
2017-07-24 15:35     ` Dr. David Alan Gilbert
2017-07-24 16:33       ` Paolo Bonzini
2017-07-24 19:03         ` Dr. David Alan Gilbert
2017-07-24 20:38           ` Paolo Bonzini
2017-07-25 19:15             ` Dr. David Alan Gilbert
2017-07-27 14:26               ` Paolo Bonzini
2017-07-25  7:29         ` Jay Zhou
2017-07-25  8:18           ` Paolo Bonzini
2017-07-25  7:09       ` Jay Zhou
2017-07-25 10:34         ` Dr. David Alan Gilbert
2017-07-31  7:04           ` Jay Zhou [this message]
2017-07-31 13:33             ` 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=597ED67B.4000904@huawei.com \
    --to=jianjay.zhou@huawei.com \
    --cc=aarcange@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=jdenemar@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=wangxinxin.wang@huawei.com \
    --cc=weidong.huang@huawei.com \
    --cc=zhang.zhanghailiang@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 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.