XENNET(4)

📦 version 11.0, in nixpkgs unstable

💅 xennet(4) — like, the Xen frontend paravirtualized network interface, bestie 🦋

okay so real quick — this page lives in the xen Kernel Interfaces Manual, and it's all about xennet, the Xen frontend paravirtualized network interface. yes it's a mouthful, no we're not skipping any of it. let's go ✨

🌸 NAME 🌸

xennet — Xen frontend paravirtualized network interface. that's the whole vibe. she's a frontend, she's paravirtualized, she's a network interface. iconic.

🎀 SYNOPSIS 🎀

xennet* at xenbus?

that's it. that's the whole config line. so clean, so minimal, main character energy fr fr.

💖 DESCRIPTION 💖

okay so picture this: the xennet interface is the frontend part of the paravirtualized drivers that Xen guest domains use to get network connectivity. like, your guest domain wants internet? xennet is the girl handing it the aux cord 🎧

when the host domain is NetBSD, the endpoint of the xennet interface is a xvif(4) interface. and in the XenStore, xvif and xennet are identified by “vif” (virtual interface) entries. yep, that's literally what they're called, no notes.

conceptually, frontends and backends drivers are basically two Ethernet cards connected via a crossover cable. like two besties holding hands across the void 💞 no cap.

also!! xennet interfaces can pass VLAN tagged packets. she's flexible, she's accommodating, she ate. 🔥

⭐ DIAGNOSTICS ⭐

these are the messages she might yell at you. all of them. every single one. 🫶

  • xennet%d: can't read mac address, err %d — the MAC address for this interface could not be read from XenStore. 😭 it's not there, she can't find it, she's trying her best.
  • 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. 🚩 like, girl, that's not a MAC address, what is that.
  • xennet%d: using event channel %d — the Xen event channel (virtual interrupt) ID associated to this xennet. basically her little virtual-interrupt ID tag 💅
  • 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. copying, not sharing. respectful boundaries. periodt. 🧚

🦋 SEE ALSO 🦋

the whole squad, fr fr 🫶

🌈 HISTORY 🌈

the xennet driver first appeared in NetBSD 3.0. she's been around. she's a legacy icon. 👑

💜 AUTHORS 💜

the xennet driver was written by Manuel Bouyer <bouyer@NetBSD.org> and Christian Limpach <chris@pin.lu>. absolute legends, both of them. 🎀

ok so that's the whole page bestie, every flag, every message, every name — nothing skipped, nothing invented, we ate and left no crumbs 💅✨

and that's a wrap on the Debian build of this page, dated April 5, 2020 — xennet(4), signing off 🍓💖

📦 where this page comes from