tests: reduce maxmem of HVM when running in nested virt#842
Merged
Conversation
Nested EPT is super slow, which makes the initial balloon down very long
- sometimes over a minute. PVH are not affected, as those are running
with memory hotplug instead of populate-on-demand on boot, and balloon
down doesn't happen. But HVM are incompatible with memory hotplug
(looks like QEMU limitation), so initial balloon down does happen
there. And before that, Linux thinks it has up to maxmem memory and will
try to clear it. This may look like this for example:
[ 0.879054] mem auto-init: stack:all(zero), heap alloc:on, heap free:on
[ 0.879060] mem auto-init: clearing system memory may take some time...
[ 86.287478] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Reduce the impact when running tests in nested virt by reducing maxmem
to 1G in those cases.
QubesOS/qubes-issues#10723
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #842 +/- ##
==========================================
- Coverage 70.35% 70.34% -0.01%
==========================================
Files 61 61
Lines 14157 14131 -26
==========================================
- Hits 9960 9941 -19
+ Misses 4197 4190 -7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This was referenced Jul 16, 2026
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2026071518-devel&flavor=pull-requests Test run included the following:
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2026050504-devel&flavor=update
Failed tests13 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/176874#dependencies 32 fixed
Unstable testsDetails
Performance TestsPerformance degradation:16 performance degradations
Remaining performance tests:95 tests
|
This was referenced Jul 16, 2026
Member
Author
|
It works! Those seems to be related to this PR:
|
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.
Nested EPT is super slow, which makes the initial balloon down very long
sometimes over a minute. PVH are not affected, as those are running
with memory hotplug instead of populate-on-demand on boot, and balloon
down doesn't happen. But HVM are incompatible with memory hotplug
(looks like QEMU limitation), so initial balloon down does happen
there. And before that, Linux thinks it has up to maxmem memory and will
try to clear it. This may look like this for example:
[ 0.879054] mem auto-init: stack:all(zero), heap alloc:on, heap free:on
[ 0.879060] mem auto-init: clearing system memory may take some time...
[ 86.287478] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Reduce the impact when running tests in nested virt by reducing maxmem
to 1G in those cases.
QubesOS/qubes-issues#10723