Description of problem: The IO performance of VMs when running on a host with the IO scheduler set as deadline is better than when running with the default scheduler (CFQ). The os-installer should change the IO scheduler. Just add elevator=deadline to the kernel args. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Perf team used to have a tool called tuna that made it possible to apply profiles to hosts, and one of the profiles was for a 'kvm host' @mwagner, can you assist with info here?
(In reply to comment #2) > Perf team used to have a tool called tuna that made it possible to apply > profiles to hosts, and one of the profiles was for a 'kvm host' > > @mwagner, can you assist with info here? I thought Packstack was going to use otopi/ovirt-host-deploy. It's available there: http://gerrit.ovirt.org/gitweb?p=ovirt-host-deploy.git;a=blob;f=src/plugins/ovirt-host-deploy/tune/iosched.py;hb=HEAD
Hi, tuned is a user space package that controls the profiles. There are profiles for virtual-host and virtual-guest amongst others. It should be possible to install and configure the use of the virtual-host profile. Note that tuna is a different tool.
I have to translate this into a equivalent puppet manifest but would something like this be appropriate ? if ! tuned-adm active | grep virtual-host 2> /dev/null ; then tuned-adm profile virtual-host fi This probably changes more then just the IO scheduler but its all good stuff right? Also does this changed persist on reboot? thanks, Derek.
Fix submitted upstream https://review.openstack.org/#/c/22540/
Verified NVR: openstack-packstack-2012.2.3-0.1.dev454.el6ost.noarch 1. Verified that 'tuned-adm active | grep virtual-host' returned no output. 2. Used packstack to install openstack. 3. Verified Active Profile again: # tuned-adm active | grep virtual-host Current active profile: virtual-host
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-0671.html