WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] collecting info on platforms with VT-d BIOS problems

To: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>
Subject: Re: [Xen-devel] collecting info on platforms with VT-d BIOS problems
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Sat, 23 Jan 2010 15:11:23 +0200
Cc: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Han, Weidong" <weidong.han@xxxxxxxxx>
Delivery-date: Sat, 23 Jan 2010 05:11:41 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <987664A83D2D224EAE907B061CE93D530C8A3D08@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <987664A83D2D224EAE907B061CE93D530C8A3D08@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Fri, Jan 22, 2010 at 04:22:08PM -0800, Kay, Allen M wrote:
> We would like to collect information on platforms that have problem with VT-d 
> PCI device passthrough using non-IGD PCI devices.  Note that IGD (integrated 
> display device) device passthrough code is still being worked on.
> 
> If you have encountered  VT-d problems on a particular platform using latest 
> xen-unstable, please provide the following information so that we can work 
> with OEM's to get their BIOS's fixed:
> 
>     (a) Platform details (OEM, Product/Model#,  Other identifying info)
>     (b) BIOS version/number
>     (c) Version of Xen with which failure is seen (if not the latest 
> xen-unstable)
>     (d) Specific error/failure details such as serial log
> 
> Thanks!
> 

I forwarded this email to xen-users.. Might get some feedback from there.

-- Pasi


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel