Important Update - On Mar 20 2018, VMware VMSA-2018-0004.3 announced that CVE-2017-5715 (Spectre-2) mitigation is now included in the latest patch that you should be using instead of the older patch featured in the original article below. You'll find the newer article that features an even easier update method here:
- How to easily update your VMware Hypervisor from 6.x to 6.5 Update 1 Patch Release ESXi650-201803001 (ESXi Build 7967591) with Spectre mitigation
Article below as it originally appeared.
It's that time of year when some IT Pros are lucky enough to have a few days off to spend upgrading their home labs. This VMware update arrives just in time for the holidays, and this article gets us ready to start 2018 off right, featuring an easy upgrade method that works even for the free hypervisor that has no connection to a VCSA. Of course, it's a lot more fun to have VCSA in your home lab, and doing so beyond the 60 day trial has gotten a whole lot more affordable.
Below, you'll find both the detailed Step-By-Step Instructions and the walk-thru Video, but you should really read the whole article first, including a way to backup your ESXi media before you begin described in the Prerequisites section, and a way to roll-back easily if things don't go right, see Reverting to a previous version of ESXi (1033604).
Once you've performed this patch and rebooted, various UIs will show your ESXi version, depending upon where you look:
6.5.0 Update 1 (Build 7388607)
Version: 6.5.0 Update 1 (Build 7388607)
(Updated) ESXi-6.5.0-20171204001-standard (VMware, Inc.)
6.5.0 #1 SMP Release build-7388607 Dec 18 2017 03:01:41 x86_64 x86_64 x86_64 ESXi
If you'd like to see how to use VMware Update Manager (VUM) instead, it's all detailed here, requiring an active my.vmware.com account and a some more download/upload steps, a better way to go once you've already made it to a 6.5.x release.
You may be interested in the new NVMe inbox (included) driver that just arrived in this 6.5 Path 02, it's named:
Read both of these KB articles for details on what this Express Patch fixes:
- VMware ESXi 6.5, Patch Release ESXi650-201712001 (2151102)
Release Date: December 19, 2017
See also details about the original 6.5 Update 1 Release below.
- vCenter/VCSA 6.5 should be upgraded to 6.5 Update 1d before upgrading your host(s) to ESXi 6.5 Patch 02 Build 7388607, see:
How to easily update your VMware vCenter Server Appliance from 6.5.x to 6.5 Update 1d (VCSA 6.5 U1d)
Jul 28 2017
- I have only tested this method when upgrading from 6.5.0 U1 EP4 Build 5969303 to Build 7388607, your experience from earlier 6.x versions may vary.
- I have been able to replicate that the Xeon D 10GbE X552/X557 driver VIB needs to be re-installed right after the upgrade.
- This is not official VMware documentation, it's merely a convenient upgrade technique that may help in lab tests, a little simpler than the official procedure VMware documents and demonstrates in KB2008939. It's up to you to adhere to the backup-first advice detailed below, full Disclaimer found at below-left, at the bottom of very TinkerTry page.
- See also the Drawbacks section below.
All the background story on how this easy ESXCLI upgrade method came about was covered in my earlier articles about updating 6.0 U2 and 6.5.
If you're in production, beware, this code just came out just 3 days ago. This article is for the lab, where you may want to give this critical patch a try.
- No new license needed to go from 6.0.x or 6.5.x to 6.5 U1 Build 6765664
- Users of the free hypervisor and folks who can't download the GA Offline bundle now have a path forward as well, without needing to read TinkerTry's My VMware's "You either are not entitled or do not have permissions to download this product." error, and what to do about it.
- See also Differences Between vSphere Upgrades and Updates and Upgrade or Update a Host with Image Profiles:
esxcli software profile updatecommand brings the entire contents of the ESXi host image to the same level as the corresponding upgrade method using an ISO installer. However, the ISO installer performs a pre-upgrade check for potential problems, and the
esxcliupgrade method does not. The ISO installer checks the host to make sure that it has sufficient memory for the upgrade, and does not have unsupported devices connected. For more about the ISO installer and other ESXi upgrade methods, see Upgrade Options for ESXi 6.0.
- See also Upgrading Hosts by Using esxcli Commands and Overview of the ESXi Host Upgrade Process.
- Before proceeding, you should read Overview of the ESXi Host Upgrade Process. This article below is just about the quick and easy way, effective and safe for most folks. For those more interested in "clean installs", where you login to My VMware, download the ESXi 6.5U1 ISO, shut down the ESXi on USB that you're already running, eject that USB flash drive and label it and set it aside, then boot from another USB drive like the SanDisk Ultra Fit with a fresh install of 6.5U1 imaged onto it. This clean install is much more time consuming than the easy method outlined below. Why? This is because once ESXi 6.5U1 is freshly installed, at a minimum you'll also have to use Datastore Browser to locate your VMs on your VMFS datastores, then add those files with *.vmx extensions back into your inventory, then add the host back to your cluster that should already be at 6.5U1. While this extra work may help you be sure that you don't have any drivers or changes carried over from your previous build, for many users, that's not a concern.
Once you've completed ALL of the following preparation steps:
- upgraded to the latest VCSA, which is currently 6.5 U1f, see How to easily update your VMware vCenter Server Appliance from 6.5.x to 6.5 Update 1f (VCSA 6.5 U1f) for Meltdown/Spectre-1 mitigation
read and understood Mike Foley's warnings in Secure Boot for ESXi 6.5 – Hypervisor Assurance
Possible upgrade issues
UEFI secure boot requires that the original VIB signatures are persisted. Older versions of ESXi do not persist the signatures, but the upgrade process updates the VIB signatures.
If your host was upgraded using the ESXCLI command then your bootloader wasn’t upgraded and doesn’t persist the signatures. When you enable Secure Boot after the upgrade, an error occurs. You can’t use Secure Boot on these installations and will have to re-install from scratch to gain that support.
- ensured your ESXi 6.5.x host has a working internet connection
- reviewed the release notes
- reviewed How to easily update your VMware Hypervisor to ESXi 6.0 Update 2 for the full back story that includes some warnings about potential gotchas/driver issues
- backed up the ESXi 6.5.x you've already got, if its on USB or SD, then use something like one of the home-lab-friendly and super easy methods such as USB Image Tools under Windows, as detailed by Florian Grehl here
you can now continue with this simple approach to upgrading your lab environment. Unsupported, at your own risk, see the full disclaimer at below-left.
You should wind up with the same results after this upgrade as folks who upgrade by downloading the full ESXi 6.5 U1 ISO / creating bootable media from that ISO / booting from that media (or mounting the ISO over IPMI/iLO/iDRAC/IMM/iKMV) and booting from it:
File size: 332.63 MB
File type: iso
Release Date: 2017-07-27
Build Number: 5969303
installing it, rebooting, then running the patch process described below.
Download and upgrade to 6.5 Patch 02 update using the patch directly from the VMware Online Depot
The entire process including reboot is usually well under 10 minutes, and many of the steps below are optional, making it appear more difficult than it is. Triple-clicking on a line of code below highlights the whole thing with a carriage return, so you can then right-click and copy it into your clipboard, which gets executed immediately upon pasting into your SSH session. If you want to edit the line before it's executed, manually swipe your mouse across the code rather than triple-clicking the lines of code.
- Open an SSH session (eg. PuTTY) to your ESXi 6.0.x server
(if you forgot to enable SSH, here's how)
- Turn on maintenance mode, or ensure you've set your ESXi host to automatically gracefully shutdown all VMs upon host reboot, or shutdown all the VMs gracefully that you care about, including VCSA.
- Firewall allow outbound http requests - This command might not be needed, but I'm trying to make these instructions applicable to the broadest set of readers. Paste the one line below into into your SSH session, then press enter:
esxcli network firewall ruleset set -e true -r httpClient
More details about the firewall here.
- Pull down ESXi Image Profile using https and run patch script - Paste the line below into into your SSH session, then hit enter and wait while nothing seems to happen, taking somewhere between roughly 3 to 10 minutes before the completion screen (sample below) appears:
esxcli software profile install -p ESXi-6.5.0-20171204001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
It MAY just do it's thing after a several minute pause, or it may immediately fail and warn you what VIBs will be removed if you proceed. Note that next command is the same as the one above, but with
added at the end. This allows the upgrade to proceed, now that you've been properly warned. Be sure to make note of what VIBs it says will be removed, just in case the inbox (included) drivers it installs don't work for your system.
esxcli software profile install -p ESXi-6.5.0-20171204001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml --ok-to-remove
If you don't have Xeon D, the next command is:
and you're done!
Be sure all your devices still work afterward, and if not, you'll need to locate the original VIB download site and install it, using the detailed install instructions usually found at the vendor's VIB download site. Now that the included AHCI/SATA driver has been fixed, home lab enthusiasts are likely to find such issues much less common.
esxcli software profile install commands fails, you may want to try changing
install, details below, see also Douglas' comment. Wait time for the successful install depending mostly on the the speed of the ESXi's connection to the internet, and somewhat on the write speed of the storage media that ESXi is installed on.
- OPTIONAL - Xeon D with 10GbE - If your system includes two 10GbE Intel X552/X557 RJ45 or SFP+ NICs ports, they can be used for 1GbE or 10GbE speeds, but you'll need to regain the 10GbE Intel driver VIB that the upgrade process replaced with an older one that doesn't work with your X557. Simply copy and paste the following one-liner fix:
esxcli software vib install -v https://cdn.tinkertry.com/files/net-ixgbe_4.5.3-1OEM.600.0.0.2494585.vib --no-sig-check
as described in detail here before proceeding.
- OPTIONAL - Xeon D-1567 - If your system uses the Xeon D-1567 (12 core) you may find the VMware ESXi 6.0 igbn 1.4.1 NIC Driver for Intel Ethernet Controllers 82580,I210,I350 and I354 family performs better for the service console on either ETH0 or ETH1 instead of the included-with-6.5U1EP4 VMware inbox driver for I-350 called
VMW_bootbank_net-igb_18.104.22.168.1-5vmw.622.214.171.12464106. No need to download separately. Simply copy and paste the following one-liner fix:
esxcli software vib install -v https://cdn.tinkertry.com/files/igbn-1.4.1-1OEM.600.0.0.2768847.x86_64.vib --no-sig-check
- OPTIONAL - Intel Optane P4800X - If your system has an Intel Optane P4800X NVMe SSD of either the PCIe or U.2 type, or a consumer 900P version, you'll need the Intel driver for full speed support under ESX. First, find your NVMe firmware version, then reference this version to verify the exact VIB you should be using on the VMware HCL - IO Devices Keyword P4800X. If it's intel-nvme version 126.96.36.199, simply paste the easy one-liner fix:
esxcli software vib install -v https://cdn.tinkertry.com/files/intel-nvme-188.8.131.52-1OEM.6184.108.40.20698673.x86_64.vib --no-sig-check
before proceeding. This method is here as a reference only, you should use your own internal web host to make pulling/installing this VIB easy, or just download it to a local directory on the ESXi and install it from there.
- Firewall disallow outbound http requests - To return your firewall to how it was before this online upgrade, simply copy and paste the following:
esxcli network firewall ruleset set -e false -r httpClient
- If you turned on maintenance mode earlier, remember to turn maintenance mode off.
- If you normally leave SSH access off, go ahead and disable it now.
- Type or paste
and hit return (to restart your ESXi server), or use your favorite ESXi UI to restart the host.
- After the reboot is done, it would be a good idea to test login using ESXi host client, pointing your browser to the IP or hostname of your just-graded server, to be sure everthing seems to be working right.
Special thanks to VMware ESXi Patch Tracker by Andreas Peetz at the VMware Front Experience Blog. This upgrade test was performed on a TinkerTry'd VMware HCL system. Yes, on both the very popular 8 core and the rather special 12 core version of the beloved Supermicro SuperServer SYS-5028D-TN4T system.
That's it! When the reboot is complete, you'll see for yourself that you now have the latest ESXi, Build 7388607, as pictured above. Now you have more spare time to read more TinkerTry articles!
When the upgrade is complete, on the ESXi Host Client UI, under Host / Configuration, you should see the following "Image profile"
(Updated) ESXi-6.5.0-20171204001-standard (VMware, Inc.)
- Depending upon your ESXi firewall configuration, if the above command results in a network related error such as:
'NoneType' object has no attribute 'close'
then you skipped the firewall configuration step above, try again!
Alternatively, you could have used VMware Update Manager on a Windows system or VM, but for one-off upgrades typical in a small home lab, pasting these 3 or 4 lines of code is pretty darn easy.
Looking ahead, since VUM is now built into VCSA 6.5, this adds another way to do future upgrades and patches, even in a small home lab environment.
This release is also known as:
- ESXi 6.5 U1 Patch 2
- ESXi 6.5 U1 EP4
- ESXi 6.5 U1 P02
- ESXi 6.5U1 P02
- ESXi 6.5 U1 P2
- ESXi 6.5U1P2
All ESXi releases have been nicely documented by VMware here:
From the above table, I created this summary of this 6.5U1EP4 release:
- Version - ESXi 6.5 U1 Express Patch 4
Release Date - 2017-10-05
Build Number - 6765664
Installer Build Number - N/A
It's quite possible the above upgrade technique will work for all of the following 6.x versions of ESXi, but I haven't tested:
Version | Release Date | Build Number | Installer Build Number ESXi 6.5 U1 Express Patch 4 2017-10-05 6765664 N/A ESXi 6.5 U1 2017-07-27 5969303 N/A ESXi 6.5.0d 2017-04-18 5310538 N/A ESXi 6.5. Express Patch 1a 2017-03-28 5224529 N/A ESXi 6.5. Patch 01 2017-03-09 5146846 5146843 ESXi 6.5.0a 2017-02-02 4887370 N/A ESXi 6.5 GA 2016-11-15 4564106 N/A ESXi 6.0 Patch 6 2017-11-09 6921384 N/A ESXi 6.0 Express Patch 11 2017-10-05 6765062 N/A ESXi 6.0 Update 3a (ESXi 6.0 Patch 5) 2017-07-11 5572656 N/A ESXi 6.0 Express Patch 7c 2017-03-28 5251623 N/A ESXi 6.0 Express Patch 7a 2017-03-28 5224934 N/A ESXi 6.0 Update 3 2017-02-24 5050593 N/A ESXi 6.0 Patch 4 2016-11-22 4600944 N/A ESXi 6.0 Express Patch 7 2016-10-17 4510822 N/A ESXi 6.0 Patch 3 2016-08-04 4192238 N/A ESXi 6.0 Express Patch 6 2016-05-12 3825889 N/A ESXi 6.0 Update 2 2016-03-16 3620759 N/A ESXi 6.0 Express Patch 5 2016-02-23 3568940 N/A ESXi 6.0 Update 1b 2016-01-07 3380124 N/A ESXi 6.0 Express Patch 4 2015-11-25 3247720 N/A ESXi 6.0 U1a (Express Patch 3) 2015-10-06 3073146 N/A ESXi 6.0 U1 2015-09-10 3029758 N/A ESXi 6.0.0b 2015-07-07 2809209 N/A ESXi 6.0 Express Patch 2 2015-05-14 2715440 N/A ESXi 6.0 Express Patch 1 2015-04-09 2615704 2615979 ESXi 6.0 GA 2015-03-12 2494585 N/A
Did you realize that vSAN Support Insight arrives in this ESXi 6.5 U1 Express Patch patch?
- vSAN Support Insight
Dec 18 2017 by John Nicholson at VMware Virtual Blocks
Don't miss the overview video featuring Pete Fletcha's always pleasant voiceover at the vSAN Support Insight page on storagehub, as also seen below.
Nice short summary of CVE-2017-5753 & CVE-2017-5715 (Spectre) & CVE-2017-5754 (Meltdown) by William Lam:
VMware Customers - See https://blogs.vmware.com/security/2018/01/vmsa-2018-0002.html … for addressing CVE-2017-5753 & CVE-2017-5715 (Spectre) & CVE-2017-5754 (Meltdown)
FYI - VMware Hypervisors not affected by Meltdown but you still need to apply whatever patches are issued by the GuestOS vendors
- Meltdown and Spectre – what you need to know!
Jan 05 2018 - Michael White at Notes from MWhite
- VMware Security Advisories / VMSA-2018-0002.3 / VMware ESXi, Workstation and Fusion updates address side-channel analysis due to speculative execution.
where you'll discover that it recommends ESXi 6.5 users patch with
ESXi650-201712101-SG from https://my.vmware.com/group/vmware/patch that has this documentation. That is the very same
ESXi650-201712101-SG that is included in the
ESXi650-201712001 patch that this article above is all about! In other words, currently, this article covers what is currently the Spectre/Meltdown mitigation patch. The more recent patch ESXi650-201801001 (ESXi Build 7388607) that I covered in my more recent article has been pulled, based on Intel's findings.
VMware support has informed me that it's now recommended that Intel I350 NICs get the Sep 20 2017 version 1.4.1, found here.
References to 5.3.3:
VMware ESXi 6.0 igb 5.3.3 NIC Driver for Intel Ethernet Controllers 82580, I210, I350, and I354
have now been removed from the above article.
Reference to 4.5.3 removed as well.
esxcli software vib install -v https://cdn.tinkertry.com/files/net-ixgbe_4.5.3-1OEM.600.0.0.2494585.vib --no-sig-check
- Meltdown and Spectre side-channel attack risk mitigation information from processor, server, and software vendors
Jan 10 2018
- Order a TinkerTry'd Supermicro SuperServer Bundle - powerful and efficient home virtualization lab solutions
VMware vSAN 6.6 GA - Download Links Available
Apr 18 2017 by Florian Grehl
ESXi 6.5 Release Notes for free license and white box users
Nov 24 2016 by Andreas Peetz at VMware Front Experience
VMware ESXi Patch Tracker
Nov 24 2016 by Andreas Peetz at VMware Front Experience
- VMware vSphere 6.5 Documentation Center - Upgrade or Update a Host with Image Profiles
Below, I've pasted the full text of my upgrade, helps you see what drivers were touched, use the horizonal scroll bar or shift + mousewheel to look around, and Ctrl+F to Find stuff quickly:
login as: root Using keyboard-interactive authentication. Password: The time and date of this login have been sent to the system logs. WARNING: All commands run on the ESXi shell are logged and may be included in support bundles. Do not provide passwords directly on the command line. Most tools can prompt for secrets or accept them from standard input. VMware offers supported, powerful system administration tools. Please see www.vmware.com/go/sysadmintools for details. The ESXi Shell can be disabled by an administrative user. See the vSphere Security documentation for more information. [root@xd-1541-5028d:~] esxcli network firewall ruleset set -e true -r httpClient [root@xd-1541-5028d:~] esxcli software profile install -p ESXi-6.5.0-20171204001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml [Exception] You attempted to install an image profile which would have resulted in the removal of VIBs ['VMware_bootbank_vscsi-statsd_1.0.26-5.1.u2', 'INT_bootbank_intel-nvme_220.127.116.11- 1OEM.618.104.22.16898673', 'Intel_bootbank_intel_ssd_data_center_tool_3.0.4-400']. If this is not what you intended, you may use the esxcli software profile update command to p reserve the VIBs above. If this is what you intended, please use the --ok-to-remove option to explicitly allow the removal. Please refer to the log file for more details. [root@xd-1541-5028d:~] esxcli software profile install -p ESXi-6.5.0-20171204001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml --ok-to-remove Installation Result Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. Reboot Required: true VIBs Installed: VMW_bootbank_igbn_0.1.0.0-15vmw.622.214.171.12488607, VMW_bootbank_misc-drivers_6.5.0-1.36.7388607, VMW_bootbank_net-igb_126.96.36.199.1-5vmw.6188.8.131.5264106, VMW_bootbank_net-ixgbe_184.108.40.206.14iov-20vmw.6220.127.116.1164106, VMW_bootbank_ntg3_18.104.22.168-1vmw.622.214.171.12488607, VMW_bootbank_nvme_126.96.36.199-5vmw.6188.8.131.5288607, VMW_bootbank_nvmxnet3_184.108.40.206-1vmw.6220.127.116.1188607, VMW_bootbank_vmkata_0.1-1vmw.618.104.22.16888607, VMW_bootbank_vmkusb_0.1-1vmw.622.214.171.12488607, VMware_bootbank_esx-base_6.5.0-1.36.7388607, VMware_bootbank_esx-dvfilter-generic-fastpath_6.5.0-1.36.7388607, VMware_bootbank_esx-tboot_6.5.0-1.36.7388607, VMware_bootbank_esx-ui_1.23.0-6506686, VMware_bootbank_vsan_6.5.0-1.36.7388608, VMware_bootbank_vsanhealth_6.5.0-1.36.7388609, VMware_locker_tools-light_6.5.0-1.33.7273056 VIBs Removed: INT_bootbank_intel-nvme_126.96.36.199-1OEM.6188.8.131.5298673, INT_bootbank_net-igb_5.3.3-1OEM.600.0.0.2494585, INT_bootbank_net-ixgbe_4.5.1-1OEM.600.0.0.2494585, Intel_bootbank_intel_ssd_data_center_tool_3.0.4-400, VMW_bootbank_igbn_0.1.0.0-14vmw.6184.108.40.20669303, VMW_bootbank_misc-drivers_6.5.0-1.26.5969303, VMW_bootbank_ntg3_220.127.116.11-1vmw.618.104.22.16869303, VMW_bootbank_nvme_22.214.171.124-4vmw.6126.96.36.19969303, VMW_bootbank_nvmxnet3_188.8.131.52-1vmw.6184.108.40.20664106, VMW_bootbank_vmkata_0.1-1vmw.6220.127.116.1169303, VMW_bootbank_vmkusb_0.1-1vmw.618.104.22.16869303, VMware_bootbank_esx-base_6.5.0-1.29.6765664, VMware_bootbank_esx-dvfilter-generic-fastpath_6.5.0-0.0.4564106, VMware_bootbank_esx-tboot_6.5.0-1.29.6765664, VMware_bootbank_esx-ui_1.21.0-5724747, VMware_bootbank_vsan_6.5.0-1.29.6765666, VMware_bootbank_vsanhealth_6.5.0-1.29.6765667, VMware_bootbank_vscsi-statsd_1.0.26-5.1.u2, VMware_locker_tools-light_6.5.0-0.23.5969300 VIBs Skipped: VMW_bootbank_ata-libata-92_3.00.9.2-16vmw.622.214.171.12464106, VMW_bootbank_ata-pata-amd_0.3.10-3vmw.6126.96.36.19964106, VMW_bootbank_ata-pata-atiixp_0.4.6-4vmw.6188.8.131.5264106, VMW_bootbank_ata-pata-cmd64x_0.2.5-3vmw.6184.108.40.20664106, VMW_bootbank_ata-pata-hpt3x2n_0.3.4-3vmw.6220.127.116.1164106, VMW_bootbank_ata-pata-pdc2027x_1.0-3vmw.618.104.22.16864106, VMW_bootbank_ata-pata-serverworks_0.4.3-3vmw.622.214.171.12464106, VMW_bootbank_ata-pata-sil680_0.4.8-3vmw.6126.96.36.19964106, VMW_bootbank_ata-pata-via_0.3.3-2vmw.6188.8.131.5264106, VMW_bootbank_block-cciss_3.6.14-10vmw.6184.108.40.20664106, VMW_bootbank_char-random_1.0-3vmw.6220.127.116.1164106, VMW_bootbank_ehci-ehci-hcd_1.0-4vmw.618.104.22.16846846, VMW_bootbank_elxnet_22.214.171.124-1vmw.6126.96.36.19964106, VMW_bootbank_hid-hid_1.0-3vmw.6188.8.131.5264106, VMW_bootbank_i40en_1.3.1-5vmw.6184.108.40.20669303, VMW_bootbank_ima-qla4xxx_2.02.18-1vmw.6220.127.116.1164106, VMW_bootbank_ipmi-ipmi-devintf_39.1-4vmw.618.104.22.16864106, VMW_bootbank_ipmi-ipmi-msghandler_39.1-4vmw.622.214.171.12464106, VMW_bootbank_ipmi-ipmi-si-drv_39.1-4vmw.6126.96.36.19964106, VMW_bootbank_ixgben_1.4.1-2vmw.6188.8.131.5269303, VMW_bootbank_lpfc_184.108.40.206-1vmw.6220.127.116.1164106, VMW_bootbank_lsi-mr3_6.910.18.00-1vmw.618.104.22.16864106, VMW_bootbank_lsi-msgpt2_20.00.01.00-3vmw.622.214.171.12464106, VMW_bootbank_lsi-msgpt3_12.00.02.00-11vmw.6126.96.36.19964106, VMW_bootbank_misc-cnic-register_1.78.75.v60.7-1vmw.6188.8.131.5264106, VMW_bootbank_mtip32xx-native_3.9.5-1vmw.6184.108.40.20664106, VMW_bootbank_ne1000_0.8.0-16vmw.6220.127.116.1169303, VMW_bootbank_nenic_18.104.22.168-1vmw.622.214.171.12464106, VMW_bootbank_net-bnx2_2.2.4f.v60.10-2vmw.6126.96.36.19964106, VMW_bootbank_net-bnx2x_1.78.80.v60.12-1vmw.6188.8.131.5264106, VMW_bootbank_net-cdc-ether_1.0-3vmw.6184.108.40.20664106, VMW_bootbank_net-cnic_1.78.76.v60.13-2vmw.6220.127.116.1164106, VMW_bootbank_net-e1000_18.104.22.168-5vmw.622.214.171.12464106, VMW_bootbank_net-e1000e_126.96.36.199-2vmw.6188.8.131.5264106, VMW_bootbank_net-enic_184.108.40.206-2vmw.6220.127.116.1164106, VMW_bootbank_net-fcoe_18.104.22.168.3-7vmw.622.214.171.12464106, VMW_bootbank_net-forcedeth_0.61-2vmw.6126.96.36.19964106, VMW_bootbank_net-libfcoe-92_188.8.131.52.4-8vmw.6184.108.40.20664106, VMW_bootbank_net-mlx4-core_220.127.116.11-1vmw.618.104.22.16864106, VMW_bootbank_net-mlx4-en_22.214.171.124-1vmw.6126.96.36.19964106, VMW_bootbank_net-nx-nic_5.0.621-5vmw.6188.8.131.5264106, VMW_bootbank_net-tg3_3.131d.v60.4-2vmw.6184.108.40.20664106, VMW_bootbank_net-usbnet_1.0-3vmw.6220.127.116.1164106, VMW_bootbank_net-vmxnet3_18.104.22.168-3vmw.622.214.171.12464106, VMW_bootbank_nhpsa_2.0.6-3vmw.6126.96.36.19964106, VMW_bootbank_nmlx4-core_188.8.131.52-1vmw.6184.108.40.20664106, VMW_bootbank_nmlx4-en_220.127.116.11-1vmw.618.104.22.16864106, VMW_bootbank_nmlx4-rdma_22.214.171.124-1vmw.6126.96.36.19964106, VMW_bootbank_nmlx5-core_188.8.131.52-1vmw.6184.108.40.20664106, VMW_bootbank_ohci-usb-ohci_1.0-3vmw.6220.127.116.1164106, VMW_bootbank_pvscsi_0.1-1vmw.618.104.22.16869303, VMW_bootbank_qedentv_22.214.171.124-1vmw.6126.96.36.19964106, VMW_bootbank_qfle3_188.8.131.52-1vmw.6184.108.40.20664106, VMW_bootbank_qflge_220.127.116.11-1vmw.618.104.22.16864106, VMW_bootbank_qlnativefc_22.214.171.124-1vmw.6126.96.36.19969303, VMW_bootbank_sata-ahci_3.0-26vmw.6188.8.131.5269303, VMW_bootbank_sata-ata-piix_2.12-10vmw.6184.108.40.20664106, VMW_bootbank_sata-sata-nv_3.5-4vmw.6220.127.116.1164106, VMW_bootbank_sata-sata-promise_2.12-3vmw.618.104.22.16864106, VMW_bootbank_sata-sata-sil24_1.1-1vmw.622.214.171.12464106, VMW_bootbank_sata-sata-sil_2.3-4vmw.6126.96.36.19964106, VMW_bootbank_sata-sata-svw_2.3-3vmw.6188.8.131.5264106, VMW_bootbank_scsi-aacraid_184.108.40.206-9vmw.6220.127.116.1164106, VMW_bootbank_scsi-adp94xx_18.104.22.168-6vmw.622.214.171.12464106, VMW_bootbank_scsi-aic79xx_3.1-5vmw.6126.96.36.19964106, VMW_bootbank_scsi-bnx2fc_1.78.78.v60.8-1vmw.6188.8.131.5264106, VMW_bootbank_scsi-bnx2i_2.78.76.v60.8-1vmw.6184.108.40.20664106, VMW_bootbank_scsi-fnic_220.127.116.11-3vmw.618.104.22.16864106, VMW_bootbank_scsi-hpsa_22.214.171.124-1vmw.6126.96.36.19964106, VMW_bootbank_scsi-ips_7.12.05-4vmw.6188.8.131.5264106, VMW_bootbank_scsi-iscsi-linux-92_184.108.40.206-3vmw.6220.127.116.1164106, VMW_bootbank_scsi-libfc-92_18.104.22.168.3-5vmw.622.214.171.12464106, VMW_bootbank_scsi-megaraid-mbox_126.96.36.199-6vmw.6188.8.131.5264106, VMW_bootbank_scsi-megaraid-sas_6.603.55.00-2vmw.6184.108.40.20664106, VMW_bootbank_scsi-megaraid2_2.00.4-9vmw.6220.127.116.1164106, VMW_bootbank_scsi-mpt2sas_19.00.00.00-1vmw.618.104.22.16864106, VMW_bootbank_scsi-mptsas_4.23.01.00-10vmw.622.214.171.12464106, VMW_bootbank_scsi-mptspi_4.23.01.00-10vmw.6126.96.36.19964106, VMW_bootbank_scsi-qla4xxx_5.01.03.2-7vmw.6188.8.131.5264106, VMW_bootbank_shim-iscsi-linux-9-2-1-0_6.5.0-0.0.4564106, VMW_bootbank_shim-iscsi-linux-9-2-2-0_6.5.0-0.0.4564106, VMW_bootbank_shim-libata-9-2-1-0_6.5.0-0.0.4564106, VMW_bootbank_shim-libata-9-2-2-0_6.5.0-0.0.4564106, VMW_bootbank_shim-libfc-9-2-1-0_6.5.0-0.0.4564106, VMW_bootbank_shim-libfc-9-2-2-0_6.5.0-0.0.4564106, VMW_bootbank_shim-libfcoe-9-2-1-0_6.5.0-0.0.4564106, VMW_bootbank_shim-libfcoe-9-2-2-0_6.5.0-0.0.4564106, VMW_bootbank_shim-vmklinux-9-2-1-0_6.5.0-0.0.4564106, VMW_bootbank_shim-vmklinux-9-2-2-0_6.5.0-0.0.4564106, VMW_bootbank_shim-vmklinux-9-2-3-0_6.5.0-0.0.4564106, VMW_bootbank_uhci-usb-uhci_1.0-3vmw.6184.108.40.20664106, VMW_bootbank_usb-storage-usb-storage_1.0-3vmw.6220.127.116.1164106, VMW_bootbank_usbcore-usb_1.0-3vmw.618.104.22.16869303, VMW_bootbank_vmkplexer-vmkplexer_6.5.0-0.0.4564106, VMW_bootbank_vmw-ahci_1.0.0-39vmw.622.214.171.12469303, VMW_bootbank_xhci-xhci_1.0-3vmw.6126.96.36.19964106, VMware_bootbank_cpu-microcode_6.5.0-0.0.4564106, VMware_bootbank_emulex-esx-elxnetcli_188.8.131.52-0.0.4564106, VMware_bootbank_esx-xserver_6.5.0-0.23.5969300, VMware_bootbank_lsu-hp-hpsa-plugin_2.0.0-5vmw.6184.108.40.20669303, VMware_bootbank_lsu-lsi-lsi-mr3-plugin_1.0.0-10vmw.6220.127.116.1169303, VMware_bootbank_lsu-lsi-lsi-msgpt3-plugin_1.0.0-7vmw.618.104.22.16869303, VMware_bootbank_lsu-lsi-megaraid-sas-plugin_1.0.0-8vmw.622.214.171.12469303, VMware_bootbank_lsu-lsi-mpt2sas-plugin_2.0.0-6vmw.6126.96.36.19969303, VMware_bootbank_native-misc-drivers_6.5.0-0.0.4564106, VMware_bootbank_rste_2.0.2.0088-4vmw.6188.8.131.5264106, VMware_bootbank_vmware-esx-esxcli-nvme-plugin_184.108.40.206-1.26.5969303 [root@xd-1541-5028d:~] esxcli software vib install -v https://cdn.tinkertry.com/files/net-ixgbe_4.5.3-1OEM.600.0.0.2494585.vib --no-sig-check Installation Result Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. Reboot Required: true VIBs Installed: INT_bootbank_net-ixgbe_4.5.3-1OEM.600.0.0.2494585 VIBs Removed: VMW_bootbank_net-ixgbe_220.127.116.11.14iov-20vmw.618.104.22.16864106 VIBs Skipped: [root@xd-1541-5028d:~] esxcli network firewall ruleset set -e false -r httpClient [root@xd-1541-5028d:~] reboot [root@xd-1541-5028d:~] esxcli software vib install -v https://cdn.tinkertry.com/files/net-igb_5.3.3-1OEM.600.0.0.2494585.vib --no-sig-check Installation Result Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective. Reboot Required: true VIBs Installed: INT_bootbank_net-igb_5.3.3-1OEM.600.0.0.2494585 VIBs Removed: VMW_bootbank_net-igb_22.214.171.124.1-5vmw.6126.96.36.19964106 VIBs Skipped: [root@xd-1541-5028d:~]