-
Notifications
You must be signed in to change notification settings - Fork 381
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.
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
T6484: Smoketest: Increase KVM memory limit #656
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are there specific tests that may fail due to insufficient memory? I have nothing against the change, but if possible, we should document the motivation for it in a comment.
The snippet of OP has this information already included - Reproduced via Smoketest running via
|
@Mergifyio backport sagitta |
✅ Backports have been created
|
Change Summary
Types of changes
Related Task(s)
https://vyos.dev/T6484
Component(s) name
smoketest
Proposed changes
When running smoketests in the vyos-build container, an error message similar to the following appears:
DEBUG - test_fastnetmon (__main__.TestServiceIDS.test_fastnetmon) ... [ 4213.579433] Out of memory: Killed process 543005 (fastnetmon) total-vm:2301048kB, anon-rss:7432kB, file-rss:1812608kB, shmem-rss:0kB, UID:0 pgtables:3804kB oom_score_adj:0
Further investigation reveals that the KVM created for the smoketests is limited to 3GB of memory. Increasing this to 4GB allows the smoketests to complete and pass.
How to test
Run smoketests with
make test
after building ISO. When the KVM memory limit is set to 3GB, the smoketests will fail asfastnetmon
is OOM killed. When it is set to 4GB, the smoketests pass.Checklist: