In a previous article I discuss how an ESX host can halt if LUN metadata updates are done the same time a LUN path fails. Thankfully VMware has released a patch for this problem, along with a few others. I strongly suggest you to upgrade if your running VMware ESX 3.5 U3 and block level storage.
ESX350-200901401-SG – PATCH – Security – KB 1006651 – Updates VMkernel VMX hostd. But most important fix that this patch contains definitely is: VMware ESX and ESXi 3.5 U3 I/O failure on SAN LUNs, and LUN queue is blocked indefinitely. For a full description of this issue, see
- ESX350-200901402-SG – PATCH – Security – KB 1006652 – Security Update to ESX Scripts
- ESX350-200901404-BG – PATCH – Critical – KB 1006654 – Updates VMware Tools
- ESX350-200901405-BG – PATCH – General – KB 1006655 – Updates VMware-esx-lnxcfg
- ESX350-200901406-BG – PATCH – General – KB 1006656 – Updates Kernel Source and VMNIX
- ESX350-200901407-BG – PATCH – General – KB 1006657 – Updates Pegasus
- ESX350-200901408-BG – PATCH – Critical – KB 1006658 – Updates SATA Drivers
- ESX350-200901409-SG – PATCH – Security –KB 1006659 – SNMP Security Update
- ESX350-200901410-SG – PATCH – Security – KB 1006660 – Security Update for libxml2
There’s one “patch” released for ESXi (installable and embedded) 3.5:
If you are using SRM in combination with ESX be sure to read the KB1006661 cause this patch contains several fixes related to SRM.
There’s also a whole bunch of 3.0.x patches released, so if you’re still running 3.0.x be sure to look into these new patches.
Thanks to Duncan where I grabbed the above table.