Installation with Legacy CPU

If you try to install ESXi vii on an hardware with older CPU(southward) that is no longer officially supported past VMware, y'all will get a error message similar to this when booting the installation medium:

              VMB: 611: Unsupported CPU: Intel family 0x06, model 0x1a, stepping 0x5 Intel(R) Xeon(R) CPU		E5520  @ ii.27GHz Encounter http://www.vmware.com/resources/compatibility

Even if it is unsupported it might work in practice.
To bypass this fault in the boot, do as follows:

  • Reboot into boot media once again
  • After the ESXi boot carte du jour when the "Loading ESXi Installer" is starting click SHIFT+O within five seconds to add boot options.
  • Type " allowLegacyCPU=true" backside the line. Similar this:
              <ENTER: Utilise options and boot> > cdromBoot runweasel allowLegacyCPU=true
  • Click ENTER and go on installation as normal.
  • Eventually you will come beyond error messages similar this:
              Error(s)/Alert(due south) Constitute During Organisation Browse  			Alert(south)  <CPU_SUPPORT WARNIG: The CPU in this host is not supported by ESXi 7.0.0. Delight refer to the VMware Compatibility Guide (VCG) for the list of supported CPUs.>
  • Click ENTER to continue, and finnish the installation.
  • After the installation medium is removed and the server is restarted the kick options have to be set every time you restart the server.
    This tin be avoided, read on.

Permanently let kick from Legacy CPU

The easiest manner to reach automatic kicking with a legacy CPU is to exercise as follows:

  • Shut downwardly the ESXi Server and remove the kicking-USB-drive.
  • Insert the drive in another computer. It will contain ii FAT-partitions.
  • Open the the drive with multiple files including Boot.CFG, and open information technology in a text-editor.
    One of the partitions is just containing a BOOT.CFG file and naught else. this is Not the one you should edit.
The bottom drive in this picture is the correct ane to edit BOOT.CFG on
  • Add " allowLegacyCPU=true" to the end of the line starting with "kernelopt="
              bootstate=0 title=Loading VMware ESXi timeout=5 prefix= kernel=b.b00 kernelopt=autoPartition=Fake allowLegacyCPU=true 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 --- brcmfcoe.v00 --- brcmnvme.v00 --- elxiscsi.v00 --- elxnet.v00 --- i40en.v00 --- i40iwn.v00 --- iavmd.v00 --- igbn.v00 --- iser.v00 --- ixgben.v00 --- lpfc.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 --- nmlx4_co.v00 --- nmlx4_en.v00 --- nmlx4_rd.v00 --- nmlx5_co.v00 --- nmlx5_rd.v00 --- ntg3.v00 --- nvme_pci.v00 --- nvmerdma.v00 --- nvmxnet3.v00 --- nvmxnet3.v01 --- pvscsi.v00 --- qcnic.v00 --- qedentv.v00 --- qedrntv.v00 --- qfle3.v00 --- qfle3f.v00 --- qfle3i.v00 --- qflge.v00 --- rste.v00 --- sfvmk.v00 --- smartpqi.v00 --- vmkata.v00 --- vmkfcoe.v00 --- vmkusb.v00 --- vmw_ahci.v00 --- crx.v00 --- elx_esx_.v00 --- btldr.v00 --- esx_dvfi.v00 --- esx_ui.v00 --- esxupdt.v00 --- tpmesxup.v00 --- weaselin.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 --- qlnative.v00 --- vdfs.v00 --- vmware_e.v00 --- vsan.v00 --- vsanheal.v00 --- vsanmgmt.v00 --- xorg.v00 --- imgdb.tgz --- country.tgz build=vii.0.0-1.25.16324942 updated=one
  • Save the file and move the bulldoze dorsum to the server
  • First the server, ESXi should now boot upwards without the need of any manual kick choice input.

Fixing "This host does not support virtualizing real mode" fault

At present when VMware ESXi vii.0 is up and running and all looks practiced you still might meet bug, non unlikely this one (when trying to beginning a VM):

              Failed to power on virtual machine Home-Banana. This host does not support virtualizing existent mode. The Intel "VMX Unrestricted Guest" characteristic is necessary to run this virtual car on an Intel processor. Click here for more details.            
              Power On VM Key haTask-2-vim.VirtualMachine.powerOn-3629474806 Description Power On this virtual auto Virtual machine:  Home-Assistant Land Failed - This host does non support virtualizing real mode. The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor.  Errors - This host does non back up virtualizing real style. The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor. - Module 'CPUIDEarly' power on failed. - Failed to get-go the virtual machine.

This result has to be solved for every electric current and future VM, simply the process is piece of cake and fast when you know how.

  • Click "Edit" on the VM
  • Select "VM Options"
  • Open "Advanced" and select "Edit Configuration…"
  • Click "Add parameter" and make full as follows:
    Key: monitor.allowLegacyCPU
    Value: true
  • Click "OK" and "Save"
  • The VM should at present piece of work, just exist patient. It tin take a very long time to kicking.

I hope this is to proficient use. Running unsupported is however non recommended, merely for uncritical servers why not.

Sources:

  • https://www.youtube.com/watch?v=RbHGeN-T-dg
  • https://world wide web.virtuallyghetto.com/2020/04/quick-tip-allow-unsupported-cpus-when-upgrading-to-esxi-7-0.html
  • https://planetvm.net/blog/?p=3253
  • https://www.enterpriseinfosec.internet/install-vmware-esxi-seven-on-a-r710-with-an-intel-55xx-cpu/