Hide Forgot
Libvirt supports the ability to set the migration bandwidth through the API but not via virsh. So VMs will migrate at qemu's default (30mbs) There are a couple of ways we could approach this, one would be to add a new parameter to the migrate verb another would be to add a separate call. Since we already use migrate-setmaxdowntime to set the downtime maybe a consistent approach would be to add a migrate-setspeed call ?
(In reply to comment #0) > Libvirt supports the ability to set the migration bandwidth through the API but > not via virsh. So VMs will migrate at qemu's default (30mbs) > > There are a couple of ways we could approach this, one would be to add a new > parameter to the migrate verb another would be to add a separate call. > > Since we already use migrate-setmaxdowntime to set the downtime maybe a > consistent approach would be to add a migrate-setspeed call ? Another advantage of using a separate command is that we could use this command to adjust a migration that's already in progress.
patch pushed into upstream: commit b73f1f8d5c63ee28afc01c999e65dd93d092a720 Author: Osier Yang <jyang> Date: Wed Jun 8 10:40:57 2011 +0800 virsh: Expose virDomainMigrateSetMaxSpeed API to virsh API virDomainMigrateSetMaxSpeed was introduced since 0.9.0, but no command in virsh yet.
Verify pass on kernel-2.6.32-223.el6.x86_64 libvirt-0.9.9-1.el6.x86_64 qemu-kvm-0.12.1.2-2.213.el6.x86_64 # virsh migrate-setspeed kvm-rhel6u2-x86_64-new 1000 # virsh migrate-getspeed kvm-rhel6u2-x86_64-new 1000 # virsh migrate --live kvm-rhel6u2-x86_64-new qemu+ssh://10.66.83.197/system cat /var/log/libvirt/libvirtd.log 2012-01-10 11:47:08.178+0000: 29358: debug : virDomainMigrateSetMaxSpeed:16037 : dom=0x7f35180c3890, (VM: name=kvm-rhel6u2-x86_64-new, uuid=43ed7ac4-20e3-8c6c-8d9d-b9c672c0eb46), bandwidth=1000, flags=0 2012-01-10 11:47:28.392+0000: 29362: debug : qemuMonitorSetMigrationSpeed:1613 : mon=0x7f350c009110 bandwidth=1000
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No documentation needed.
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. http://rhn.redhat.com/errata/RHSA-2012-0748.html