Kritieke bug in VMWare ESX 3.5 update 2 - NIET UPGRADEN !
Geplaatst: 12 aug 2008, 12:00
Aangezien het aanpassen van de datum tot desastreuze gevolgen kan leiden zou ik volgende workaround toepassen aangezien het probleem zich limiteert tot het starten van de VM's die in stopped of suspended state zijn.VMWARE schreef:An issue has been uncovered with ESX 3.5 Update 2 and ESXi 3.5 Update 2 that causes the product license to expire on August 12. VMware is alerting customers and partners of this issue. VMware regrets the inconvenience caused to customers. Updated product bits with correct licensing will be made available for download as soon as possible.
The work-around: 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.
This seems to affect initial VM power-on (including from suspended state) and VMotion.
Code: Selecteer alles
service ntpd stop
date -s 08/10/2008
vmware-cmd /vmfs/volumes/<pad-naar-vm-storage>/<vmx-bestand-van-je-guest> start
service ntpd start
Grtz,
X-2datop
