Ability to configure ethtool options from within RHEV-M.
RHEV-M by default only configures a small subset of the configurable values of a network interface.
However, some users would like to use the ethtool utility to customize their usage of network interface, e.g. to prevent a faulty interface driver from performing hardware offloading.
Any ethtool options can now be supplied when provisioning a network on a host via a "custom properties" mechanism, similar to others in RHEV-M, using the key "ethtool_opts" of a network that is to reside on the physical interface.
Note that the engine-config has to be used initially for the "ethtool_opts" key to be made available. If no validation of the supplied ethtool arguments is required, the following command will achieve this:
engine-config -s 'UserDefinedNetworkCustomProperties=ethtool_opts=.*' --cver='3.5'
Moreover, the hook corresponding to this pre-defined custom property - vdsm-hook-ethtool-options - should be installed on the relevant hosts (via yum).
These properties are accessible both via the Setup Host Networks dialog in the webadmin console (when configuring a specific network), and via the Setup Networks action in the RESTful API (and derived SDKs).
Install/ Admin Guide shared topic:
Technical Guide may require new topic.
Additional Info: http://www.ovirt.org/Features/Network_Custom_Properties#Ethtool_options
SME Contact: Lior (email@example.com)
Created attachment 936727 [details]
Changing status back to 'New' until re-assignment.
Closing this as a duplicate of the newly opened bug as BZ#1250877 has two support cases attached.
*** This bug has been marked as a duplicate of bug 1250877 ***