Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

virtio vs virtio-net

Featured Replies

Could somebody please explain to me in basic terms what the difference is between virtio and virtio-net when using VM's

Thanks in advance.

  • 1 month later...
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's

Thanks in advance.

unraid usis qemu via libvirt usig domin xml format.
https://libvirt.org/formatdomain.html
see docs as well: https://docs.unraid.net/unraid-os/using-unraid-to/create-virtual-machines/vm-setup/


virtio vs. virtio-net

Feature

virtio

virtio-net

Meaning

General paravirtualized device framework

Network device built on VirtIO

Purpose

Supports network, disk, memory, and other devices

Specifically virtual networking

QEMU network device

Usually virtio-net-pci

virtio-net-pci

Performance

Depends on device type

High-performance virtual networking

Guest drivers

Depends on device

Linux virtio_net, Windows NetKVM

Recommended for VM networking

Yes, when referring to VirtIO networking

Yes

Bottom 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 Unraid

For 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 setting

Purpose

type='bridge'

Connects the VM to a host network bridge

source bridge='br0'

Uses Unraid's br0 bridge

model type='virtio'

Selects the VirtIO network adapter

driver name='vhost'

Uses kernel-accelerated networking

mac address

VM's virtual MAC address; preserve its existing value

The 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 models

These are the most relevant models for modern x86-64 Unraid VMs.

Model

Emulated hardware

Guest support

General recommendation

virtio

VirtIO paravirtual NIC

Linux, Windows with VirtIO drivers

Best overall

virtio-transitional

Legacy-compatible VirtIO

Older and newer VirtIO drivers

Compatibility

virtio-non-transitional

Modern VirtIO 1.0+

Modern Linux and Windows VirtIO

Modern VMs

e1000

Intel 82540EM-class Gigabit

Broad OS support

Compatibility

e1000e

Intel PCIe Gigabit

Modern OS support

Good fallback

igb

Intel 82576 Gigabit

Modern OS with igb driver

Specialized testing

rtl8139

Realtek RTL8139 100 Mbps

Very broad older OS support

Legacy systems

vmxnet3

VMware paravirtual NIC

VMware-compatible guest drivers

VMware migrations

pcnet

AMD PCnet PCI NIC

Older operating systems

Legacy systems

ne2k_pci

NE2000-compatible PCI NIC

Older operating systems

Very old guests

Not 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 explained

virtio

Default, broadly compatible VirtIO network device. Usually the best choice for Unraid VMs.

Recommended

virtio-transitional

Supports 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-transitional

Supports 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 models

These are documented by libvirt or available in particular QEMU configurations.

Model or family

Intended platform

vmxnet, vmxnet2

Older VMware-compatible NICs

vlance

Older VMware/AMD-compatible networking

82540EM, 82545EM, 82543GC

Specific Intel Gigabit controller models

Am79C970A, Am79C973

AMD PCnet hardware variants

netfront

Xen paravirtual networking

spapr-vlan

IBM POWER/pSeries

lan9118

ARM embedded networking

scm91c111

ARM embedded networking

usb-net

USB-based virtual networking

ne2k_isa

Legacy ISA NE2000 network adapter

i82551, i82557b, i82559er

Older Intel Fast Ethernet adapters

The exact accepted libvirt model name can differ from the corresponding QEMU device name.

Performance and compatibility comparison

These are qualitative expectations, not benchmark results.

Model

Host CPU efficiency

Potential throughput

Compatibility

virtio

Excellent

Very high

High with drivers

virtio-non-transitional

Excellent

Very high

Modern guests

e1000

Lower

Good

Very high

e1000e

Lower

Good

High

igb

Lower

Good

High

vmxnet3

Very good

Very high

Driver-dependent

rtl8139

Low

Low

Very high for legacy guests

pcnet

Low

Low

Legacy

ne2k_pci

Low

Low

Legacy

The 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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.