Free yourself from the tyranny of your cloud provider!
summary
Explains how to boot a self-contained, signed kernel inside a PV domU using kexec with no changes to dom0 or Xen, so instances can run newer kernels and fall back to a safe kernel on failure; details the kernel patches and modified kexec tools required, uses kexec crash-to-new-kernel for full memory dumps, and reports fast two-kernel boot cycles in KVM/QEMU. Notes cloud-provider PV-domU kexec is partially implemented today and not yet a drop-in solution for all Xen hosts.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:09Free your kernel from the tyranny of your cloud provider!
- 1:35Problem: Cloud provider controls your kernel
- 2:49pvgrub config files custom images
- 3:34Run Linux from Linux
- 4:15kdump tiny kernel to save crash data
- 6:59Linux is the bootloader
related talks
21m(Ab)using Linux as a Trusted Bootloader
43mpkernfs: Persisting guest memory and kernel/device state safely...
50mMultikernel Architecture: Kernel-to-Kernel Isolation and Resource Management
26mMulti-KVM Abstract
31mKVM Nested Virtualization: Workings and Usecases
26mStateless Linux Kernel Crashdumps
37mHardware Error Handling Improvement for Reliable KVM Hypervisor
50mPanel Discussion: KVM-based Virtualization Contributor Q&A