From: Xiao Guangrong <guangrong.xiao@gmail.com>
To: pbonzini@redhat.com, mst@redhat.com, mtosatti@redhat.com
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, dgilbert@redhat.com,
peterx@redhat.com, jiang.biao2@zte.com.cn, wei.w.wang@intel.com,
Xiao Guangrong <xiaoguangrong@tencent.com>
Subject: Re: [Qemu-devel] [PATCH] migration: introduce decompress-error-check
Date: Thu, 26 Apr 2018 17:19:58 +0800 [thread overview]
Message-ID: <f58e5e7d-da9c-6424-f0a7-29b5cadd72e4@gmail.com> (raw)
In-Reply-To: <20180426091519.26934-1-xiaoguangrong@tencent.com>
Hi Dave,
On 04/26/2018 05:15 PM, guangrong.xiao@gmail.com wrote:
> From: Xiao Guangrong <xiaoguangrong@tencent.com>
>
> QEMU 2.13 enables strict check for compression & decompression to
> make the migration more robuster, that depends on the source to fix
> the internal design which triggers the unexpected error conditions
>
> To make it work for migrating old version QEMU to 2.13 QEMU, we
> introduce this parameter to disable the error check on the
> destination
We noticed this issue when evaluated your pull request, could you
please review this fix and pull it to 2.13 release? Sorry, i did
not realize it before. :(
next prev parent reply other threads:[~2018-04-26 9:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 9:15 [Qemu-devel] [PATCH] migration: introduce decompress-error-check guangrong.xiao
2018-04-26 9:19 ` Xiao Guangrong [this message]
2018-04-26 9:34 ` Dr. David Alan Gilbert
2018-04-26 13:18 ` Xiao Guangrong
2018-04-26 14:01 ` Eric Blake
2018-04-27 3:15 ` Xiao Guangrong
2018-04-27 9:31 ` Peter Xu
2018-04-27 10:40 ` Xiao Guangrong
2018-05-02 3:03 ` Peter Xu
2018-05-02 14:57 ` Dr. David Alan Gilbert
2018-05-03 2:10 ` Peter Xu
2018-04-27 11:29 ` Dr. David Alan Gilbert
2018-04-28 6:13 ` Xiao Guangrong
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=f58e5e7d-da9c-6424-f0a7-29b5cadd72e4@gmail.com \
--to=guangrong.xiao@gmail.com \
--cc=dgilbert@redhat.com \
--cc=jiang.biao2@zte.com.cn \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wei.w.wang@intel.com \
--cc=xiaoguangrong@tencent.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).