Bug 1330721 - [RFE] set HostedEngine VM process nice value
Summary: [RFE] set HostedEngine VM process nice value
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-hosted-engine-ha
Classification: oVirt
Component: RFEs
Version: 1.3.5.1
Hardware: x86_64
OS: Linux
low
low vote
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact: Nikolai Sednev
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-26 19:29 UTC by Pat Riehecky
Modified: 2018-06-06 12:28 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-06 12:28:49 UTC
oVirt Team: SLA
dfediuck: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description Pat Riehecky 2016-04-26 19:29:47 UTC
Description of problem:
Occasionally my Hosted Engine ends up on a system with heavy CPU usage.  This leaves the Hosted Engine a bit less responsive than I'd like.

Can there be an option added to set the Hosted Engine's " /usr/libexec/qemu-kvm -name HostedEngine -S -machine ...." process to Nice -1.  When I set this manually the VM responds more like I'd expect.

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-setup-1.3.4.0-1.el7.centos.noarch
ovirt-hosted-engine-ha-1.3.5.1-1.el7.centos.noarch


How reproducible: 100%


Steps to Reproduce:
1.Review Nice value of Hosted Engine process
2.
3.

Actual results:
Nice 0

Expected results:
Ability to set if desired.

Additional info:

Comment 1 Martin Sivák 2016-04-27 08:06:37 UTC
This should be quite easy to do, we already have all infrastructure present in all components. What we can do is:

1) Enable editing of the cpu shares and nice value fields in the Edit VM dialog. That should be a matter of adding one annotation to the code

2) Set a sensible default when creating the initial configuration during HE setup

Comment 2 Red Hat Bugzilla Rules Engine 2016-04-27 08:06:42 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 3 Sandro Bonazzola 2016-05-02 09:52:56 UTC
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Comment 4 Doron Fediuck 2016-06-09 10:49:45 UTC
Editing additional aspects of the HE VM requires extensive testing.
Moving to 4.1.

Comment 5 Red Hat Bugzilla Rules Engine 2016-06-09 10:49:50 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 7 Yaniv Lavi 2018-06-06 12:28:49 UTC
Closing old RFEs. Please reopen if needed.
Patches are welcome.


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