2,187
edits
(→Build Notes: Added "USB Image") |
(→Hardware: Reworked) |
||
Line 164: | Line 164: | ||
= Configuration Considerations = | = Configuration Considerations = | ||
== Hardware == | == Hardware == | ||
=== | === CPU === | ||
{|cellpadding="1" cellspacing="0" border="1" | |||
|- style="background-color:#bbddff;" | |||
! Feature !! Set to !! Intel name !! AMD name | |||
|- | |||
| Node Interleaving || Disabled (allows NUMA operation) | |||
|- | |||
| Execute Protection || Enabled || eXecute Disable (XD) || No-Execute Page-Protection | |||
|- | |||
| Virtualisation assist || Enabled || Intel VT || AMD-V | |||
|} | |||
=== CPU Power vs Performance === | |||
'''If in doubt put server BIOS settings to maximum performance''' - this ensures that ESX can get the most out of the hardware, allowing the BIOS to balance or use low power modes may impact VM performance. ESX's are expected to work hard, that's how they save you money, and so they should be set-up to be able to perform. In theory, allowing the motherboard to throttle back the CPUs when under low load shouldn't cause a problem. | |||
'''When using ESX4.1 or higher''' then set the BIOS to allow the OS (ie ESX) control of CPU performance (if the setting is available), this allows the CPU Performance to be controlled dynamically by ESX as it manages VM load (and configurable through the VI Client). | |||
See [http://kb.vmware.com/kb/1018206 VM KB 1018206 - Poor virtual machine application performance may be caused by processor power management settings] for further info | |||
See [http://kb.vmware.com/kb/ | === HP ASR === | ||
'''Should be disabled.''' | |||
VMware don’t recommend that we use the HP ASR feature (designed to restart a server in the case of an OS hang), they’ve come across occasions when an ESX under load will suddenly restart due to ASR time-outs. See [http://kb.vmware.com/kb/1010842 VM KB 1010842 - HP Automatic Server Recovery in a VMware ESX Environment] for further info. | |||
== Networking == | == Networking == |