Also in Australia and experiencing the same issue just as you have described. Looking forward to a proper fix from VMware as we have raised a support case as well.
Same happened here.
Except we're unable to change times due to legal obligations. oh well... I'm sure this will be fixed once the US and Europe start calling in too.
Has anyone experienced this problem with a fixed/expiring licence?
Interesting - we run our stuff in GMT, so we should have been hit by this, but we havent....maybe a TZ issue?
> Except we're unable to change times due to legal obligations. oh well... I'm sure this will be fixed once the US and Europe start calling in too.
Tech we spoke to wouldn't commit to a timeframe for a permanent fix, but I'd imagine they'll have to get something out today.
> Has anyone experienced this problem with a fixed/expiring licence?
Yup - our hosts are fully licensed (Enterprise licenses) using a license server (VM, shared with VirtualCenter).
Thanks mate! I just wasted 4 hours at least trying to solve this issue.
This was time right when my RAID failed too. Rebuilt esx and couldnt figure out why it wouldnt start any vm's. Keep us informed if ESX bring a patch out! This is a major problem!
Thanks. I was just about to open a SR on this exact issue.
I can confirm that I've also seen exactly the same behaviour and that disabling NTP and setting the date backwards a week via the client or so did resolve it for the moment.
Time to set a job to keep resetting the date I guess (from external management host) until VMWare can release a fix.
One thing to note is that it seems to stop collection for all the performance monitoring graphs on the VM servers (but actually being able to turn on VMs is more important to me)
getting this already in our AAA region, cant wait for rest of the world to wake up, going to be a fun day.
Yep we got it too luckily not all of the servers in our DRS cluster are upgraded yet, so the powered on ones are OK but nothing new on the "broken U2" servers, doh!
My uneducated guess is that the beta for U2 expired on 12th August...
Don't forget if the answers help, award points
I just ran into the same issue.
/me sighs ?:|
Just got off the phone with tech support and they've been inudated by calls about this very problem. It only affects ESX and ESXi 3.5 Update 2. Setting the time back a day in ESXi should be ok because if memory serves, VMware Tools will only reset time forward and not backwards.
Been bashing my head on this last couple of hours, thought licence issue of some kind.
ESX 3.5 update 2 misbehaving here as described.
Everything was working fine on Friday.
NTP/Date work around working (phew).
Same here, thanks for the workaround.
Dear VMware customers,
We are actively working on rootcausing the problem. Once we know the appropriate action to take here, we’ll provide an update.
Apologies for any inconvenience.
The ESX Product Team