From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Williamson Subject: Re: KVM Test report, kernel a685b38... qemu 671d89d... Date: Wed, 16 Feb 2011 08:01:11 -0700 Message-ID: <1297868471.14733.186.camel@x201> References: <4D5B9487.2030309@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: "Hao, Xudong" , "kvm@vger.kernel.org" To: Avi Kivity , chrisw Return-path: Received: from mx1.redhat.com ([209.132.183.28]:65263 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751306Ab1BPPBS (ORCPT ); Wed, 16 Feb 2011 10:01:18 -0500 In-Reply-To: <4D5B9487.2030309@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, 2011-02-16 at 11:10 +0200, Avi Kivity wrote: > On 02/16/2011 11:05 AM, Hao, Xudong wrote: > > Hi, all, > > This is KVM test result against kvm.git a685b38e272587e644fedd37269ddb82df21c052, and qemu-kvm.git 671d89d6411655bb4f8058ce6eb86bb0bb8ec978. > > > > Currently qemu-kvm can build successfully on RHEL5, and Qcow image create failure issue also got fixed, our nightly testing resumed. One VT-d device assignment issue opened on latest KVM. > > > > New issue: > > 1. [VT-d] VT-d device passthrough fail to guest > > https://bugzilla.kernel.org/show_bug.cgi?id=29232 > > Extremely reproducible. Looks like it's a result of this kernel change: commit 47970b1b2aa64464bc0a9543e86361a622ae7c03 Author: Chris Wright Date: Thu Feb 10 15:58:56 2011 -0800 pci: use security_capable() when checking capablities during config space re Eric Paris noted that commit de139a3 ("pci: check caps from sysfs file open to read device dependent config space") caused the capability check to bypass security modules and potentially auditing. Rectify this by calling security_capable() when checking the open file's capabilities for config space reads. Reported-by: Eric Paris Signed-off-by: Chris Wright Signed-off-by: James Morris Chris, why isn't this working for us? Thanks, Alex