Differences between version 3 and predecessor to the previous major change of XenPciPassthrough.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 3 | Last edited on Thursday, May 3, 2007 8:40:45 am | by GreigMcGill | Revert |
| Older page: | version 2 | Last edited on Tuesday, July 4, 2006 12:13:58 am | by AristotlePagaltzis | Revert |
@@ -3,9 +3,14 @@
This could be used for passing a [SCSI] controller or [NIC] through to one domain, eg. for a file server or FireWall domU.
!! What you'll need
-You'll have to compile in the right [PCI] backend driver for [Xen]. I can't remember which this is at this point, I'll update this page next time I look at it.
+You'll have to compile in the right [PCI] backend driver for [Xen].
+
+<verbatim>
+ CONFIG_XEN_PCIDEV_FRONTEND=y (for DomU kernels)
+ CONFIG_XEN_PCIDEV_BACKEND=y (for Dom0 kernels)
+</verbatim>
You'll also need the [PCI] ID of the device in question, in the <tt>xx:xx:x</tt> notation displayed by lspci(8). Note that the formatting is important – don't drop or add leading 0's!
In some cases it is required to set the <tt>pciback.permissive</tt> option – this is for drivers which need to write to registers on the [PCI] device itself. Apparently some [NIC]s will fail to operate without this, and from what I've read it doesn't hurt to have it enabled regardless.
