Hello All,
VMware has described this bug in details as refer to this link: http://blogs.vmware.com/vsphere/2012/07/clarification-on-the-auto-start-issues-in-vsphere-51-update-1.html.
1. As for me, I will need to download the patch for ESXi 5.0.0. Go to this page: http://www.vmware.com/patchmgr/findPatch.portal and login into your VMware account. Search with following criteria in that page:
“ESXI (Embedded and Installable)” “5.0.0” “release date” “All categories” “All Serverities”
Download the patch and install it
Enable SSH. Go to vSphere Client > ESXi host > Configuration > Security Profile > Services > Properties and make sure SSH is enable.
Go to vSphere Client > ESXi host > Configuration > right click storage > Browse Datastore. Create a new folder called ‘update’ inside the datastore and upload the patch.
Login into the ESXi server using SSH. Run following command to verify the image profiles:
$ esxcli software sources profile list --depot=[datastore1]/update/ESXi500-201207001.zip Name Vendor Acceptance Level -------------------------------- ------------ ---------------- ESXi-5.0.0-20120701001s-standard VMware, Inc. PartnerSupported ESXi-5.0.0-20120704001-no-tools VMware, Inc. PartnerSupported ESXi-5.0.0-20120701001s-no-tools VMware, Inc. PartnerSupported ESXi-5.0.0-20120704001-standard VMware, Inc. PartnerSupported Put the host into maintenance mode. Go to vSphere client > right click to the ESXi node > Enter Maintenance Mode > Yes.
Start the update process by running following command. We will use profile ESXi-5.0.0-20120701001s-standard for this update:
esxcli software profile update --depot=[datastore1]/update/ESXi500-201207001.zip --profile=ESXi-5.0.0-20120701001s-standard Reboot the ESXi node using command line or using vSphere client. Once up, exit the maintenance mode and you can verify whether it is fixed by enabling Virtual Machine Startup/Shutdown options under vSphere client > ESXi node > Configuration > Software > Virtual Machine Startup/Shutdown > Properties and enable the VM auto start. Start the VM now. Regards,
