[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xen-bugs
Subject:    [Xen-bugs] [Bug 659] only one CPU is detected when dom0 boots up
From:       bugzilla-daemon () lists ! xensource ! com
Date:       2006-06-20 7:04:29
Message-ID: E1FsaHl-0007BD-V2 () bugzilla ! xensource ! com
[Download RAW message or body]

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


qun.li@intel.com changed:

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




------- Comment #5 from qun.li@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".


-- 
Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@lists.xensource.com
http://lists.xensource.com/xen-bugs
[prev in list] [next in list] [prev in thread] [next in thread]