Description of problem: The /usr/share/doc/<vdsm-version>/vdsm.conf.sample file has the following information. # Maximum bandwidth for migration, in mbps, 0 means libvirt's default # (30mbps?). # migration_max_bandwidth = 0 In RHEL 6.4 with libvirt-0.10.2-18,the maximum available bandwidth is used by default for migration of KVM guests.So,this needs to be changed to reflect the change made in libvirt. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=6cfdeaac552e1ef744f269ed4cef3d74e663d677 With this commit,the default maximum migration bandwidth of 32 Mb/s in the older versions of libvirt has been removed and in RHEL 6.4/libvirt-0.10.2-18.el6.x86_64.rpm,the maximum available bandwidth is used by default for migration of KVM guests. -Nandini
*** Bug 948353 has been marked as a duplicate of this bug. ***
This can cause overload of network interfaces as the whole bandwidth is used in case of mass migration (either manual or induced by moving a host to maintenance mode) The fix would be to use the former 30Mbps value as the default in vdsm config. something like: - ('migration_max_bandwidth', '0', - 'Maximum bandwidth for migration, in mbps, 0 means libvirt\'s ' - 'default (30mbps?).'), + ('migration_max_bandwidth', '32', + 'Maximum bandwidth for migration, in Mbps, 0 means unlimited, former libvirt\'s ' + 'default is 32Mbps.'), plus we need to fix upgrade as well, I guess
merged as ovirt:9974c596737c5f59ad6c2add02111efc12cb1d1c preparing backports
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-2013-0886.html