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 b350497... qemu 27f3686...
Date: Mon, 07 Mar 2011 11:03:42 +0200 [thread overview]
Message-ID: <4D749F6E.7010109@redhat.com> (raw)
In-Reply-To: <CE59C043D0EC3349B2BF41C0EC72229B337A1248@shsmsx501.ccr.corp.intel.com>
Copying Alex for a device assignment issue.
On 03/07/2011 08:07 AM, Ren, Yongjie wrote:
> Hi, all,
> This is KVM test result against kvm.git b35049715d619c9badaea07dec766787b433facf based kernel 2.6.38-rc6, and qemu-kvm.git 27f368604a3d27ca4ddac0f62a6928bb93cdacd5.
>
> No. 29232 bug "VT-d device passthrough fail to guest" has been fixed.
> There's a new bug about NIC assignment. NIC doesn't work with "pci=nomsi" configuration in grub.conf.
>
> New issues:
> 1. [VT-d] VT-d device passthrough fail to guest
> https://bugs.launchpad.net/qemu/+bug/730441
>
> Fixed issues:
> https://bugzilla.kernel.org/show_bug.cgi?id=29232
>
> Old Issues:
> ================================================
> 1. ltp diotest running time is 2.54 times than before
> https://sourceforge.net/tracker/?func=detail&aid=2723366&group_id=180599&atid=893831
> 2. perfctr wrmsr warning when booting 64bit RHEl5.3
> https://sourceforge.net/tracker/?func=detail&aid=2721640&group_id=180599&atid=893831
>
>
> Best Regards,
> Yongjie Ren (Jay)
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-03-07 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 6:07 Biweekly KVM Test report, kernel b350497... qemu 27f3686 Ren, Yongjie
2011-03-07 9:03 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-07 9:02 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=4D749F6E.7010109@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