You can configure the setting while the server is running, but it won’t take affect until it’s restarted. via the ILO for each blade individually.via the console of each blade individually.You must change the power management setting in the BIOS but there are a couple of options You can also use PowerCLI (ESX4 only) by querying the host’s Advanced setting ‘Power.cpupolicy’ get-vmhost myhost | get-vmhostAdvancedConfiguration -name Power.cpupolicy.You can also configure it using the Properties button. For a 4.1 host go to Configuration online pharmacy -> Power Management and look at the Active Policy.For a 40 host go to Configuration -> Processors and look at the Power Management settings.Where to check depends on your version of ESX (or ESXi) ie the hardware is controlling power management. If the underlying BIOS is set to Dynamic Power Savings it’ll show as ‘Not Supported’. via the ILO (under Power Management, Power settings) or via the ILO CLI.in the BIOS settings (slow and potentially disruptive).You can check the current power management setting in various ways Not necessarily a show stopper but definitely an improvement.įor my infrastructure (with around 160 physical blades) changing them all was a time consuming process (and could potentially be disruptive depending on whether your ESX/i hosts are all clustered). After changing the power setting the same VMs (under a similar load) dropped to under 1% CPU Ready (the change was made at 17:00 if you look at the graph). Using a mixture of ESXTOP and vCenter’s performance charts I was able to confirm that the %CPU Ready was hovering around the 4% mark even when the physical host was using less than 15% pCPU. We run HP C-class blades and after checking the VMware knowledgebase article KB1018206 and a sample of our BIOS settings we found that it applied to us too – not surprising as we don’t modify the BIOS defaults during provisioning.
To check for these symptoms you could use the VI client, ESXTOP in batch mode combined with the batch processing scripts in the vMA to capture pCPU statistics from a group of servers, or PowerCLI -whichever suits your skillset. Having investigated I thought I’d record it here for others convenience. Julian Wood has also blogged about this issue ( Your HP blades may be underperforming) but neither go into too much detail about the fix. In a great blogpost by Andre Leibovicihe highlighted a default HP BIOS setting which could be impacting the performance of your VMs if your environment matches the following
0 kommentar(er)
