Tag: vSphere Page 1 of 2

Enable Memory Tiering over NVMe in ESXi 8.0 U3

As I have access to a new, fresh lab server with a spare NVMe SSD, I’ve installed ESXi 8.0 U3 on this server (see my previous blog post) to make use of a new feature called “Memory tiering over NVMe”.

“Memory tiering over NVMe” is a feature in Technical Preview that allows users to add memory capacity to a host by using NVMe devices that are installed locally in the host.

The feature utilizes the NVMe devices as tiered memory and reduces the impact to performance by intelligently choosing which VM memory locations should be stored in the slower NVMe device vs faster DRAM in the host.

In this post, I’ll briefly explain how to setup this feature.

Upgrade ESXi using vSphere Lifecycle Manager

With the introduction of vSphere 8, vSphere Lifecycle Manager baselines (VUM) have been deprecated. We can instead manage the lifecycle of the ESXi hosts in our environment by using “desired” images (vLCM).

In this post, we’ll upgrade an ESXi 7 host to ESXi 8 using a vLCM image.

Setup a vSphere image factory with Hashicorp Packer and Gitlab CI

Updating OS images in a cloud infrastructure is often a tedious and manual task. HashiCorp Packer makes this easier and leveraging CI/CD tools help us to build a strong centralized image pipeline.

In this blog post, I’ll demonstrate how to easily configure Packer to build OS images for Ubuntu Linux and Microsoft Windows Server and how to save these images in an image repository. To automate this build and deploy process, the Packer configuration will be stored in a SCM system, and builds will be automatically triggered using a CI pipeline.

How to resolve unavailability of vSphere Cluster Service VMs

Recently, I wanted to create a new provider VDC with a vSphere cluster as resource pool in a customer VMware Cloud Director environment. It failed with the error message “[ … ] class com.vmware.vcloud.api.presentation.service BadRequestException”.

While checking the cluster in the resource vCenter Server (version 7.x), the following error was shown in the vSphere Client:

“vSphere DRS functionality was impacted due to unhealthy state vSphere Cluster Services caused by the unavailability of vSphere Cluster Service VMs. vSphere Cluster Service VMs are required to maintain the health of vSphere DRS”

Deploying the vCenter Server Appliance 8.0.0 to VMware Cloud Director

Recently, I needed to deploy VCSA 8.0.0 in a VMware Cloud Director environment, which initially ended up with the following cryptic error message when trying to import the VCSA OVA file from the installer ISO into a VCD vApp template:

Error: Validation failed for the OVF file you provided: Fatal: Line/char 578/96: cvc-minInclusive-valid: Value ‘-100’ is not facet-valid with respect to minInclusive ‘0’ for type ‘unsignedShort’.

Although not officially supported by VMware, I came up with the following solution: Replace the mentioned value with a valid one in the OVF file as an unsigned short data type cannot have a negative value, i.e. it must be in the range of 0 to 65535. Thus, we’ll simply remove the sign from the value and store it as “100” in the OVF file.

Page 1 of 2

All your base are belong to us.