This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 837] New: "cpus" affinity setting in the config file is

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 837] New: "cpus" affinity setting in the config file is not available
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 14 Dec 2006 22:10:26 -0800
Delivery-date: Thu, 14 Dec 2006 22:11:26 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: "cpus" affinity setting in the config file is not
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: HVM
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: yuanqing.ye@xxxxxxxxx
                CC: jingke.zhang@xxxxxxxxx

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.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>