<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Homelab on MichelleWayZ | Michelle Goossens | Blog</title><link>https://blog.michellewayz.com/categories/homelab/</link><description>Recent content in Homelab on MichelleWayZ | Michelle Goossens | Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2019-2026, Michelle Goossens.</copyright><lastBuildDate>Mon, 27 Jul 2026 16:45:00 +0000</lastBuildDate><atom:link href="https://blog.michellewayz.com/categories/homelab/index.xml" rel="self" type="application/rss+xml"/><item><title>A New Start - With an update</title><link>https://blog.michellewayz.com/a-new-start-with-an-update/</link><pubDate>Mon, 27 Jul 2026 16:45:00 +0000</pubDate><guid>https://blog.michellewayz.com/a-new-start-with-an-update/</guid><description>
&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;As part of my rebrand from an old domain I've had for many years to a new one that fits my identity better, I've succesfully migrated the blog to a new domain and new backend (it runs on a self-hosted Kubernetes cluster now).
I've left a redirect in place, however please do try to update any URLs you might have from blog.masterwayz.nl to &lt;a href="https://blog.michellewayz.com"&gt;https://blog.michellewayz.com&lt;/a&gt;, as this will be the new URL going forward.&lt;/p&gt;</description></item><item><title>Quick Lab Tip: Deploy VCF workload domain with single NSX Manager</title><link>https://blog.michellewayz.com/quick-lab-tip-deploy-vcf-wld-single-nsx-manager/</link><pubDate>Thu, 03 Apr 2025 14:00:00 +0000</pubDate><guid>https://blog.michellewayz.com/quick-lab-tip-deploy-vcf-wld-single-nsx-manager/</guid><description>
&lt;p&gt;In this post I will share a quick tip on how I've managed to deploy a VCF Workload Domain with a single NSX Manager, instead of the standard three.&lt;/p&gt;
&lt;div class="notice warning" &gt;
&lt;p class="notice-title"&gt;
&lt;span class="icon-notice baseline"&gt;
&lt;svg xmlns="http://www.w3.org/2000/svg" viewBox="126 76.5 300 300"&gt;
&lt;path d="M297.431 324.397v-34.255c0-3.245-2.344-5.95-5.358-5.95h-32.146c-3.014 0-5.358 2.705-5.358 5.95v34.255c0 3.245 2.344 5.95 5.358 5.95h32.146c3.014 0 5.358-2.705 5.358-5.95Zm-.335-67.428 3.014-82.753c0-1.081-.502-2.524-1.674-3.425-1.005-.902-2.512-1.983-4.019-1.983h-36.834c-1.507 0-3.014 1.081-4.019 1.983-1.172.901-1.674 2.704-1.674 3.786l2.846 82.392c0 2.344 2.512 4.146 5.693 4.146h30.975c3.013 0 5.525-1.803 5.692-4.146Zm-2.344-168.39L423.34 342.425c3.683 7.032 3.516 15.686-.335 22.717-3.85 7.031-10.883 11.358-18.417 11.358H147.413c-7.534 0-14.566-4.327-18.417-11.358-3.85-7.031-4.018-15.685-.335-22.716L257.248 88.578C260.93 81.188 268.13 76.5 276 76.5c7.87 0 15.069 4.688 18.752 12.08Z"/&gt;
&lt;/svg&gt;
&lt;/span&gt;Warning&lt;/p&gt;</description></item><item><title>Fixing missing component(s) nmlx5 during vib update</title><link>https://blog.michellewayz.com/esxi-nmlx5-vib-prevents-update/</link><pubDate>Sat, 23 Nov 2024 16:11:00 +0000</pubDate><guid>https://blog.michellewayz.com/esxi-nmlx5-vib-prevents-update/</guid><description>
&lt;p&gt;Recently while I was trying to update a new homelab server from ESXi 8 to ESXi 8 U3b using the command &lt;code&gt;esxcli software vib update --depot=/vmfs/volumes/&amp;lt;datastore&amp;gt;/depot.zip&lt;/code&gt;, I stumbled upon the following error: &lt;code&gt;Profile &amp;lt;&amp;gt; is missing component(s) ESXi,Mellanox-nmlx5&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;After trying to remove the installed VIBs (that are for Mellanox cards, I do not have any) using &lt;code&gt;esxcli software vib list | grep nml&lt;/code&gt;, and then &lt;code&gt;esxicli software vib remove &amp;lt;vib name&amp;gt;&lt;/code&gt;, the issue still occured.&lt;/p&gt;</description></item><item><title>Fixing slow vService Manager</title><link>https://blog.michellewayz.com/fixing-vservice-manager-stuck/</link><pubDate>Sat, 03 Feb 2024 20:03:00 +0000</pubDate><guid>https://blog.michellewayz.com/fixing-vservice-manager-stuck/</guid><description>
&lt;p&gt;This is about an issue I encountered in my lab recently. This issue affects vCenter version 8 U2 build 22617221&lt;/p&gt;
&lt;p&gt;If you see that cloning VMs and powering on VMs takes forever and they get stuck at 95% and 66% respectively, but eventually finishes after an hour, you can check if you are affected by this issue.
Go to the task once it's finished, and check if this is shown in the task log: &lt;code&gt;Failed to retrieve OVF environment sections for VM &amp;lt;VM name&amp;gt; from extension vService Manager&lt;/code&gt;.
If you see that, you are affected by this issue.&lt;/p&gt;</description></item><item><title>Cost savings in the Lab</title><link>https://blog.michellewayz.com/cost-savings-in-the-lab/</link><pubDate>Sat, 15 Apr 2023 13:20:52 +0000</pubDate><guid>https://blog.michellewayz.com/cost-savings-in-the-lab/</guid><description>
&lt;p&gt;With power pricing getting severely out of hand (well, it has been for months now), I figured I should do my part.&lt;/p&gt;
&lt;p&gt;Currently, my lab consists of four ESXi servers, two storage servers, one backup server and one personal tinkering server.&lt;/p&gt;
&lt;p&gt;My ESXi cluster has always ran on about 1.5 hosts worth of redundancy. In order to save some power, what I did:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Leveraged VMware vRealize Operations Manager (or.. &lt;a href="https://www.vmware.com/products/aria.html"&gt;VMware Aria&lt;/a&gt;) to appropriately downsize virtual machines to the resources they actually need,&lt;/li&gt;
&lt;li&gt;Looked at all the virtual machines again and powered off all VMs that I wasn’t using anymore, or will not use for the foreseeable future,&lt;/li&gt;
&lt;li&gt;Decided that for the lab, I will be okay with having no host redundancy at the moment as I do not touch my lab nearly as often anymore as I used to.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For vRealize Operations Manager, part of what the product allows you to do is look whether virtual machines can be upscaled or downscaled. If a VM is short on resources, it will give a recommendation as to what it thinks it would need. The same if it has too many resources, it will tell you whereabouts you can downsize the VM to. In my case, I was able to de-allocate 24 vCPUs and 56GB of memory worth of compute&lt;/p&gt;</description></item><item><title>My lab Bill of Materials</title><link>https://blog.michellewayz.com/my-lab-bill-of-materials/</link><pubDate>Tue, 12 Jan 2021 16:52:47 +0000</pubDate><guid>https://blog.michellewayz.com/my-lab-bill-of-materials/</guid><description>
&lt;p&gt;Hi everyone,&lt;/p&gt;
&lt;p&gt;For this post, we’re going to look into all the gear I have in my lab. Note that these are all links and prices that I paid for at the time.&lt;/p&gt;
&lt;p&gt;Let’s start with compute. I will list a table here of the servers.&lt;/p&gt;
&lt;h2 id="note-this-bom-is-outdated-and-is-yet-to-be-updated-pending-upgrades-that-im-saving-up-for-however-since-the-cost-is-about-1800-euros-this-will-take-a-while-and-i-may-have-to-decommission-my-current-lab-as-you-see-below-to-be-able-to-save-that-together-within-any-reasonable-timeframe"&gt;NOTE: This BoM is outdated and is yet to be updated pending upgrades that I'm saving up for. However since the cost is about 1800 euros this will take a while and I may have to decommission my current lab as you see below to be able to save that together within any reasonable timeframe&lt;/h2&gt;
&lt;p&gt;ESXi1:&lt;/p&gt;</description></item><item><title>VMware Purple Screen of Death troubleshooting for random crashes with disk errors in the homelab.</title><link>https://blog.michellewayz.com/vmware-purple-screen-of-death-troubleshooting-for-random-crashes-with-disk-errors-in-the-homelab/</link><pubDate>Thu, 04 Jun 2020 21:18:52 +0000</pubDate><guid>https://blog.michellewayz.com/vmware-purple-screen-of-death-troubleshooting-for-random-crashes-with-disk-errors-in-the-homelab/</guid><description>
&lt;p&gt;Hi everyone,&lt;/p&gt;
&lt;p&gt;Time for a new blog post about the adventure I’ve been having for the past two days.&lt;/p&gt;
&lt;p&gt;On June 2nd, my server, a DL380G6 started to suddenly take-off. The fans were roaring at 70%, and the temperature sensor near the PCI Riser was showing 110 C. Of course this is not supposed to happen, in this blog post, I will take you through my experience of troubleshooting this and hopefully this can help you.&lt;/p&gt;</description></item></channel></rss>