WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple
You are here: Home / Automation / Quick Tip - Changes to building custom ESXi images in vSphere 8

Quick Tip - Changes to building custom ESXi images in vSphere 8

11.03.2022 by William Lam // 2 Comments

Historically, when a new version of ESXi is released, customers will use vSphere Image Builder either through the vSphere Image Builder UI or PowerCLI Image Builder cmdlets to create a custom ESXi image to include additional drivers such as the USB Network Native Driver for ESXi Fling.

Note: The current version of the USB Network Native Driver for ESXi Fling is not compatible with ESXi 8.0 and a new version of the driver will be needed. There is currently no ETA on when a new version will be available.

Typically, customers will use their existing vCenter Server deployment, which is usually running an older version to create their new custom ESXi image. This means you are importing a newer ESXi release into your vCenter Server or in the case of the PowerCLI Image Builder cmdlets, you are using an older release of PowerCLI. While this may have worked with previous releases, the assumption that vSphere Image Builder is "forward" compatible with future releases of ESXi is actually an incorrect assumption that many have made, including myself.

I bring this up because in vSphere 8, there have been changes in ESXi where this incompatibility will be observed when attempting to create a custom ESXi 8.0 image using a non-compatible vCenter Server or a PowerCLI release.

This is also the reason you do not see an ESXi 8.0 Image in the vSphere Lifecycle Manager (vLCM) depot by default for those running vSphere 7.x as it understands this incompatibility and will also prevent you from importing an ESXi 8.0 Image Profile.

However, if you use Image Builder (UI or PowerCLI) in a vSphere 7.x environment, which will allow you to import ESXi 8.0 Image Profile, but it does not understand this incompatibility and you will still run into issues with following errors:

is claimed by multiple non-overlay VIBs


To properly create a custom ESXi 8.0 image, you will need to either use a vCenter Server that is already running vSphere 8.0 or wait for an upcoming PowerCLI (12.8) release that will be compatible with vSphere 8 for those that do not have an existing vCenter Server.

Lastly, since there have been some questions about the size of the ESXi 8.0 Image Profile / ISO, here is a quick tidbit on the reason for that:

The ESXi 8.0 ISO / Offline Bundle is larger because it contains BOTH the x86 and Arm bits (latter for running vSphere Distributed Service Engine). You can identify the Arm VIBs by looking for "esxio" in the filenames

— William Lam (@lamw.bsky.social | @*protected email*) (@lamw) October 28, 2022

Note: It is currently NOT supported to create a custom ESXi 8.0 image that only contains the x86 VIBs, this will impact future upgrades as there are built-in pre-checks to ensure all VIBs (x86 and Arm) are contained within your installation.

More from my site

  • USB Network Native Driver Fling for ESXi 8.0 Update 1
  • 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 
  • Heads Up - Unable to open VIB archive in streaming mode using Export-EsxImageProfile with PowerCLI 13.0

Categories // Automation, ESXi, vSphere 7.0, vSphere 8.0 Tags // ESXi 8.0, image builder, vSphere 8.0

Comments

  1. *protectedparambil says

    11/03/2022 at 5:42 pm

    Thanks William. Ran into the same issue today and opened a case. Looks like I will have to wait until the PowerCLI 12.8 release 🙁

    Reply
  2. *protectedTom says

    11/08/2022 at 12:50 am

    [quote]The current version of the USB Network Native Driver for ESXi Fling is not compatible with ESXi 8.0 and a new version of the driver will be needed. There is currently no ETA on when a new version will be available.[/quote]

    Well bummer. That's what I'm waiting for.

    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...