Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   9087 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

XENNET(4)		 BSD 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 driv‐
     ers 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 inter‐
     face 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 inter‐
     rupt) 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

                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 

Vote for polarhome