Nephilgrim

You just fix all the issues I had! Changing both mount points and now it just performs as it should!

Someone may have to correct me, but i think it's needed to have this tag inside <cpu> for the nested virtualization to work prior to everything else you have tried: <cpu mode='host-passthrough' check='none'> ... <feature policy='require' name='vmx'/> ... </cpu> At least it was needed when i tried to do some nested virtualization a year or so ago.

Change to q35 instead of i440fx. I cannot start my 1070 if i dont create the VM as q35 + the modified rom file (as spaceinvaderone tutorial).

Im on mobile, but first thing I noticed is that you set the emulatorpin to a core/thread from node 0. Try using 11cores on your vm from the node1 instead of 12 and change the emulatorpin to that free core/thread. Probably that wil get rid of your latency issue since a core in node 0 is taking control of your vm in node1.

I just signed to confirm this. I had to create all my VM's with Q35 due to this issue when drivers are installed using i440 with an MSI RX 470 Gaming X. Only way to workaround the problem was converting/creating my VMs to Q35. Adittionally, with Q35 i can have Hyper-V turned ON with a GTX 1070 without suffering the error 34 (or was it 43?). I don't know if it's just a coincidence (the combination of my mobo and GPU,some bios option or whatever) but actually i can enjoy like 30 or 40 more fps in games thx to being able to enable HyperV in a gaming VM at the moment. I'm actually using the latest drivers without having to fix anything at all. For me at least, being unable to use Q35 will be a serious NO to continue using unraid right now.