@sapcode
Found a description here: https://linux.die.net/man/1/xm
But no idea why it starts some CPUs in the pause state....
Will do some testing with C states and govenor performance....

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.