Bug 1109157

Summary:	[RFE] provide an option to turn off KSM on a per VM basis
Product:	[oVirt] ovirt-engine	Reporter:	Sven Kieske <s.kieske>
Component:	RFEs	Assignee:	Dudi Maroshi <dmaroshi>
Status:	CLOSED WONTFIX	QA Contact:	Shira Maximov <mshira>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	---	CC:	amureini, bugs, danken, dfediuck, gklein, iheim, istein, rbalakri, sbonazzo, s.kieske, yeylon, ykaul
Target Milestone:	---	Keywords:	FutureFeature, Reopened
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	sla
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-17 13:39:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sven Kieske 2014-06-13 11:20:05 UTC

Description of problem:

due to security considerations, you may want to turn of KSM
(Kernel Same Page Merging) for some VMs.

It would be cool if this could be achieved via REST/GUI in a simple way.

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


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
See this thread on the users ML:
http://lists.ovirt.org/pipermail/users/2014-June/025099.html

Comment 1 Allon Mureinik 2015-04-07 21:14:09 UTC

We saw this won't be closed in a hackathon, returning assignee to SLA stakeholders to rethink.

Comment 2 Sandro Bonazzola 2015-09-04 09:03:23 UTC

This is an automated message.
This Bugzilla report has been opened on a version which is not maintained anymore.
Please check if this bug is still relevant in oVirt 3.5.4.
If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution)
If it's an RFE please update the version to 4.0 if still relevant.

Comment 3 Sandro Bonazzola 2015-10-02 10:28:55 UTC

This is an automated message.
This Bugzilla report has been opened on a version which is not maintained
anymore.
Please check if this bug is still relevant in oVirt 3.5.4 and reopen if still
an issue.

Comment 4 Sven Kieske 2015-10-09 13:52:44 UTC

This is an RFE, thus it was never implemented, and still applies to latest master branch.

You should not automatically close RFEs, but retarget them to the last release.

Thanks

Sven

Comment 5 Red Hat Bugzilla Rules Engine 2015-10-19 10:49:08 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 6 Yaniv Kaul 2015-11-17 13:39:33 UTC

Since we have a KSM policy per cluster, I'm not sure we are going to invest in per VM policy (one may argue that it's worthwhile to do it per host, as KSM does consume CPU resources from the host). Closing for now, unless we get more demand  for such granularity.

Comment 7 Sven Kieske 2015-11-18 13:03:36 UTC

Why do you close RFEs without further discussion with the community?

was it somehwere decided (where?) that this will never get implemented?

are there any informations regarding this topic available to the public?

Comment 8 Yaniv Kaul 2015-11-18 13:32:10 UTC

(In reply to Sven Kieske from comment #7)
> Why do you close RFEs without further discussion with the community?

My apologies - set my closing comment as private by accident. Should be OK now.

> 
> was it somehwere decided (where?) that this will never get implemented?

We are trying to keep a sane list of requests 'alive' (we have over 900) - since no one has done any work on this in the last 1.5 years, and since it did not get more (repeated/escalated) requests in that time frame, I don't think it'll be implemented soon. If you feel differently, we can keep it open for someone to pick it up.

> 
> are there any informations regarding this topic available to the public?

I don't think there has been a discussion around this apart from 'it can be done per VM' in the mailing list - which is part of the reason why I've closed it.