.png "vmware esxi 6.7 slow boot issue")
I also had some folks internally reach out to me regarding this issue and provided a workaround.
#VMWARE ESXI 6.7 SLOW BOOT ISSUE PATCH#
At least from the couple of folks I spoke with, it seems like the use of Patch baseline is something they have done for some time and has never given them issues whether it was for a patch or major upgrade release.
I normally would import the ESXi ISO and create an Upgrade baseline. 6.7p03, 7.0p01) and never for major ESXi upgrades. Interestingly, I personally have only used Patch baselines for creating ESXi patches (e.g. Upon reboot, the ESXi host would then hit the error as shown above.
#VMWARE ESXI 6.7 SLOW BOOT ISSUE UPDATE#
It turns out that the upgrade was being initiated from vCenter Server using vSphere Update Manager (VUM) and applying a custom ESXi 7.x Patch baseline to remediate. It was not immediately clear to me on how folks were reaching this state and I had reached out to a few folks in the community to better understand their workflow. UPDATE () - VMware has just published KB 83063 which includes official guidance relating to the issue mentioned in this blog post. A new patch is actively being developed and customers should hold off upgrading until that is made available. UPDATE () - It looks like VMware has just pulled the ESXi online/offline depot and has updated KB 83063 to NOT recommend customers upgrade to ESXi 7.0 Update 2. Please make sure to read over the release notes and do not forget to first upgrade your vCenter Server to the latest 7.0 Update 2a release which came out earlier this week. UPDATE () - VMware has just released ESXi 7.0 Update 2a which resolves this issue and includes other fixes. Upgrading my #VMware #homelab to #vSphere7Update2 is not going so well. I started to notice yesterday that a few folks in the community were running into the following error after upgrading their ESXi hosts to latest 7.0 Update 2 release:
0 kommentar(er)
