From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Wolf Subject: Re: Biweekly KVM Test report, kernel 51bfd299... qemu a1fce560... Date: Mon, 21 May 2012 11:05:07 +0200 Message-ID: <4FBA0543.7060008@redhat.com> References: <1B4B44D9196EFF41AE41FDA404FC0A100C2A83@SHSMSX101.ccr.corp.intel.com> <4FB9FC76.2040802@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "Ren, Yongjie" , "kvm@vger.kernel.org" To: Avi Kivity Return-path: Received: from mx1.redhat.com ([209.132.183.28]:20347 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932084Ab2EUJFU (ORCPT ); Mon, 21 May 2012 05:05:20 -0400 In-Reply-To: <4FB9FC76.2040802@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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. 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? If the bug does still exist in current master, it would be helpful to bisect it. Kevin