Reverting to a previous version of ESXi 6.x, 7.x and 8.x
search cancel

Reverting to a previous version of ESXi 6.x, 7.x and 8.x

book

Article ID: 316592

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Reverting to a previous version or build of ESXi using the Direct Console User Interface (DCUI)

Environment

VMware vSphere ESXi 6.x
VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x

Resolution

Process to revert to a previous version of ESXi:

Video Tutorial to revert to a previous version of ESXi:

Steps to revert to a previous version of ESXi:

To revert to a previous version of ESXi follow the steps below:
 
Notes:
  • Back up the configuration data before making any changes. For more information, see Backing up and restoring ESXi configuration using the vSphere Command-Line Interface and vSphere PowerCLI.
  • Reverting to a previous build does not revert the tools-light vib version installed on the ESXi host
  • Reverting an ESXi host is only valid if the host was updated using these methods:
    • VIB installation or removal
    • Profile installation or removal
    • ESXi host update using VMware Update Manager
    • Updated from a ISO
  • Reverting to an earlier version is not possible after upgrading to ESXi 7.0 due to partition changes to the boot device.
Note: To use an earlier version of ESXi after upgrading to version 7.0, create a backup of the boot device before the upgrade or reinstall the desired version.
  • Rolling from ESXi 8.0 to 7.0 is acceptable, as there are no partition changes between the two versions.
  1. In the console screen of the ESXi host, press Ctrl+Alt+F2 to see the Direct Console User Interface (DCUI) screen.
  2. Press F12 to view the shutdown options for the ESXi host.
  3. Press F11 to reboot.
  4. When the Hypervisor progress bar starts loading, press Shift+R (This must be done while the bar is loading, and not after. Optionally, press Shift+R repeatedly once "system is preparing to boot" to ensure not missing the time frame to execute the command). A warning will appear:

    Current hypervisor will permanently be replaced
    with build: X.X.X-XXXXXX. Are you sure? [y/n]
     
  5. Press Y to roll back the build.
  6. Press Enter to boot.

Additional Information

In some case we will be Unable to rollback ESXi Version "Bootbank and Altbootbank has same build number- 

Bootbank Directory:

less boot.cfg
bootstate=0
title=Loading VMware ESXi
timeout=5
prefix=
kernel=b.b00
kernelopt=autoPartition=FALSE
modules=jumpstrt.gz --- useropts.gz --- features.gz --- k.b00 --- uc_intel.b00 --- uc_amd.b00 --- uc_hygon.b00 --- procfs.b00 --- vmx.v00 --- vim.v00 --- tpm.v00 --- sb.v00 --- s.v00 --- bnxtnet.v00 --- bnxtroce.v00 --- lpfc.v00 --- amsd.v00 --- amsdv.v00 --- stage.v00 --- payload.v00 --- ilo.v00 --- ilorest.v00 --- sut.v00 --- stage.v06 --- i40en.v00 --- iavmd.v00 --- icen.v00 --- igbn.v00 --- ixgben.v00 --- nmlx4cor.v00 --- nmlx4en.v00 --- nmlx4rdm.v00 --- nmlx5cor.v00 --- nmlx5rdm.v00 --- nmst.v00 --- smartpqi.v00 --- ssacli.v00 --- qlnative.v00 --- qcnic.v00 --- qedentv.v00 --- qedf.v00 --- qedi.v00 --- qedrntv.v00 --- qfle3.v00 --- qfle3f.v00 --- qfle3i.v00 --- atlantic.v00 --- brcmfcoe.v00 --- elxiscsi.v00 --- elxnet.v00 --- ionic_en.v00 --- irdman.v00 --- iser.v00 --- lpnic.v00 --- lsi_mr3.v00 --- lsi_msgp.v00 --- lsi_msgp.v01 --- lsi_msgp.v02 --- mtip32xx.v00 --- ne1000.v00 --- nenic.v00 --- nfnic.v00 --- nhpsa.v00 --- ntg3.v00 --- nvme_pci.v00 --- nvmerdma.v00 --- nvmetcp.v00 --- nvmxnet3.v00 --- nvmxnet3.v01 --- pvscsi.v00 --- qflge.v00 --- rste.v00 --- sfvmk.v00 --- vmkata.v00 --- vmkfcoe.v00 --- vmkusb.v00 --- vmw_ahci.v00 --- bmcal.v00 --- crx.v00 --- elx_esx_.v00 --- btldr.v00 --- esx_dvfi.v00 --- esx_ui.v00 --- esxupdt.v00 --- tpmesxup.v00 --- weaselin.v00 --- esxio_co.v00 --- loadesx.v00 --- lsuv2_hp.v00 --- lsuv2_in.v00 --- lsuv2_ls.v00 --- lsuv2_nv.v00 --- lsuv2_oe.v00 --- lsuv2_oe.v01 --- lsuv2_oe.v02 --- lsuv2_sm.v00 --- native_m.v00 --- trx.v00 --- vdfs.v00 --- vmware_e.v00 --- vmware_f.v00 --- vsan.v00 --- vsanheal.v00 --- vsanmgmt.v00 --- xorg.v00 --- gc.v00 --- imgdb.tgz --- basemisc.tgz --- state.tgz
build=7.0.3-0.125.23794027
updated=6
boot.cfg (END)

Altbootbank Directory:

less boot.cfg
bootstate=0
title=Loading VMware ESXi
timeout=5
prefix=
kernel=b.b00
kernelopt=autoPartition=FALSE
modules=jumpstrt.gz --- useropts.gz --- features.gz --- k.b00 --- uc_intel.b00 --- uc_amd.b00 --- uc_hygon.b00 --- procfs.b00 --- vmx.v00 --- vim.v00 --- tpm.v00 --- sb.v00 --- s.v00 --- bnxtnet.v00 --- bnxtroce.v00 --- lpfc.v00 --- amsd.v00 --- amsdv.v00 --- stage.v00 --- payload.v00 --- ilo.v00 --- ilorest.v00 --- sut.v00 --- stage.v06 --- i40en.v00 --- iavmd.v00 --- icen.v00 --- igbn.v00 --- ixgben.v00 --- nmlx4cor.v00 --- nmlx4en.v00 --- nmlx4rdm.v00 --- nmlx5cor.v00 --- nmlx5rdm.v00 --- nmst.v00 --- smartpqi.v00 --- ssacli.v00 --- qlnative.v00 --- qcnic.v00 --- qedentv.v00 --- qedf.v00 --- qedi.v00 --- qedrntv.v00 --- qfle3.v00 --- qfle3f.v00 --- qfle3i.v00 --- atlantic.v00 --- brcmfcoe.v00 --- elxiscsi.v00 --- elxnet.v00 --- ionic_en.v00 --- irdman.v00 --- iser.v00 --- lpnic.v00 --- lsi_mr3.v00 --- lsi_msgp.v00 --- lsi_msgp.v01 --- lsi_msgp.v02 --- mtip32xx.v00 --- ne1000.v00 --- nenic.v00 --- nfnic.v00 --- nhpsa.v00 --- ntg3.v00 --- nvme_pci.v00 --- nvmerdma.v00 --- nvmetcp.v00 --- nvmxnet3.v00 --- nvmxnet3.v01 --- pvscsi.v00 --- qflge.v00 --- rste.v00 --- sfvmk.v00 --- vmkata.v00 --- vmkfcoe.v00 --- vmkusb.v00 --- vmw_ahci.v00 --- bmcal.v00 --- crx.v00 --- elx_esx_.v00 --- btldr.v00 --- esx_dvfi.v00 --- esx_ui.v00 --- esxupdt.v00 --- tpmesxup.v00 --- weaselin.v00 --- esxio_co.v00 --- loadesx.v00 --- lsuv2_hp.v00 --- lsuv2_in.v00 --- lsuv2_ls.v00 --- lsuv2_nv.v00 --- lsuv2_oe.v00 --- lsuv2_oe.v01 --- lsuv2_oe.v02 --- lsuv2_sm.v00 --- native_m.v00 --- trx.v00 --- vdfs.v00 --- vmware_e.v00 --- vmware_f.v00 --- vsan.v00 --- vsanheal.v00 --- vsanmgmt.v00 --- xorg.v00 --- gc.v00 --- imgdb.tgz --- basemisc.tgz --- state.tgz
build=7.0.3-0.125.23794027
updated=7

Actions such as ESXi upgrade/update, vib installation/removal will discard the older (n-2) copy in the altbootbank and only retain the (n-1) copy.

After the first reboot following a successful ESXi host upgrade, if any changes are made, such as installing VIBs (vSphere Installation Bundles) or Software VIB's that require another reboot, the option to roll back to the previous version will be lost.

After removing the host from Maintenance Mode, if the host is part of an HA (High Availability) cluster, the FDM (Fault Domain Manager) VIB is installed on the host.
- Note: FDM VIB does not require a reboot.

In above such cases the rollback option to previous version is unavailable. 

Powered by Wolken Software