@jeff Hi jeff, we have the same issue with another Xeon CPU's.
This thread should be linked with:
https://xcp-ng.org/forum/topic/4604/xcp-8-2-vcpus-max-80-but-vm-shows-64-cpu-only-numa-nodes-and-threads-per-core-not-matching/12
Can you fire the following command during all your VM's are started: xl vcpu-list
In our case we see all vCPUS's greater than 64 in the state "--p" which is bad:
Name ID VCPU CPU State Time(s) Affinity (Hard / Soft)
Domain-0 0 0 79 r-- 257.2 all / all
0__Confluence & Jira & Gitlab 1 0 40 -b- 142.2 all / all
0__SAP S4H S4HANA 2.0 1709 SP4 2 64 - --p 0.0 all / all
0__SAP S4H S4HANA 2.0 1709 SP4 2 65 - --p 0.0 all / all
0__SAP S4H S4HANA 2.0 1709 SP4 2 66 - --p 0.0 all / all
0__SAP S4H S4HANA 2.0 1709 SP4 2 67 - --p 0.0 all / all
0__SAP S4H S4HANA 2.0 1709 SP4 2 68 - --p 0.0 all / all
0__SAP S4H S4HANA 2.0 1709 SP4 2 69 - --p 0.0 all / all
0__SAP S4H S4HANA 2.0 1709 SP4 2 70 - --p 0.0 all / all
0__SAP S4H S4HANA 2.0 1709 SP4 2 71 - --p 0.0 all / all
0__SAP S4H S4HANA 2.0 1709 SP4 2 72 - --p 0.0 all / all
0__SAP S4H S4HANA 2.0 1709 SP4 2 73 - --p 0.0 all / all
0__SAP S4H S4HANA 2.0 1709 SP4 2 74 - --p 0.0 all / all
0__SAP S4H S4HANA 2.0 1709 SP4 2 75 - --p 0.0 all / all
0__SAP S4H S4HANA 2.0 1709 SP4 2 76 - --p 0.0 all / all
0__SAP S4H S4HANA 2.0 1709 SP4 2 77 - --p 0.0 all / all
0__SAP S4H S4HANA 2.0 1709 SP4 2 78 - --p 0.0 all / all
0__SAP S4H S4HANA 2.0 1709 SP4 2 79 - --p 0.0 all / all
It looks like that XEN passes only 64 vCPU's and the rest of CPU's has state "--p" in the pause state, god only knows why and where this limit has been implemented....
Source: https://linux.die.net/man/1/xm
STATES
The State field lists 6 states for a Xen Domain, and which ones the current Domain is in.
r - running The domain is currently running on a CPU
b - blocked The domain is blocked, and not running or runnable. This can be caused because the domain is waiting on IO (a traditional wait state) or has gone to sleep because there was nothing else for it to do.
p - paused The domain has been paused, usually occurring through the administrator running xm pause. When in a paused state the domain will still consume allocated resources like memory, but will not be eligible for scheduling by the Xen hypervisor.
s - shutdown The guest has requested to be shutdown, rebooted or suspended, and the domain is in the process of being destroyed in response.
c - crashed The domain has crashed, which is always a violent ending. Usually this state can only occur if the domain has been configured not to restart on crash. See xmdomain.cfg for more info.
d - dying The domain is in process of dying, but hasn't completely shutdown or crashed.