Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Design and implement ballooning #398

Closed
2 tasks
Tracked by #602
fabiand opened this issue Aug 30, 2017 · 17 comments
Closed
2 tasks
Tracked by #602

Design and implement ballooning #398

fabiand opened this issue Aug 30, 2017 · 17 comments
Labels
kind/enhancement lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/backlog Indicate that the issue or PR is a lower priority and can be worked on in the future sig/virtualization size/M topic/scale

Comments

@fabiand
Copy link
Member

fabiand commented Aug 30, 2017

Ballooning is a technique to let the guest free memory to be reused by the host for other things.
This is one way to do over provisioning of memory.

Proper ballooning requires informations which go beyond what libvirt (and thus the VM.spec.domain parts) provide.

libvirt provides memory, maxMemory and currentMemory which care about the VM frontent related memory aspects. In addition to these fields, a field is required to define how much memory the guest needs at least.
This information is needed to tell, how much memory the guest at least needs to to allow to operate.
This information is guest dependent and is thus not provided by libvirt.

  • Find a proper API design for reflecting all relevant values
  • Understand if libvirt should/would improve in this area
@fabiand fabiand mentioned this issue Aug 30, 2017
Closed
@fabiand fabiand added the priority/backlog Indicate that the issue or PR is a lower priority and can be worked on in the future label Apr 4, 2018
@fabiand fabiand added this to the v2 milestone May 24, 2018
@kubevirt-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 11, 2018
@kubevirt-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@kubevirt-bot kubevirt-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 11, 2018
@kubevirt-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@kubevirt-bot
Copy link
Contributor

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

kubevirt-bot pushed a commit to kubevirt-bot/kubevirt that referenced this issue Nov 6, 2020
@aglitke @awels
doc: Remove deprecated cdi-controller-deployment.yaml manifest (kubev…
c404d57 
…irt#398)

cdi-controller-deployment.yaml is deprecated for release 1.2 which is
imminent.  Remove it and update the documentation to provide current
installation instructions.

Signed-off-by: Adam Litke <alitke@redhat.com>
kubevirt-bot pushed a commit to kubevirt-bot/kubevirt that referenced this issue Dec 7, 2021
@jean-edouard
Add new maintainers to OWNERS file (kubevirt#398)
6d367f9 
Signed-off-by: Jed Lejosne <jed@redhat.com>
@m-yosefpor
Copy link

/reopen

@kubevirt-bot
Copy link
Contributor

@m-yosefpor: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@m-yosefpor
Copy link

any plans on supporting this? (should we reopen the issue?)

@kvaps
Copy link
Member

kvaps commented Feb 23, 2023

/reopen

@kubevirt-bot kubevirt-bot reopened this Feb 23, 2023
@kubevirt-bot
Copy link
Contributor

@kvaps: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kvaps kvaps mentioned this issue Feb 24, 2023
Open
89 tasks
@kvaps
Copy link
Member

kvaps commented Feb 28, 2023

ref #1367

@kvaps kvaps mentioned this issue Mar 2, 2023
Closed
@kvaps
Copy link
Member

kvaps commented Mar 2, 2023

I just prepared a new design proposal for this feature, I invite you to discuss kubevirt/community#212
Any suggestions are welcome 🙂

@kubevirt-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@kubevirt-bot
Copy link
Contributor

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kvaps
Copy link
Member

kvaps commented Apr 2, 2023

/reopen

@kubevirt-bot kubevirt-bot reopened this Apr 2, 2023
@kubevirt-bot
Copy link
Contributor

@kvaps: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kubevirt-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@kubevirt-bot
Copy link
Contributor

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/backlog Indicate that the issue or PR is a lower priority and can be worked on in the future sig/virtualization size/M topic/scale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@fabiand @MarSik @kvaps @kubevirt-bot @m-yosefpor