Bug 1484818
| Summary: | Bandwidth is ignored for VLAN migration network | |||
|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Roman Hodain <rhodain> | |
| Component: | BLL.Network | Assignee: | Leon Goldberg <lgoldber> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.1.5 | CC: | aperotti, bugs, danken, edwardh, ipinto, mburman, rhodain, ylavi | |
| Target Milestone: | ovirt-4.2.1 | Flags: | rule-engine:
ovirt-4.2+
|
|
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1530063 (view as bug list) | Environment: | ||
| Last Closed: | 2018-02-12 11:49:35 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1530063 | |||
|
Description
Roman Hodain
2017-08-24 10:59:58 UTC
Bug 1464055 tracks the issue with bond interfaces. Has this been attempted with a migration network over a bond or over a nic? I check it with:
Software Version:4.2.0-0.0.master.20171119135709.git6d448d3.el7.centos
Steps:
1. Set migration network and migration VM with AUTO BW in policy Legacy.
2. Migration VM
During the migration:
1. Check on source host BW with: virsh -r domjobinfo 2
2. check on Engine the network migration status
Results:
Engine:
No report on migration-net speed
engine=# select name, network_name, is_bond, bond_name, bond_type,bond_opts, vlan_id, speed, addr, bridged, base_interface from vds_interface where vds_id='88d8e154-8307-4865-8e21-1e3e0a08b20c';
name | network_name | is_bond | bond_name | bond_type | bond_opts | vlan_id | speed | addr | bridged | base_interface
------------+---------------+---------+-----------+-----------+-----------+---------+-------+---------------+---------+----------------
enp4s0 | ovirtmgmt | f | | | | | 1000 | 10.35.128.15 | t |
enp6s0 | | f | | | | | 1000 | | f |
ens1f1 | | f | | | | | 1000 | | f |
ens1f0 | | f | | | | | 1000 | | f |
enp6s0.162 | migration-net | f | | | | 162 | | 10.35.129.146 | t | enp6s0
(5 rows)
On host:
BW is reported during migration:
Memory bandwidth: 111.401 MiB/s
[root@orchid-vds1 ~]# virsh -r domjobinfo 2
Job type: Unbounded
Operation: Outgoing migration
Time elapsed: 15547 ms
Data processed: 1.488 GiB
Data remaining: 113.613 MiB
Data total: 4.095 GiB
Memory processed: 1.488 GiB
Memory remaining: 113.613 MiB
Memory total: 4.095 GiB
Memory bandwidth: 111.401 MiB/s
Dirty rate: 0 pages/s
Iteration: 1
Constant pages: 656537
Normal pages: 387741
Normal data: 1.479 GiB
Expected downtime: 101 ms
Setup time: 67 ms
Also check with: uncheck the VM option on migration-net
Same results.
engine=# select name, network_name, is_bond, bond_name, bond_type,bond_opts, vlan_id, speed, addr, bridged, base_interface from vds_interface where vds_id='88d8e154-8307-4865-8e21-1e3e0a08b20c';
name | network_name | is_bond | bond_name | bond_type | bond_opts | vlan_id | speed | addr | bridged | base_interface
------------+---------------+---------+-----------+-----------+-----------+---------+-------+--------------+---------+----------------
ens1f0 | | f | | | | | 1000 | | f |
enp6s0.162 | migration-net | f | | | | 162 | | | f | enp6s0
enp4s0 | ovirtmgmt | f | | | | | 1000 | 10.35.128.15 | t |
enp6s0 | | f | | | | | 1000 | | f |
ens1f1 | | f | | | | | 1000 | | f |
(5 rows)
It looks like it not worked before.
(In reply to Edward Haas from comment #2) > Has this been attempted with a migration network over a bond or over a nic? It is over bond. The network is a VM network with a VLAN tag. VM-private (migration network) -> bond0.500 -> bond0 -> LACP (em3,em4) Verified on - 4.2.1.1-0.1.el7 Bandwidth is no longer ignored for vlan migration network. -[ RECORD 5 ]--+-------------- name | enp6s0.162 network_name | migration-net is_bond | f bond_name | bond_type | bond_opts | vlan_id | 162 speed | 1000 addr | 10.35.1x9.x bridged | t base_interface | enp6s0 -[ RECORD 1 ]--+------------------------------------- name | bond0.162 network_name | migration-net is_bond | bond_name | bond_type | bond_opts | vlan_id | 162 speed | 2000 addr | 10.35.1x9.1x9 bridged | t base_interface | bond0 -[ RECORD 2 ]--+------------------------------------- name | bond0 network_name | is_bond | t bond_name | bond_type | bond_opts | mode=4 miimon=100 xmit_hash_policy=2 vlan_id | speed | 2000 addr | bridged | f base_interface | -[ RECORD 3 ]--+------------------------------------- name | enp12s0f0 network_name | is_bond | f bond_name | bond0 bond_type | bond_opts | vlan_id | speed | 1000 addr | bridged | f base_interface | -[ RECORD 6 ]--+------------------------------------- name | enp12s0f1 network_name | is_bond | f bond_name | bond0 bond_type | bond_opts | vlan_id | speed | 1000 addr | bridged | f base_interface | maxBandwidth parameter is sent. Examples: AUTO in legacy - maxBandwidth='500' (1Gb link) [root@silver-vdsb ~]# virsh -r domjobinfo 4 Memory bandwidth: 112.766 MiB/s CUSTOM in legacy - maxBandwidth='25' (set custom with 50Mbps limit) [root@orchid-vds2 ~]# virsh -r domjobinfo 7 Memory bandwidth: 25.021 MiB/s This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |