If you deploy Nested ESX and wish to use it beyond the default 90 day evaluation, you will need to license the ESX host, just like you would with a physical host.
Whether you create your own Nested ESX VM or simply deploy the the Nested ESX Virtual Appliance, make sure the cores per CPU configuration on the VM is correct or you may need a much larger CPU entitlement than what you had expected.
The default behavior of vSphere when you create a VM is to automatically manage the CPU topology (cores per CPU) when the VM is powered on for optimal GuestOS and Application consumption.
However, this automatic assignment or even a manual assignment could have some unexpected consequences when it comes to ESX licensing ...
