Ruben Hakobyan b5ddcdc74a hypervisor: handle VcpuExit::MemoryFault for AP boot page conversions ...

During SNP boot all guest RAM is initially marked
KVM_MEMORY_ATTRIBUTE_PRIVATE. Pages imported via SNP_LAUNCH_UPDATE are
properly accepted by the guest, but generic RAM pages (e.g. the AP
trampoline at GPA 0xD000) are not. When stage0 on the BSP starts
secondary vCPUs via x2APIC, the APs try to execute from the trampoline
page through the shared mapping while KVM still has it marked private,
causing a KVM_EXIT_MEMORY_FAULT (flags=KVM_MEMORY_EXIT_FLAG_PRIVATE)
that previously fell through to the catch-all error, killing the VM.

Handle VcpuExit::MemoryFault by toggling the page's memory attribute
between private and shared based on the exit flags, allowing the vCPU
to retry the access.

Signed-off-by: Ruben Hakobyan <hruben@meta.com>

2026-04-17 12:28:55 +00:00

..

src

hypervisor: handle VcpuExit::MemoryFault for AP boot page conversions

2026-04-17 12:28:55 +00:00

Cargo.toml

build(deps): bump the non-rust-vmm group across 2 directories with 10 updates

2026-04-10 18:12:11 +00:00