cacharo wrote: That was posted last night? I have not heard the world explode yet... I have plenty of ESX customers and not one call.
tiersten wrote: I'm surprised the VMware for releasing something with such a major flaw. Their temporary "fix" is to roll back your clock to the 10th. Not too great if you actually want a correct timestamp for anything... Kinda slow as well on releasing a patch as well. Not very enterprisey is it if you've gotta wait a day for an urgent fix... Thankfully I've not upgraded to 3.5u2
astorrs wrote: Yeah the community is pissed. And they've done this kind of thing before, heck they even screwed up when they released update 1... Would love to see some stock movement to "encourage" better testing in the future.
astorrs wrote: Yeah so that means VMotion doesn't work... And god help anyone who has automatic updates enabled (it's Tuesday) or who is using/testing DPM.
HeroPsycho wrote: Actually, VM restarts should be fine. It's "powering on" VM's that would be the problem.
astorrs wrote: I hate these LOL cat things too, but had to pass this along: http://vmprofessional.com/2008/08/esx-lolcat.html
tiersten wrote: Another undocumented "feature" that VMware added to 3.5u2 is that all the nodes in your HA cluster must have the service consoles used for the heartbeat on the same network. It didn't used to be like this but they did a stealth change in 3.5u2 which enforced it. VMware forum link
