RE: Biweekly KVM Test report, kernel 51bfd299... qemu a1fce560...

Ren, Yongjie
2012-06-15T01:13:15Z

> -----Original Message-----
> From: Kevin Wolf [mailto:kwolf@redhat.com]
> Sent: Wednesday, June 13, 2012 6:33 PM
> To: Ren, Yongjie
> Cc: Marcelo Tosatti; Stefan Hajnoczi; Avi Kivity; kvm@vger.kernel.org; Liu,
> RongrongX; Anthony Liguori
> Subject: Re: Biweekly KVM Test report, kernel 51bfd299... qemu
> a1fce560...
>
> Am 13.06.2012 12:28, schrieb Ren, Yongjie:
> >> -----Original Message-----
> >> From: Marcelo Tosatti [mailto:mtosatti@redhat.com]
> >> Sent: Wednesday, June 13, 2012 7:25 AM
> >> To: Kevin Wolf
> >> Cc: Stefan Hajnoczi; Ren, Yongjie; Avi Kivity; kvm@vger.kernel.org; Liu,
> >> RongrongX; Anthony Liguori
> >> Subject: Re: Biweekly KVM Test report, kernel 51bfd299... qemu
> >> a1fce560...
> >>
> >> On Tue, Jun 12, 2012 at 09:45:16AM +0200, Kevin Wolf wrote:
> >>> 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.
> >>
> >> OK, Ren, can you please retest with qemu-kvm.git master? TIA.
> >>
> > Yes, I re-tested with latest qemu-kvm.git master branch (commit:
> 0a948cbb).
> > I found the qcow2 image 'disk error' issue can't be reproduced in latest
> tree.
> > And, I can still reproduce it against commit e54f008e (May 9) as I
> reported for this bug.
> > Any recent patch has been checked in to fix this issue?
> > Maybe, Jan's "kvm: i8254: Fix conversion of in-kernel to userspace
> state"?
>
> Yes, this is what we expected to fix the problem. If you like to verify,
> you can try applying only this patch on top of the broken commit e54f008e.
>
Confirmed. Jan's patch "kvm: i8254: Fix conversion of in-kernel to userspace state" fixed the following issue.