xbd(4) [netbsd man page]

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

NAME

     xbd -- Xen frontend paravirtualized block device interface

SYNOPSIS

     xbd* at xenbus?

DESCRIPTION

     The xbd interface forms the frontend part of the paravirtualized drivers used by Xen guest domains to have a block device interface.

     From a guest point of view, xbd is similar to a hard disk, and can be treated in the very same way regarding partitioning, file systems cre-
     ation and usage, and mounting.  By default, a NetBSD guest domain will assume that ``xbd0a'' serves as the root file system.

     When the host is NetBSD, the xbd interface is backed by a xbdback(4) interface.  In the XenStore, xbd and xbdback are identified by ``vbd''
     (virtual block device) entries.

DIAGNOSTICS

     xbd%d: using event channel %d  Specifies the event channel used by this xbd interface.

     xbd%d: %s MB, %d bytes/sect x %u sectors  Gives the total size of the xbd block device, its sector size and total number of sectors.

     xbd%d: WARNING: cache flush not supported by backend  The backend driver associated with this xbd device does not support cache flushing
     operation.  This can be problematic for file system operations that require cache sync to avoid data loss or corruption.

SEE ALSO

     xbdback(4), xenbus(4), dkctl(8)

HISTORY

     The xbd driver first appeared in NetBSD 3.0.

AUTHORS

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

BSD
								  January 8, 2011							       BSD

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

NAME

     xvif -- Xen backend paravirtualized network interface

SYNOPSIS

     pseudo-device xvif

DESCRIPTION

     The xvif interface forms the backend part of the paravirtualized drivers used by Xen domains to offer network connectivity.

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

     All xvif interfaces follow the ``xvifXiY'' naming convention, where 'X' represents the guest domain identifier, and 'Y' an arbitrary identi-
     fier; most of the time, it is the frontend interface identifier, e.g.  ``xennetY''.

     For convenience, the MAC address of an xvif interface is chosen by incrementing the third byte of the MAC address of the frontend device.

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

DIAGNOSTICS

     xvif%di%d: can't read %s/mac: %d  The MAC address for this interface could not be read from XenStore.

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

     xvif%di%d: Ethernet address %s  MAC address of the xvif interface.

SEE ALSO

     ifmedia(4), xennet(4), ifconfig(8)

HISTORY

     The xvif driver first appeared in NetBSD 4.0.

AUTHORS

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

BSD
								   April 7, 2011							       BSD