From: Avi Kivity <avi@redhat.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Alex Williamson <Alex.Williamson@redhat.com>
Subject: Re: Biweekly KVM Test report, kernel 681fb677... qemu 05f17375...
Date: Sun, 19 Jun 2011 11:57:36 +0300 [thread overview]
Message-ID: <4DFDBA00.9000608@redhat.com> (raw)
In-Reply-To: <CE59C043D0EC3349B2BF41C0EC72229B12D187CE7A@shsmsx501.ccr.corp.intel.com>
On 06/18/2011 07:43 AM, Ren, Yongjie wrote:
> Hi All,
> This is KVM test result against kvm.git 681fb677ace0754589792c92b8dbee9884d07158 based on kernel 3.0.0-rc2+, and qemu-kvm.git 05f1737582ab6c075476bde931c5eafbc62a9349.
>
> We found a new vt-d bug about “NIC assignment order in command line makes some NIC can't work”.
> A vt-d bug was fixed in kvm.git upstream.
>
> New issue:
> 1. NIC assignment order in command line make some NIC can't work
> https://bugs.launchpad.net/qemu/+bug/799036
>
> Fixed issue:
> 1. [VT-d] NIC cannot work when it had been used before
> https://bugs.launchpad.net/qemu/+bug/754591
cc += Alex
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-06-19 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 4:43 Biweekly KVM Test report, kernel 681fb677... qemu 05f17375 Ren, Yongjie
2011-06-19 8:57 ` Avi Kivity [this message]
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=4DFDBA00.9000608@redhat.com \
--to=avi@redhat.com \
--cc=Alex.Williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox