Panel Discussion: KVM-based Virtualization Contributor Q&A
summary
KVM work shows concrete wins and clear limits: pkvm in Android 13 is shipping and runs parts of the Android runtime compiler, using stage-two translation so the host cannot access guest memory, but migrating TrustZone workloads into VMs remains slow because silicon ties and firmware block easy porting. Rust appears in user-space VMMs and a guest bootloader, cutting entry overhead by entering guests with MMU enabled. Review bottlenecks and reviewer scarcity, attestation fragmentation, and VFIO plumbing on mobile remain practical blockers.
AI-written summary · about
chapters (9)
- 0:00Welcome
- 1:25KVM for security
- 5:58KVM extensions challenges
- 11:52Confidential virtualization
- 18:55Arm virtualization update
- 23:14KVM on Arm 64
- 26:46Rust in KVM
- 32:27Type 1 vs Type 2 hypervisors relevance
- 36:21Closing
related talks
50mPanel Discussion: KVM-based Virtualization Contributor Q&A
27mDay 2 Keynote Sessions
23mHyper-V's Virtual Secure Mode in KVM project update
25mThe Qemu/KVM ecosystem: Navigating the code!
15mKeynote: KVM
31mKVM Nested Virtualization: Workings and Usecases
16mUnifying KVM API for protected VM and utilities
21mSupporting guest private memory in Protected KVM on Android