4 Processors initialized but only one in /proc/cpuinfo

4 Processors initialized but only one in /proc/cpuinfo

[Stefan Berger]

This is about a blade that I am using. It has 2 processors with
hyperthreading. I see that the Xen brings up 4 processors (xm dmesg) and
I see that domain 0 initializes 4 processors (dmesg). However, I only
see one processor in /proc/cpuinfo. Any (obvious) configuration that I
might have done wrong on this machine?

  Stefan

Re: 4 Processors initialized but only one in /proc/cpuinfo

[Ryan Harper]

* Stefan Berger <stefanb@us.ibm.com> [2006-05-12 13:06]:
> This is about a blade that I am using. It has 2 processors with
> hyperthreading. I see that the Xen brings up 4 processors (xm dmesg) and
> I see that domain 0 initializes 4 processors (dmesg). However, I only
> see one processor in /proc/cpuinfo. Any (obvious) configuration that I
> might have done wrong on this machine?

Try running xm vcpu-set 0 4, this should restore dom0's vcpus to 4.

The previous enforce_dom0_cpus test case didn't properly restore vcpu
availability for dom0 and when starting xend, it may have restored the
state from xenstore to dom0.


-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

Re: 4 Processors initialized but only one in /proc/cpuinfo

[Stefan Berger]

[-- Attachment #1.1: Type: text/plain, Size: 1124 bytes --]

ryanh@us.ltcfwd.linux.ibm.com wrote on 05/12/2006 02:21:33 PM:

> * Stefan Berger <stefanb@us.ibm.com> [2006-05-12 13:06]:
> > This is about a blade that I am using. It has 2 processors with
> > hyperthreading. I see that the Xen brings up 4 processors (xm dmesg) 
and
> > I see that domain 0 initializes 4 processors (dmesg). However, I only
> > see one processor in /proc/cpuinfo. Any (obvious) configuration that I
> > might have done wrong on this machine?
> 
> Try running xm vcpu-set 0 4, this should restore dom0's vcpus to 4.

This didn't help but crashed the system and after the reboot I still only 
had one processor.
> 
> The previous enforce_dom0_cpus test case didn't properly restore vcpu
> availability for dom0 and when starting xend, it may have restored the
> state from xenstore to dom0.

This must have been the case. Removing the whole xenstore file (tdb) did 
the trick and after a reboot I had the four processor back.

 Thanks for the hint.
   Stefan

> 
> 
> -- 
> Ryan Harper
> Software Engineer; Linux Technology Center
> IBM Corp., Austin, Tx
> (512) 838-9253   T/L: 678-9253
> ryanh@us.ibm.com

[-- Attachment #1.2: Type: text/html, Size: 1521 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel