WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] "xm vcpu-pin" error

To: "Huang2, Wei" <Wei.Huang2@xxxxxxx>
Subject: Re: [Xen-devel] "xm vcpu-pin" error
From: Andre Przywara <andre.przywara@xxxxxxx>
Date: Wed, 9 Jul 2008 09:01:44 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 09 Jul 2008 00:02:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <85CE8AA0A115F64E8267A90E4535A9748ABFF7@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <85CE8AA0A115F64E8267A90E4535A9748ABFF7@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.10 (X11/20070409)
Huang2, Wei wrote:
I saw a warning message when using "xm vcpu-pin" command on latest xen-unstable tree. ========
# xm vcpu-pin 0 0 0
Error: Cannot pin vcpu: 0 to cpu: [0] - list assignment index out of range
Usage: xm vcpu-pin <Domain> <VCPU|all> <CPUs|all>
Set which CPUs a VCPU can use.
========
I have seen this before, this issue is on my list. The problem is only occurring on Dom0 repinning. After having done the actual xc.vcpu_setaffinity call in XendDomain.py:1426, xend wants to set an entry in the Python array: cpus[v] = cpumap. This array has not been properly allocated for Dom0, thus forcing an assignment to an empty list. This is more or less cosmetic as long as you only pin one VCPU, but pinning all (e.g. xm vcpu-pin 0 all 4-7) will stop after the first VCPU, so you have to use some kind of shell-for-loop workaround _and_ ignore the error message. I haven't found a proper way to fix this yet.

Regards,
Andre.


--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 277-84917
----to satisfy European Law for business letters:
AMD Saxony Limited Liability Company & Co. KG,
Wilschdorfer Landstr. 101, 01109 Dresden, Germany
Register Court Dresden: HRA 4896, General Partner authorized
to represent: AMD Saxony LLC (Wilmington, Delaware, US)
General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy


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

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