Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Support Memory constrains #158

Closed
4 tasks done
egernst opened this issue Apr 2, 2018 · 3 comments
Closed
4 tasks done

Support Memory constrains #158

egernst opened this issue Apr 2, 2018 · 3 comments
Assignees

Comments

@egernst
Copy link
Member

egernst commented Apr 2, 2018

From @devimc on January 22, 2018 15:1

Notes:

  • on x86 only chucks/multiples of 128mb can be added
  • memory hot remove is not possible

Copied from original issue: containers/virtcontainers#578

@jcvenegas
Copy link
Member

@WeiZhang555
Copy link
Member

WeiZhang555 commented Jun 14, 2018

Is there any reason for that "on x86 only chucks/multiples of 128mb can be added"? We once got a requirement of tiny VM isolated container with 64M memory

@linzichang
Copy link
Contributor

@jcvenegas @bergwolf Hi, I have seen cpu-hotplug support for "docker update" is done. About "memory-hotplug", I find there is already some implementations like "hotplugMemory", but they haven't combined with kata-runtime update yet. What is the plan for this?

@devimc devimc self-assigned this Aug 27, 2018
@devimc devimc closed this as completed Sep 18, 2018
zklei pushed a commit to zklei/runtime that referenced this issue Jun 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants