Description of problem: "migrate_set_downtime" is deprecated since qemu-2.8 and should be replaced by 'migrate-set-parameters". Libvirt still uses it in qemuDomainMigrateSetMaxDowntime without alternative. When fixing this, please also adjust the test case to mark the command as okay to be removed.
Patches sent upstream for review: https://www.redhat.com/archives/libvir-list/2020-June/msg00444.html
Fixed upstream by commit 65de5f6fe4c2ba4f7baabb43a66d64877a9c95fd Refs: v6.4.0-124-g65de5f6fe4 Author: Jiri Denemark <jdenemar> AuthorDate: Wed Jun 10 16:13:15 2020 +0200 Commit: Jiri Denemark <jdenemar> CommitDate: Wed Jun 17 10:25:33 2020 +0200 qemu: Avoid deprecated migrate_set_downtime QMP command The same functionality can be achieved using migrate-set-parameters QMP command with downtime-limit parameter. https://bugzilla.redhat.com/show_bug.cgi?id=1829543 Signed-off-by: Jiri Denemark <jdenemar> Reviewed-by: Peter Krempa <pkrempa>
Verify with: libvirt-client-6.5.0-1.module+el8.3.0+7323+d54bb644.x86_64 qemu-kvm-5.0.0-2.module+el8.3.0+7379+0505d6ca.x86_64 Result: migrate-set-parameters is used when set maxdowntime Steps: # virsh migrate-setmaxdowntime rhel7-min 200 2020-07-31 09:34:21.770+0000: 70043: info : qemuMonitorSend:946 : QEMU_MONITOR_SEND_MSG: mon=0x7f95b8047020 msg={"execute":"migrate-set-parameters","arguments":{"downtime-limit":200},"id":"libvirt-382"}
Still need to verify with qemu-kvm that doesn't support set maxdowntime via migrate-set-parameters
(In reply to Fangge Jin from comment #6) > Still need to verify with qemu-kvm that doesn't support set maxdowntime via > migrate-set-parameters To test this scenario, I will have to test upgrade from RHEL7.3 to RHELAV-8.3, which is not supported. So this bug can be marked as verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (virt:8.3 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:5137