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


[Xen-users] PCI Passthrough

To: "XEN Mailing List" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] PCI Passthrough
From: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
Date: Wed, 30 Sep 2009 09:00:46 -0600
Delivery-date: Wed, 30 Sep 2009 08:01:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

A question that I think I probably know the answer to, but I want to verify.  Do PCI Passthrough to HVM domUs require VTd or IOMMU?  From what I've read in various places around the Internet, the answer is yes, but it's never been explicitly stated.  I have a multi-port PCI serial card on a non-VTd-capable machine that I want to passthrough to a Windows domU.  PCI passthrough would be the easiest option, except for the lack of VTd.  I tried doing something with the IRQ and IOPORTS to pass it through, but I ended up with a device type "Xen Ioports" in my Windows domU and couldn't really get the correct driver installed.  Any hints would be appreciated - even if it's to say, "Sorry, you're out of luck - go buy a machine with VTd."



This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>