How to update any 6.x VMware ESXi Hypervisor to 7.0 using ESXCLI for easy download and install

Поделиться
HTML-код
  • Опубликовано: 27 окт 2024

Комментарии • 25

  • @jackharvest1
    @jackharvest1 4 года назад +1

    Been following the article for a long time. Thank you so much. :)

    • @TinkerTry
      @TinkerTry  4 года назад

      Great to hear that, and I'm so glad it was still helpful!

    • @jackharvest1
      @jackharvest1 4 года назад

      @@TinkerTry I had so much fun following along to get to 7.0 (which worked perfectly on all my Intel NUC6i7kyk Skull Canyons, that I had to make an article on how to "pimp it out".
      ganon.club/index.php/2020/04/18/how-to-change-the-host-server-icon-in-vsphere-7-0-and-6-7u3/
      Haha, Thanks Again Paul. Forever follower here.

  • @DerpyNoodIe
    @DerpyNoodIe 4 года назад

    I wish you would have gave this link in the description (click on "Read more"), it took me a second to find the exact page you were on in the video. Thank you though for this video, I was able to successfully update my ESXi host! Subbed and liked!
    Here's the link to the page in the video:
    tinkertry.com/easy-update-to-latest-esxi
    Edit: If you are getting the dreaded "enabled/needs reboot" bug with your GPU, I found a work around, at least for my GTX 1660 Super. First I made sure the VM using the GPU is shutdown and then I removed the PCI device for the GPU in the settings for that VM (it might display a blank name for it). Next go to "Manage > Hardware > PCI Devices" and disable the passthrough. It took me a second because there's a weird bug when you select your GPU, it would highlight and tick/untick other devices above and below it. just select your GPU regardless of this bug and spam the "Toggle passthrough" button until it tells you that you have successfully passed a device (for me it said "
    Successfully toggled passthrough for device NVIDIA Corporation TU116 High Definition Audio Controller") and then when you go back to the "Hardware > PCI Devices" section, there you will see your GPU enabled! For me, I did not need to reboot the host, but I got GPU passthrough working! Hope this helps. :)

    • @TinkerTry
      @TinkerTry  4 года назад +1

      Awesome, thank you! I had totally forgotten to have that link in a RUclips card, but now I've added it, thanks to you! As for the GPU thing, see also my workaround video ruclips.net/video/w-Ez4Bqt33s/видео.html (that has no article to go with it just yet). Are you seeing the same exact GPU toggle oddness? Still trying to find the best way to report bugs to VMware...

    • @DerpyNoodIe
      @DerpyNoodIe 4 года назад

      Paul Braren Sweet! And alright. Yeah I’m gonna have to check it out because the GPU passthrough was working for a few hours and then my host machine crashed and became unresponsive. So I had to reboot, only to find out that the passthrough for my 1660 super was disabled again. :/ thanks for the heads up! :)

  • @Vaikis2006
    @Vaikis2006 4 года назад +1

    Tried on supermicro x11ssm build, all went fine.... But after reboot couldn't see samsung 970 as local storage (esxi boots from same drive)... One more reboot and all back to 6.7u3...(it reverted back automatically)

    • @TinkerTry
      @TinkerTry  4 года назад

      That is odd, the first I’ve heard of a spontaneous revert, thank you for letting me know! Is your system on VMware’s HCL? Curious, are you able to back up ESXi before trying again to reduce risk/pain? TinkerTry.com/clone-esxi-with-usb-image-tool Do you have VCSA 7 installed, to try Update Manager instead?

    • @Vaikis2006
      @Vaikis2006 4 года назад +1

      All compatible within HCL. Just tried different approach today as its my home lab server, mounted ISO and upgraded in such way :) No any problems.

    • @TinkerTry
      @TinkerTry  4 года назад

      Strange, but glad it worked out!

  • @VirtualTechBox
    @VirtualTechBox 4 года назад

    Command "esxcli software sources profile list -d hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml" giving me below output.
    [VibFormatError]
    Could not parse VIB XML data: None.
    Please refer to the log file for more details.

  • @VirtualTechBox
    @VirtualTechBox 4 года назад

    If I run same command with proxy I am getting below output.
    [MetadataDownloadError]
    Could not download from depot at hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml, skipping (('hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml', '', ''))
    url = hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
    Please refer to the log file for more details.
    Note: I am able to ping google.com.Any guess what could be the issue.

    • @TinkerTry
      @TinkerTry  4 года назад +1

      Such errors are usually some sort of dns failure, what happens if you SSH to the ESXi host, then type
      nslookup hostupdate.vmware.com

    • @VirtualTechBox
      @VirtualTechBox 4 года назад

      @@TinkerTry Above issue resolved after doing this--Host--Manage--System--swap--datastore1 instead of none.
      Now I am trying to upgrade with command "esxcli software profile update -d hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml -p ESXi-7.0.0-15843807-standard" . But getting below output,
      Got no data from process: LANG=en_US.UTF-8 /usr/lib/vmware/esxcli-software profile.update -d "hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml" -p "ESXi-7.0.0-15843807-standard"
      I am getting below output of nslookup hostupdate.vmware.com,
      [root@localhost:~] nslookup hostupdate.vmware.com
      Server: 8.8.8.8
      Address: 8.8.8.8:53
      Non-authoritative answer:
      hostupdate.vmware.com canonical name = esd751.vmware.com.ds.edgekey.net
      esd751.vmware.com.ds.edgekey.net canonical name = e751.dscd.akamaiedge.net
      Name: e751.dscd.akamaiedge.net
      Address: 92.122.196.69
      Non-authoritative answer:
      hostupdate.vmware.com canonical name = esd751.vmware.com.ds.edgekey.net
      esd751.vmware.com.ds.edgekey.net canonical name = e751.dscd.akamaiedge.net
      Name: e751.dscd.akamaiedge.net
      Address: 2600:140f:5:886::2ef
      Name: e751.dscd.akamaiedge.net
      Address: 2600:140f:5:89a::2ef

  • @237311
    @237311 4 года назад

    It throws me some error message. How can I fix this error?
    [root@esxi6:~] esxcli software profile update -p ESXi-7.0.0-15843807-standard -d hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.x
    ml
    [InstallationError]
    ('VMW_bootbank_nhpsa_2.0.50-1vmw.700.1.0.15843807', 'Could not find a trusted signer.')
    vibs = VMW_bootbank_nhpsa_2.0.50-1vmw.700.1.0.15843807
    Please refer to the log file for more details.
    [root@esxi6:~]

  • @dudanken
    @dudanken 4 года назад

    Hi, i would like update my lab cluster, but it seems that esxi 7.0 don't like mellanox 10Gbit adapter, but in the hcl it seems that the card are compatible with esxi 7.0.
    Any hints?
    Many thanks

    • @TinkerTry
      @TinkerTry  4 года назад

      I don’t have any Mellanox gear in my home lab, so I can only generally give guidance that you’ll want to be sure the firmware that the VMware Hardware Compatibility Guide has for your exact card needs to be matched with the exact recommended driver VIB. My article may help a little too: TinkerTry.com/how-to-check-which-network-driver-your-esxi-server-is-currently-using

    • @dudanken
      @dudanken 4 года назад

      @@TinkerTry Thank you very much for fast answer

  • @LumpiDeluxe
    @LumpiDeluxe 4 года назад

    Do licences keys for 6.x work with 7.0?

    • @Vaikis2006
      @Vaikis2006 4 года назад

      Nope, you need to upgrade them

    • @TinkerTry
      @TinkerTry  4 года назад

      Thank you Vaikis2006 for answering RT 76, really appreciate it, as I was heads-down doing lab test for my many new articles about vSphere 7.

  • @JensHove
    @JensHove 4 года назад

    They should have released it on April 1st :-)

  • @cryptmind4202
    @cryptmind4202 4 года назад

    Just be careful if/when upgrading vCenter before hand, if you have it. Not all vCenter v6.5 have an upgrade path to 6.7. kb.vmware.com/s/article/67077

    • @TinkerTry
      @TinkerTry  4 года назад +1

      Good point, thank you!