Critical 2009 last-minute ESX3.5 patches

I just noticed that VMware released a couple of critical ESX3.5 fixes on December 29th, shortly after releasing ESX3.5 Update5 on December 3rd. Wading through the patch details I stumbled upon some severe issues addressed by the ESX350-200912401-BG patch. I quote some issues that caught my eye: 

  • ESX hosts might get disconnected from VirtualCenter Server. This issue occurs when the ESX hosts are a part of DRS cluster and snapshots and VCB operations are performed on their virtual machines.
    Symptom
    The host agent on ESX hosts might stop responding to VI Client connections, VirtualCenter Server connection and internal or third-party SDK scripts or applications connections.
  • Enabling NTP service through VI Client or VirtualCenter might generate incorrect /etc/ntp.conf and /etc/ntp/step-tickers configuration files, and might cause the NTP service not to synchronize with the NTP Server. After applying this fix, the strings in ntp.conf and the step-tickers files in /etc/ntp/ are updated correctly.
  • Storage vMotion fails with the following error:
    Source detected that destination failed to resume.
    This occurs when performing storage vMotion of a virtual machine having at least two disks, of which one is RDM (located in the same folder as VMX), and the others are normal VMDK files in the destination VMFS volume. Both the RDM pointer and the normal VMDK file should have the same name for this issue to occur. The normal VMDK files are also deleted when storage vMotion fails.
    When the virtual machine is powered on the next time after this failure, the following error is displayed: Cannot open the disk.

Now that are issues that can get you in a really awkward position IMHO. Especially notice the yellow marked line, Ouch!. So take my advice and implement these patches a.s.a.p.

Related posts:

  1. HOW-TO: Recover from failed Storage VMotion Tweet A while ago I received a request from the storage department to move a whole ESX cluster to another storage I/O-Group. This would be a disruptive action. I was...
  2. Geographically dispersed cluster design Tweet Nowadays more and more companies have or are considering a 2nd datacenter in another site. Mostly the main reason for this 2nd datacenter is for disaster recovery purposes. There...
  3. VMware ESX(i) 3.5 Update4 released Tweet VMware has released ESX(i) 3.5 update4. Do not forget to read the release notes here or you can go to the download page here While going through the release notes...
  4. VMware Storage Sudoku Tweet Last Friday I was brainstorming with Gabrie van Zanten about the optimal placement of the VMDKs across our LUNs. We tried to come up with an algorithm that could...
  5. Unattended upgrade of HP management agents Tweet After upgrading to ESX 3.5 to update3, I found out that the HP management agents needed to be upgraded to version 8.1.1, since this version supports ESX3.5 update3. So...

0 Comments on “Critical 2009 last-minute ESX3.5 patches”

Leave a Comment