Re: [Qemu-devel] qemu -numa option and non-contiguous CPU ranges

2012-06-22 Thread Eduardo Habkost
On Fri, Jun 22, 2012 at 11:00:57AM +0100, Daniel P. Berrange wrote: > On Thu, Jun 21, 2012 at 11:39:46PM +0200, Andre Przywara wrote: > > On 06/21/2012 07:51 PM, Eduardo Habkost wrote: > > >Hi, > > > > > >I just noticed libvirt tries to use the -numa option in a way that qemu > > >never understood:

Re: [Qemu-devel] qemu -numa option and non-contiguous CPU ranges

2012-06-22 Thread Daniel P. Berrange
On Thu, Jun 21, 2012 at 11:39:46PM +0200, Andre Przywara wrote: > On 06/21/2012 07:51 PM, Eduardo Habkost wrote: > >Hi, > > > >I just noticed libvirt tries to use the -numa option in a way that qemu > >never understood: if a node is configured to have a non-contiguous set > >of CPUs, it tries to ge

Re: [Qemu-devel] qemu -numa option and non-contiguous CPU ranges

2012-06-21 Thread Andre Przywara
On 06/21/2012 07:51 PM, Eduardo Habkost wrote: Hi, I just noticed libvirt tries to use the -numa option in a way that qemu never understood: if a node is configured to have a non-contiguous set of CPUs, it tries to generate a command-line option that looks like: "-numa node,nodeid=...,cpus=0,2,

[Qemu-devel] qemu -numa option and non-contiguous CPU ranges

2012-06-21 Thread Eduardo Habkost
Hi, I just noticed libvirt tries to use the -numa option in a way that qemu never understood: if a node is configured to have a non-contiguous set of CPUs, it tries to generate a command-line option that looks like: "-numa node,nodeid=...,cpus=0,2,4,mem=..." ^ But