Numerous vulnerabilities in VMware products

JDMurray

Something to be aware of: http://www.h-online.com/security/news/item/Numerous-vulnerabilities-in-VMware-products-867427.html

And for your convenience:

VMware vCenter Server 4 Update 1, build 208156
Release Date 2009/11/19
http://downloads.vmware.com/download/download.do?downloadGroup=VC40U1

ESXi 4.0 Update 1
https://hostupdate.vmware.com/software/VUM/OFFLINE/release-155-20091116-013169/ESXi-4.0.0-update01.zip
http://kb.vmware.com/kb/1014886

ESX 4.0 Update 1
https://hostupdate.vmware.com/software/VUM/OFFLINE/release-158-20091118-187517/ESX-4.0.0-update01.zip md5sum:
http://kb.vmware.com/kb/1014842

RTmarc

The updates for ESX and ESXi were pushed out through Update Manager this week. Took all of 5 minutes to install.

blargoe

Patched mine too. Update 1 has the added bonus of supporting vCenter client on Windows 7 and officially supporting 2008 R2 VM's.

RTmarc

blargoe wrote: »

Patched mine too. Update 1 has the added bonus of supporting vCenter client on Windows 7 and officially supporting 2008 R2 VM's.

I'm just as guilty of jumping on the pro-VMware bandwagon as the next guy but the fact it took months to get the client working on Windows 7 without having to make changes to the configuration file and environmental variables is ridiculous. I'm glad to see this resolved.

astorrs

Hold off on installing ESX 4.0 U1, it just got pulled a few minutes ago because of this: VMware Self-Service- Upgrading ESX 4.0 to 4.0 U1 using Update Manager fails or times out and rebooting the host results in a purple diagnostic screen

PSOD's suck.

More info from Rick Blythe:
http://www.vmwarewolf.com/upgrading-esx-4-0-to-update-1-using-update-manager/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+vmwarewolf+%28VMwarewolf%29

JDMurray

So the problem occurs only when using UpdateManager to apply U1. Those of us who are still managing ESXi manually won't PSOD over this.

astorrs

JDMurray wrote: »

So the problem occurs only when using UpdateManager to apply U1. Those of us who are still managing ESXi manually won't PSOD over this.

ESXi wouldn't have the issue since it doesn't have a service console to install 3rd party management agents in so you'd be fine their either way.

RTmarc

We have three ESX hosts in our environment. So far, this has not been an issue for any of them.

JDMurray

Yeah, the problem is with UpdateManager and not with U1 itself. *whew!*

blargoe

Good thing my servers are Dell and not HP. I was running the latest OpenManage client on all my ESX servers and didn't get any PSOD's.

PSOD's suck very much. My VMWare instructor said I'd probably never see a PSOD, I've already seen 2 this year.