Manual Reference Pages - XNB (4)
- Xen Paravirtualized Backend Ethernet Driver
To compile this driver into the kernel, place the following lines in your
kernel configuration file:
.Cd options XENHVM
.Cd device xenpci
driver provides the back half of a paravirtualized
The netback and netfront drivers appear to their respective operating
systems as Ethernet devices linked by a crossover cable.
will run on Domain 0 and the netfront driver will run on a guest domain.
However, it is also possible to run
on a guest domain.
It may be bridged or routed to provide the netfront
domain access to other guest domains or to a physical network.
In most respects, the
device appears to the OS as any other Ethernet device.
It can be configured at runtime entirely with
In particular, it supports MAC changing, arbitrary MTU sizes, checksum
offload for IP, UDP, and TCP for both receive and transmit, and TSO.
before enabling txcsum, rxcsum, or tso.
The following read-only variables are available via
Displays information about the ring buffers used to pass requests between the
netfront and netback.
Mostly useful for debugging, but can also be used to
get traffic statistics.
Runs a builtin suite of unit tests and displays the results.
Does not affect the operation of the driver in any way.
Note that the test suite simulates error conditions; this will result in
error messages being printed to the system log.
device driver first appeared in
.Fx 10.0 .
driver was written by
.An Alan Somers Aq Mt asomers@FreeBSD.org
and John Suykerbuyk.
Packets sent through Xennet pass over shared memory, so the protocol includes
no form of link-layer checksum or CRC.
Furthermore, Xennet drivers always report to their hosts that they support
receive and transmit checksum offloading.
They "offload" the checksum calculation by simply skipping it.
That works fine for packets that are exchanged between two domains on the same
However, when a Xennet interface is bridged to a physical interface,
a correct checksum must be attached to any packets bound for that physical
lacks any mechanism for an Ethernet device to
inform the OS that newly received packets are valid even though their checksums
So if the netfront driver is configured to offload checksum calculations,
it will pass non-checksumed packets to
which must then calculate the checksum in software before passing the packet
to the OS.
For this reason, it is recommended that if
is bridged to a physical interface, then transmit checksum offloading should be
disabled on the netfront.
The Xennet protocol does not have any mechanism for the netback to request
the netfront to do this; the operator must do it manually.
driver does not properly checksum UDP datagrams that span more than one
Nor does it correctly checksum IPv6 packets.
To workaround that bug, disable transmit checksum offloading on the
Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.