On Mon, Aug 10 2026, Sean Christopherson wrote:
> On Tue, Jul 28, 2026, Tarun Sahu wrote:
>> Register a Live Update Orchestrator (LUO) file handler for KVM VM files
>> to serialize and deserialize VM state across kexec live updates.
>>
>> Currently, Only VM type (e.g. arch.vm_type on x86) is preserved as part
>> of VM preservation.
>
> Why?
>
>> On retrieval, kvm_luo_retrieve() recreates the KVM VM file via
>> kvm_create_vm_file() and use an atomically incremented ID for the internal
>> fdname, as the final fdname assigned by userspace is not yet known during
>> retrieval. As this fdname is only used in debugfs infra, This will not break
>> any UAPI.
>>
>> This infrastructure establishes the foundation for preserving guest_memfd
>> instances across live updates, and can be expanded in the future to
>> preserve additional VM state.
>
> Uh, why guest_memfd? As much as I want to push guest_memfd adoption, it seems
> guest_memfd should be the _last_ thing we support, not the first. As
> evidenced
> by the last two decades, it's very doable to have KVM VMs without guest_memfd,
> but it's rather hard to have VMs without vCPUs.
You _can_ preserve vCPUs today using KVM_{GET,SET}_REGS, they just won't
run in the background during the reboot. This series can save you from
dumping VM memory to disk if it is backed by guest_memfd.
>
>> Also updates MAINTAINERS to include virt/kvm/kvm_luo.c and
>> include/linux/kho/abi/kvm.h.
>>
>> Signed-off-by: Tarun Sahu <[email protected]>
>> ---
>> MAINTAINERS | 11 ++
>> include/linux/kho/abi/kvm.h | 39 ++++++++
>> virt/kvm/Makefile.kvm | 1 +
>> virt/kvm/kvm_luo.c | 195 ++++++++++++++++++++++++++++++++++++
>> virt/kvm/kvm_main.c | 8 ++
>> virt/kvm/kvm_mm.h | 8 ++
>> 6 files changed, 262 insertions(+)
>> create mode 100644 include/linux/kho/abi/kvm.h
>> create mode 100644 virt/kvm/kvm_luo.c
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index a3ed337e827d..0283f0fd6ef4 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -14539,6 +14539,17 @@ S: Maintained
>> F: Documentation/devicetree/bindings/leds/backlight/kinetic,ktz8866.yaml
>> F: drivers/video/backlight/ktz8866.c
>>
>> +KVM LIVE UPDATE
>> +M: Pasha Tatashin <[email protected]>
>> +M: Mike Rapoport <[email protected]>
>> +M: Pratyush Yadav <[email protected]>
>> +R: Tarun Sahu <[email protected]>
>> +L: [email protected]
>> +L: [email protected]
>> +S: Maintained
>> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux.git
>
> NAK on taking changes through a different tree. This is KVM code, period.
>
> In general, I'm skeptical of the dedicated MAINTAINERS entry. It's extremely
> difficult to tell since this series is little more than a skeleton (either
> that
> or liveupdate is way simpler that I was expecting), but I suspect that
> maintaining
It's a bit of both. This series of course doesn't support everything
that guest_memfd can. At the same time, I also keep being (pleasantly)
surprised at preservation being relatively simple. For example, the code
to preserve a shmem file (via memfd) is roughly 600 lines, a big chunk
of which is comments. The code of course has some limitations, but it is
good enough for use in production.
> liveupdate for KVM (or for any subsystem) will require more subsystem-specific
> knowledge than liveupdate knowledge.
>
> E.g. the LUO APIs seem pretty straightforward; I assume the bulk of the
> complexity
> is going to be in knowing what to save/restore, and how, which is much more
> about
> KVM than it is about liveupdate.
I think it is fine if you want to take these changes through the KVM
tree, but I would like live update maintainers to be listed as reviewers
at least.
For one, we care about ABI breakages and versioning. The serialized
state is a part of live update ABI and changes to it should be ACKed by
us. For another, how the file handlers interact with their dependencies
can affect the behaviour that VMMs observe. Those changes should also
pass by some live update eyes.
So I think we should have a separate entry for KVM LIVE UPDATE that
lists the live update maintainers (or perhaps only kexec@) as a
reviewer. The patches can still flow through KVM tree but we'd get a
chance to ACK/NACK them.
Of course this all can evolve later as we see fit but I think this is a
good starting point.
>
>> +F: virt/kvm/kvm_luo.c
>> +
>> KVM PARAVIRT (KVM/paravirt)
>> M: Paolo Bonzini <[email protected]>
>> R: Vitaly Kuznetsov <[email protected]>
[...]
--
Regards,
Pratyush Yadav
