0 views collected around this technical thread.
This article explains how vhost/virtio solves virtual device communication bottlenecks, walks through a hand‑written implementation with shared memory and ring buffers, and details QEMU's backend driver creation, device realization, and the vhost‑user/vhost‑net interfaces that enable high‑performance virtual networking.
Virtio, the Linux standard I/O virtualization framework, uses a semi‑virtualized front‑end driver and back‑end device linked by virtqueues, works across hypervisors (e.g., QEMU/KVM) via PCI or MMIO, enabling high‑performance, low‑overhead device emulation—as illustrated by the virtio‑snd driver—while supporting cloud and Android virtualization scenarios.
This article explains the architecture and implementation of the virtio/vhost device model, details how QEMU creates and initializes virtio‑net‑pci devices, describes the vhost‑user communication protocol and its integration with DPDK and the Linux vhost‑net kernel driver, and provides practical command‑line examples and code snippets.
This article explains how virtual networks operate in cloud computing by covering virtual NIC implementation, Virtio frontend/backend mechanisms, KVM signal interaction, and both layer‑2 and layer‑3 forwarding within a node using OVS and related technologies.
This article explains the principles and performance characteristics of virtio networking, OVS virtual switching, and the related vhost‑net, vhost‑user, and vdpa mechanisms, comparing their architectures, data‑plane offloads, and suitability for cloud‑native environments.
This article explains the concept, architecture, and API of Virtio—a semi‑virtualization abstraction layer in Linux hypervisors—covering its role in device modeling, differences between full and para‑virtualization, driver hierarchy, buffer management, and practical usage in kernel development.