Skip to content
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

Cannot choose some combinations of the CPU topology values #1503

Open
hstastna opened this issue Aug 14, 2021 · 2 comments
Open

Cannot choose some combinations of the CPU topology values #1503

hstastna opened this issue Aug 14, 2021 · 2 comments

Comments

@hstastna
Copy link
Member

Description of a problem:
In the current web-ui, it is not possible to set all the valid combinations of the values for the number of sockets, cores, threads, according to the total VCPUs. For example, for 9 total VCPUs, it is not possible to reach the CPU topology with 1 socket, 1 core and 3 threads. This should be possible in both Create VM Wizard's Basic settings and also in VM Details card.

Steps to Reproduce:
128033580-40b457cd-4188-471e-b3a9-261fcde1dda5

Additional info:
This issue was originally mentioned here: #1489 (comment)
In webadmin it works, it is possible to choose any valid combination of the values.

@sgratch
Copy link
Member

sgratch commented Aug 16, 2021

This whole CPU topology fields validation is not so user friendly as well since in case of an error, the user can't understand what is the exact invalid cpu topology - the values are auto changed to some different invalid values than the original values entered by the user. This is also mentioned here: #1489 (comment)
Not sure if worth fixing as a standalone issue but maybe as part of this fix if possible.

@hstastna
Copy link
Member Author

hstastna commented Aug 24, 2021

This whole CPU topology fields validation is not so user friendly as well since in case of an error, the user can't understand what is the exact invalid cpu topology - the values are auto changed to some different invalid values than the original values entered by the user. This is also mentioned here: #1489 (comment)
Not sure if worth fixing as a standalone issue but maybe as part of this fix if possible.

I've opened a separate issue for this: #1506

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

No branches or pull requests

2 participants