WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
    • VMware Cloud Foundation 9.1
    • VMware Cloud Foundation 9.0
  • VKS
  • Homelab
    • Hardware Options
    • Hardware Reviews
    • Lab Deployment Scripts
    • Nested Virtualization
    • Homelab Podcasts
  • VMware Nostalgia
  • Apple

vSphere 8 on Apple Mac Hardware

10.10.2022 by William Lam // 55 Comments

While vSphere 7.x is the last vSphere release to officially support Apple MacOS Virtualization running on ESXi, my own curiosity got the best of me and I was just curious if ESXi 8.0 could still run on recent Apple Mac Hardware ...

Disclaimer: VMware does NOT officially support running ESXi 8.0 on Apple Hardware nor Apple MacOS Virtualization using vSphere 8, this is purely for educational and informational purposes. Please use at your own risk.

Attempting to boot the ESXi 8.0 installer on an Apple Mac Mini 8,1 (2018) will halt the installer and result in the following exception.


UPDATE (07/26/23) - ESXi 8.0 Update 1a installs fine on an Apple Mac Mini 5,3 (2011), but you will need to ensure you have Apple Thunderbolt 2 network adapter as ESXi no longer supports the onboard adapter. You also will need to append an additional ESXi boot option (SHIFT+O) allowLegacyCPU=true to by pass the CPU check.

UPDATE (10/11/22) - Thanks to user psm (MacAdmins Slack Group) for sharing ESXi 8.0 works on Apple Mac Mini 7,1 (2014)✅ and reader Jon (left comment) that ESXi 8.0 works on Apple Mac Pro 7,1 (2019)✅

[Read more...]

Categories // Apple, vSphere 8.0 Tags // apple, ESXi 8.0, mac mini, vSphere 8.0

Is the vCenter Server Unique ID still important today?

10.05.2022 by William Lam // 4 Comments

When I was a customer back in the day, one of my operational checklist items for deploying a vCenter Server was to configure the vCenter Server ID and ensure that it was unique from other vCenter Servers within my environment.


The vCenter Server ID is a value between 0-63 that is randomly generated by default, but it can updated by a user after the vCenter Server has been deployed.

Why should you care about the vCenter Server ID? vCenter Server uses this ID to generate Virtual Machine MAC Addresses and if two vCenter Servers have the same ID, it can potentially generate duplicate VM MAC Addresses as explained in this VMware KB 1024025.

With this background in mind, is having a unique vCenter Server ID still relavent and applicable today in 2022?

[Read more...]

Categories // vSphere 7.0, vSphere 8.0 Tags // vCenter Server, vSphere 5.5

How to deploy the vCenter Server Appliance (VCSA) 8.0 to VMware Fusion or Workstation?

10.04.2022 by William Lam // 55 Comments

VMware Fusion and Workstation continues to be another popular way for customers to run a VMware Homelab while leveraging a users existing desktop. In the early days of vSphere 6.5, the method to deploy the vCenter Server Appliance (VCSA) to Fusion/Workstation was less than ideal with a lot of manual steps. In 2017, the Fusion/Workstation team introduced native OVF support and that made deploying the VCSA much simpler, especially with the VCSA two stage installer.

Even though this is not an officially supported method from VMware for deploying the VCSA, the process has not changed for the last several releases and it just works which was great for our users. With vSphere 8, it looks like there has been a change to the VCSA installer that causes a failure during the Stage 2 configuration.


I was made aware of this issue from a colleague who was looking to setup a vSphere 8 environment using VMware Workstation.

Taking a look at the log file, he noticed the error was regarding the upgrade.import.directory OVF property not being set, which seems to be causing the issue.

# cat /var/log/firstboot/vlcm_firstboot.py_9117_stderr.log
Traceback (most recent call last):
  File "/usr/lib/vmware-vlcm/firstboot/vlcm_firstboot.py", line 167, in <module>
    main()
  File "/usr/lib/vmware-vlcm/firstboot/vlcm_firstboot.py", line 129, in main
    fb = VlcmFirstboot(VLCM_COMP, VLCM_SOLUSERNAME)
  File "/usr/lib/vmware-vlcm/firstboot/vlcm_firstboot.py", line 50, in __init__
    os.path.join(get_install_parameter('upgrade.import.directory'), "vlcm")
  File "/usr/lib/vmware/site-packages/cis/tools.py", line 88, in get_install_parameter
    raise InstallParameterException('Install-parameter %s not set' % param)
cis.exceptions.InstallParameterException: {
    "detail": [
        {
            "id": "install.ciscommon.internal.error",
            "translatable": "Encountered an internal error.\n\n%(0)s",
            "args": [
                "Install-parameter upgrade.import.directory not set"
            ],
            "localized": "Encountered an internal error.\n\nInstall-parameter upgrade.import.directory not set"
        }
    ],
    "componentKey": null,
    "problemId": null,
    "resolution": {
        "id": "install.default.failure.resolution",
        "translatable": "This is an unrecoverable error, please retry install. If you encounter this error again, please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request.",
        "localized": "This is an unrecoverable error, please retry install. If you encounter this error again, please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request."
    }
}

Using one of my previous blog post for guidance, he discovered a quick workaround to the problem by simply ensuring this variable is configured with a default value. After running into the problem myself and verifying the solution, I figure this might be useful for anyone looking to run vSphere 8 using VMware Fusion or Workstation, so here are the instructions to work around this issue.

Disclaimer: This is not officially supported by VMware, use at your own risk
[Read more...]

Categories // Fusion, Home Lab, vSphere 8.0, Workstation Tags // fusion, VCSA, vSphere 8.0, workstation

  • « Previous Page
  • 1
  • …
  • 38
  • 39
  • 40
  • 41
  • 42
  • …
  • 44
  • Next Page »

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

  • What Host Lifecycle Operations Are Available after Importing vCenter into VCF 9.x Fleet? 06/24/2026
  • VCF 9.1 - Enabling High Availability for a Small VCF Management Services (VCFMS) Deployment 06/22/2026
  • Clarifying Minimum Required ESX Hosts for VCF Deployments 06/18/2026
  • VCF 9.1 - Auditing VCF Management Services (VCFMS) IP Pool Usage  06/17/2026
  • VCF 9.1 - Auditing vCenter Server Connections using the Connection Utilization API 06/15/2026
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 © 2026

Loading Comments...