We don't know yet what libvirt will provide, but the following strings from the QEMU source code are important: - "Zero copy only available for non-compressed non-TLS multifd migration". - "Requires that QEMU be permitted to use locked memory for guest RAM pages." Translated to oVirt terms it means this feature can be used only with non-encrypted parallel-connections migrations and we may need to set memtune hard limit for all VMs, not just those with q35 and VFIO devices. It would be easiest to use this feature automatically whenever the given constraints are satisfied. The only reason, currently known to me, not to do it is that it is a new feature, which may have unanticipated issues. Alternatively, there could be an Engine config option to enable/disable support for this feature, or a parallel migration connections option.
Verified with: ovirt-engine-4.5.3-0.2.el8ev.noarch vdsm-4.50.3.1-1.el8ev.x86_64 libvirt-8.0.0-5.4.module+el8.6.0+16370+bb85faee.x86_64 Steps: Run the cases in the attached Polarion test plan. Results: All cases passed.
What's the status this one, do you have an eta when it will end up in ovirt?
It's in oVirt 4.5.3 (and the corresponding RHV version).
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days