Skip to content
This repository has been archived by the owner on Feb 24, 2020. It is now read-only.

stage1/kvm: Change RAM calculation, and increase minimum #3572

Merged
merged 1 commit into from
Feb 10, 2017

Conversation

grahamwhaley
Copy link

Improve the memory allocation calculation for kvm.
And bump up the minimum.

I'm going to say:
Fixes: #3382
And if we need then lets open a new ticket to cover any future more dynamic solutions.

Signed-off-by: Graham Whaley graham.whaley@intel.com

@grahamwhaley
Copy link
Author

@lucab PTAL

@lucab
Copy link
Member

lucab commented Feb 1, 2017

And if we need then lets open a new ticket to cover any future more dynamic solutions.

If you have some central place for this kind of things in ClearContainers, that would be a good place for the umbrella issue.

Copy link
Member

@lucab lucab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lucab
Copy link
Member

lucab commented Feb 1, 2017

Semaphore is currently under maintenance, so this will have to wait a bit for the CI to pick it up.

@lucab
Copy link
Member

lucab commented Feb 1, 2017

@grahamwhaley this one as well needs to be re-pushed :(

@lucab lucab modified the milestones: v1.25.0, v1.24.0 Feb 2, 2017
@grahamwhaley
Copy link
Author

Hi @lucab I rebased and pushed, but it looks like semaphore has gone wrong again - I'll try re-pushing again, and if that fails then I'll look harder at it.

The current values and algorithm for working out the VM memory
mean that, for cases such as empty pods, we could end up with as
little as 128Mi of RAM. This is too little, and can impact some
startup functions (init/systemd) as the kernel sets some resources
(such as max-threads) according to how much memory the system has.

Improve the situation by setting a minimum RAM size we need,
and adjusting the calculations accordingly.

Modify the relevant unit tests to match, and extend slightly.

Other potential more dynamic solutions (hotplug memory, ballooning
solutions etc. ) are much more complex, and will be investigated for
the future.

Signed-off-by: Graham Whaley <graham.whaley@intel.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants