From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:44394) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Si0fx-0005EF-RB for qemu-devel@nongnu.org; Fri, 22 Jun 2012 06:01:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Si0fv-00039x-P7 for qemu-devel@nongnu.org; Fri, 22 Jun 2012 06:01:13 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59000) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Si0fv-00039I-HT for qemu-devel@nongnu.org; Fri, 22 Jun 2012 06:01:11 -0400 Date: Fri, 22 Jun 2012 11:00:57 +0100 From: "Daniel P. Berrange" Message-ID: <20120622100057.GD10128@redhat.com> References: <20120621175125.GJ5073@otherpad.lan.raisama.net> <4FE394A2.8070709@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4FE394A2.8070709@amd.com> Subject: Re: [Qemu-devel] qemu -numa option and non-contiguous CPU ranges Reply-To: "Daniel P. Berrange" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andre Przywara Cc: libvir-list@redhat.com, Bharata B Rao , Eduardo Habkost , qemu-devel@nongnu.org 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 generate a command-line option that looks like: > > > >"-numa node,nodeid=...,cpus=0,2,4,mem=..." > > ^^^^^ > > > >But this format was never supported by qemu. This format is even a bit > >weird, as "," is an option separator, and it is being used as a > >separator _inside_ an option. > > Exactly this was the reason back then to not support non-contiguous > set of CPUs. Inside qemu there is no reason why this shouldn't work, > it was just hard to write on the command line. So after a short > discussion we decided to drop this for the time being. If you have a > great idea how to specify this (I think a comma will not work, > because it will be catched earlier), I am all ears. Lets just use a ';' or ':' as the seperator instead ? Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|