WilliamLam.com

ESXi on Intel NUC 11 Extreme (Beast Canyon)

by // 8 Comments


The NUC 11 Extreme (codenamed Beast Canyon) is the latest in Intel's Tiger Lake based NUC lineup which includes the NUC 11 Performance (Panther Canyon), NUC 11 Enthusiast (Phantom Canyon) and NUC 11 Pro (Tiger Canyon). As you can see from the picture above, the codename for the NUC 11 Extreme is quite fitting as this is currently the largest "NUC" that Intel has built to date, coming in at 8L. Yes, this is definitely "stretching" the NUC label in terms of what folks historically expect but I believe Intel is simply expanding on their well known NUC brand, especially as there are also NUC laptops.

However, this is also not the first time Intel has explored a larger NUC design. In 2020, Intel introduced the NUC 9 Pro (Quartz Canyon) and Extreme (Ghost Canyon) which took advantage of the new NUC Compute Element and enabled a new modular design and form factor adding support for discrete GPU and PCIe expandability. As a successor to the NUC 9, the NUC 11 Extreme extends this concept further by adding support for a full length discrete GPU, which is the primary driver for the larger form factor.

The NUC 11 Extreme can also enhance your homelab experience with LED lights which are located underneath the chassis and on the front with the classic Intel NUC Skull. Even cooler, the design in the front is customizable and can be user replaced with a different graphic. For an example of what this could look like, jump down to the customizable logo section of this blog post 🙂

I know there are a number of folks in the VMware community who are currently using the NUC 9 for their VMware Homelab, especially for those with GPU and/or additional network and storage requirements. Let's now take a closer look at what the NUC 11 Extreme has to offer the VMware Community.

[Read more...]

Introduction to the new ESXi Configuration Store CLI (configstorecli)

by // 8 Comments

I was looking into a customer inquiry this morning and found myself looking at the configstorecli, which is an ESXi Shell CLI that enables access to the new ESXi Configuration Store (ConfigStore). 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. There is actually not much documentation out there for configstorecli, other than this blog post by Duncan and these two VMware KBs (here and here).

While searching online, I ended up clicking Duncan's blog as I figured it probably has the best information and I do recall this topic awhile back on the change in behavior for renaming a standard virtual switch. I started to play with the configstore CLI and what was not immediately clear was how to actually use it, especially identifying some of the parameters it was looking for. I figured I might as well share some of my findings as I explore configstorecli a bit more.

My first observation is that the Config Store is a JSON document store and each configuration is stored as individual JSON documents. Before you can access a specific configuration, you first need to understand the schema. To view the entire schema, run the following command:

configstorecli schema list

Since the output is JSON, you can actually save the contents to a file on your desktop and use any JSON supported tool such as jq to explore further. In the example below, I have loaded an online copy of the configstorecli output from ESXi 7.0 Update 2 using my Chrome browser, which has this JSON Viewer extension installed. The benefit with a visual tool, is that you can easily expand or collapse specific nodes within the JSON document.

[Read more...]

New storage devices added to Community NVMe Driver for ESXi Fling

by // 8 Comments

We have an exciting update for the VMware Community today with the release of the Community NVMe Driver for ESXi Fling v1.1. After the release of ESXi 6.7, a number of consumer NVMe devices were no longer bering detected which had previously worked with ESXi 6.5.

One workaround that many folks had to implement, including myself, was to replace the 6.7 NVMe driver. with the previous 6.5 version of the NVMe driver. Although this method still works with the latest ESXi 7.0 Update 2, it is less than ideal as you are using an extremely old version of the NVMe driver and you are giving up new NVMe device enablement, bug fixes and enhancements with the latest version of the driver.

Given the amount of comments and feedback that I had received in the previous blog post, I wanted to explore a way in which we can enable some of these consumer NVMe devices for the community. With the help from Yibo, we have updated the Community NVMe Driver for ESXi Fling to include support for the following storage devices:

[Read more...]