ram_filter ignores hugepages which can create unstable guests

Bug #1689753 reported by lica on 2017-05-10
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)

Bug Description

environment info:

problem description:
There are 220G memory in compute-node.The 200G of them are hugepages.The page_size is 1G.
Other 20G of them are normal memorys.

When I boot a normal instance with the flavor of 30G mem and no hugepages.
The instance is created successfully.But the OS become unstable even OOM because memory exhausted

I think the instance should boot failed with ram_filter return 0 hosts.Rather than think that the memory is sufficient
and spawn the instance in that compute_node

赵明俊 (falseuser) wrote :

Seems compute node just report instance used resources and reserved resources, hugepage does not belong to one of them,so ram_filter can not filter it out,even if you actually use the memory in other ways.

Sean Dague (sdague) wrote :

Automatically discovered version ocata in description. If this is incorrect, please update the description to include 'nova version: ...'

tags: added: openstack-version.ocata
Sean Dague (sdague) on 2017-07-27
summary: - ram_filter fail when computer-node has hugepages
+ ram_filter ignores hugepages which can create unstable guests
Changed in nova:
status: New → Confirmed
tags: added: hugepages
Changed in nova:
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers