RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 673811 - [RFE] VIRSH : Add ability to specify max migration bandwidth
Summary: [RFE] VIRSH : Add ability to specify max migration bandwidth
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Osier Yang
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-30 17:29 UTC by Andrew Cathrow
Modified: 2014-09-07 22:53 UTC (History)
12 users (show)

Fixed In Version: libvirt-0.9.9-1.el6
Doc Type: Enhancement
Doc Text:
No documentation needed.
Clone Of:
Environment:
Last Closed: 2012-06-20 06:26:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:0748 0 normal SHIPPED_LIVE Low: libvirt security, bug fix, and enhancement update 2012-06-19 19:31:38 UTC

Description Andrew Cathrow 2011-01-30 17:29:13 UTC 
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 ?
Comment 1 Andrew Cathrow 2011-01-30 17:33:10 UTC 
(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.
Comment 3 Osier Yang 2011-06-08 02:45:29 UTC 
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.
Comment 6 weizhang 2012-01-10 11:52:01 UTC 
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
Comment 7 Osier Yang 2012-05-04 09:47:09 UTC 
    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.
Comment 9 errata-xmlrpc 2012-06-20 06:26:09 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.