You COULD simply SSH into the host, and execute the following commands; esxcli network firewall ruleset set -e true -r http Client esxcli software profile install -p ESXi-6.5.0-20170702001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/Well that’s great but if you are using a custom ESXi image, the process won’t even start, you simply get warned that this won’t work as it will break all the vendor specific drivers/software, (which is a good thing I suppose!) Still, if you have a vendor modified copy of ESX what do you do?That being the case, it seemed fitting to go through the patch process for the affected i LO driver in this post.Despite this being a very specific patch, the general patch procedure can be applied to other driver updates as well.
VMware ESXi 6.5 host fails with a Purple Screen Diagnostic, indicating that CPU XX / World XXXXXX tried to re-acquire a lock.
Our next step will be to attach the baseline to the cluster. With your cluster or host selected, choose Attach Baseline. To verify the compliance of your Patch Baseline, select Scan for Updates. Lastly, specify the Cluster Options for the remediation.
When complete, the summary will show the applicable missing patches. For hosts in a cluster, the remediation process will run sequentially by default.
Fortunately this isn’t really a problem and is very easy to fix. During a v Center Upgrade the VMware HA Agent on all of the ESXi hosts will be updated.
After this happens the “require reboot” flag is set on the hosts, as explained in VMware KB 2034945.