From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: "Zhou, Chao" <chao.zhou@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: KVM Test report, kernel 205befd9... qemu ca916d37...
Date: Mon, 19 Aug 2013 16:17:42 +0800 [thread overview]
Message-ID: <5211D4A6.9080209@linux.vnet.ibm.com> (raw)
In-Reply-To: <40352EBA8B4DF841A9907B883F22B59B11733D50@SHSMSX101.ccr.corp.intel.com>
On 08/19/2013 03:44 PM, Zhou, Chao wrote:
>> -----Original Message-----
>> From: Xiao Guangrong [mailto:xiaoguangrong@linux.vnet.ibm.com]
>> Sent: Monday, August 19, 2013 3:34 PM
>> To: Zhou, Chao
>> Cc: kvm@vger.kernel.org
>> Subject: Re: KVM Test report, kernel 205befd9... qemu ca916d37...
>>
>> On 08/19/2013 03:06 PM, Zhou, Chao wrote:
>>> Hi All,
>>>
>>> This is KVM upstream test result against kvm.git next branch and
>> qemu-kvm.git uq/master branch.
>>> kvm.git next branch:
>> 205befd9a5c701b56f569434045821f413f08f6d based on kernel 3.11.0-rc1
>>> qemu-kvm.git uq/master branch:
>> ca916d3729564d0eb3c2374a96903f7e8aced8a7
>>>
>>> We found one new bug and one bug fixed in the past two weeks.
>>>
>>> New issue (1):
>>> 1. Guest hang after live migration
>>> https://bugs.launchpad.net/qemu/+bug/1213797
>>
>> Could you please do bisect to find the bad commit out? :)
>
> This commit cause the bug:
> commit 0779caeb1a17f4d3ed14e2925b36ba09b084fb7b
> Author: Arthur Chunqi Li <yzt356@gmail.com>
>
Can not find this comment on neither next nor queue branch...
could you please show the full log?
next prev parent reply other threads:[~2013-08-19 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8F9B1D95D29E8A42905D3F4AAB23ED140A617B7C@SHSMSX103.ccr.corp.intel.com>
2013-08-19 7:06 ` KVM Test report, kernel 205befd9... qemu ca916d37 Zhou, Chao
2013-08-19 7:34 ` Xiao Guangrong
2013-08-19 7:44 ` Zhou, Chao
2013-08-19 8:17 ` Xiao Guangrong [this message]
2013-08-19 8:30 ` Ren, Yongjie
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=5211D4A6.9080209@linux.vnet.ibm.com \
--to=xiaoguangrong@linux.vnet.ibm.com \
--cc=chao.zhou@intel.com \
--cc=kvm@vger.kernel.org \
/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