xennet(4) [netbsd man page]

XENNET(4)						 BSD/xen Kernel Interfaces Manual						 XENNET(4)

NAME

     xennet -- Xen frontend paravirtualized network interface

SYNOPSIS

     xennet* at xenbus?

DESCRIPTION

     The xennet interface forms the frontend part of the paravirtualized drivers used by Xen guest domains to have network connectivity.

     When the host domain is NetBSD, the endpoint of the xennet interface is a xvif(4) interface.  In the XenStore, xvif and xennet are identified
     by ``vif'' (virtual interface) entries.

     Conceptually, frontends and backends drivers are similar to two Ethernet cards connected via a crossover cable.

DIAGNOSTICS

     xennet%d: can't read mac address, err %d  The MAC address for this interface could not be read from XenStore.

     xennet%d: %s is not a valid mac address  The MAC address specified in the configuration file of the newly created guest domain is invalid.

     xennet%d: using event channel %d  The Xen event channel (virtual interrupt) ID associated to this xennet.

     xennet%d: using RX copy mode  The xennet and its associated endpoint use copy mode for communication: packets are copied from one domain's
     memory to another.

     xennet%d: using RX flip mode  The xennet and its associated endpoint use flip mode for communication: packets are passed by remapping memory
     pages between domains.

SEE ALSO

     ifmedia(4), xenbus(4), xvif(4), ifconfig(8)

HISTORY

     The xennet driver first appeared in NetBSD 3.0.

AUTHORS

     The xennet driver was written by Manuel Bouyer <bouyer@NetBSD.org> and Christian Limpach <chris@pin.lu>.

BSD
								  January 8, 2011							       BSD

PCIBACK(4)						 BSD/xen Kernel Interfaces Manual						PCIBACK(4)

NAME

     pciback -- Xen backend paravirtualized PCI pass-through driver

SYNOPSIS

     pciback* at pci?

DESCRIPTION

     The pciback driver is the backend part of the PCI pass-through functionality that can be used by the Xen dom0 to export pci(4) devices to a
     guest domain.  To export a PCI device to a guest domain, the device has to be attached to pciback in the dom0.

     When the guest domain is NetBSD, the device attached to the pciback driver will attach to a xpci(4) bus inside the guest domain.

EXAMPLES

     To attach a device to the pciback driver, follow these steps:
	   1.	look for the device PCI ID, via pcictl(8).
	   2.	edit boot.cfg(5) and add the PCI ID to the list of PCI IDs that you want to attach to pciback, in bus:device.function notation.
		The list is passed to dom0 module via the pciback.hide parameter:
		      pciback.hide=(bus:dev.fun)(bus:dev.func)(...)
		See also boot(8).
	   3.	reboot dom0.
	   4.	add the PCI ID to the list of PCI devices in the domain configuration file:
		      pci = ['bus:dev.fun', '...']
	   5.	start the guest domain.

SEE ALSO

     pci(4), xpci(4), boot(8), pcictl(8)

HISTORY

     The pciback driver first appeared in NetBSD 5.1.

AUTHORS

     The pciback driver was written by Manuel Bouyer <bouyer@NetBSD.org>.

CAVEATS

     Currently, to attach a device to the pciback backend, this procedure has to be performed at boot(8) time.	In the future, it will be possible
     to do it without requiring a dom0 reboot.

SECURITY CONSIDERATIONS

     As PCI passthrough offers the possibility for guest domains to send arbitrary PCI commands to a physical device, this has direct impact on
     the overall stability and security of the system.	For example, in case of erroneous or malicious commands, the device could overwrite physi-
     cal memory portions, via DMA.

BSD
								  January 8, 2011							       BSD