Ok no worries , sorry the reason I ask is that HyperV detects that a hypervisor exists if you try and create another hypervisor within a VM . Which is nothing to do with domains either , that ' s almost certainly an issue with the existing hypervisor not exposing the virtualisation features of the CPU to the subhypervisor . I have the standalone versions of HyperV 2008 R 2 , 2012 and 2012 R 2 joined to our AD domain for testing , and there are no problems at all . Strange train of thought you must have to turn you can ' t run nested hypervisors into you can ' t run two physical VM hosts with hypervisors from different vendors , but I think you ' ve just overinflated the problem in your head . <| sep |> If you ' ve ever owned an old Citroen you ' d know that they drive smoother over speed bumps the faster you go thanks to their hydropneumatic suspension . My dad had one and tailgaters would cause themselves grief without him having to give it any thought .