Bug 1398736 - Can't use 10G nic capabilities in QoS
Summary: Can't use 10G nic capabilities in QoS
Keywords:
Status: CLOSED EOL
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Documentation
Version: 4.0.5.5
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1417900
TreeView+ depends on / blocked
 
Reported: 2016-11-25 17:53 UTC by exploit
Modified: 2022-03-16 08:47 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1417900 (view as bug list)
Environment:
Last Closed: 2017-02-07 09:03:40 UTC
oVirt Team: SLA
Embargoed:
sbonazzo: ovirt-4.1-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-45306 0 None None None 2022-03-16 08:47:30 UTC

Description exploit 2016-11-25 17:53:54 UTC
Description of problem:
I want to create a new VM/Host network QoS related to a 10G nic, but there is an issue that says : "the field must contain an integer nulber between 0 and 1024" when filling with a superior value to a 1G nic.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. go to Datacenter -> QoS substab -> VM/Host network
2. average, peak or burst are limited to 1024Mbps
3.

Actual results:


Expected results:
should be superior to 1024Mbps when using a 10G nic.

Additional info:

Comment 1 Phillip Bailey 2016-12-20 14:42:53 UTC
The maximum values for those fields are controlled by the config keys below and can be modified by running ./bin/engine-setup -s <config key>=<config value> from the ovirt-engine home directory.

The config value should be an integer and will be used as the inclusive upper boundary for the specified field. Note that if you modify the values while the engine is running, you will need to restart it in order for the changes to take effect.

UI Element Label => Config Key

VM QoS Popup:
Average => MaxAverageNetworkQoSValue
Peak    => MaxPeakNetworkQoSValue
Burst   => MaxBurstNetworkQoSValue

Host QoS Popup:
Rate Limit     => OutAverageUpperlimit
Committed Rate => OutAverageRealtime

Comment 2 exploit 2016-12-28 16:39:01 UTC
(In reply to Phillip Bailey from comment #1)
> The maximum values for those fields are controlled by the config keys below
> and can be modified by running ./bin/engine-setup -s <config key>=<config
> value> from the ovirt-engine home directory.
> 
> The config value should be an integer and will be used as the inclusive
> upper boundary for the specified field. Note that if you modify the values
> while the engine is running, you will need to restart it in order for the
> changes to take effect.
> 
> UI Element Label => Config Key
> 
> VM QoS Popup:
> Average => MaxAverageNetworkQoSValue
> Peak    => MaxPeakNetworkQoSValue
> Burst   => MaxBurstNetworkQoSValue
> 
> Host QoS Popup:
> Rate Limit     => OutAverageUpperlimit
> Committed Rate => OutAverageRealtime

engine-config -s OutAverageUpperlimit=10000
Error setting OutAverageUpperlimit's value. No such entry

Seems that OutAverageUpperlimit or OutAverageRealtime parameter don't still exist, so it is still not possible to modify Host QoS limit.

Comment 3 Yaniv Lavi 2017-01-10 12:26:04 UTC
Moving back to SLA to allow doing this in engine config.

Comment 4 Phillip Bailey 2017-01-10 20:01:06 UTC
(In reply to exploit from comment #2)

> > Host QoS Popup:
> > Rate Limit     => OutAverageUpperlimit
> > Committed Rate => OutAverageRealtime
> 
> engine-config -s OutAverageUpperlimit=10000
> Error setting OutAverageUpperlimit's value. No such entry
> 
> Seems that OutAverageUpperlimit or OutAverageRealtime parameter don't still
> exist, so it is still not possible to modify Host QoS limit.

I apologize. I made a mistake in comment 1. The maximum value for both of the Host QoS fields are controlled by the same config key that controls the VM Average Network QoS field: MaxAverageNetworkQoSValue.

Please try this and let me know if it is successful or not.

Comment 5 exploit 2017-01-12 17:53:13 UTC
(In reply to Phillip Bailey from comment #4)
> (In reply to exploit from comment #2)
> 
> > > Host QoS Popup:
> > > Rate Limit     => OutAverageUpperlimit
> > > Committed Rate => OutAverageRealtime
> > 
> > engine-config -s OutAverageUpperlimit=10000
> > Error setting OutAverageUpperlimit's value. No such entry
> > 
> > Seems that OutAverageUpperlimit or OutAverageRealtime parameter don't still
> > exist, so it is still not possible to modify Host QoS limit.
> 
> I apologize. I made a mistake in comment 1. The maximum value for both of
> the Host QoS fields are controlled by the same config key that controls the
> VM Average Network QoS field: MaxAverageNetworkQoSValue.
> 
> Please try this and let me know if it is successful or not.

Thank you it works fine

Comment 11 Yaniv Lavi 2017-02-07 09:03:40 UTC
Can you please open a github issue to fix and add info on this in the oVirt site?

Comment 12 exploit 2017-10-16 12:33:23 UTC
(In reply to Yaniv Lavi (Dary) from comment #11)
> Can you please open a github issue to fix and add info on this in the oVirt
> site?

please, close this ticket, I am not able to answer to it, I've been receiving the same request mail for months and months.


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