The Value VCPUs_Max Must Be a Multiple of This Field in XCP-NG
-
@Pete-S Right
-
-
I haven't seen this, but I am using XCP-ng and I often can do the VMs through the XCP-ng client too.
-
I generally just keep the default vCPU config and thus haven't seen this myself either.
It's possible that this is a bug though. With that @olivier would need to know exactly what version of xo-web and xo-server you're running, how you built your instance etc as well.
-
My initial thought is that the configuration is saying how many socket do you want this guest to have, which then doesn't make sense when you say 1 CPU with 2 cores, when you have 2 listed in the above field.
-
You can either have 2 vcpu and follow the default host config or you can have something that divides evenly based on the number of filled sockets your host has.
-
Based on this the field is saying VCPUs_max has to be a multiple of cores per socket
And later this VCPUs_max must be a multiple of this field meaning what you're telling the system to create this guest with, doesn't make logical sense.
If you wanted the guest to have 2 CPU with 1 core each, you have to use the settings as shown in the second image. If you wanted this guest to have more CPU, set it to something like 8 and have the Topology be 2 cpu with 4 core each. Ideally mimic the hardware that your host has though.
-
I'm guessing XenCenter is just running some behind the scenes magic and changing it to work, where XO is telling you to fix the issue.
-
Tags updated as this is XCP-NG.
-
@scottalanmiller It's not. I changed after I posted this.
