WilliamLam.com

Search Results for: NUC

Quick Tip - TPM 2.0 connection cannot be established after upgrading to ESXi 8.0

by // 12 Comments

There has been several reports from folks internally and within the community that after upgrading to ESXi 8.0, they are now seeing the following TPM error message:

TPM 2.0 device detected but a connection cannot be established.


The common theme between all these reported cases that I have seen is that they are all using an Intel NUC. While the Intel NUCs may list TPM support, they do not support either TPM Interface Specification (TIS) for TPM 1.2 or the First In, First Out (FIFO) for TPM 2.0, which are industry standards for communicating with a TPM device that ESXi uses.

[Read more...]

Quick Tip - Automating ESXi 8.0 install using allowLegacyCPU=true

by // 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?

[Read more...]

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

by // 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...]