On Saturday 04 July 2009, Andre Przywara wrote:
> Paul Brook wrote:
> >> currently SMP guests happen to see vCPUs as different sockets.
> >> Some guests (Windows comes to mind) have license restrictions and refuse
> >> to run on multi-socket machines.
> >> So lets introduce a "cores=" parameter t
Andre Przywara, le Sat 04 Jul 2009 01:28:43 +0200, a écrit :
> Maybe one could describe cores, threads, sockets and nodes in -smp and
> declare the memory topology only in -numa.
Mmm, I'd rather just describe both in a -topology option.
Samuel
--
To unsubscribe from this list: send the line "uns
Paul Brook wrote:
currently SMP guests happen to see vCPUs as different sockets.
Some guests (Windows comes to mind) have license restrictions and refuse
to run on multi-socket machines.
So lets introduce a "cores=" parameter to the -cpu option to let the user
specify the number of _cores_ the
Samuel Thibault wrote:
Andre Przywara, le Fri 03 Jul 2009 16:41:56 +0200, a écrit :
-smp 16 -cpu host,cores=8
That means 8 cores with 2 threads each, thus 16 threads?
No, that meant: 16 vCPUs total with 8 cores per physical packages. I
don't have any notion for threads in the current code, al
> currently SMP guests happen to see vCPUs as different sockets.
> Some guests (Windows comes to mind) have license restrictions and refuse
> to run on multi-socket machines.
> So lets introduce a "cores=" parameter to the -cpu option to let the user
> specify the number of _cores_ the guest shou
Andre Przywara, le Fri 03 Jul 2009 16:41:56 +0200, a écrit :
> -smp 16 -cpu host,cores=8
That means 8 cores with 2 threads each, thus 16 threads? Ok, that can be
later generalized into for instance
-smp 16 -cpu host,nodes=2,sockets=2,cores=2
to define 2 NUMA nodes of 2 sockets of 2 cores, each c
