xenbus(4) [netbsd man page]

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

NAME

     xenbus -- Xen bus abstraction for paravirtualized drivers

SYNOPSIS

     xenbus* at hypervisor?

DESCRIPTION

     The xenbus interface offers an abstraction layer used for communications between domains.	xenbus is mainly used by split paravirtualized
     drivers, so backend and frontend devices can exchange configuration information, properties, and statistics.

     xenbus is not used for data transfer (network frames, blocks, PCI commands, ...). This functionality is implemented by each paravirtualized
     driver independently, typically via shared memory pages and an event channel that serves as a virtual interrupt, for signaling.

     The xenbus abstraction offers guests the possibility to read and write information directly from and to XenStore, a centralized database
     accessible to all domains.  For this reason, it also has an event channel associated to it, so that domains can post messages to the XenStore
     facility.

DIAGNOSTICS

     xenbus0: using event channel %d  The event channel associated to the xenbus interface, for communication with the XenStore database.

SEE ALSO

     pciback(4), xbd(4), xbdback(4), xennet(4), xpci(4), xvif(4)

HISTORY

     The xenbus driver first appeared in NetBSD 3.0.

AUTHORS

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

BSD
								  January 8, 2011							       BSD

Check Out this Related Man Page

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

NAME

     xpci -- Xen frontend paravirtualized PCI pass-through driver

SYNOPSIS

     xpci* at xenbus?
     pci* at xpci?

DESCRIPTION

     The xpci driver is the frontend part of the PCI pass-through functionality that can be used by Xen guest domains to communicate with PCI
     devices.

     From a guest point of view, xpci is similar to a pci(4) bus, except that the guest talks with the PCI backend driver instead of the real
     physical device directly.

     When the host domain is NetBSD, the xpci driver is backed by a pciback(4) driver within the dom0.

SEE ALSO

     pci(4), pciback(4), xenbus(4)

HISTORY

     The xpci driver first appeared in NetBSD 5.1.

AUTHORS

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

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

Linux and UNIX Man Pages

xenbus(4) [netbsd man page]

Check Out this Related Man Page

We Also Found This Discussion For You

1. Linux

additional interfaces in XEN environment

Discussion started by: sap4ever