Description of problem: 1. VDSM should depend on tuned package. 2. Upon host installation, install script should change host profile via tuned-adm to 'enterprise-storage' (until there's one, (RHEL 6.3?) for KVM). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
(In reply to comment #0) > Description of problem: > 1. VDSM should depend on tuned package. > 2. Upon host installation, install script should change host profile via > tuned-adm to 'enterprise-storage' (until there's one, (RHEL 6.3?) for KVM). Absolutely not. 'enterprise-storage' gives worse performance than what we are currently using. Perf team has an rfe to create a 'virt' profile and once that's done (hopefully rhel 6.3), we should use it. keeping open because the general idea of using tuned is correct. > > > Version-Release number of selected component (if applicable): > > > How reproducible: > > > Steps to Reproduce: > 1. > 2. > 3. > > Actual results: > > > Expected results: > > > Additional info:
(In reply to comment #1) > (In reply to comment #0) > > Description of problem: > > 1. VDSM should depend on tuned package. > > 2. Upon host installation, install script should change host profile via > > tuned-adm to 'enterprise-storage' (until there's one, (RHEL 6.3?) for KVM). > > Absolutely not. 'enterprise-storage' gives worse performance than what we are > currently using. > Perf team has an rfe to create a 'virt' profile and once that's done (hopefully > rhel 6.3), we should use it. > keeping open because the general idea of using tuned is correct. how is it being tracked? please block this to the RFE BZ for virt profile and ask cpelland to add it to the 6.3 rhev tracker bug.
Yaniv, why does this bz (host profile) depends on bug 740977 which is the guest one?
(In reply to comment #3) > Yaniv, why does this bz (host profile) depends on bug 740977 which is the > guest one? No idea, removed the dependency.
*** Bug 838440 has been marked as a duplicate of this bug. ***
Minor update: the hypervisor now has virt-host profile. So this is what bootstrap will apply.
bootstrap rewrite support tuned.
Ayal, what's our stance on changing this from a support point of view (read: should changing the tuned profile on the hosts in a RHEV environment be documented in the RHEV documentation)? For now on the basis that I have created a documentation clone to reflect the need to name check this and refer readers to the RHEL Performance Tuning Guide for more information about the profiles I am setting docs_scoped+.
(In reply to comment #10) > Ayal, what's our stance on changing this from a support point of view (read: > should changing the tuned profile on the hosts in a RHEV environment be > documented in the RHEV documentation)? Sure. > > For now on the basis that I have created a documentation clone to reflect > the need to name check this and refer readers to the RHEL Performance Tuning > Guide for more information about the profiles I am setting docs_scoped+.
Verified. tuned-adm list Available profiles: - enterprise-storage - virtual-host - server-powersave - spindown-disk - default - laptop-ac-powersave - throughput-performance - virtual-guest - desktop-powersave - laptop-battery-powersave - latency-performance Current active profile: virtual-host
This bug is currently attached to errata RHEA-2013:14491. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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-0888.html