Why are all the VCPUs assiged to a Xen Windows 2003 R2 Standard Edition guest not detected?
Issue
When four VCPUs are assiged to a Xen Windows 2003 R2 Standard Edition guest, only one is detected. Using command xm vcpu-list shows one VCPU in blocked state and the other three in paused state.
# xm vcpu-list win2k3
Name ID VCPUs CPU State Time(s) CPU Affinity
win2k3 73 0 2 -b- 8607.3 any cpu
win2k3 73 1 - --p 0.0 any cpu
win2k3 73 2 - --p 0.0 any cpu
win2k3 73 3 - --p 0.0 any cpu
Within the Windows guest, in device manager 4 CPUs are shown but Windows Task Manager shows only one CPU:

In View > CPU History customer has "One Graph PER CPU" selected and still only a single graph is displayed, indicating that Windows is only utilizing one VCPU instead of four.
Environment
- Physical server with two quadcore CPU(8 processors)
- Red Hat Enterprise Linux 5.3
- Architecture of xen host(dom0): i686
- Xen packages: xen-3.0.3-80, xen-libs-3.0.3-80, kernel-xen-2.6.18-128
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.