From: Avi Kivity <avi@redhat.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Kevin Wolf <kwolf@redhat.com>
Subject: Re: Biweekly KVM Test report, kernel 51bfd299... qemu a1fce560...
Date: Mon, 21 May 2012 11:27:34 +0300 [thread overview]
Message-ID: <4FB9FC76.2040802@redhat.com> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A100C2A83@SHSMSX101.ccr.corp.intel.com>
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?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-05-21 8:27 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 [this message]
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
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=4FB9FC76.2040802@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.