All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Daniel Cho <danielcho@qnap.com>,
	chen.zhang@intel.com, zhang.zhanghailiang@huawei.com
Cc: qemu-devel@nongnu.org
Subject: Re: The issues about architecture of the COLO checkpoint
Date: Tue, 11 Feb 2020 17:47:56 +0000	[thread overview]
Message-ID: <20200211174756.GA2798@work-vm> (raw)
In-Reply-To: <CA+XQNE44kZjcw=0dtzaS4HwbPcRG6GpcQ3g3QfL5VS84EBWS_g@mail.gmail.com>


cc'ing in COLO people:

* Daniel Cho (danielcho@qnap.com) wrote:
> Hi everyone,
>      We have some issues about setting COLO feature. Hope somebody could
> give us some advice.
> 
> Issue 1:
>      We dynamic to set COLO feature for PVM(2 core, 16G memory),  but the
> Primary VM will pause a long time(based on memory size) for waiting SVM
> start. Does it have any idea to reduce the pause time?
> 
> 
> Issue 2:
>      In https://github.com/qemu/qemu/blob/master/migration/colo.c#L503,
> could we move start_vm() before Line 488? Because at first checkpoint PVM
> will wait for SVM's reply, it cause PVM stop for a while.
> 
>      We set the COLO feature on running VM, so we hope the running VM could
> continuous service for users.
> Do you have any suggestions for those issues?
> 
> Best regards,
> Daniel Cho
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK



  reply	other threads:[~2020-02-11 17:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11  6:30 The issues about architecture of the COLO checkpoint Daniel Cho
2020-02-11 17:47 ` Dr. David Alan Gilbert [this message]
2020-02-12  3:18   ` Zhanghailiang
2020-02-12  5:45     ` Zhang, Chen
2020-02-12  8:37       ` Daniel Cho
2020-02-13  1:45         ` Zhanghailiang
2020-02-13  2:10           ` Zhang, Chen
2020-02-13  2:17             ` Zhang, Chen
2020-02-13  3:02               ` Daniel Cho
2020-02-13 10:37                 ` Dr. David Alan Gilbert
2020-02-15  3:35                   ` Daniel Cho
2020-02-17  1:25                     ` Zhanghailiang
2020-02-17  5:36                     ` Zhang, Chen
2020-02-18  9:22                       ` Daniel Cho
2020-02-20  3:07                         ` Zhang, Chen
2020-02-20  3:49                           ` Daniel Cho
2020-02-20  3:51                             ` Daniel Cho
2020-02-20 19:43                               ` Dr. David Alan Gilbert
2020-02-24  6:57                               ` Zhanghailiang
2020-02-23 18:43                             ` Zhang, Chen
2020-02-24  7:14                               ` Daniel Cho
2020-03-04  7:44                                 ` Zhang, Chen
2020-03-06 15:22                                   ` Lukas Straub
2020-03-12 16:39                                     ` Dr. David Alan Gilbert
2020-03-17  8:32                                       ` Zhang, Chen
2020-02-13  0:57       ` Zhanghailiang

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=20200211174756.GA2798@work-vm \
    --to=dgilbert@redhat.com \
    --cc=chen.zhang@intel.com \
    --cc=danielcho@qnap.com \
    --cc=qemu-devel@nongnu.org \
    --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.