From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Huang2, Wei" Subject: "xm vcpu-pin" error Date: Tue, 8 Jul 2008 15:28:11 -0500 Message-ID: <85CE8AA0A115F64E8267A90E4535A9748ABFF7@sausexmb5.amd.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0010550423==" Return-path: Content-Class: urn:content-classes:message List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0010550423== Content-Class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8E139.244F1478" ------_=_NextPart_001_01C8E139.244F1478 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I saw a warning message when using "xm vcpu-pin" command on latest xen-unstable tree.=20 =20 =3D=3D=3D=3D=3D=3D=3D=3D # xm vcpu-pin 0 0 0 Error: Cannot pin vcpu: 0 to cpu: [0] - list assignment index out of range Usage: xm vcpu-pin =20 Set which CPUs a VCPU can use. =3D=3D=3D=3D=3D=3D=3D=3D =20 But the command was executed successfully. This must be a bogus warning. Could someone verify it? =20 =20 -Wei ------_=_NextPart_001_01C8E139.244F1478 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
I saw a=20 warning message when using "xm vcpu-pin" command on latest=20 xen-unstable tree.
 
=3D=3D=3D=3D=3D=3D=3D=3D
# xm vcpu-pin 0 = 0=20 0
Error: Cannot = pin vcpu: 0=20 to cpu: [0] - list assignment index out of range
Usage: xm vcpu-pin=20 <Domain> <VCPU|all> <CPUs|all>
 
Set which CPUs = a VCPU can=20 use.
=3D=3D=3D=3D=3D=3D=3D=3D
 
But the=20 command was executed successfully. This must be a bogus = warning.=20 Could someone verify it?
 
 
-Wei
------_=_NextPart_001_01C8E139.244F1478-- --===============0010550423== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0010550423==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Masaki Kanno Subject: Re: "xm vcpu-pin" error Date: Wed, 09 Jul 2008 09:34:40 +0900 Message-ID: <60C8E15B9322F7kanno.masaki@jp.fujitsu.com> References: <85CE8AA0A115F64E8267A90E4535A9748ABFF7@sausexmb5.amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <85CE8AA0A115F64E8267A90E4535A9748ABFF7@sausexmb5.amd.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Huang2, Wei" , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hi Wei, Thanks for your report. The issue was crept in by my mistake. I will solve the issue as soon as possible. Best regards, Kan Tue, 8 Jul 2008 15:28:11 -0500, "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 > >Set which CPUs a VCPU can use. >======== > >But the command was executed successfully. This must be a bogus warning. >Could someone verify it? > > >-Wei > >-------------------------------text/plain------------------------------- >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.xensource.com >http://lists.xensource.com/xen-devel From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andre Przywara Subject: Re: "xm vcpu-pin" error Date: Wed, 9 Jul 2008 09:01:44 +0200 Message-ID: <48746258.6060709@amd.com> References: <85CE8AA0A115F64E8267A90E4535A9748ABFF7@sausexmb5.amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <85CE8AA0A115F64E8267A90E4535A9748ABFF7@sausexmb5.amd.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Huang2, Wei" Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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 > > 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