Actions
Bug #8097
closedInvalid maximum core counts are listed
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Description
On a single core VM, I see the cores dropdown list 1-8 as valid options, but none of those above 1 are valid (subject to #8096). The form does appear to query for the max_cpu_count, but I guess that's either inaccurate at some lower layer, or it doesn't correspond to cpuset configuration.
Actions