VMware just released a bunch of patches for ESX 3.5 and 3.0.x. Those of you who did not yet upgrade to vSphere 4 might want to look in to these new patches as they contain security and critical updates.
Normally I would give you guys a nice overview of the patches + KB articles but I’m on a holiday this week with limited access to wifi. Because I’m typing this on my blackberry this post will lack the details, feel a bit like Rev. Run ;-), but you guys know the drill anyway.
In total 11 new patches (9 for ESX and two for ESXi) are up for download. Make sure to read the accompanied KB articles first and of course test the patches before implementing!
I just noticed this SRM update, it’s just a small patch but looking at the problems it corrects it might be beneficial to upgrade!
Site Recovery Manager 1.0 Update 1 Patch 3 Latest Release Version: 184.108.40.20687 | 04/09/09 | 154949
This patch corrects the following problems:
- a problem that prevents protected virtual machines from following recommended Distributed Resource Scheduler (DRS) settings when recovering to more than one DRS cluster.
- a problem observed at sites that support more than seven ESX hosts. If you refresh inventory mappings when connected to such a site, the display becomes unresponsive for up to ten minutes.
- a problem that could prevent SRM from computing LUN consistency groups correctly when one or more of the LUNs in the consistency group did not host any virtual machines.
- a problem that could cause the client user interface to become unresponsive when creating protection groups with over 300 members several problems that could cause SRM to log an error rmessage vim.fault.AlreadyExists when recomputing datastore groups.
- a problem that could cause SRM to log an Assert Failed: “ok” @ src/san/consistencyGroupValidator.cpp:64 error when two different datastores match a single replicated device returned by the SRA.
- a problem that could cause SRM to remove static iSCSI targets with non-test LUNs during test recovery several problems that degrade the performance of inventory mapping.
VMware ESX 3.5, Patch ESX350-200904201-SG: Updates VMX RPM
Issues fixed in this patch (and their relevant symptoms, if applicable) include:
- A critical vulnerability in the virtual machine display function might allow a guest operating system to run code on the host. The Common Vulnerabilities and Exposures Project (cve.mitre.org) has assigned the name CVE-2009-1244 to this issue.
I’m running OpenSuse as my primary OS at the moment. One of the problems I had was getting VMware Workstation to work in a normal way. The problem was that the kernel modules weren’t compiled correctly. It’s been bugging me ever since, but due to the fact that it’s the end of the quarter I never had the time to actually look in to it. Luckily VMTN user Krellan did have some extra time on his hands and managed to fix the problem, Thanks!!
Fixing your broken installation is fairly easy:
To use this patch, download it from the attachment, gunzip it, then go to your /usr/lib/vmware/modules/source directory. Untar all of the files. Apply the patch with “patch -p1”. After the patch has applied, re-tar all the files. Then, run “vmware-modconfig –console –install-all” again, under Linux 2.6.29, and it should now work.
Go to the VMTN Forums and download the patch if you are having trouble getting the VMware Workstation kernel modules compiled correctly!