[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] qemu -numa option and non-contiguous CPU ranges
From: |
Daniel P. Berrange |
Subject: |
Re: [Qemu-devel] qemu -numa option and non-contiguous CPU ranges |
Date: |
Fri, 22 Jun 2012 11:00:57 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
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 :|