It seems that enabling hyper -v (win features), prevents VB to use nested-v. Only one virtual process is able to use it.
I have disabled it, and am going to try and see what’s in the BIOS while restarting for changes to take effect…
It seems that enabling hyper -v (win features), prevents VB to use nested-v. Only one virtual process is able to use it.
I have disabled it, and am going to try and see what’s in the BIOS while restarting for changes to take effect…