Bug 948353 - default migration bandwidth capping is not honored anymore
Summary: default migration bandwidth capping is not honored anymore
Keywords:
Status: CLOSED DUPLICATE of bug 925981
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.1.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.1.4
Assignee: Saveliev Peter
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-04 16:03 UTC by Michal Skrivanek
Modified: 2014-01-01 08:46 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-04 16:14:56 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Michal Skrivanek 2013-04-04 16:03:28 UTC
up till libvirt 0.10.0, i.e. RHEL 6.3 there was a default maximum speed of migrating VM of 30Mbps.
vdsm relied on the default libvirt/qemu behavior.
This was changed in 6.4 nd so starting with RHEV-M 3.1.3 there is no limit enforced anymore. 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', '30',
+            'Maximum bandwidth for migration, in mbps, 0 means unlimited, former libvirt\'s '
+            'default is 30Mbps.'),

plus we need to fix upgrade as well, I guess

Comment 1 Michal Skrivanek 2013-04-04 16:14:56 UTC

*** This bug has been marked as a duplicate of bug 925981 ***


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