<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>vSphere on Why did IT fail</title><link>https://www.why-did-it.fail/tags/vsphere/</link><description>Recent content in vSphere on Why did IT fail</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2026 Dominik Textoris (formerly Zorgnotti). All Rights Reserved.</copyright><lastBuildDate>Fri, 26 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.why-did-it.fail/tags/vsphere/index.xml" rel="self" type="application/rss+xml"/><item><title>ESX HCL Checker</title><link>https://www.why-did-it.fail/blog/2026-06-esx-hcl-checker/main/</link><pubDate>Fri, 26 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2026-06-esx-hcl-checker/main/</guid><description>On LinkedIn I just posted this:
On your way to update your VCF/vSphere environment (perhaps to VCF 9.1?) but tired of manually checking each component in your vCenter again the Broadcom compatibility guide? This is a situation I often hear from my customers and I can totally relate to this.
Before You Upgrade, Someone Has to Check the Hardware
Every vSphere or VCF upgrade comes with the same prerequisite: verify that your host hardware — CPUs, NICs, HBAs, SSDs — is certified for the target release.</description></item><item><title>vSphere 8 Update 3 - What is the "Retain virtual NUMA topology"-feature</title><link>https://www.why-did-it.fail/blog/2024-03-vsphereu3-vnuma-retain/</link><pubDate>Mon, 08 Jul 2024 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2024-03-vsphereu3-vnuma-retain/</guid><description>_ Credits: I would like to thank my colleague Vladimir Petrov from the VCF BU for providing me with additional information that allowed me to write this summary _
The vSphere 8 Update 3 release notes contain lots of changes, but one of them caught my attention:
Cluster-wide option to retain virtual NUMA topology: vSphere 8.0 Update 3 adds a setting to retain preconfigured vNUMA topology even if the VM moves, allowing for better NUMA topology tuning for VMs across all the hosts in the cluster.</description></item><item><title>Hey dude, why is the EVC mode for my virtual machine going wild</title><link>https://www.why-did-it.fail/blog/2024-02-hey-dude-why-is-evc-mode-going-crazy/</link><pubDate>Thu, 04 Jul 2024 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2024-02-hey-dude-why-is-evc-mode-going-crazy/</guid><description>_ Disclaimer: This blog has been created to the best of my knowledge and understanding. If I need to correct a statement, I will mark that accordingly in a future update. _
_ Credits: I would like to thank our colleagues from the VCF BU for their support and patience with me, Ellen Mai from the PM team and especially Ross Knippel from the development side. Also, thanks to Thomas Thimm, Pascal Hanke, and Michael Hempel for testing things out.</description></item><item><title>Thanks to U3</title><link>https://www.why-did-it.fail/blog/2023-03-vcenter8-ciphers/</link><pubDate>Fri, 22 Sep 2023 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2023-03-vcenter8-ciphers/</guid><description>Update on 2024-08-15:
Good news, with vSphere 8 update 3 the previous content became obsolte and I decided to take it offline and adjust the content here
Update 3 contains some major enhancements which makes the life in this regards much easier:
Starting in 8.0 Update 3, vSphere supports TLS 1.3 and 1.2 through the use of TLS profiles. TLS profiles simplify the job of administering TLS parameters and also improve supportability.</description></item><item><title>Howto - Query host Driver and Firmware via vCenter API</title><link>https://www.why-did-it.fail/blog/2022-05-how-to-query-hcl-api/</link><pubDate>Wed, 12 Oct 2022 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2022-05-how-to-query-hcl-api/</guid><description>Yet again, customer questions make the best blog posts. This time, it&amp;rsquo;s about retrieving the firmware and drivers from an ESXi host.
So far, the customer uses esxcli which required either PowerCLI or direct SSH access, both were not the preferred choices in this case.
High-level overview Starting with vSphere 7, vSphere Lifecycle Manager (vLCM) can handle this task. This blog post will show you how to create a HCL report for a given host which contains all the required information about firmware and drivers, as well as the bonus information about the support status of the system and devices.</description></item><item><title>Howto - Attach an ISO file from a Content Library</title><link>https://www.why-did-it.fail/blog/2022-04-howto-attatch-clib-iso/</link><pubDate>Thu, 14 Jul 2022 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2022-04-howto-attatch-clib-iso/</guid><description>A few days ago I was asked by a customer on how to attach an ISO file to a VM using RestAPI calls in the vCenter. Having never done this before I had a look at the problem today and want to share the steps with you.
High-level overview Assuming you uploaded the ISO file to the content library prior to reading this, you need to obtain three information before you can attach an ISO file:</description></item><item><title>Tagging the vCenter (object)</title><link>https://www.why-did-it.fail/blog/2021-03-tag-vcenter-object/</link><pubDate>Tue, 16 Mar 2021 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2021-03-tag-vcenter-object/</guid><description>I am working on enhancing my vSphere release tagging script with the ability to tag the vCenter with a human-readable release name. As shown in the screenshot, it&amp;rsquo;s easy enough in the UI.
Tags applied to the vCenter in the UI However, in PowerCLI there is no commandlet like get-vcenter. After many tries I gave up trying to force the object returned from
$global:DefaultVIServers[0] to accept any tag-related operations. Today, I had the idea of working backwards from the assigned tags with Get-TagAssignment</description></item><item><title>Tagging ESXi hosts with canonical release names</title><link>https://www.why-did-it.fail/blog/2021-02-set-esxi-release-names-with-tags/</link><pubDate>Fri, 05 Mar 2021 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2021-02-set-esxi-release-names-with-tags/</guid><description>Update [2022-10-17] The VMware APIs for the KnowledgeBase have introduced a breaking change. This means the releases can no longer be updated without further development.
Update [2021-03-09] The repository has been renamed to VMware-vSphere-Release-Tagging as the future scope should include the vCenter as well. Thank you for all the feedback!
In this blog post I want to show you a practial application for the automation that I have built in my last project:</description></item><item><title>Automating vSphere template builds with a pipeline - IV</title><link>https://www.why-did-it.fail/blog/2020-05-automating-templates-part4/</link><pubDate>Tue, 04 Feb 2020 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2020-05-automating-templates-part4/</guid><description>This is the fourth part in a multi-part series about the automation of VMware vSphere template builds. A template is a pre-installed virtual machine that acts as master image for cloning virtual machines from it. In this series I am describing how to get started on automating the process. As I am writing these blog post while working on the implementation some aspects may seem &amp;ldquo;rough around the edges&amp;rdquo;.
Part 1: Overview/Motivation Part 2: Building a pipeline for a MVP Part 3: An overview of packer Part 4: Concourse elements and extending the pipeline The focus in this part are the concourse basics.</description><enclosure url="https://www.why-did-it.fail/blog/2020-05-automating-templates-part4/feature.png" length="40551" type="image/png"/></item><item><title>Automating vSphere template builds with a pipeline - III</title><link>https://www.why-did-it.fail/blog/2020-05-automating-templates-part3/</link><pubDate>Thu, 23 Jan 2020 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2020-05-automating-templates-part3/</guid><description>This is the third part in a multi-part series about the automation of VMware vSphere template builds. A template is a pre-installed virtual machine that acts as master image for cloning virtual machines from it. In this series I am describing how to get started on automating the process. As I am writing these blog post while working on the implementation some aspects may seem &amp;ldquo;rough around the edges&amp;rdquo;.
Part 1: Overview/Motivation Part 2: Building a pipeline for a MVP Part 3: An overview of packer Part 4: Concourse elements and extending the pipeline If all went well, part 2 left you with a functional Ubuntu template.</description></item><item><title>Automating vSphere template builds with a pipeline - II</title><link>https://www.why-did-it.fail/blog/2020-05-automating-templates-part2/</link><pubDate>Tue, 21 Jan 2020 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2020-05-automating-templates-part2/</guid><description>This is the second part in a multi-part series about the automation of VMware vSphere template builds. A template is a pre-installed virtual machine that acts as master image for cloning virtual machines from it. In this series I am describing how to get started on automating the process. As I am writing these blog post while working on the implementation some aspects may seem &amp;ldquo;rough around the edges&amp;rdquo;.
Part 1: Overview/Motivation Part 2: Building a pipeline for a MVP Part 3: An overview of packer Part 4: Concourse elements and extending the pipeline This part will focus on getting you started with a minimum viable product by building a single Ubuntu 18.</description><enclosure url="https://www.why-did-it.fail/blog/2020-05-automating-templates-part2/feature.png" length="56539" type="image/png"/></item><item><title>Automating vSphere template builds with a pipeline - I</title><link>https://www.why-did-it.fail/blog/2020-05-automating-templates-part1/</link><pubDate>Sun, 19 Jan 2020 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2020-05-automating-templates-part1/</guid><description>This is a multi-part series about the automation of VMware vSphere template builds. A template is a pre-installed virtual machine that acts as master image for cloning virtual machines from it. In this series I am describing how to get started on automating the process. As I am writing these blog post while working on the implementation some aspects may seem &amp;ldquo;rough around the edges&amp;rdquo;.
Part 1: Overview/Motivation Part 2: Building a pipeline for a MVP Part 3: An overview of packer Part 4: Concourse elements and extending the pipeline If you want to know more about the topic here is an awesome blog series about automated template management from Eric Lee - many thanks to Timo Sugliani for the recommendation.</description><enclosure url="https://www.why-did-it.fail/blog/2020-05-automating-templates-part1/feature.png" length="55278" type="image/png"/></item><item><title>An overview of the vSphere MAC address space</title><link>https://www.why-did-it.fail/blog/2019-05-vsphere-mac-address-space/</link><pubDate>Mon, 07 Oct 2019 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2019-05-vsphere-mac-address-space/</guid><description>Recently another TAM requested some infos on this topic in VMware’s slack, finally giving me the push to publish as I had this post for ages in my drafts. Given, it is somewhat of an edge case for only a hand full of customers and the problem itself is not new but here is my take. As always please do your own research before you put this untested into production.</description></item></channel></rss>