Hi,
Today I updated from build 515841 to 623860, the update reportedly was successful.
However, I've noticed something very annoying - the host no longer automatically starts or shutdowns guests as configured. I've tried to turn the feature on and off, moved guests to "Manual Startup" then back to "Automatic Startup" - with various combinations of these settings, also rebooted host in between changes. But alas, no luck. :smileyplain:
In the "Recent Tasks" list in vSphere Client, the Auto Power On tasks shows up as completed, initiated by root, with "Start Time" and "Completed Time" having the same timestamp. The server log reports the following error (3rd line below):
2012-03-16T07:08:27.296Z [6DE40B90 info 'TaskManager'] Task Created : haTask--vim.host.AutoStartManager.autoPowerOn-97171136
2012-03-16T07:08:27.297Z [6DE40B90 verbose 'Hostsvc::AutoStartManager'] Powering on VM 5 with delay 120
2012-03-16T07:08:27.333Z [6DE40B90 error 'Hostsvc::AutoStartManager'] Error in initializing PowerOp for VM 5 : vim.fault.RestrictedVersion
2012-03-16T07:08:27.334Z [6DE40B90 info 'TaskManager'] Task Completed : haTask--vim.host.AutoStartManager.autoPowerOn-97171136 Status success
RestrictedVersion? Did something happen to licensing features for free ESXi? :smileyconfused:
Anyone else with the same problem/a solution?
Thanks in advance!
Yes, it's a bug. It only affects folks running the free hypervisor. Not aware of a fix/workaround yet...
Ahhh crap
I`m in the same boat. Just updated 2 servers rebooted went to coffe and got many calls lol
Same error, same log entries...
Someone can explain why?
Hi jlamp,
It seems licencse file got corupted .
could you please re-enter the key and activate it again .
I did that in a first place...
Did not help...
Anyone else having this unpleasant issue?
Waz up with this AutoStartManager and updates....?
Looks like the same thing that happend in ESXi 3.5 Update 1 back then... http://communities.vmware.com/message/982402
/Rubeck
Me too...
Thanks, Rubeck - this is useful info. History repeats itself...
I've been fighting this problem since last night, so I'm at least happy to see that I'm not the only one. The problem appeared after I upgraded my existing ESX 5.0 to Update 1. I verified that I was not in lockdown mode. I tried removing all my VMs from the inventory and re-adding them. I even tried wiping out my ESX installation, reinstalling, and relicensing as opposed to upgrading. I can't seem to fix it.
Also, I'm not sure if this other problem is related (I think it also existed before the update), but when I click Configuration - Virtual Machine Startup/Shutdown - Properties, then click OK, I immediately get duplicates in my Startup Order list. If I click on another page and then come back, everything looks normal though, so maybe it doesn't matter.
This update did fix a problem I was having where a Windows 2000 server wouldn't power down. But with no automatic startup, this update is worthless IMO. I guess I'm gonna have to reinstall the previous version. Not too impressive for an enterprise grade product.
sundayhustler wrote:
Also, I'm not sure if this other problem is related (I think it also existed before the update), but when I click Configuration - Virtual Machine Startup/Shutdown - Properties, then click OK, I immediately get duplicates in my Startup Order list. If I click on another page and then come back, everything looks normal though, so maybe it doesn't matter.
I've seen this too, both BEFORE and AFTER Update 1, getting three entries for each VM - think it's just cosmetic, but cannot know for sure. Either way, at least AutoStart worked before U1 when this "issue" was there... :smileyplain:
hi:
I got the same problem. I hope I can get some "known issues" notice before update. but it is too late now...
Hello same Problem here.
on 17. one Day after the Update release date
i installed it. No Autostart at all.
Funny Saturday ......
Back to the previous Version all works fine.
I tried some things.
New install with original installer CD -> direkt Update to update 1 -> same behavior.
So i get back to last Revision which works.
If everyony know´s an answere. it would be nice to know.
This Might Only effect hosts with the Free Hypervisor license assigned
Hi
I also have the same problem ...
Someone has a solution to this "embarrassing" :smileycry: issue ?
I've installed this update on hosts that are licensed (essentials) and autostart still works fine
Hopefully it's not a new licensing restriction.
Hello everybody,
venkyVM is right, it depends on the license. Last weekend I ran into the same problem. After reading the posts on this
site I installed - for testing - one of our company licenses and - voilá - problem disappeared!
Don't know, what VMware is doing. Don't they test patches and updates before releasing them? IMHO - it is a basic and
not a very special feature to autostart VMs, so this should work, even with the free license...
martinelli
Hi all!
I went trough release notes and there is no evidence that VmWare would restrict this feature in free version.
Its a bug 100%!
Yes, it's a bug. It only affects folks running the free hypervisor. Not aware of a fix/workaround yet...
Hi,
Thanks to all who chipped in and to VMware for responding to this issue. Hopefully a patch/fix will be available soon.....
I have the same trouble and mailed with support.
Last Info from Support:
"As per the previous email, the latest version of ESXi 5.0 hypervisor update 1 do not have auto starting feature, this is because the product ESXi hypervisor is free product, it will not have all the feature.
If you have any technical issue, you can log on to VMware communities or with the VMware knowledge base : http://kb.vmware.com/"
That's a bad joke !
Seriously?
Oh well there is always XEN or Microsoft for us home users