Skip to content

Fixing maxvcpu mismatch with topology issue, making it dynamic!#19

Open
Anushree-Mathur wants to merge 1 commit into
lop-devops:KVMCIfrom
Anushree-Mathur:Topology
Open

Fixing maxvcpu mismatch with topology issue, making it dynamic!#19
Anushree-Mathur wants to merge 1 commit into
lop-devops:KVMCIfrom
Anushree-Mathur:Topology

Conversation

@Anushree-Mathur

Copy link
Copy Markdown

Maxvcpu is hardcoded for the specific testcase in virsh_emulatorpin.py. When smp value, vcpu_cores, vcpu_threads, vcpu_sockets is specified at the time of running the testcase then the hardcoded value will fail. Adding the code to get this value dynamically based on the smp value provided in the test suite config file.
1 example is that hardcoded value is 7 in virsh_emulatorpin.cfg but in the testsuite config smp value given is 32 not topology will be affected in this case my check will help.

Signed-off-by: Anushree-Mathur anushree.mathur@linux.ibm.com

Maxvcpu is hardcoded for the specific testcase in virsh_emulatorpin.py.
When smp value, vcpu_cores, vcpu_threads, vcpu_sockets is specified at the
time of running the testcase then the hardcoded value will fail.
Adding the code to get this value dynamically based on the smp value
provided in the test suite config file.
1 example is that  hardcoded value is 7 in virsh_emulatorpin.cfg but in the testsuite
config smp value given is 32 not topology will be affected in this case my check
will help.
Signed-off-by: Anushree-Mathur <anushree.mathur@linux.ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant