KVM settings

[sanelka]

Hello, I've been trying Proxmox for a while and I'm trying to create a gaming VM that connects via Parsec. It's working very well, but I'm getting detected by anti-cheats. Is there a way to bypass EAC/BE?

In the image, you can see my specs. Yes, I use both an RTX and a GTX, and I have 2 VMs — one for me and one for someone else.

in the next image is about computer

its getting flagged by bios brand names etc
this is my config for my VM

args: -cpu host,kvm=off,-hypervisor
bios: ovmf
boot: order=ide0;ide2;net0
cores: 12
cpu: host,hidden=1,flags=+pcid
cpuunits: 1024
efidisk0: local-lvm:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
hostpci0: 0000:01:00,pcie=1,x-vga=1
ide0: local-lvm:vm-100-disk-1,size=800G,ssd=1
ide2: local:iso/Win10_22H2_Czech_x64v1.iso,media=cdrom,size=5863502K
machine: pc-q35-7.1
memory: 8048
meta: creation-qemu=8.1.5,ctime=1734781289
name: WinMain
net0: e1000=3A:89:03:C9:1D:DA,bridge=vmbr0,firewall=1
numa: 1
onboot: 1
ostype: win10
scsihw: lsi
smbios1: uuid=9a06ff3e-9394-4844-8a03-8ea92640a21a
sockets: 1
vmgenid: e1fc4102-a958-4921-9703-c6615a76363c

 

[fba]

Hello,
do these programs complain about something specific? Because if not, it can be any of hundreds of things which triggers it.
Proxmox VE itself is not made for hiding the virtualisation layer to it's guests. So as long as you don't know, which mechanism is triggering detection you might try a lot without being successful.
May be just customising SMBIOS Variable Values helps, like described here:

modifying the SMBIOS type 1 on the Proxmox control panel option under VM >> Options >> SMBIOS settings (type1). I copy UUID, product name and manufacturer from a similar machine (MB chip that compatible with hypervisor CPU). My VM has CPU pass-through enabled, with UEFI+TPM.