Differences between version 2 and revision by previous author of XenPciPassthrough.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Tuesday, July 4, 2006 12:13:58 am | by AristotlePagaltzis | Revert |
| Older page: | version 1 | Last edited on Saturday, July 1, 2006 4:31:13 pm | by DanielLawson | Revert |
@@ -1,33 +1,34 @@
+Xen has a feature which lets you pass a [PCI] device through to an unpriviledged domain. Only the unpriviledged domain has access to this specific [PCI] device – the priviledged domain binds to the [PCI] device with a dummy drive that stops the dom0 from accessing it as well.
-Xen has a feature which lets you pass a PCI device through to an unpriviledged domain. Only the unpriviledged domain has access to this specific PCI device - the priviledged domain binds to the PCI device with a dummy drive that stops the dom0 from accessing it as well.
-
-network interface
through to one domain, eg for a fileserver
or firewall
domU.
+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]
. I can't remember which this is at this point, I'll update this page next time I look at it.
-You'll also need the PCI id
of the device in question, in the xx:xx:x notation displayed by lspci. Note that the formatting is important -
don't drop or add leading 's!
+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 's!
-In some cases it is required to set the pciback.permissive option -
this is for drivers which need to write to registers on the pci
device itself. Apparently some network cards
will fail to operate without this, and from what I've read it doesn't hurt to have it enabled regardless.
+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.
!! Kernel options
-In grub.conf, add something like the following to your kernel line. This assumes the device we are passing through has a PCI id of 03:00.
+In <tt>
grub.conf</tt>
, add something like the following to your <tt>
kernel</tt>
line.
<verbatim>
pciback.permissive pciback.hide=(03:00.0)
</verbatim>
-!! Xen config file
+This assumes the device we are passing through has a [PCI] ID of <tt>03:00.</tt>.
+
+
!! [
Xen]
config file
-In your xen
config file for the domain, add a line that looks like the following, again assuming a PCI id
of 03:00.
+In your [Xen]
config file for the domain, add a line that looks like the following, again assuming a [
PCI] ID
of <tt>
03:00.</tt>:
<verbatim>
pci = ['03:00.0']
</verbatim>
-Note that if this is a network interface, it will come up in addition to any you specify with you
vif config option
+Note that if this is a network interface, it will come up in addition to any you specify with your <tt>
vif</tt>
config option.
----
Part of CategoryXen
