The future of the desktop is on hypervisor powered containers
summary
A working Xen-based Qubes OS desktop isolates apps into ZEN VMs with per-VM X servers stitched in dom0 via a GUI daemon, Vchan RPC and shared-memory X plumbing, LVM snapshot root templates plus overlay/persist volumes, split global clipboard and vault-assisted SSH where keys never leave the vault. Performance requires 8–16+ GB RAM and SR‑IOV can expose GPUs for gaming (they run Steam and Factorio today; goal: Crysis). Containers like Docker/LXC lack IOMMU access and share one kernel, so they cannot provide equivalent hardware isolation.
AI-written summary · about
chapters (19)
- 0:00orion VM
- 2:26So what is Qubes?
- 2:54GUI Isolation
- 3:12Qubes GUI System DOMO
- 4:46Firefox and a password manager
- 5:32Vchan/Qubes RPC
- 5:53Split clipboards
- 6:52Vault isolation
- 7:56Network - Qubes
- 9:58Network - Containers
- 10:59Qube storage
- 12:05Container storage
- 12:49Disposable Qube
- 13:39Qubes Memory
- 14:20Containers Memory
- 16:26Qubes made of containers?
- 17:30Recommended Hardware
- 19:23Our Wish list: Container integration
- 23:16Help wanted
related talks
32mQubes OS: Security Through Isolation
22mQubes OS
45mLife Behind the Tinfoil: A Look at Qubes and Copperhead
41mSecuring Your Xen-Based Cloud
27mVMs in a container-centric world
53mXen: Open Source Hypervisor Designed for Clouds
38mSecure Containers in Embedded Deployments
24mVirtual workstation as a daily computer