VMware ESXi 5.0 Update 1 breaks AutoStartManager (free license ONLY, awaiting patch/fix)

[EirikTF]

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!

[steve_quinn]

Hey everybody

I've been watching this thread like a hawk as I really miss this feature.

I did a quick test with Ernst's vmware-autostart.sh under the latest ESXi 5 patch. (Build Number: 721882)

Ernst, Mello, Gijsbert, whomever I may have missed ... A great big thank you !!

I'll be putting this into production tomorrow and will share any findings

Thanks again

Take care

Steve

[gwiesenekker]

I am not sure why my procedure breaks your boot, I have tested it on three ESXi servers.

Is there any error shown in the console or the log? I have attached my modified files for reference.

Regards,

Gijsbert

[Gleed]

Good news!  The Auto Start fix is finally here.  VMware released a new ESXi patch (ESXi500-201207001) this evening (7/12/2012) that includes the fix to the Auto Start problem affecting vSphere Hypervisor.

You can get the patch here:

http://www.vmware.com/patchmgr/findPatch.portal

For information about the patch:

http://kb.vmware.com/kb/2019107

[prinz3noll3]

Hi,

and thanks gleed.

2 questions:

- Where can i find the information thats fixed in the KB?

- How can i apply the patch?

Thanks a lot

[Gleed]

This blog should answer your questions:

http://blogs.vmware.com/vsphere/2012/07/vsphere-hypervisor-auto-start-bug-fixed.html

[gernst]

I have no idea why it is wrong.

ESXi shows at the very beginning (first message) of boot :

/shudown.tgz not found

Fatal error

Thats all, I have to repair the installation.

Ernst

[gwiesenekker]

So it could be a typo? shudown instead of shutdown in bootmgr.cfg? Also make sure the shutdown.tgz resides in /bootbank.

Regards,

Gijsbert

[gernst]

May I am blind, but I have checked this so often.

Everything was right for me, but it was not working for me.

This was the reason why I looked for an simpler version.

As you could see in my post I found a much simpler version.

Ernst

[venkyVM]

Hi All ,

Please install the patch ESXi500-201207001  from VMware Download site http://www.vmware.com/patchmgr/findPatch.portal . This patch contains the fix from VMware for the AutoStartManager issue reported here and was released yesterday.

Patch Link : https://hostupdate.vmware.com/software/VUM/OFFLINE/release-346-20120706-638484/ESXi500-201207001.zip

Thanks

[gernst]

Already done, thanks a lot, is really working. Great !

Ernst

[Datarad]

You might want to be a bit cautious when applying the ESXi500-201207001 patch. Just installed it on a HP Proliant DL380 gen8 (running HP's ESX 5 u1 image) and after the required reboot it can't find any compatible network adapters.

[Gideon1000]

i've been having this issue and thankfully it was resolved.
But I've found that my autoshutdown script not working. I'm using vcli from inside Windows VM to automatically shutdown host wen UPS battery runs out. Before update 1, command:
[vicfg-hostops.pl --operation shutdown --force --server XX.XX.XX.XX --username XXXX --password YYYYY]
was working fine, but now i get error:

SOAP Fault:
-----------
Fault string: fault.RestrictedVersion.summary
Fault detail: RestrictedVersionFault

Is this a BUG or vMware fixed a previous "BUG" with licensing ?

[dennis_w]

Hi there,
there is a Rollup Pack 2 available on the vmware site. Download ist, burn a cd, boot it, select the esxi partition an update it fron 5.0 to 5.0. After that the vm's will boot automaticaly.

cu dennis

[prinz3noll3]

hi,

where can i find the download?

the only update i found is the Driver Rollup Pack 2 or VMware ESXi 5.0 Update 1 Installable.

thx

[a_p_]

Please see Re: VMware ESXi 5.0 Update 1 breaks AutoStartManager (free license ONLY, awaiting patch/fix but remember that you may (depending on your current build) have to apply other patches before this one! See the Release Notes of the different patches for details.

André

[dennis_w]

it is called:

Vsphere 5.0 Rollup ISO images View details

Build Number:563984

Version:2.0

Type:Drivers & Tools

Product Family: VMware vSphere Hypervisor (ESXi)  5.0 View family

End User License Agreement: Not applicable

Files	Information
VMWARE-ESXi-5.0.0-Rollup-20111216.iso 298 Mb | Release Date 2012-02-08 Show Checksums	vSphere Hypervisor ESXi 5.0 Driver Rollup 2	Download Manager Manually Download

[wcrad]

The number of bad posts and people providing bad information in this thread, while it's apparent they have absolutely _no_ clue, is astounding. The fact that VMware themselves have not stepped in to clear up the confusion and provide a difinitive answer as to the status of this bug and its fix is even more over the top. I have no choice but to categorize this as a huge failure on VMware's part. I am thoroughly disgusted.

[RSW-Orga]

Hi wcrad,

have you read this whole thread?

Even http://communities.vmware.com/message/2076695#2076695 ?

Or http://blogs.vmware.com/vsphere/2012/07/vsphere-hypervisor-auto-start-bug-fixed.html ?

I think someone should close this thread ...

[peetz]

As stated before the problem originally described in this thread (VM Autostart Manager broken in the free version of ESXi 5.0) was fixed with the release of patch ESXi500-201207001" on July 12, 2012 (see http://communities.vmware.com/message/2076695#2076695)

I will lock this thread now to avoid any more misleading comments.

- Andreas