Merged
Conversation
Because some cases raised error log created by memory_threshold_check, like 'free memory xx is less than memory threshold xx'. Signed-off-by: Chun'ang Li <[email protected]>
wangxin
approved these changes
Jan 13, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of PR
Increase KVM sonic memory from 3GiB to 4GiB. Because some cases raised error log created by the tool
memory_threshold_check, likefree memory xx is less than memory threshold xx. And the threshold is based on total memory.Signed-off-by: Chun'ang Li [email protected]
Type of change
Back port request
Approach
What is the motivation for this PR?
Increase KVM sonic memory from 3GiB to 4GiB. Because some cases raised error log created by the tool
memory_threshold_check, likefree memory xx is less than memory threshold xx. And the threshold is based on total memory.How did you do it?
Modify memory set in
ansible/roles/vm_set/templates/sonic.xml.j2.Notes:
memorytag is the maximum allocation of memory andcurrentMemorytag is the actual allocation of memory.How did you verify/test it?
Run TC and no memory_threshold_check issue.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation