Re: [Xen-devel] [PATCH] Fix cpumap setting before passing to XEN

2016-05-04 Thread Konrad Rzeszutek Wilk
On Thu, Apr 28, 2016 at 06:02:54PM +0100, Ian Jackson wrote: > Wei Liu writes ("Re: [Xen-devel] [PATCH] Fix cpumap setting before passing to > XEN"): > > So what is the conclusion of this discussion so far? I admit I'm a bit > > lost here. > > Undoubted

Re: [Xen-devel] [PATCH] Fix cpumap setting before passing to XEN

2016-04-28 Thread Ian Jackson
Wei Liu writes ("Re: [Xen-devel] [PATCH] Fix cpumap setting before passing to XEN"): > So what is the conclusion of this discussion so far? I admit I'm a bit > lost here. Undoubtedly: * That "xm ..." generates the reported error is definitely a bug. * "xm"

Re: [Xen-devel] [PATCH] Fix cpumap setting before passing to XEN

2016-04-28 Thread Wei Liu
On Tue, Apr 26, 2016 at 11:54:32AM +0800, Zhenzhong Duan wrote: > On 2016/4/25 21:26, Ian Jackson wrote: > >Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] [PATCH] Fix cpumap setting > >before passing to XEN"): > >>On Wed, Apr 20, 2016 at 03:33:13PM +0100, Wei Li

Re: [Xen-devel] [PATCH] Fix cpumap setting before passing to XEN

2016-04-25 Thread Zhenzhong Duan
On 2016/4/25 21:26, Ian Jackson wrote: Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] [PATCH] Fix cpumap setting before passing to XEN"): On Wed, Apr 20, 2016 at 03:33:13PM +0100, Wei Liu wrote: In principle I think having python binding and xl/libxl behave more or less the same is

Re: [Xen-devel] [PATCH] Fix cpumap setting before passing to XEN

2016-04-25 Thread Ian Jackson
Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] [PATCH] Fix cpumap setting before passing to XEN"): > On Wed, Apr 20, 2016 at 03:33:13PM +0100, Wei Liu wrote: > > In principle I think having python binding and xl/libxl behave more or less > > the same is the right dir

Re: [Xen-devel] [PATCH] Fix cpumap setting before passing to XEN

2016-04-22 Thread Konrad Rzeszutek Wilk
On Wed, Apr 20, 2016 at 03:33:13PM +0100, Wei Liu wrote: > Sorry I was at the Xen hackathon in the last two days. > > On Tue, Apr 12, 2016 at 11:35:20AM +0800, Zhenzhong Duan wrote: > > 在 2016/4/11 19:27, Wei Liu 写道: > > >On Mon, Apr 11, 2016 at 09:42:57AM +0800, Zhenzhong Duan wrote: > > >>It's

Re: [Xen-devel] [PATCH] Fix cpumap setting before passing to XEN

2016-04-20 Thread Wei Liu
Sorry I was at the Xen hackathon in the last two days. On Tue, Apr 12, 2016 at 11:35:20AM +0800, Zhenzhong Duan wrote: > 在 2016/4/11 19:27, Wei Liu 写道: > >On Mon, Apr 11, 2016 at 09:42:57AM +0800, Zhenzhong Duan wrote: > >>It's tool's duty to pass a correct cpumap to XEN. On a host with less than

Re: [Xen-devel] [PATCH] Fix cpumap setting before passing to XEN

2016-04-17 Thread Zhenzhong Duan
On 2016/4/12 11:35, Zhenzhong Duan wrote: On 2016/4/11 19:27, Wei Liu wrote: On Mon, Apr 11, 2016 at 09:42:57AM +0800, Zhenzhong Duan wrote: It's tool's duty to pass a correct cpumap to XEN. On a host with less than 64 CPUS, it just shows below error. [root@localhost /]# xm vcpu-pin 3 all

Re: [Xen-devel] [PATCH] Fix cpumap setting before passing to XEN

2016-04-11 Thread Zhenzhong Duan
在 2016/4/11 19:27, Wei Liu 写道: On Mon, Apr 11, 2016 at 09:42:57AM +0800, Zhenzhong Duan wrote: It's tool's duty to pass a correct cpumap to XEN. On a host with less than 64 CPUS, it just shows below error. [root@localhost /]# xm vcpu-pin 3 all all Error: Cannot pin vcpu: 0 to cpu: [0, 1, 2, 3,

Re: [Xen-devel] [PATCH] Fix cpumap setting before passing to XEN

2016-04-11 Thread Wei Liu
On Mon, Apr 11, 2016 at 09:42:57AM +0800, Zhenzhong Duan wrote: > It's tool's duty to pass a correct cpumap to XEN. On a host with less than > 64 > CPUS, it just shows below error. > > [root@localhost /]# xm vcpu-pin 3 all all > Error: Cannot pin vcpu: 0 to cpu: [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10,

[Xen-devel] [PATCH] Fix cpumap setting before passing to XEN

2016-04-10 Thread Zhenzhong Duan
It's tool's duty to pass a correct cpumap to XEN. On a host with less than 64 CPUS, it just shows below error. [root@localhost /]# xm vcpu-pin 3 all all Error: Cannot pin vcpu: 0 to cpu: [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28,