Hide Forgot
RHEV-M should take advantage of this through libvirt +++ This bug was initially created as a clone of Bug #863264 +++ This new feature will help live migration converge when the guest is dirtying pages too fast for the network throughput. The performance team is using a script like this: # cat migrated_cgroup.sh # Enter guest name $1 # # Try for 120 seconds with 10 percent of 1-cpu echo 10000 > /cgroup/cpu/libvirt/qemu/$1/vcpu0/cpu.cfs_quota_us echo 10000 > /cgroup/cpu/libvirt/qemu/$1/vcpu1/cpu.cfs_quota_us sleep 120 # Try for 2 minutes with 1% of the cpu of 1-cpu echo 1000 > /cgroup/cpu/libvirt/qemu/$1/vcpu0/cpu.cfs_quota_us echo 1000 > /cgroup/cpu/libvirt/qemu/$1/vcpu1/cpu.cfs_quota_us sleep 120 # Increase the period to then reduce to .1% of 1-cpu. echo 1000000 > /cgroup/cpu/libvirt/qemu/$1/vcpu0/cpu.cfs_period_us echo 1000000 > /cgroup/cpu/libvirt/qemu/$1/vcpu1/cpu.cfs_period_us echo 1000 > /cgroup/cpu/libvirt/qemu/$1/vcpu0/cpu.cfs_quota_us echo 1000 > /cgroup/cpu/libvirt/qemu/$1/vcpu1/cpu.cfs_quota_us This logic should be refined and put into libvirt so it's automatic for the customer. --- Additional comment from eblake on 2012-10-04 19:28:03 EDT --- Additionally, libvirt should be using the qemu 1.2 feature of XBZRLE migration, if it can determine that both sides of the migration support it (which also means that XBZRLE needs to be backported into RHEL qemu). --- Additional comment from jdenemar on 2012-10-08 08:15:58 EDT --- XBZRLE support is requested by bug 842857
*** Bug 863264 has been marked as a duplicate of this bug. ***
*** Bug 1098291 has been marked as a duplicate of this bug. ***
+1 I reproduced the bug too, even if dirty the pages rate is every 30 sec which is not too fast, and if the pages dynamically freed.
Verify with version : RHEVM: 3.6 build: rhevm-3.6.0-0.18.master.el6.noarch VDSM:vdsm-4.17.8-1.el7ev libvirt: libvirt-1.2.17-5.el7 1. Performance test pass see comment 11 2. Functionality test check with last build (rhevm-3.6.0-0.18)
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, 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://rhn.redhat.com/errata/RHEA-2016-0376.html