Tracing VMs Seeing How Host and Guest Interact
summary
Shows how to record and correlate host and guest kernel traces using trace-cmd and KernelShark, enabling synchronized host/guest timelines via a trace-cmd agent over vsockets. Focuses on concrete artifacts: enabling 100+ KVM events, capturing sysbench MySQL runs pinned to CPU1, detecting thousands of EPT violations (one function hit ~2113 times) and microsecond/nanosecond exit timings, a small analyzer kvm-exit.c and libtracecmd for merged parsing, and zero-copy guest→host transfer via splice; several features work now, some are still laptop-only.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:04KVM Trace Events
- 3:02Tools to determine Virtual Machine Overhead
- 8:05Using libtracecmd
- 11:03Running on the trace.dat file created by our record
- 13:43Using trace-cmd agent
- 19:09Seeing Guest exit functions
related talks
20mHost & Guest Tracing in Virtualization: "To sync, or not to sync?"
41mSynthetic Events and Tracing Latency Within the Kernel
31mFantastic tracepoints and where to find them
55mAdvanced Tracing Features to See What Your Application is Waiting On
30mMix Kubernetes with Linux Kernel Tracing to Boost the Observability of Your Cluster
43mEfficient Performance Profiling for Virtual Machines- 30mMix Kubernetes with Linux Kernel Tracing to Boost the Observability of Your Cluster
37mKernel and userspace tracing with LTTng and friends