Can you store the depot files on the same datastore as virtual machine directories? Will the datastores come back after upgrade? Does your virtual machines come back? I have 6.5, does this still work the same way as with your example and 6.7? Thank you
Thanks Ashfaq for sharing the video! I may want to check about upgrade ESXi from 6.7 to 8.x, since 8.0 will ask much more disk space for system (100G+?), will this method of upgrade get 8.x so much allocation after that? I think there’s way to modify the vol size when new install the system, not sure if upgrade mode can also do that?
The compatibility guide confirms HP Proliant DL360 Gen10. Would it work also on a DL360 Gen9 machine. In the past it worked for me. Or shall I just try?
If i am on vsphere 6.7 all esi host and windows based vcenter. Shall we upgarde all esxi host 1st and redeploy vcenter 8.0 instead of upgrade? Bcoz after 6.7 no windows based vcenter available
my current esxi 6.7 instances are installed on SD cards but I think version 8 requires actual SSD/HDD. How would I target the existing SSDs in the hosts with that command?
VMware Cust Support gave me this to add on the end of my script: --no-hardware-warning --no-sig-check. It was supposed to bypass the VIBs errors; but failed.
The profile is the path of the offline bundle saved in the datastore of ESXi and the image profile is the profile to which you want to upgrade your ESXi to.
@@VirtualTechBox I was able to get the server back. No harm done. I now will follow your video instructions. The only difference I see is that you passed a zip file in the command line. What I have is an ISO file, would this command work if I specify the iso file instead of the zip. Please advise. Thank you!
@@VirtualTechBox I got errors with the command line provided...here they are [DependencyError] VIB QLC_bootbank_qedf_1.3.22.0-1OEM.600.0.0.2768847 requires qedentv_ver = X.10.23.0, but the requirement cannot be satisfied within the ImageProfile. VIB QLC_bootbank_qfle3f_1.0.63.0-1OEM.670.0.0.8169922 requires vmkapi_2_2_0_0, but the requirement cannot be satisfied within the ImageProfile. VIB QLC_bootbank_qedf_1.3.22.0-1OEM.600.0.0.2768847 requires vmkapi_2_2_0_0, but the requirement cannot be satisfied within the ImageProfile. VIB QLC_bootbank_qedf_1.3.22.0-1OEM.600.0.0.2768847 requires vmkapi_2_3_0_0, but the requirement cannot be satisfied within the ImageProfile. VIB QLC_bootbank_qedi_2.10.5.3-1OEM.670.0.0.8169922 requires qedentv_ver = X.10.23.0, but the requirement cannot be satisfied within the ImageProfile. VIB HPE_bootbank_scsi-hpdsa_5.5.0.66-1OEM.550.0.0.1331820 requires vmkapi_2_2_0_0, but the requirement cannot be satisfied within the ImageProfile. VIB QLC_bootbank_qedi_2.10.5.3-1OEM.670.0.0.8169922 requires vmkapi_2_2_0_0, but the requirement cannot be satisfied within the ImageProfile. VIB HPE_bootbank_scsi-hpdsa_5.5.0.66-1OEM.550.0.0.1331820 requires com.vmware.driverAPI-9.2.2.0, but the requirement cannot be satisfied within the ImageProfile. Please refer to the log file for more details. I could try using the ISO installation method and see if I have better luck. My host currently has ESXi 6.7. Please point me to the right video for this ISO method. Thank you in advance!
You can enter boot options by pressing Shift+O in the boot loader. Refer -- docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.upgrade.doc/GUID-A33C4CAB-18EE-4C8C-A55D-8AD7E8042BFA.html
Thanks ashfaq for your all videos
You're Welcome.
Thank you very much for share with us this content. It'll be very useful to me in my next implantation! Congrats here from Brazil!
Glad it was helpful!
Thanks ashfaque for making the video - the upgrade went very well.
Glad it was helpful.
Thanks for your videos!
My pleasure!
Can you store the depot files on the same datastore as virtual machine directories? Will the datastores come back after upgrade? Does your virtual machines come back? I have 6.5, does this still work the same way as with your example and 6.7? Thank you
Yes you can. Datastore will definitely come back after upgrade. 6.5 cannot be directly upgraded to 8.
Thanks ashfaq great job.
You're Welcome.
Great video. Thank you.
Thanks Ashfaq for sharing the video! I may want to check about upgrade ESXi from 6.7 to 8.x, since 8.0 will ask much more disk space for system (100G+?), will this method of upgrade get 8.x so much allocation after that? I think there’s way to modify the vol size when new install the system, not sure if upgrade mode can also do that?
It will not affect size of datastore and it will not occupy more space.
@ Thanks a lot for the sharing!
The compatibility guide confirms HP Proliant DL360 Gen10. Would it work also on a DL360 Gen9 machine. In the past it worked for me. Or shall I just try?
It should work but verify once with HP support before proceeding if its a production environment.
Do you change the swap setting back when finished? Are there any positives or negatives leaving set?
swap setting were changed for this upgradation process only. Once upgrade completed, you can revert back the swap settings.
Que buena explicacion
Thank you. If you are importing existing VMs, will it be affected by the new version? I heard if we import the old VMs on 6.7 they won't work on 8.0.
VM will work fine, you only need to upgrade the vmware tool.
@@VirtualTechBox how do you upgrade the tool? That's found on broadcom?
@@jamaalrobinson5036 Yes, once complete migration is completed to Broadcom you can download in-guest vmware tool & install.
If i am on vsphere 6.7 all esi host and windows based vcenter. Shall we upgarde all esxi host 1st and redeploy vcenter 8.0 instead of upgrade? Bcoz after 6.7 no windows based vcenter available
There are methods to upgrade windows based vCenter directly to 8. But first upgrade vcenter to 8 or install new vcenter 8 then upgrade esxi.
my current esxi 6.7 instances are installed on SD cards but I think version 8 requires actual SSD/HDD. How would I target the existing SSDs in the hosts with that command?
Yes version 8 requires HDD, U never tried to upgrade esxi which is on SD card.
@@VirtualTechBox No, I have never upgraded a hypervisor before.
Unfortunately I have never upgraded any esxi which is running on SD card@@gregchin6456
I followed your instructions to the T and I cannot get a successful installation screen still.
What error are you getting and at which step?
@@VirtualTechBox Getting 3 VIB SHA-256 errors.
VMware Cust Support gave me this to add on the end of my script: --no-hardware-warning --no-sig-check. It was supposed to bypass the VIBs errors; but failed.
@@VirtualTechBox I asked VMware could the VIBs be upgraded or removed and they didn't recommend it. Instead they stated I had to go to 7.0 vice 8.0.
@@nicholasstarks8074 Hope you have downloaded a compatible version of VIB.
My environment does not have access to the internet, it is required to have one in order to upgrade the system?
Internet is only required to download the offline bundle. Once you have offline bundle, you can proceed without internet.
Can you explain the entire command like why we used profile command and image profile
The profile is the path of the offline bundle saved in the datastore of ESXi and the image profile is the profile to which you want to upgrade your ESXi to.
Could you please help me? I tried to upgrade from 6.7 to 8.0 via the UI and now I have no access to the host via the web browser. How can I fix it?
Are you able to get username/password page while browsing the host IP?
@@VirtualTechBox I was able to get the server back. No harm done. I now will follow your video instructions. The only difference I see is that you passed a zip file in the command line. What I have is an ISO file, would this command work if I specify the iso file instead of the zip.
Please advise.
Thank you!
Upgrade method for ISO is different which is also available on my channel. For this method kindly download zip file@@mcastellanosjr
@@VirtualTechBox I got errors with the command line provided...here they are
[DependencyError]
VIB QLC_bootbank_qedf_1.3.22.0-1OEM.600.0.0.2768847 requires qedentv_ver = X.10.23.0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qfle3f_1.0.63.0-1OEM.670.0.0.8169922 requires vmkapi_2_2_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qedf_1.3.22.0-1OEM.600.0.0.2768847 requires vmkapi_2_2_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qedf_1.3.22.0-1OEM.600.0.0.2768847 requires vmkapi_2_3_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qedi_2.10.5.3-1OEM.670.0.0.8169922 requires qedentv_ver = X.10.23.0, but the requirement cannot be satisfied within the ImageProfile.
VIB HPE_bootbank_scsi-hpdsa_5.5.0.66-1OEM.550.0.0.1331820 requires vmkapi_2_2_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLC_bootbank_qedi_2.10.5.3-1OEM.670.0.0.8169922 requires vmkapi_2_2_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB HPE_bootbank_scsi-hpdsa_5.5.0.66-1OEM.550.0.0.1331820 requires com.vmware.driverAPI-9.2.2.0, but the requirement cannot be satisfied within the ImageProfile.
Please refer to the log file for more details.
I could try using the ISO installation method and see if I have better luck. My host currently has ESXi 6.7. Please point me to the right video for this ISO method. Thank you in advance!
4:00 Why is it required to enable swap?
The offline bundle is in zip format, to extract it swap is required.
May I know your lab configurations?
I have installed Windows Server 2019 on HP Proliant ML 30 Gen 10 and On Windows server 2019 I have VMware Workstation.
Why do you need to make the storage swap?
Actually to unzip the offline bundle we need to enable swap. If you don't enable the swap, it will through an error.
i get message no image profile with the name
How so i get to the boot.cfg on cli?
You can enter boot options by pressing Shift+O in the boot loader.
Refer -- docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.upgrade.doc/GUID-A33C4CAB-18EE-4C8C-A55D-8AD7E8042BFA.html
I am getting an error modulenotfound error
Seems to be hardware compatibility issue. Verify the hardware compatibility before upgrading.