The vast majority of VMware Homelabs is still Intel-based today but I have been seeing a slow rise of AMD-based kits being adopted, especially with AMD's desktop line of CPUs known as Ryzen. One of the considerations on whether you could use an AMD processor was whether you were planning to deploy NSX-T and in earlier releases, only Intel was supported as the NSX-T Edge required support for Data Plane Development Kit (DPDK) and this was only supported with Intel-based processors.
With the latest NSX-T 3.0 release, AMD-based processors are now supported and per the release notes, the following CPUs can be used:
- AMD EPYC 7xx1 Series (Naples)
- AMD EPYC 3000 Embedded Family and newer
- AMD EPYC 7xx2 Series (Rome)
You will notice that only AMD's server line of CPUs known as EPYC are currently supported, which makes sense for running Production workloads. If you attempt to deploy an NSX-T Edge Node running on a non-EPYC platform, you will get an error message stating the CPU is not supported and I figured this was probably due to the lack of DPDK support in the consumer CPUs.
Yesterday, in our internal "Homelab" Slack channel, I came across an interesting tidbit from Andrea Spagnolo, a Sr. Field Engineer in our Cloud Native Business Unit who shared a pretty neat trick on how to get latest NSX-T 3.0 release to work with a Ryzen-based CPU.
Disclaimer: This is not officially supported by VMware. The behaviors described here can change in the future
First off, I want to thank Andrea for sharing but also credit to Beniamino Guarnaschelli and his blog post here which actually gave Andrea the idea to take a closer look as he was trying to get this setup in his own personal homelab.
The way NSX-T ensures you that you a supported AMD CPU is by looking for the "AMD EPYC" string in the model name which is performed within the NSX-T Edge using the following /opt/vmware/nsx-edge/bin/config.py script. To bypass this check, we just need to comment out the lines that does the actual check.
Step 1 - Deploy an NSX-T Edge (either standalone or using the NSX-T Manager workflow)
Step 2 - SSH to NSX-T Edge as root and comment out lines 181-184
Step 3 - Run the following command to start the dataplane service which will cause the VM to reboot
su - admin
start service dataplane
Step 4 - You can now configure the NSX-T Edge as a Transport Node and you will not run into any errors
Note: One additional issue that Andrea ran into was that IOMMU was NOT enabled on his motherboard which is requirement. Once this was done along with the configuration tweak above, he was able to get NSX-T Edge working on his AMD (3700x) kit.
Andrea has also confirmed this trick works with both NSX-T 2.5 as well as the latest 3.0 release in case folks wanted to try this out on an earlier version.
Hi William,
thanks for the credits and for mentioning me.
Ciao
Benja
With this clarification, please note that AMD have a very good “baby EPYC” processor series out. A Supermicro motherboard with a SoC EPYC 3251 8 cores and 16 threads is a very attractive home lab solution that is equivalent to a Xeon D but probably a couple of hundred dollars less.
Thanks for this. I just ran up against the problem and was a little bit worried.
Thank you, thank you, thank you. This did the trick. I am running a Threadripper cluster and this did the trick really nice and saved me Thousands. I had also been planning to upgrade the primary datacenter to Epycs and it is really nice to know that the Edge is fully supported on it now. I was beginning to panic. The last day has been a nightmare.