[Xen-bugs] [Bug 837] New: "cpus" affinity setting in the config file is not available - bugz...@lists.xensource.com - com.xensource.lists.xen-bugs

4 messages in com.xensource.lists.xen-bugs[Xen-bugs] [Bug 837] New: "cpus" affi...

From	Sent On	Attachments
bugz...@lists.xensource.com	14 Dec 2006 22:10
bugz...@lists.xensource.com	14 Dec 2006 22:17
bugz...@lists.xensource.com	28 Jun 2007 18:50
bugz...@lists.xensource.com	28 Jun 2007 18:51

Subject:	[Xen-bugs] [Bug 837] New: "cpus" affinity setting in the config file is not available
From:	bugz...@lists.xensource.com (bugz...@lists.xensource.com)
Date:	12/14/2006 10:10:03 PM
List:	com.xensource.lists.xen-bugs

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

Summary: "cpus" affinity setting in the config file is not available Product: Xen Version: unstable Platform: All OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: HVM AssignedTo: xen-...@lists.xensource.com ReportedBy: yuan...@intel.com CC: jing...@intel.com

Against CS 12757. When we set cpus="0" in configuration file, the Linux VMX domain's vcpus should be bond to CPU0, but against CS 12757, I can see CPU affinity is "any cpu" in `xm vcpu-list`, and, VMX domain's vcpus were not only bond to CPU0, it also bond to CPU1.

reproduce steps: 1. prepare a Linux image 2. prepare a configuration file with vcpus=4, memory=512, cpus = "0" 3. xm cr "configuration file" 4. after guest OS boot up, run "xm vcpu-list" you can see what I just described.