Bug 925981 – default migration bandwidth capping is not honored anymore

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 925981 - default migration bandwidth capping is not honored anymore

Summary:	default migration bandwidth capping is not honored anymore

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	vdsm (Show other bugs)
Sub Component:
Version:	3.1.3
Hardware:	Unspecified Unspecified

Priority	urgent Severity medium
Target Milestone:	---
Target Release:	3.2.0
Assigned To:	Saveliev Peter
QA Contact:	Pavel Stehlik
Docs Contact:

URL:
Whiteboard:	virt
Keywords:	ZStream

Duplicates:	948353 (view as bug list)
Depends On:	948821
Blocks:	950603
	Show dependency tree / graph

Reported:	2013-03-22 23:00 EDT by Nandini Chandra
Modified:	2013-06-10 16:46 EDT (History)
CC List:	17 users (show)

See Also:
Fixed In Version:	vdsm-4.10.2-16.0.el6ev
Doc Type:	Bug Fix
Doc Text:	Previously, libvirt changed the default behaviour from the limited migration bandwidth to unlimited one. This meant that without any migration bandwidth limitation, the network could be saturated during mass migrations. The default limit was set to "on". This solution is compatible with all versions, and preserves the original behaviour. This fix ensures that customers with large networks will notice no change in migration behavior.
Story Points:	---
Clone Of:
Clones:	950603 (view as bug list)
Environment:
Last Closed:	2013-06-10 16:46:30 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Knowledge Base (Solution)	344073	None	None	None	Never
oVirt gerrit	13781	None	None	None	Never
Red Hat Product Errata	RHSA-2013:0886	normal	SHIPPED_LIVE	Moderate: rhev 3.2 - vdsm security and bug fix update	2013-06-10 20:25:02 EDT

Groups: None (edit)

Description Nandini Chandra 2013-03-22 23:00:41 EDT

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:

Comment 1 Nandini Chandra 2013-03-22 23:02:58 EDT

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

Comment 2 Michal Skrivanek 2013-04-04 12:14:56 EDT

*** Bug 948353 has been marked as a duplicate of this bug. ***

Comment 3 Michal Skrivanek 2013-04-04 12:25:55 EDT

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

Comment 10 Saveliev Peter 2013-04-11 03:36:50 EDT

merged as ovirt:9974c596737c5f59ad6c2add02111efc12cb1d1c

preparing backports

Comment 21 errata-xmlrpc 2013-06-10 16:46:30 EDT

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

Note You need to log in before you can comment on or make changes to this bug.