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

Ren, Yongjie
2012-05-22T07:40:33Z

> -----Original Message-----
> From: Kevin Wolf [mailto:kwolf@redhat.com]
> Sent: Monday, May 21, 2012 11:30 PM
> To: Ren, Yongjie
> Cc: Avi Kivity; kvm@vger.kernel.org; Liu, RongrongX
> Subject: Re: Biweekly KVM Test report, kernel 51bfd299... qemu
> a1fce560...
>
> Am 21.05.2012 11:45, schrieb Ren, Yongjie:
> >> -----Original Message-----
> >> From: Kevin Wolf [mailto:kwolf@redhat.com]
> >> Sent: Monday, May 21, 2012 5:05 PM
> >> To: Avi Kivity
> >> Cc: Ren, Yongjie; kvm@vger.kernel.org
> >> Subject: Re: Biweekly KVM Test report, kernel 51bfd299... qemu
> >> a1fce560...
> >>
> >> Am 21.05.2012 10:27, schrieb Avi Kivity:
> >>> On 05/21/2012 06:34 AM, Ren, Yongjie wrote:
> >>>> Hi All,
> >>>>
> >>>> This is KVM upstream test result against kvm.git
> >> 51bfd2998113e1f8ce8dcf853407b76a04b5f2a0 based on kernel
> 3.4.0-rc7,
> >> and qemu-kvm.git a1fce560c0e5f287ed65d2aaadb3e59578aaa983.
> >>>>
> >>>> We found 1 new bug and 1 bug got fixed in the past two weeks.
> >>>>
> >>>> New issue (1):
> >>>> 1. disk error when guest boot up via qcow2 image
> >>>> https://bugs.launchpad.net/qemu/+bug/1002121
> >>>> -- Should be a regression on qemu-kvm.
> >>>>
> >>>
> >>> Kevin, is this the known regression in qcow2 or something new?
> >>
> >> If the commit ID is right, it must be something new. The regression that
> >> Marcelo found was fixed in 54e68143.
> >>
> > Yes, it's right. This should be a new regression.
> > I looked at the comment of 54e68143, and found it was not related the
> issue I reported.
> >
> >> The Launchpad bug refers to commit e54f008ef, which doesn't include
> this
> >> fix indeed. So was the test repeated with a more current qemu-kvm
> >> version after filing the bug in Launchpad, or is the commit ID in this
> >> mail wrong?
> >>
> > Latest commit 3fd9fedb in qemu-kvm master tree still has this issue.
> > And, the commit ID provided in Launchpad is correct.
>
> Can you please check if the bug exists in upstream qemu.git as well?
>
This bug doesn't exist on upstream qemu.git with latest commit: fd4567d9.
So, it should only exists on qemu-kvm tree.

> In any case, it would be helpful to bisect the problem.
>
> Kevin