[Xen-users] PCI Passthrough of Perle Serial Card: Failed to assign device to IOMMU

["Nick Couchman" <Nick.Couchman@xxxxxxxxx>]

I'm trying to pass through a 4-port PCIe serial card to a Windows-based HVM 
domU, but am getting the error "Failed to assign device to IOMMU" when I try to 
power on the domU.  I'm running openSuSE 11.3, Xen 4.0.0 with kernel 
2.6.34.4-0.1-xen.  I have the following options specified on the Linux kernel 
module boot line:

pciback.hide=(04:00.0)(05:00.0)(05:00.1) pci=resource_alignment=05:00.0

The pciback module is loaded correctly, and correctly seizes all of the devices 
specified.  If I look at lspci information, I see the following:

pt-r310-4:~ # lspci -vt
-[0000:00]-+-00.0  Intel Corporation Core Processor DMI
           +-03.0-[04-05]----00.0-[05]--+-00.0  Perle Systems Ltd Device 0331
           |                            \-00.1  Perle Systems Ltd Device 0331

Looking at it without the -t option shows that 00:03.0 is my PCIe slot, 04:00.0 
is some sort of Perle PCIe to PCI bridge:

04:00.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI 
Bridge (rev aa)

05:00.0 is the serial controller, and 05:00.1 is another bridge of some sort.  
The serial controller is the one I'm really interested in passing in, and the 
one that generates this error.  If I just specify 05:00.1, I don't get any 
errors, but the domU dies immediately after startup.  If I specify the 04:00.0 
bridge, I get an error that the device is not owned by PCI Back or pci-stub, 
even though the output of lspci -v says that it is.

Any hints would be appreciated - I saw some similar issues regarding network 
card passthrough, but no apparent solutions.

Thanks,
Nick



--------
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
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users