On 11/3/26 10:50, Nikolaos Karaolidis wrote: > virtio-mem adds memory without MHP_MEMMAP_ON_MEMORY. With the memory > onlined to ZONE_MOVABLE, a VM that grows to many times its boot size > can run short of unmovable memory. I ran into this while working on > a guest-initiated memory negotiation project.
Care to pitch the use case to me? I'm all for making virtio-mem better suitable for some workloads, but my time is limited. Is this something that your use case would actually benefit from, or was that project already discarded? Why so much MOVABLE memory, and how do other kernel allocations (page tables etc) cope with that? -- Cheers, David
