+++ This bug was initially created as a clone of Bug #1289285 +++ Description of problem: With extreme memory write intensive workloads, normal live migration will never complete because the guest is writing to memory faster than Qemu can transfer the memory changes to the destination system. In this case normal migration will continue forever, not making enough progress to stop the guest and proceed to the non-live "finishing up" phase of migration. This feature provides a method for slowing down guest execution speed, thus hopefully, also slowing down guest memory write speed. As time advances autoconverge will continually increase the amount of guest cpu throttling until guest memory write speed slows enough to allow the guest to be stopped and migration to finish. As of Qemu 2.5 dynamic throttling has been added to autoconverge dramatically increasing its effectiveness. This feature will be available in RHEL7.3 qemu-kvm-rhev with the rebase to qemu 2.5. The qemu feature page can be found in: http://wiki.qemu.org/Features/AutoconvergeLiveMigration Version-Release number of selected component (if applicable): qem-kvm-rhev How reproducible: Always. Steps to Reproduce: Please refer to the qemu feature page above. Actual results: Live migration fails due to high page dirty rate (i.e. intensive memory writes). Expected results: Live migration successfully complete. Additional info:
tentatively setting 4.0 based on tentative 7.3 on RHEL side should be an enhancement/replacement to the 3.6 autoconvergence
the base autoconvergence mechanism is in place and the new algorithm will be used in 7.3. we don't plan to configure increments at the moment - awaiting feedback on recent migration improvement bug 1252426
Verify with: Engine: 4.1.0.3-0.1.el7 Host: OS Version:RHEL - 7.3 - 7.el7 Kernel Version:3.10.0 - 550.el7.x86_64 KVM Version:2.6.0 - 28.el7_3.3.1 LIBVIRT Version:libvirt-2.0.0-10.el7_3.4 VDSM Version:vdsm-4.19.4-1.el7ev SPICE Version:0.12.4 - 20.el7_3 Run migration sanity and load cases All Pass