KVM: Add multi_vms_multi_boot memory sweep test#561
Merged
xhao22 merged 1 commit intointel:mainfrom Mar 18, 2026
Merged
Conversation
fanchen2
force-pushed
the
memory
branch
3 times, most recently
from
bdfcfd7 to
87886a3
Compare
xhao22
reviewed
Mar 16, 2026
| - 1td_1vm: | ||
| machine_type_extra_params_vm2 = "kernel-irqchip=split" | ||
| vm_secure_guest_type_vm2 = tdx | ||
| variants: |
Contributor
There was a problem hiding this comment.
Does this patch remove the original case, multi_vms.1td_1vm?
Same comments for below cases: 4td, 4vm.
Contributor
Author
There was a problem hiding this comment.
Yes, thanks, updated, added default for them.
xhao22
reviewed
Mar 16, 2026
| LOG = logging.getLogger("avocado.test") | ||
|
|
||
|
|
||
| def _host_available_mem_mb(): |
Contributor
There was a problem hiding this comment.
There is existing API: utils_misc.get_usable_memory_size()
| Returns a list of dicts: | ||
| [ {vm_name: {param_name: value, ...}, ...}, ... ] | ||
| """ | ||
| loop_params = _parse_series(params.get("loop_params", "mem")) |
Contributor
There was a problem hiding this comment.
seems no loop_params define in any .cfg file.
Contributor
Author
There was a problem hiding this comment.
yes, updated, removed this variable
xhao22
reviewed
Mar 16, 2026
| test.cancel("No VMs configured for multi_vms_multi_boot") | ||
|
|
||
| try: | ||
| iteration_plan = _resolve_iteration_plan(params, vm_names) |
Contributor
There was a problem hiding this comment.
Not sure the purpose of variable iteration_plan?
Contributor
Author
There was a problem hiding this comment.
We need to boot VM from 1024M to all free memory in host, boot VM for many iterations.
fanchen2
force-pushed
the
memory
branch
3 times, most recently
from
c78d5a0 to
2faab00
Compare
Add multi_vms_multi_boot test that boots VMs/TDs with varying memory configurations using a random_32g_window generator to sample memory sizes across sliding 32G windows up to host free memory. Each iteration boots all VMs with a specific memory size, verifies guest login, then destroys all VMs before proceeding to the next memory size. All cases start from 1024M: - multi_vms.1vm.from1G_toall: single VM - multi_vms.1td.from1G_toall: single TD - multi_vms.1td_1vm.from1G_toall: 1 TD + 1 VM - multi_vms.2td.from1G_toall: 2 TDs - multi_vms.4td.from1G_toall: 4 TDs - multi_vms.2vm.from1G_toall: 2 VMs - multi_vms.4vm.from1G_toall: 4 VMs Signed-off-by: Farrah Chen <farrah.chen@intel.com>
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.
Add multi_vms_multi_boot test that boots VMs/TDs with varying memory configurations using a random_32g_window generator to sample memory sizes across sliding 32G windows up to host available memory.
Each iteration boots all VMs with a specific memory size, verifies guest login, then destroys all VMs before proceeding to the next memory size. All cases start from 1024M: