[pve-devel] unknown setting 'maxcpus'

Alexandre DERUMIER aderumier at odiso.com
Mon Jul 6 09:01:40 CEST 2015


>>Maybe will be better change the terms in the GUI of PVE, ie, for create or 
>>change the CPU configuration, instead say "Cores", must say "Threads of 
>>Processor", of this mode, all people will know that the threads also are 
>>considered when should choose the configuration more right.

That's wrong because they exist also a thread option for processor (we don't use it currently).

full topology  = processor * cores * threads

(like for hyperthreading, you can have multiple threads by core)


----- Mail original -----
De: "Cesar Peschiera" <brain at click.com.py>
À: "dietmar" <dietmar at proxmox.com>, "aderumier" <aderumier at odiso.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Dimanche 5 Juillet 2015 16:33:04
Objet: Re: [pve-devel] unknown setting 'maxcpus'

----- Original Message ----- 
From: "Dietmar Maurer" <dietmar at proxmox.com> 
To: "Stefan Priebe" <s.priebe at profihost.ag>; "Alexandre DERUMIER" 
<aderumier at odiso.com> 
Cc: "pve-devel" <pve-devel at pve.proxmox.com> 
Sent: Friday, July 03, 2015 5:08 PM 
Subject: Re: [pve-devel] unknown setting 'maxcpus' 


> cores*socket is the maximum, so vcpus needs to be smaller/equal. 

Maybe will be better change the terms in the GUI of PVE, ie, for create or 
change the CPU configuration, instead say "Cores", must say "Threads of 
Processor", of this mode, all people will know that the threads also are 
considered when should choose the configuration more right. 

Regards 
Cesar 



More information about the pve-devel mailing list