KubeVirt: connect KVM-in-a-Pod to a host interface
summary
KubeVirt replaces a costly L2 chain (host NIC → bridge → veth → in‑pod bridge → tap) with a direct host macvtap device, requiring changes in qemu, libvirt and KubeVirt and a new macvtap device plugin plus a Multus + macvtap CNI to move the char device and interface into the pod without extra privileges. Demo allocates two macvtaps on a node from a 50 device capacity pool, VMs get DHCP IPs, ping each other and the Internet, and the known limitation is that guests cannot reach host.
AI-written summary · about
chapters (3)
related talks
43mKubeVirt - Kubernetes, Virtualization and Your Future Data Center
33mPlug & Play: Modular Networking for Kubernetes Virtualization
37mHigh Performance Networking with Kubevirt
25mKubeVirt: Converge IT infrastructure into one single Kubernetes platform
31mKubeVirt: What If Kubernetes Orchestrated Your VMs?
38mKubeVirt Intro: Virtual Machine Management on Kubernetes
32mKubeVirt - making running virtual machines in a k8s cluster
27mKubeVirt vDPA Workflow: From Host to Pod to Domain