From: "Zhoujian (jay)" <jianjay.zhou@huawei.com>
To: Yi Sun <yi.y.sun@linux.intel.com>
Cc: "pbonzini@redhat.com" <pbonzini@redhat.com>,
"yi.l.liu@intel.com" <yi.l.liu@intel.com>,
"sanjay.k.kumar@intel.com" <sanjay.k.kumar@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Huangweidong \(C\)" <weidong.huang@huawei.com>
Subject: RE: Question about delaying dirty log stop to next vm_start
Date: Wed, 4 Aug 2021 01:44:18 +0000 [thread overview]
Message-ID: <ed55f836280f41be8429114c6bf01d42@huawei.com> (raw)
In-Reply-To: <20210802075349.GA2565@yi.y.sun>
Hi Yi,
> -----Original Message-----
> From: Yi Sun [mailto:yi.y.sun@linux.intel.com]
> Sent: Monday, August 2, 2021 3:54 PM
> To: Zhoujian (jay) <jianjay.zhou@huawei.com>
> Cc: qemu-devel@nongnu.org; pbonzini@redhat.com; sanjay.k.kumar@intel.com;
> yi.l.liu@intel.com; yi.y.sun@linux.intel.com
> Subject: Question about delaying dirty log stop to next vm_start
>
> Hi, Jay,
>
> We are testing some live migration cases recently. We found your below patch
> delays the dirty log stop to the next vm_start.
>
> commit 1931076077254a2886daa7c830c7838ebd1f81ef
> Author: Jay Zhou <jianjay.zhou@huawei.com>
> Date: Fri Jul 28 18:28:53 2017 +0800
>
> migration: optimize the downtime
>
> We understand this commit can optimize the downtime. But we observed that
> the dirty log stop cannot be executed if user inputs "quit" in qemu monitor after
> migration completes. Have you considered such case before?
If the migration is successfully finished, the src VM should be destroyed.
If user inputs "quit" in qemu monitor after migration completes, the VM is still
paused(vcpu is stopped), dirty log takes no effect; if the migration failed, the dirty log
stop can be executed after src VM started.
Thanks,
Jay Zhou
prev parent reply other threads:[~2021-08-04 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 7:53 Question about delaying dirty log stop to next vm_start Yi Sun
2021-08-04 1:44 ` Zhoujian (jay) [this message]
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=ed55f836280f41be8429114c6bf01d42@huawei.com \
--to=jianjay.zhou@huawei.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sanjay.k.kumar@intel.com \
--cc=weidong.huang@huawei.com \
--cc=yi.l.liu@intel.com \
--cc=yi.y.sun@linux.intel.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).