Apr 03
Der fehlerhafte Patch und die daraus folgenden Probleme mit VMTools und VCB sind mit dem aktuellen ESX3.5 U4 release behoben worden.
Apr 01
At the beginning of this month VMware released the Update 4 for its management tier vCenter.
Yesterday the company also pushed the big update for the hypervisor itself.
The new Update 4 (build 153875) is available for both ESX 3.5 and ESXi and includes:
- support for Intel Xeon 5500 series CPUs (codename Nehalem)
- support for Novell SUSE Enterprise Linux 11 (both Server and Desktop, both 32bit and 64bit),
- Ubuntu 8.10 (both Server and Desktop, both 32bit and 64bit), Windows PE 2.0 as guest OSes
- support for new SATA Controllers (from PMC, Intel, CERC and HP)
- support for new NICs (from HP, NetXtreme and Intel, including the just announced ones with VT-c)
- support for new storage arrays (from Sun)
- support for new management agents (from Dell and HP)
- an enhanced VMXNET driver for Windows XP and 2003 (which will require the re-installation of VMware Tools)
Nov 07
This new release of ESX/ESXi 3.5 comes with the following enhancements:
- Increase number of vCPUs per Core Limit (from 8 to 20)
- New supported servers, NICs and storage IO controllers
- New supported Guest Operating Systems
… and many more improvements and bug fixes.
ESX Server 3.5 Update 3 Release Notes
ESXi Server 3.5 Update 3 Installable Release Notes
Okt 13
Am 3.10.2008 erschien das Update 3 für das VirtualCenter 2.5 von WMware
Neben Updates für Converter und Updatemanager wurden vorallem die bekannten Fehler im HA-Agent, Maintenancemode und DRS behoben.
Alle weiteren Updates und Downloads sind auf der VMware Seite zu finden.
Aug 12
Das Update 2 wurde ab sofort zurückgezogen aufgrund eines heute (12.08.2008) aufgetretenen Fehlers. Seit heute können virtuelle Maschinen welche gestoppt/supsend/reset wurden, nicht mehr gestartet werden. Weiter funktioniert VMotion nicht mehr.
Es sind alle ESX 3.5 Update2 Systeme betroffen. Solange keine Tätigketien gemacht werden, laufen die virtuellen Maschinen auf den Hosts weiter.
Ein Patch steht noch nicht zur Verfügung!
Temporärer Workaround:
turn off NTP (if you’re using it), and then manually set the date of all ESX 3.5u2 hosts back to 10th of August. This can be done either through the VI Client (Host -> Configuration -> Time Configuration) or by typing date -s “08/10/2008″ at the Service Console command line on the ESX hosts.
Weitere Details sind aus der KB von VMware zu entnehmen.
KB von VMware 1006716
A virtual machine fails to power on, fails to leave suspend mode, or fails to migrate with VMotion and the following message is displayed in the vmware.log file for the virtual machine:
This product has expired. Be sure that your host machine’s date and time are set correctly.There is a more recent version available at the VMware web site: http://www.vmware.com/info?id=4.
————–
Module License Power on failed.
Currently running virtual machines will continue to run but will not be able to perform migration with VMotion, suspend or power on virtual machines.
An issue with ESX/ESXi 3.5 Update 2 causes the product license to expire on August 12, 2008. VMware engineering has isolated the root cause of this issue and will reissue the various upgrade media including the ESX 3.5 Update 2 ISO, ESXi 3.5 Update 2 ISO, ESX 3.5 Update 2 upgrade tar and zip files by noon, PST on August 13.
These will be available from the page: http://www.vmware.com/download/vi. Until then, VMware advises against upgrading to ESX/ESXi 3.5 Update 2.
Weitere Links mit Informationen:
http://communities.vmware.com/thread/162377?tstart=0
http://www.virtualization.info/2008/08/vmware-mistake-shuts-down-thousands-of.html
http://www.heise.de/newsticker/Vorsicht-Zeitbombe-in-VMware-ESX-3-5–/meldung/114126
