Towards a Cross-Hypervisor Test Framework for VirtIO Backend Validation Using VirtIO...
Talkat Open Source Summit Japan + AI_dev: Open Source GenAI & ML Summit + Automotive Linux Summit 2025 · 2025-12-08..12-10·
summary
A VirtIO conformance suite integrates VirtIO CTS into a cross‑hypervisor framework, implemented in Rust and developed with Linaro for open‑source release, with two test types: unicorn minimal kernel unit checks and rootfs Linux AArch64 with Mesa user‑space tests (GPU, glmark). It currently validates six backend devices (block, net, GPU, console, sound, bus), runs on QEMU (x86_64 host using TCG for AArch64), emits TAP output, and measures per‑command virtqueue latency during benchmarks to report functional compliance and performance visibility.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:05Need for SDVs and virtualization
- 3:54Hardware and device virtualization
- 8:34VirtIO as device abstraction
- 10:24What is VirtIO in automotive
- 15:28VirtIO in AGL and SDV
- 18:03Implementation challenges
- 19:10VirtIO Conformance Test Suite
- 21:22Unicorn-based compliance tests
- 23:55Root FS image tests
- 24:41Live test demo
- 26:31Test results vs specification
- 27:16Test results and benchmarks
- 29:10Summary and future plans
- 30:37Q&A
- 31:18Testing VirtIO backend drivers
- 33:28Additional VirtIO devices in CTS
- 34:56Backend device testing focus
- 36:27Hypervisor latency with eBPF
- 38:17Future performance testing
- 39:46Extending CTS for silicon tests
related talks
37mHypervisor-less virtio for Real-time and Safety
35mValidating Freedom From Interference in Automotive Linux
30mHA-IOV: Applying Hardware-assisted Techniques to IO Virtualization Framework
45mTrust, confidentiality, and hardening: the virtio lessons
49mTransport-level Testing of NVMe Devices using VFIO
34mVirtio-msg: Making Virtio Work Where It Does Not Today
34mTailor-Made Security: Building a Kubernetes Specific Hypervisor
42mAMP Virtio: A New Virto Transport for AMP Systems, with Focus on Zephyr, Linux, and Xen