"xm vcpu-pin" error

"xm vcpu-pin" error

[Huang2, Wei]

[-- Attachment #1.1: Type: text/plain, Size: 411 bytes --]

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.
========
 
But the command was executed successfully. This must be a bogus warning.
Could someone verify it?
 
 
-Wei

[-- Attachment #1.2: Type: text/html, Size: 1832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: "xm vcpu-pin" error

[Masaki Kanno]

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 <Domain> <VCPU|all> <CPUs|all>
> 
>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

Re: "xm vcpu-pin" error

[Andre Przywara]

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