XVIF(4)

💅 xvif(4) — Xen backend paravirtualized network interface ✨

okay so this is from the xen Kernel Interfaces Manual, and it’s literally the backend-paravirtualized-network-interface moment. Let’s get into it bestie 🫶

🌸 NAME 🌸

xvif — Xen backend paravirtualized network interface 💖

🎀 SYNOPSIS 🎀

the whole synopsis is just this one line, no cap:

pseudo-device xvif

✨ DESCRIPTION ✨

The xvif interface is literally the backend part of the paravirtualized drivers Xen domains use to offer network connectivity. main character backend energy 🔥

When the guest domain is NetBSD, the endpoint of the xvif interface is a xennet(4) interface. In XenStore, xvif and xennet are identified by “vif” (virtual interface) entries.

All xvif interfaces follow the “xvifXiY” naming convention, where ‘X’ represents the guest domain identifier, and ‘Y’ an arbitrary identifier; most of the time, it is the frontend interface identifier, e.g. “xennetY”. iykyk 💅

For convenience, the MAC address of an xvif interface is chosen by incrementing the third byte of the MAC address of the frontend device. cute little byte glow-up tbh ✨

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

💀 DIAGNOSTICS 💀

these are the messages you might see, and what they mean:

• 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>. slay 🫶

---

mwah 💋 this cutie is from Debian, dated April 7, 2011, and the footer calls it XVIF(4). byeeee bestie 🎀✨