Timebomb in VMware patch
Heise.de reports about a timebomb in the Update 2. The system denies the migration, creation and suspension of virtual machines with the message that the product has expired. That matches my opinion about VMware with all this big vendors introducing virtualisation solutions, but that´s a different story ;) Well, Heise writes that the suggest workaround ist to set a date in the past and to disable the time synchronisation. But as virtual clocks are just a rough guess of the actual time, this doesn´t look as a viable workaround for me. BTW: They have annother problem. The support website seems to suffer the slashdot effect started by the link on the heise website.