[pve-devel] Optimizing CPU flags

[Alexandre DERUMIER]

>> this might also need the enforce parameter. 

enforce is currently buggy on 2.6.32, but works fine with 3.10 kernel.




----- Mail original -----
De: "Stefan Priebe" <s.priebe at profihost.ag>
À: "dietmar" <dietmar at proxmox.com>, "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Mercredi 11 Février 2015 08:17:01
Objet: Re: [pve-devel] Optimizing CPU flags

Am 11.02.2015 um 06:28 schrieb Dietmar Maurer: 
> On 01/30/2015 10:23 PM, Stefan Priebe wrote: 
>> "For mixed clusters, use the lowest available CPU version, so if one 
>> host is Penryn and the other Nehalem, use Penryn on both. If you are 
>> using RHEV or oVirt, this is already built in. VMWare have this called 
>>> "EVC" and position it as a huge feature." 

> What exactly is a fixed cluster? The admin can always add an additional 
> node, and it is not possible to 
> know the CPU features of new nodes in advance. 

Sure live migration may fail - but this is also true for using the host 
option. 

The optimize option has the advantage that the maximum features will be 
used for new VMs - this might also need the enforce parameter. 

Stefan 

_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel