The Best way to hide KVM from Guest OS - Wendell method?

Hello lovely community,

at the end of this Video ( level1techs[dot]com/video/seamless-mode-microsoft-office-linux-windows-vm-threadripper-pro )
Wendell mentions that he has less problems with VMs & AntiCheat since he is good at hiding the KVM.

What are those things?

at the moment i read of the following:
<feature policy="disable" name="hypervisor"/>
(on github another line is mentioned ( github[dot]com/bryansteiner/gpu-passthrough-tutorial#part3 ):

        <relaxed state="on"/>
        <vapic state="on"/>
        <spinlocks state="on" retries="8191"/>
        <vendor_id state="on" value="kvm hyperv"/>


<hidden state="on"/>

and to close in this forums you can read about:

monitor_control.virtual_rdtsc = “FALSE”
monitor_control.restrict_backdoor = “TRUE” = “TRUE” = “TRUE” = “TRUE” = “TRUE”
monitor_control.disable_directexec = “TRUE”
hypervisor.cpuid.v0 = “FALSE”

where ever this goes ?

Does anyone know which are correct? Or if Wendell uses something else?

Maybe we can even build a comprehensive guide of all tweaks to hide the KVM
so we can use a VM instead of dualboot without the fear of randomly loosing hundreds of dollars
worth of accounts due to random gamedevs mind changes?

with kind regards

//EDIT: sorry i cant include links … so they are botched

even you try to fully hide the hypervisor the dev can still detect you run in vm its a mater of time before they found out ! the only solution is like finding the ultimate type zero hypervisor that can share hardware directly between os without any type of virtualisation lets say like sriov but full hardware sharing like a bios level hypervisor that you can configure HVM(hardware VM) pining cpu core passthrough portion of gpu and pcie storage controller directly to OS even the io and chipset all that before booting to system … seem like alien dream to go live in another planet :sweat_smile: