[Xen-bugs] [Bug 659] only one CPU is detected when dom0 boots up - bugz...@lists.xensource.com - com.xensource.lists.xen-bugs

7 messages in com.xensource.lists.xen-bugs[Xen-bugs] [Bug 659] only one CPU is ...

From	Sent On	Attachments
bugz...@lists.xensource.com	26 May 2006 13:35
bugz...@lists.xensource.com	28 May 2006 20:54
bugz...@lists.xensource.com	13 Jun 2006 00:08
bugz...@lists.xensource.com	13 Jun 2006 00:08
bugz...@lists.xensource.com	13 Jun 2006 00:30
bugz...@lists.xensource.com	19 Jun 2006 03:31
bugz...@lists.xensource.com	20 Jun 2006 00:04

Subject:	[Xen-bugs] [Bug 659] only one CPU is detected when dom0 boots up
From:	bugz...@lists.xensource.com (bugz...@lists.xensource.com)
Date:	06/20/2006 12:04:06 AM
List:	com.xensource.lists.xen-bugs

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=659

qun...@intel.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |qun...@intel.com

------- Comment #5 from qun...@intel.com 2006-06-20 00:04 ------- Tested against chgset 10449, IA-32e on Paxville(8G mem, 16LPs) % grep -c processor /proc/cpuinfo 1

"xm vcpu-list" see 16 LPs, and "xm vcpu-set 0 16" really works. Machine did not restart.

In "/etc/xen/xend-config.sxp", modify "(dom0-cpus 0)" to be "(dom0-cpus 16)" and restart xend, % grep -c processor /proc/cpuinfo 16

Change "(dom0-cpus 16)" back to "(dom0-cpus 0)" and restart xend, % grep -c processor /proc/cpuinfo 16

Restart machine, we can still get 16. It seems that when setting "dom0-cpus" to 0, xend will use the non-zero number set last time, rather than the number of all CPUs available.

To confirm this, I tried on another Paxville which could see 16 VCPUs since Cset 10175. I changed "(dom0-cpus 0)" to "(dom0-cpus 4)", and got 4 VCPUs as expected after restart xend. Then I change 4 back to 0, restart xend or restart machine always give me 4 CPUs in "/proc/cpuinfo".