Posted by: Raj Perumal
3.5, ESX, ESX 3.5 Update 2, patches, Update 2, VMWare, VMWare bug
Hi folks, breaking news in the virtual world! Apparently ESX 3.5 Update 2 is wreaking havoc with people’s ESX servers. According to reports it is throwing “A general system error occurred: Internal Error”. This is a known problem at VMWare and there is no known fix as of yet.
You can read more about it here.
This goes back to a rule of thumb I always like to follow with patching. When a patch comes out, don’t apply it right away. Sit on it for awhile and adopt a wait and see approach to see if there are any ill effects experienced by others in the industry before you apply to your production systems. Also install the patch in a sandbox environment and do a flurry of tests to see if you can get it to break.
After it seems that the patch is acceptable then you can apply it to your production systems. This will save you a lot of headaches in the long run.