This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] VMX status report. Xen: #17061 & Xen0: #424 -- one new i

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] VMX status report. Xen: #17061 & Xen0: #424 -- one new issue
From: "Li, Haicheng" <haicheng.li@xxxxxxxxx>
Date: Tue, 19 Feb 2008 22:19:03 +0800
Delivery-date: Tue, 19 Feb 2008 06:19:33 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3E093FC.1CAB3%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <FC1D1B23302A22499C60C967336B2AE002636F4F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C3E093FC.1CAB3%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchzAKjIKUmxwJI5QxCmzyNuGXeDMQAAJzQsAAAL9wA=
Thread-topic: [Xen-devel] VMX status report. Xen: #17061 & Xen0: #424 -- one new issue
Keir Fraser wrote:
> On 19/2/08 14:06, "Li, Haicheng" <haicheng.li@xxxxxxxxx> wrote:
>> New issues:
>> ==============================================
>> 1) lots of error messages for l1e flags conflict are printed by
>> mtrr.c on PAE host
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1172 
> Presumably this is only if the guest has a VT-d device passed through
> to it? It would be handy to actually point that out in the bug report.

Yes, we found this issue on the guest with VT-d assignment; I add a
comment to this bug. Thanks.

-- haicheng

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>