The whole idea is run ESXi in a VM in Azure IaaS, where I cannot use legacy NIC ...
I'm not really sure where you are going with this. Hyper-V doesn't virtualize the hardware-assisted virtualization features of the physical processor, so you would be stuck running 32-bit nested guests with binary translation. Performance would be terrible. Moreover, unless you can set your NIC to promiscuous mode, you wouldn't be able to get networking through to your nested VMs.
Now that Windows 10 and Server 2016 support nested virtualisation, is anyone working on porting the native hyper-v Network adapter drivers to ESXi so we're not limited to 100mbit on the legacy adapter?
having the same problem hope some IT genius get a solution to this problem cheers
does anyone know how to compile / build the net-tulip driver for ESXi 6.5 or 6.7 ?
According to this article: https://www.v-front.de/2016/11/esxi-65-release-notes-for-free-license.html,
"Legacy and Community network driver compatibility
In KB2147697 VMware declares that all drivers built and certified on ESXi 5.5 and 6.0 are also supported with ESXi 6.5.
Technically even drivers that have been compiled for ESXi 5.1 can still be installed and used on ESXi 6.5. However, drivers that have been compiled for ESXi 5.0 can definitely no longer be installed on ESXi 6.5.
This affects the following drivers from the V-Front Online Depot: net-atl1, net-atl1e, net-r8101, net-8139too, net-skge, net-tulip. They can no longer be installed on and used with ESXi 6.5."
If anyone knows how to make the net-tulip driver compatible with ESXi 6.5 or 6.7, please share the information.