2024 – Time to say goodbye to cherished resources at VMware

For years I have been teaching students in my VMware courses to memorize only a few important URLs.

  • docs.vmware.com
  • configmax.vmware.com
  • VMware HCL
  • core.vmware.com

Following the takeover by Broadcom, there are understandable changes here. We take a look at where the individual sources of information have gone and which ones remain available.

Goodbye Docs – Hello Techdocs

If you visit the VMware Docs page today (December 2024), the following information catches your eye:

After December 31, 2024, the site will go offline and in future information will have to be obtained via the Broadcom Techdocs site. Here you will not only find VMware information, but documents on almost all products that Broadcom has in its portfolio. Don’t bother scrolling down to the letter “V”. That is a waste of time. Instead, type in the name of the product you are looking for.

PDF Export?

One feature that I really appreciated about the previous VMware documentation was the pleasantly readable HTML continuous text, the clearly structured outline and the optional export of the documentation as a PDF.

The continuous text and the outline are available in the Techdocs portal, but the download as PDF is missing. Maybe the link exists and I just haven’t found it yet. If someone finds it -> please send an info in the comments.

Configmax

The link to configmax.vmware.com no longer works at all. Instead of a redirect, there is only a timeout. Too bad.

The new resource can be accessed at https://configmax.broadcom.com.

Fortunately, it looks exactly the same as before – only the TLD has changed.

VMware HCL

The VMware Host Compatibility List (HCL) has always been the central point of contact in cluster design. Where has it gone? It is no surprise that it has also been migrated under the Broadcom TLD. The new URL is https://compatibilityguide.broadcom.com

The dashboard for selecting the different Compatibility Guides is a little clearer compared to the old HCL. At the top level, we have a quick selection grouped according to application areas.

What else is (still) available

When it came to design guides, the URL core.vmware.com used to be an important starting point. If you follow the URL, you come to the VMware Resource Center. At least a redirect has been set here. The navigation is somewhat cumbersome and the search field is not very helpful. Unless you know the name of the document you are looking for. The naming of the products is also not intuitive. NSX, for example, can be found under “Networking by NSX” and vSAN under “Storage by vSAN“. Sometimes you have to play with the product filters and asset types to get to the desired destination.

I was pleased to see that the URL code.vmware.com is still accessible and filled with content. We’ll see how long.

As the above-mentioned resources are still under the vmware.com TLD, it will only be a matter of time before they move to the broadcom.com TLD.

Early-Bird Registration for VMware Explore 2024 Barcelona is open

VMware (by Broadcom) Explore 2014 will take place this year from November 4-7 in Barcelona. The pre-sale for tickets started on June 25.

The early bird discount will be valid until July 29. After that, ticket prices will increase in several stages.

VMUG Advantage Discount

If you are a member of VMUG Advantage, you can get a discount of 75 $. Look up your discount code in the VMUG portal and enter it as a voucher when ordering your ticket.

ESXi Boot Media – New Requirements for v8

The requirements for ESXi boot media have changed fundamentally with ESXi v7 Update3. Partitioning has been changed and the requirements for the load capacity of the medium have also increased. I covered this in my blog article “ESXi Bootmedia – New features in v7 und legacy issues from the past v6.x“.

USB boot media did not turn out to be robust enough and were therefore no longer supported from v7U3 onwards. It is still possible to install ESXi on USB media, but the ESX-OSData partition needs to be redirected to permanent storage.

Warning! USB media and SD cards should not be used for production ESXi installations!

Valid setup targets for ESXi deployments

SD cards and USB media are unsuitable as installation targets due to their poor write endurance. Magnetic discs, SSDs and SATA DOMs (disc-on-modules) are still permitted and recommended.

SATA-DOM on a Supermicro E300-9D

New requirements from version ESXi v8 onwards

My Homelab previously used vSAN 7 and thus the classic OSA architecture. To run the cluster under the new vSAN ESA architecture, it was necessary to use vSphere 8 and new storage devices.

I tested the installation and hardware compatibility on a 64 GB USB medium (not recommended and not supported!). During the installation, there were warnings regarding the USB medium as expected. Nevertheless, I was able to successfully test the detection of the NVMe devices and the vCenter deployment.

Setup warning when trying to use an USB flash medium.

Having successfully completed the test phase, I installed ESXi 8U2 on the SATA DOM of my Supermicro E300 server. To my surprise, the setup failed at a very early stage with the message: “disk device does not support OSDATA“.

RTFM

The explaination is simple: “Read the fine manual!”

My 16 GB SATA DOM from Supermicro was simply too small.

The setup guide for ESXi 8 clearly states the requirements under “Storage Requirements for ESXi 8.0 Installation or Upgrade“:

For best performance of an ESXi 8.0 installation, use a persistent storage device that is a minimum of 32 GB for boot devices. Upgrading to ESXi 8.0 requires a boot device that is a minimum of 8 GB. When booting from a local disk, SAN or iSCSI LUN, at least a 32 GB disk is required to allow for the creation of system storage volumes, which include a boot partition, boot banks, and a VMFS-L based ESX-OSData volume. The ESX-OSData volume takes on the role of the legacy /scratch partition, locker partition for VMware Tools, and core dump destination.

VMware vSphere product doumentation

In other words: New installations will require a boot medium of at least 32 GB (128 GB recommended) and upgrading from an ESXi v7 version will require at least 8 GB, but the OSData partition of this installation must already be redirected to an alternate storage device.

Dirty Trick?

Needless to say, I tried a dirty trick. I first successfully installed an ESXi 7U3 on the 16 GB SATA DOM and then performed an upgrade installation to v8U2. This attempt also failed, as the OSData area was not redirected in the fresh v7 installation.

I don’t want to install on USB media as I have seen too many cases where these devices have failed. The only option is to invest in a larger SATA DOM.

I opted for the 64 GB model because it is a good compromise between minimum requirements and cost-effectiveness.