Bug 1041358

Summary: [RFE][nova]: mlock guest memory with libvirt
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/nova/+spec/mlock-guest-memory
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_drafting
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:33:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 15:35:44 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/mlock-guest-memory.

Description:

Guest memory may be swapped out if there is memory pressure on the host.
On the other hand, each guest has a different priority and sometimes
some guests need to avoid memory reclaim to keep their system requirement
even if there is heavy memory pressure in the host.

Current qemu has the mlock feature (-realtime mlock=on|off) to pin down
guest memory on the RAM and libvirt also supports it.

This blueprint will allow Nova to support the mlock feature in order to
avoid guest memory reclaim.

Specification URL (additional information):

None