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] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough

To: Jun Koi <junkoi2004@xxxxxxxxx>
Subject: Re: [Xen-devel] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 01 Sep 2009 11:28:05 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 01 Sep 2009 03:28:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <fdaac4d50909010241w42192736v424cc721da916e92@xxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acoq6GelFYRex3PKRbyxXPkwXCUHmQABnxmN
Thread-topic: [Xen-devel] Intel VT-d/Neocleus 1:1 mreged code for PCI passthrough
User-agent: Microsoft-Entourage/12.20.0.090605
On 01/09/2009 10:41, "Jun Koi" <junkoi2004@xxxxxxxxx> wrote:

> On Sun, Aug 30, 2009 at 4:50 PM, Keir Fraser<keir.fraser@xxxxxxxxxxxxx> wrote:
>> For passthrough to HVM guests without hardware IOMMU (e.g., VT-d), I
>> developed the attached prototype patch. I think this may already be in the
>> XCI tree. It also applies directly to Xen 3.4 branch, and could be applied
>> quite easily with a small amount of manual intervention to xen-unstable. If
>> passthough on 'old' system without hardware assistance is what you're after,
>> you might want to give the patch a go.
> 
> Could you confirm that this patch alone is enough?
> 
> I applied the patch against unstable code, and Xen hang up (or seems
> to hang up) in the middle of booting up Xen, with a black screen.

Try the attached patch. Also note that this approach only works for one HVM
domain (the first you create) and that this domain needs to be allocated all
of low physical memory -- this means for example that dom0 cannot allocate
this memory for a swiotlb and you may need 'swiotlb=off' on dom0's kernel
command line.

You can check in /var/log/xen/xend.log to see whether you created a
passthru-capable HVM guest successfully. There should be a message saying
'Domain <foo> is nativedom.' or 'Domain <foo> is NOT nativedom.'

 -- Keir

Attachment: 00-nativedom-for-unstable
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>