Add experimental memory command for balloons #4226
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #4220
The
getcommand is supposed to return a reasonable value for instance memory, with the current workload.Note: the values reported in "total" and "used" memory within the guest might or might not include the balloon
Example with VZ (4 GiB), the balloon (2GiB) is included in the "used" memory and also in the "total" memory:
Example with QEMU (4 GiB), the balloon (2 GiB) is not in the "used" memory but subtracted from "total" memory:
The
setcommand sets the target memory size, so if you want to use only half of default it would say "2048".Note: currently this only inflates the balloon inside the guest, but doesn't actually return any memory to the host
Includes workaround for issue:
More information on balloons:
https://rwmj.wordpress.com/2010/07/17/virtio-balloon/