WilliamLam.com

How to replace some of ESXi Kickstart automation with new configstorecli commands?

by // 2 Comments

I had received a question a couple of weeks back from a customer who was already automating their ESXi installation using ESXi Kickstart, also known as ESXi Scripted Installation but they had ran into an issue when migrating the exact same automation to the latest ESXi 7.0 releases.

The method the customer was using to manage their ESXi password policies, which was by updating the /etc/pam.d/passwd file, no longer function as expected and this was a result of the introduction of the ESXi ConfigStore, which I have written about here.

As mentioned in the article, the goal of the ESXi ConfigStore is the following:

The goal of the ConfigStore, initially introduced in ESXi 7.0 Update 1, is to centrally manage all configurations for an ESXi host instead of relying on different methods including a variety of configuration files.

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

Quick Tip - Using ESXi Scripted Installation (kickstart) to configure IPv6 networking

by // 5 Comments

I have written numerous articles on the topic of ESXi Scripted Installation aka Kickstart, which is just one of the many options that enables customers to fully automate the installation and configuration of their ESXi hosts. An interesting question that recently came up internally was whether you could configure ESXi networking using IPv6, rather than IPv4 using the default ESXi Kickstart network parameters?

If you look at the ESXi network params as they are labeled such as netmask, it would seem that these are only applicable to IPv4. Although my personal experience has been exclusively IPv4, I figure I would take a quick look at the python code which powers the ESXi Kickstart infrastructure which is located under /usr/lib/vmware/weasel directory. Although I am not a Developer, from what I could grok, it seems like IPv6 might actually be possible using these exact same parameters.

Using Nested ESXi and the new vSphere 7.0 Update 2 feature HTTP Boot over virtual EFI, I was able to setup a quick prototype to validate that you can indeed configure IPv6 using the same ESXi networking parameters, which are applicable to both IPv4 and IPv6.

[Read more...]