Upon reset of the VM, the entire ESXi 5.1 host to PSODs on me. After playing with the VM for a little bit, I decided to reset the virtual machines power. Added to VM inventory on the ESXi host and booted it up. I told Virtual Box to export as "OVA 9.0". I have a Windows VM that I ported over from Virtual Box. I hope this helps anyone else that comes across a similar issue. I'm going to do some testing, but it sounds like the 1.33 IMM firmware may be the cause of this issue. You will see with 1.35 firmware, there is no longer an UpperThreshold even listed.ĮDIT: I want to make a correction, at first I mentioned other blades in my environment did have the 1.33 IMM firwmare, in fact, they did not, only these new blades I built a few weeks ago did.
For some reason, the UpperThreshold is set to 0. This screenshot illustrates what I was seeing. Despite nothing being in the release notes about resolving voltage threshold issues, I flashed to 1.35 from 1.33 this morning and my issue is resolved. Yesterday, the 11th, IBM released new firmware for the Integrated Management Module which is responsible for reporting hardware data back to the vSphere host.
#Vmware esxi 5 add firewall rule upgrade#
Speaking with VMware support, it was agreed that since all firmware is equal across my environment, that I should upgrade the CIM providers that IBM provides for the IBM HS22V blades. However, the blades in this environment keep throwing "Host Hardware Voltage" errors in relation to the CMOS battery. One of my virtual datacenters contains the same blades we use throughout our environment, same firmware, same vSphere version(821296), and the same enclosures. I just wanted to share information on how I resolved an issue with "Host Hardware Voltage" errors across several of my blades in case anyone else comes across the same issue.