WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple
You are here: Home / Automation / Quick Tip - Automating ESXi 8.0 install using allowLegacyCPU=true

Quick Tip - Automating ESXi 8.0 install using allowLegacyCPU=true

10.17.2022 by William Lam // 5 Comments

For those looking to install ESXi 8.0 but have an unsupported CPU, the following kernel boot option allowLegacyCPU=true can be added which would bypass the installer pre-check as shown in the screenshot below.

When the ESXi installer bypass happens, instead of an error which forces you to reboot, you will get a warning message and user must acknowledge they understand they are using an unsupported CPU and then continue with the installation.

UPDATE (10/05/23) - ESXi 8.0 Update 2 requires CPU processors that support XSAVE instruction or you will not be able to upgrade and means you will hardware with a minimum of an Intel Sandy Bridge or AMD Bulldozer processor or later.

Note: For more information, also checkout my vSphere 8 Homelab considerations blog post for more tips and tricks.

For an interactive installation of ESXi, the additional acknowledgment is not an issue but for an automated installation of ESXi using Kickstart, this can be a problem since you are still required to manually hit enter before the installation actually begins. The question from a couple of my readers, is there a workaround for this?

Yes and there are actually a couple of options that can be passed into ESXi Kickstart script depending on which pre-check messages you would like ignored for automated installations.

  • --ignoreprereqwarnings - Will ignore warning messages
  • --ignoreprereqerrors - Will ignore error messages
  • --forceunsupportedinstall - Will ignore error/warning messages for deprecated CPUs

As you can see from the screenshot above (testing ESXi 8.0 on 2011 Apple Mac Mini), I have both an error for my unsupported CPU and a warning for my unsupported network adapter and so BOTH ignore warning/error options will required for the ESXi installer to continue with the installation without prompting for user input.

Here is a working Kickstart example that demonstrates the use of the two options:

vmaccepteula
install --firstdisk=local --overwritevmfs --ignoreprereqwarnings --ignoreprereqerrors
reboot

network --bootproto=static --ip=192.168.30.13 --netmask=255.255.255.0 --gateway=192.168.30.1 --hostname=nuc.primp-industries.com --nameserver=192.168.30.1 --addvmportgroup=1
rootpw VMware1!

%firstboot --interpreter=busybox

# enable & start SSH
vim-cmd hostsvc/enable_ssh
vim-cmd hostsvc/start_ssh

# enable & start ESXi Shell
vim-cmd hostsvc/enable_esx_shell
vim-cmd hostsvc/start_esx_shell

# Suppress ESXi Shell warning
esxcli system settings advanced set -o /UserVars/SuppressShellWarning -i 1

Note: In some cases, you may need all three options to successfully install ESXi without any prompts due to deprecated CPUs rather than unsupported CPUs

More from my site

  • USB Network Native Driver Fling for ESXi 8.0 Update 1
  • Automated ESXi Installation with a USB Network Adapter using Kickstart
  • How to bootstrap vSAN Express Storage Architecture (ESA) on unsupported hardware?
  • Nested ESXi installation using HTTPS boot over VirtualEFI in vSphere 8
  • ACPI motherboard layout requires EFI - Considerations for switching VM firmware in vSphere 8 

Categories // Automation, ESXi, vSphere 8.0 Tags // ESXi 8.0, kickstart, vSphere 8.0

Comments

  1. *protectedFereidoun says

    10/17/2022 at 9:16 am

    thank you for the info

    Reply
  2. *protectedMICHAEL S TUCKER says

    11/23/2022 at 9:14 am

    Awesome info! Thank you so much for posting.!

    Reply
  3. *protectedFranck says

    03/31/2023 at 6:43 am

    Hi there,

    I'm wondering how we will be able to patch ESXis once Baselines will be completely deprecated...

    Because so far, when I choose a single image and the CPU is unsupported, I can't patch them, despite the remediation option "Prevent remediation if hardware compatibility issues are found" is unselected.

    Is it a bug or will it be impossible in the future for us to do so?
    (I checked that in a nested lab only for now - relying on my physical ESXi 7 hosts)

    Thanks in advance for your feedback!

    Kind regards
    Franck

    Reply
  4. *protectedPhilipp Zykov says

    10/14/2024 at 11:05 am

    in this guide https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-esxi-installation/GUID-51BD0186-50BF-4D0D-8410-79F165918B16.html
    i see
    "--forceunsupportedinstall
    Blocks the installation of deprecated CPUs."
    and you
    "--forceunsupportedinstall - Will ignore error/warning messages for deprecated CPUs"

    Who is right? What can i trust?
    Thank you!

    Reply
    • William Lam says

      10/14/2024 at 1:50 pm

      Me 🙂

      I’ve actually tested these scenarios and these flags are overrides, not “blocking”, so probably miss-understanding on docs

      Reply

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • VMware Flings is now available in Free Downloads of Broadcom Support Portal (BSP) 05/19/2025
  • VMUG Connect 2025 - Minimal VMware Cloud Foundation (VCF) 5.x in a Box  05/15/2025
  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025

 

Loading Comments...