From: Lukas Straub <lukasstraub2@web.de>
To: "Zhang, Chen" <chen.zhang@intel.com>
Cc: Daniel Cho <danielcho@qnap.com>,
Zhanghailiang <zhang.zhanghailiang@huawei.com>,
Jason Wang <jasowang@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: The issues about architecture of the COLO checkpoint
Date: Fri, 6 Mar 2020 16:22:01 +0100 [thread overview]
Message-ID: <20200306162201.3a1cd3ae@luklap> (raw)
In-Reply-To: <343daa37127e424c94fa0a3edde30f0c@intel.com>
On Wed, 4 Mar 2020 07:44:11 +0000
"Zhang, Chen" <chen.zhang@intel.com> wrote:
> > -----Original Message-----
> > From: Daniel Cho <danielcho@qnap.com>
> > Sent: Monday, February 24, 2020 3:15 PM
> > To: Zhang, Chen <chen.zhang@intel.com>
> > Cc: Dr. David Alan Gilbert <dgilbert@redhat.com>; Zhanghailiang
> > <zhang.zhanghailiang@huawei.com>; qemu-devel@nongnu.org; Jason
> > Wang <jasowang@redhat.com>
> > Subject: Re: The issues about architecture of the COLO checkpoint
> >
> > Hi Zhang,
> >
> > Thanks for your help.
> > However, did you occur the error which the function qemu_hexdump in
> > colo-compare.c will crash the qemu process while doing operation with
> > network?
> >
>
> No, qemu_hexdump looks no relationship with network...
> Do you means it will crashed in qemu_hexdump sometimes?
Jeah, I hit that bug too, but it was fixed with
1e907a32b77e5d418538453df5945242e43224fa "COLO-compare: Fix incorrect `if` logic"
in qemu 4.2.
Regards,
Lukas Straub
> > We are working on VM fault tolerance study and COLO function evalutation
> > first. Currently we did not have a confirmed plan on it.
>
> OK, keep connection.
>
> Thanks
> Zhang Chen
next prev parent reply other threads:[~2020-03-06 15:26 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
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 [this message]
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=20200306162201.3a1cd3ae@luklap \
--to=lukasstraub2@web.de \
--cc=chen.zhang@intel.com \
--cc=danielcho@qnap.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.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 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).