I know many in the VMware Community have upgraded to vSphere 8.0 Update 3 to play with the exciting new NVMe Tiering feature, especially for testing various workloads including deploying VMware Cloud Foundation (VCF) for homelab or testing purposes.
A question that has come up a few times now is how do I check the amount of VM memory that has been offloaded to Tier 1 memory (NVMe Tiering) versus using Tier 0 memory (DRAM)?
Starting with Intel Meteor Lake (14th Generation) CPUs, now part of the new Intel Core Ultra Processor (Series 1) brand, an integrated Neural Processing Unit or NPU is built right into the SoC (system-on-chip) and is optimized for low power AI Inferencing.
I found this article from Chips and Cheese about the new Intel Meteor Lake NPU to be super insightful, definitely recommend a read if you are new to NPUs.
While you can already consume the Intel integrated graphics (iGPU) in platforms like the Intel NUC with ESXi for workload inferencing, I was curious on whether this new Intel NPU could actually be used by ESXi? 🤔
Since publishing my NVMe Tiering in vSphere 8.0 Update 3 is a Homelab game changer blog post, the feedback and responses have been absolutely phenomenal!
It will be just a matter of time until we can start using RAID with NVME Tiering !
When it happens, it will be a HUGR game change!
BTW, I'm already using it on my Lab Environment!!
It's F**** awesome! pic.twitter.com/h6Np972RcQ
— Chris ✈️🇧🇷🇵🇹🇺🇸🌍 (@crismsantos) September 4, 2024
In fact, during VMware Explore, I had a number of users share with me in person that they not only updated to vSphere 8.0 Update 3 after learning about the feature but they were extremely happy that they could have their hardware was even more capable with just a software upgrade and workloads varied from general infrastructure VMs to the full VMware Cloud Foundation (VCF) stack.
Right before VMware Explore, I did have a couple of users who reported that after successfully configuring NVMe Tiering and rebooting their ESXi host, they noticed the memory capacity did not change. After sharing the details along with vm-support bundles, Engineering has identified the root cause.