From: Kevin Wolf <kwolf@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
"Ren, Yongjie" <yongjie.ren@intel.com>,
Avi Kivity <avi@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Liu, RongrongX" <rongrongx.liu@intel.com>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: Biweekly KVM Test report, kernel 51bfd299... qemu a1fce560...
Date: Tue, 12 Jun 2012 09:45:16 +0200 [thread overview]
Message-ID: <4FD6F38C.4080705@redhat.com> (raw)
In-Reply-To: <20120612015255.GA1997@amt.cnet>
Am 12.06.2012 03:52, schrieb Marcelo Tosatti:
> On Thu, Jun 07, 2012 at 01:13:50PM +0100, Stefan Hajnoczi wrote:
>>>>>> The 1st bad commit in your attached list is abc551bd
>>>>>> More detailed info:
>>>>>> 171d2f2249a360d7d623130d3aa991418c53716d good
>>>>>> fd453a24166e36a3d376c9bc221e520e3ee425af good
>>>>>> abc551bd456cf0407fa798395d83dc5aa35f6dbb bad
>>>>>> 823ccf41509baa197dd6a3bef63837a6cf101ad8 bad
>>>>>
>>>>> Thanks, this points to the qcow2 v3 changes. Let's try to find the exact
>>>>> culprit. I have rebased the qcow2 patches on top of that good merge
>>>>> (fd453a24). Please apply the attached mbox on top of this merge:
>>>>>
>>>>> git checkout fd453a24
>>>>> git am qcow2v3.mbox
>>>>>
>>>>> You can then start a git bisect between your new HEAD and fd453a24.
>>>>
>>>> Another thing you could try is if reverting e82dabd and bef0fd59 fixes
>>>> the problem for you.
>>>>
>>> After reverting bef0fd59, it can work fine.
>>
>> I'm unable to reproduce this with qemu-kvm.git/master
>> (18b012756fd041556764dfa2bb1f307b6923fb71) or the commit you
>> 3fd9fedb9fae4517d93d76e93a2924559cacf2f6 reported as bad. The RHEL 6
>> guest boots without any issues. My host kernel is Linux 3.2 (Debian
>> 3.2.0-2-amd64). The guest is Linux 2.6.32-71.el6.
>>
>> Since the guest sees a disk read error, it may be useful to add
>> printfs to hw/ide/core.c:ide_sector_read_cb(). Let's find out why the
>> disk read is failing.
>
> Any news on this problem?
We're still waiting for the test results with Jan's timer fix.
But, Marcelo, you mentioned that you can reproduce it, too. Maybe you
can give it a try?
Kevin
next prev parent reply other threads:[~2012-06-12 7:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 3:34 Biweekly KVM Test report, kernel 51bfd299... qemu a1fce560 Ren, Yongjie
2012-05-21 8:27 ` Avi Kivity
2012-05-21 9:05 ` Kevin Wolf
2012-05-21 9:45 ` Ren, Yongjie
2012-05-21 15:29 ` Kevin Wolf
2012-05-22 7:40 ` Ren, Yongjie
2012-05-30 20:28 ` Marcelo Tosatti
2012-06-01 7:57 ` Ren, Yongjie
2012-06-01 13:18 ` Jan Kiszka
[not found] ` <4FC87DFF.4020005@redhat.com>
2012-06-04 13:51 ` Kevin Wolf
2012-06-06 2:17 ` Ren, Yongjie
2012-06-07 12:13 ` Stefan Hajnoczi
2012-06-12 1:52 ` Marcelo Tosatti
2012-06-12 7:45 ` Kevin Wolf [this message]
2012-06-12 11:01 ` Marcelo Tosatti
2012-06-12 23:25 ` Marcelo Tosatti
2012-06-13 10:28 ` Ren, Yongjie
2012-06-13 10:32 ` Kevin Wolf
2012-06-15 1:13 ` Ren, Yongjie
2012-05-30 20:29 ` Marcelo Tosatti
2012-06-01 8:03 ` 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=4FD6F38C.4080705@redhat.com \
--to=kwolf@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=rongrongx.liu@intel.com \
--cc=stefanha@gmail.com \
--cc=yongjie.ren@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).