Bug 48297 – Limit Host OS Memory Usage on Virtualization Hosts

Bug 48297 - Limit Host OS Memory Usage on Virtualization Hosts


Summary:	Limit Host OS Memory Usage on Virtualization Hosts

Status:	CLOSED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Virtualization - KVM
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-12-07 08:17 CET by Christian Völker
Modified:	2023-06-28 10:46 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2018112921000611
Bug group (optional):	Further conceptual development
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Christian Völker

2018-12-07 08:17:44 CET

A failure in some programs running as part of the UCS OS (ie Listener, AD-Connector, rsyslogd ...) could cause the process to hogg CPU or memory resources.

Especially consuming memory will cause the system to swap which affects the running VMs and slows them down. If at a later stage oom gets involved VMs are likely to get killed as they usually use a lot of memory.

So a failure in one of the programs will cause VMs to slow down and get terminated. 

We should limit the available resources for the host OS, too. This way we will never have a oom on the host causing a VM to get killed.

Other virtualisation hosts have limited the resources for their administrative environments (ie ESXi to 750MB) and XEN has the dom0 which is limited, too.

Comment 1 Stefan Gohmann

2019-01-03 07:30:39 CET

This issue has been filed against the UCS version "unstable" which does not really exist. Please change the version value.