@Marius_Roma
Seems like an overly-complicated way of going about setting up the environment.
In line with what @Dave Patrick said, but to call out this one very specific scenario: you never install additional roles on a domain controller.
Assuming you go ahead with this model, you'd be better off building the top-level hypervisor as a workgroup host and then establishing the domain controller as one of the guests.
Anyhow, as far as the errors you've listed go, there's a lot. I get the feeling many are going to be symptoms, not the cause.
It pays to remember that nested virtualisation has to be enabled per guest - it's not a once-and-done thing on the hypervisor itself.
Have a look at all the pre-requisites in this article (below) as there's more to configure even after you've exposed the virtualisation extensions on the guest. For example, one of your errors relates to creating the virtual switch and in the Microsoft article, you can see there's some action items around enabling MAC address spoofing (or alternatives).
Anyhow, have a read and plan the deployment before trying to wing it on the tools.
Nested Virtualization | Microsoft Docs
Cheers,
Lain
