September 10Sep 10 Could somebody please explain to me in basic terms what the difference is between virtio and virtio-net when using VM'sThanks in advance.
October 23Oct 23 On 9/10/2026 at 3:23 PM, HackerHog said:Could somebody please explain to me in basic terms what the difference is between virtio and virtio-net when using VM'sThanks in advance.unraid usis qemu via libvirt usig domin xml format.https://libvirt.org/formatdomain.htmlsee docs as well: https://docs.unraid.net/unraid-os/using-unraid-to/create-virtual-machines/vm-setup/virtio vs. virtio-netFeaturevirtiovirtio-netMeaningGeneral paravirtualized device frameworkNetwork device built on VirtIOPurposeSupports network, disk, memory, and other devicesSpecifically virtual networkingQEMU network deviceUsually virtio-net-pcivirtio-net-pciPerformanceDepends on device typeHigh-performance virtual networkingGuest driversDepends on deviceLinux virtio_net, Windows NetKVMRecommended for VM networkingYes, when referring to VirtIO networkingYesBottom line: For a normal Unraid VM network adapter, selecting virtio in the libvirt configuration typically results in QEMU using a virtio-net-pci network device. You aren't choosing between two competing network drivers.Here is an example of recommended libvirt XML for UnraidFor a VM connected to your LAN through Unraid's br0 bridge:<interface type='bridge'> <mac address='52:54:00:12:34:56'/> <source bridge='br0'/> <model type='virtio'/> <driver name='vhost'/> </interface>XML settingPurposetype='bridge'Connects the VM to a host network bridgesource bridge='br0'Uses Unraid's br0 bridgemodel type='virtio'Selects the VirtIO network adapterdriver name='vhost'Uses kernel-accelerated networkingmac addressVM's virtual MAC address; preserve its existing valueThe vhost driver is optional. Without it, libvirt normally selects vhost when supported and falls back to QEMU's userspace backend.*note the model type... this is what you're referencing...Primary network adapter modelsThese are the most relevant models for modern x86-64 Unraid VMs.ModelEmulated hardwareGuest supportGeneral recommendationvirtioVirtIO paravirtual NICLinux, Windows with VirtIO driversBest overallvirtio-transitionalLegacy-compatible VirtIOOlder and newer VirtIO driversCompatibilityvirtio-non-transitionalModern VirtIO 1.0+Modern Linux and Windows VirtIOModern VMse1000Intel 82540EM-class GigabitBroad OS supportCompatibilitye1000eIntel PCIe GigabitModern OS supportGood fallbackigbIntel 82576 GigabitModern OS with igb driverSpecialized testingrtl8139Realtek RTL8139 100 MbpsVery broad older OS supportLegacy systemsvmxnet3VMware paravirtual NICVMware-compatible guest driversVMware migrationspcnetAMD PCnet PCI NICOlder operating systemsLegacy systemsne2k_pciNE2000-compatible PCI NICOlder operating systemsVery old guestsNot every model is supported by every QEMU/libvirt version. These are model families available in various QEMU builds, not a guaranteed Unraid dropdown list...VirtIO variants explainedvirtioDefault, broadly compatible VirtIO network device. Usually the best choice for Unraid VMs.Recommendedvirtio-transitionalSupports older VirtIO 0.9 and modern VirtIO 1.0 guest drivers. Uses conventional PCI placement. Useful when maintaining compatibility with older VM images.virtio-non-transitionalSupports modern VirtIO 1.0+ only. Better suited to modern PCIe topology, particularly Q35 VMs. Not necessarily faster in actual network throughput than standard virtio.Libvirt specifically recommends the standard virtio model when there are no special guest OS requirements. Depending on Hardware and config virtio is almost always virtio-net which uses the Linux hypervisor software network to grant the VM network access...Some Additional specialized and legacy modelsThese are documented by libvirt or available in particular QEMU configurations.Model or familyIntended platformvmxnet, vmxnet2Older VMware-compatible NICsvlanceOlder VMware/AMD-compatible networking82540EM, 82545EM, 82543GCSpecific Intel Gigabit controller modelsAm79C970A, Am79C973AMD PCnet hardware variantsnetfrontXen paravirtual networkingspapr-vlanIBM POWER/pSerieslan9118ARM embedded networkingscm91c111ARM embedded networkingusb-netUSB-based virtual networkingne2k_isaLegacy ISA NE2000 network adapteri82551, i82557b, i82559erOlder Intel Fast Ethernet adaptersThe exact accepted libvirt model name can differ from the corresponding QEMU device name.Performance and compatibility comparisonThese are qualitative expectations, not benchmark results.ModelHost CPU efficiencyPotential throughputCompatibilityvirtioExcellentVery highHigh with driversvirtio-non-transitionalExcellentVery highModern guestse1000LowerGoodVery highe1000eLowerGoodHighigbLowerGoodHighvmxnet3Very goodVery highDriver-dependentrtl8139LowLowVery high for legacy guestspcnetLowLowLegacyne2k_pciLowLowLegacyThe emulated adapter's advertised link speed is not necessarily the VM's actual throughput ceiling. For example, an e1000 VM may exceed 1 Gbps in a virtualized environment, depending on the rest of the configuration...data from https://libvirt.org/formatdomain.html
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.