On Fri, Nov 06, 2026 at 09:06:52 -0500, Peter Xu wrote:
If with the comment addressed first from Jiri (making sure it only applies to QEMU that supports zero-page-detection=multifd), it looks working, but then it'll be an API likely nobody will use after a short while: all people will be using multifd detections by default.
Another option might be that Libvirt detects such support on both sides and enable it if both support it, silently with no API at all. I don't see a drawback indeed; multifd should always be better.
QEMU can't do such for old machine types because QEMU doesn't have a way to know if the other side can understand the new protocol, but Libvirt knows. Then at least we can get rid of this API to maint.
Oh so this is the reason behind the legacy default for older machine types. In this case you are right, the best option for libvirt would be to check that both sides support this parameter and if so, unconditionally switch it to multifd. Jirka