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

Ren, Yongjie
2012-06-01T08:03:12Z

> -----Original Message-----
> From: Marcelo Tosatti [mailto:mtosatti@redhat.com]
> Sent: Thursday, May 31, 2012 4:30 AM
> To: Ren, Yongjie
> Cc: Kevin Wolf; Avi Kivity; kvm@vger.kernel.org; Liu, RongrongX
> Subject: Re: Biweekly KVM Test report, kernel 51bfd299... qemu
> a1fce560...
>
> On Tue, May 22, 2012 at 07:40:29AM +0000, Ren, Yongjie wrote:
> > > >>
> > > > 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.
>
> What do you mean by "If you press some key to continue, after being
> automatically repaired, the guest can boot up." exactly?
>
I mean if I press keys to continue, the system will repair the disk automatically.
After the check or reparation, the guest will boot up.

> That the error is seen once and after pressing a key it disappears?
>
Yes, it appears only once.
After the reparation, I don't meet the issue on the same qcow2 image.

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