VIC(4)

πŸ“¦ in nixpkgs unstable

πŸ’… vic β€” the VMware VMXnet Virtual Interface Controller device, bestie

okay so this page is VIC(4) from the Kernel Interfaces Manual β€” yes we're reading kernel docs for fun now, that's the energy 🧚


✨ NAME ✨

vic β€” the VMware VMXnet Virtual Interface Controller device. that's it, that's the name, she's iconic πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

vic* at pci?

literally just that. one line. she's lowkey mysterious like that πŸ’…


🌸 DESCRIPTION 🌸

okay so the vic driver? it's the whole support system for the VMXnet virtual NIC β€” that's the virtual network card you get inside virtual machines made by VMware. and here's the gag: it looks like a plain little Ethernet device from the outside πŸŽ€ but ngl it's actually a whole virtual network interface wired straight into the underlying host operating system. main character energy fr fr.

so this driver speaks the vmxnet driver protocol, and it's the alternative to the emulated pcn(4) and em(4) interfaces β€” those also exist in the VMware environment, so you got options bestie πŸ’–. the vic driver is optimized for the virtual machine, and depending on what the underlying host OS is and what the physical network interface controller of the host is, it can bring advanced capabilities to the table. she adapts. she's versatile. πŸ”₯

the vic driver supports VMware virtual NICs from these products:

  • VMware ESX 2.0 and newer ✨
  • VMware GSX 2.5 and newer ✨
  • VMware Server 1.0 and newer ✨
  • VMware Workstation 4.5 and newer ✨
  • VMware Fusion 1.0 and newer ✨

and now the media types, because there's exactly one and she's the queen:

πŸŽ€ media types πŸŽ€

  • autoselect β€” enables autoselection of the media type and options. the driver always uses the fastest available speed plus the media options that the underlying host of the virtual machine hands over. no negotiating, no drama, she just takes the best one 🫢

for more info on configuring this device, go see ifconfig(8). iykyk πŸ’œ


🌈 EXAMPLES 🌈

you gotta add this entry to the VMware configuration file to actually get the vic device β€” no cap, it will not appear without this:

ethernet0.virtualDev = "vmxnet"

put that in and you're slaying πŸ’…βœ¨


πŸ‘‘ SEE ALSO πŸ‘‘

arp(4), em(4), ifmedia(4), intro(4), netintro(4), pci(4), pcn(4), vmx(4), hostname.if(5), ifconfig(8)

the whole friend group, we stan a linked circle πŸ«ΆπŸ“


πŸ•°οΈ HISTORY πŸ•°οΈ

the vic driver first appeared in OpenBSD 3.9. a vintage queen, honestly ⭐


πŸ’– AUTHORS πŸ’–

the vic driver was written by Reyk Floeter <reyk@openbsd.org> and David Gwynne <dlg@openbsd.org>. absolute legends, we thank them for their service πŸ™‡β€β™€οΈβœ¨


okay that's the whole page, nothing skipped, every single detail present and accounted for πŸ’€πŸ«Ά

and a lil sign-off: this beauty is from the Debian edition, dated January 4, 2018, filed under VIC(4) β€” bookmark it, screenshot it, live your truth πŸŽ€πŸ’œ

πŸ“¦ where this page comes from
  • nixpkgs unstable: cvs-export
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms