VM /ETC

A new patch for VMware ESX 3.5 Update 3 was released last week that fixes the previously reported iSCSI and FC Alert – “Queue for device has been blocked” issue. The fix was part of a bundle of patches released for ESX 3.5, ESXi 3.5 and ESX 3.0.x products.

Duncan’s summary post over at yellow-bricks.com pointed me to the new VMware KB article specific to the patch with the I/O alert fix: VMware ESX 3.5, Patch ESX350-200901401-SG: Updates VMkernel, VMX, and hostd

Upon reading the KB article I noticed that the VI Client NTP configuration issue I have posted about, and continue to run into, has also been fixed.

Read VMware’s KB for all “the other issues” corrected along with some information about applying the patches with or without Update Manager.

Related Posts

• My thoughts on the reactions to the ESX 3.5 Update 2 BUG (17)
• Failed to deploy template: The virtual disk is either corrupted or not a supported format (26)
• ESX patches released – 03/06/08 (0)
• ESX 3.5 4 socket host based license patch (0)
• ESX 3.0.1 VMs reboot when adding host to VC 2.5 (2)
• Update and Auto Patch ESX (1)
• Best Practices for vSphere (ESX 4) Service Console Partitions (19)
• vCenter 2.5 Update 5 Provides HA Improvements to Allow up to 80 VMs per ESX/ESXi host (5)
• Changing NTP Server in ESX 3.5 fails with error “failed to change host configuration” (11)
• VI 4.0 will NOT be announced at VMworld 2008 (15)