[SOLVED] Anti-Cheat KVM Settings

spartandrew18 said:
Well, I did everything you did, and it finally changed from QEMU Device to ASUS System Device. However, loading Halo Infinite still causes it to cancel out and close the game. I cannot activate "args: -cpu host,-hypervisor,kvm=off" as my computer gets stuck in the windows boot logo. Any other ideas I can try?

View attachment 59645
Click to expand...
Just hv_vendor_id=amd !!! its work!
args: -cpu host,-hypervisor,hv_vendor_id=amd
 
Hello, I'm also having problems with the NewWorld game. I can't start the game, it detects directly that it's a VM.
error message: cannot run under Virtual Machine.
I've tried your configurations but the problem is still there.
I may have made some errors in my .conf file (present on /etc/pve/nodes/pve/qemu-server)?

Can you help me please ?

Here is my Proxmox server:
CPU(s)

24 x AMD Ryzen 9 3900X 12-Core Processor (1 Socket)
Kernel Version

Linux 5.15.30-2-pve #1 SMP PVE 5.15.30-3 (Fri, 22 Apr 2022 18:08:27 +0200)
PVE Manager Version

pve-manager/7.2-3/c743d6c1


Here is one of my vm.conf files after all of this (some fields REDACTED to protect the innocent):

Code: 
agent: 1
args: -cpu host,-hypervisor,hv_vendor_id=amd
bios: ovmf
boot: order=sata0;net0
cores: 20
cpu: host
efidisk0: SSDtmp:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
hostpci0: 0000:09:00,pcie=1,x-vga=1
machine: pc-q35-6.2
memory: 50048
meta: creation-qemu=6.2.0,ctime=1663513997
name: Windows10
net0: virtio=REDACTED,bridge=vmbr0,firewall=1
numa: 1
ostype: win10
sata0: SSDtmp:vm-100-disk-1,cache=writeback,discard=on,size=200G
scsihw: lsi
smbios1: REDACTED,manufacturer=QkVTU1RBUiBURUNIIExJTUlURUQ=,product=SE04MA==,version=NS4xNg==,serial=RGVmYXVsdCBzdHJpbmc=,sku=RGVmYXVsdCBzdHJpbmc=,family=RGVmYXVsdCBzdHJpbmc=,base64=1
sockets: 1
usb0: host=1-4,usb3=1
usb1: host=7-1,usb3=1
usb2: host=7-4,usb3=1
usb3: host=7-2,usb3=1
virtio2: /dev/disk/by-id/nvme-eui.6479a72452222020,size=976762584K
vmgenid: REDACTED
 
Last edited:
Digital said:
Hello, I'm also having problems with the NewWorld game. I can't start the game, it detects directly that it's a VM.
error message: cannot run under Virtual Machine.
I've tried your configurations but the problem is still there.
I may have made some errors in my .conf file (present on /etc/pve/nodes/pve/qemu-server)?

Can you help me please ?

Here is my Proxmox server:
CPU(s)

24 x AMD Ryzen 9 3900X 12-Core Processor (1 Socket)
Kernel Version

Linux 5.15.30-2-pve #1 SMP PVE 5.15.30-3 (Fri, 22 Apr 2022 18:08:27 +0200)
PVE Manager Version

pve-manager/7.2-3/c743d6c1


Here is one of my vm.conf files after all of this (some fields REDACTED to protect the innocent):

Code: 
agent: 1
args: -cpu host,-hypervisor,hv_vendor_id=amd
bios: ovmf
boot: order=sata0;net0
cores: 20
cpu: host
efidisk0: SSDtmp:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
hostpci0: 0000:09:00,pcie=1,x-vga=1
machine: pc-q35-6.2
memory: 50048
meta: creation-qemu=6.2.0,ctime=1663513997
name: Windows10
net0: virtio=REDACTED,bridge=vmbr0,firewall=1
numa: 1
ostype: win10
sata0: SSDtmp:vm-100-disk-1,cache=writeback,discard=on,size=200G
scsihw: lsi
smbios1: REDACTED,manufacturer=QkVTU1RBUiBURUNIIExJTUlURUQ=,product=SE04MA==,version=NS4xNg==,serial=RGVmYXVsdCBzdHJpbmc=,sku=RGVmYXVsdCBzdHJpbmc=,family=RGVmYXVsdCBzdHJpbmc=,base64=1
sockets: 1
usb0: host=1-4,usb3=1
usb1: host=7-1,usb3=1
usb2: host=7-4,usb3=1
usb3: host=7-2,usb3=1
virtio2: /dev/disk/by-id/nvme-eui.6479a72452222020,size=976762584K
vmgenid: REDACTED
Click to expand...
"args: -cpu host,-hypervisor,hv_vendor_id=amd"- this configuration work not always. after reboot I've blue-screen error. i do hard stop and remove string -hypervisor, startup windows, shutdown, and again add -hypervisor and startup. and no more shutdown and reboot, because again and again bsod.
sorry for my english ¯\_(ツ)_/¯
 
Hey everyone, I just updated my computer to windows 23H2 and I can confirm that this update breaks the windows loading. If I revert before to 22H2 it works fine. Any ideas?
 
spartandrew18 said:
Well, I did everything you did, and it finally changed from QEMU Device to ASUS System Device. However, loading Halo Infinite still causes it to cancel out and close the game. I cannot activate "args: -cpu host,-hypervisor,kvm=off" as my computer gets stuck in the windows boot logo. Any other ideas I can try?

View attachment 59645
Click to expand...
Could be your windows version. When I tryed with win 11 I had the same mistake than yours, I changed for win10 and worked
 
If you are dealing with EAC, all you have to do is set up the SMBIOS of your VM, dump your OG bios data and paste them in the SMBIOS. if it doesnt work, use the Intel card with a real listed Mac address
 
Arthur Meira Lins said:
Could be your windows version. When I tryed with win 11 I had the same mistake than yours, I changed for win10 and worked
Click to expand...
It indeed was a windows update that had busted this method. I had reverted before the update and it worked. Unfortunately I run windows 11 and have not found a new solution to the problem.
 
playing fortnite since one month, noticed some issues because was running with sata and Lsi controller, changed now to scsi and virtio and everything is smooth, also no issue with anticheat
 
Bykiss said:
playing fortnite since one month, noticed some issues because was running with sata and Lsi controller, changed now to scsi and virtio and everything is smooth, also no issue with anticheat
Click to expand...
Hi. I would like to try this as well. Could you please share the conf file.
 
https://www.reddit.com/r/Proxmox/comments/quwmp7/comment/hkt75vk

Run "qm showcmd 1xx --pretty" to see the current QEMU commandline for your VM (replace 1xx with your VM's ID). Locate the "-cpu" line, for example here's mine:

-cpu 'host,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vendor_id=proxmox,hv_vpindex,kvm=off,+kvm_pv_eoi,+kvm_pv_unhalt,+pdpe1gb'
Click to expand...
Copy that, add ",-hypervisor" to the end of the feature list, then add a new line to your VM config that starts "args: " followed by that new CPU command:

args: -cpu 'host,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vendor_id=proxmox,hv_vpindex,kvm=off,+kvm_pv_eoi,+kvm_pv_unhalt,+pdpe1gb,-hypervisor'
Click to expand...
 
GlidingTurtle said:
I just went through and updated my Win10 vGPU setup to play Fortnite. The only settings I needed to change were the SMBIOS fields, and putting in a "real" MAC address. I have tweaked these machines with various other settings in the past, so YMMV. I have included my vm.conf file below for reference.

A few notes:
  1. Using the same MAC address as another machine on your network can cause issues, so don't do that. Instead, use the first three octets of a MAC on your network, and leave the last three with whatever Proxmox has. This _should_ ensure there are no duplicate MACs on your network, just be sure to double-check.
    1. Example: If the MAC for your physical machine is 1C:83:41:A1:B2:C3 and your Proxmox VM is B2:74:70:69:F3:A9. Change your VM MAC to be: 1C:83:41:69:F3:A9. You can verify this is a valid MAC by pasting it in a site like https://www.macvendorlookup.com
  2. For the SMBIOS fields, you can simply copy them straight from a physical machine on your network. I have several vGPU VMs, and I used the same info for all of them except for the UUID (just in case).
    1. Note: These fields are encoded to base64 text in the vm.conf file, but show as human-readable when edited in the Proxmox GUI.
    2. Interestingly, my Minisforum machine had several fields set to "Default string". This worked for me, but feel free to substitute as needed.
    3. If you have a Linux machine with root access, you can use the below dmidecodecommands for the matching fields:
      1. UUID: dmidecode -s system-uuid
      2. Manufacturer: dmidecode -s system-manufacturer
      3. Product: dmidecode -s system-product-name
      4. Version: dmidecode -s system-version
      5. Serial: dmidecode -s system-serial-number
      6. SKU: dmidecode -s system-sku-number
      7. Family: dmidecode -s system-family
Here is one of my vm.conf files after all of this (some fields REDACTED to protect the innocent):
Code: 
agent: 1,fstrim_cloned_disks=1
args: -uuid 00000000-0000-0000-0000-000000000501
balloon: 0
bios: ovmf
boot: order=ide2;sata0;net0
cores: 8
cpu: host
efidisk0: local-zfs:vm-501-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
hostpci0: 0000:02:00.0,mdev=nvidia-261
ide2: none,media=cdrom
machine: pc-q35-6.1
memory: 20480
meta: creation-qemu=6.1.1,ctime=1649086086
name: VDI-501
net0: virtio=1C:83:41:FF:FF:FF,bridge=vmbr1,firewall=1,tag=10
numa: 1
ostype: win10
sata0: datapool3:vm-501-disk-0,cache=writeback,discard=on,size=180G,ssd=1
sata1: local-zfs:vm-501-disk-1,size=500G
scsihw: virtio-scsi-single
smbios1: uuid=REDACTED,manufacturer=QkVTU1RBUiBURUNIIExJTUlURUQ=,product=SE04MA==,version=NS4xNg==,serial=RGVmYXVsdCBzdHJpbmc=,sku=RGVmYXVsdCBzdHJpbmc=,family=RGVmYXVsdCBzdHJpbmc=,base64=1
sockets: 1
vga: none
vmgenid: REDACTED

Hope this helps!
Click to expand...
The "dmidecode -s [...]" commands give me generic answer e.g.:

"dmidecode -s system-product-name" gives Output "System Product Name"..
 
  • Like
Reactions: ceghey
I tried everything suggested above, nothing helped. Only adding this line worked for me.
GlidingTurtle said:
smbios1: uuid=REDACTED,manufacturer=QkVTU1RBUiBURUNIIExJTUlURUQ=,product=SE04MA==,version=NS4xNg==,serial=RGVmYXVsdCBzdHJpbmc=,sku=RGVmYXVsdCBzdHJpbmc=,family=RGVmYXVsdCBzdHJpbmc=,base64=1
Click to expand...
ProxMox 9.1.4, GPU 3090 pass-through to Win11 VM, for Star Citizen EAC.
 
ceghey said:
I tried everything suggested above, nothing helped. Only adding this line worked for me.

ProxMox 9.1.4, GPU 3090 pass-through to Win11 VM, for Star Citizen EAC.
Click to expand...
I added this line and it wiped it except for UUID, so I grabbed my actual UUID with `dmidecode -s system-uuid` ... (Edit: did it through GUI it stayed)
I added a randomized Intel MAC address ...
I added `args: -cpu host,-hypervisor,kvm=off` ...

Device Manager > Computer is still showing "QEMU Standard PC" ...

No luck so far. Edit: Updating SMBIOS info with GUI it stayed, no longer shows QEMU Standard PC, but EAC still blocks as VM.

Edit: System disk showed in Device Manager as "QEMU HARDDISK" ... Disk passthrough breaks CPU host mode and GPU pass through, so has to stay virtualized. Appended serial and switched from SATA to SCSI and it wouldn't boot. Returned it to SATA and it boots. Still shows QEMU HARDDISK.

Edit: I got impatient and threw a bunch of stuff into my config, including `args: -hypervisor` among a billion other things. Have heard caution against `-hypervisor` due to performance cost. The game launched without EAC blocking VM, but then crashed. Hard to narrow it down.
 
Last edited:
branpurn said:
is there a command to run or registry keys to delete
Click to expand...
yes run \StarCitizen\LIVE\EasyAntiCheat\EasyAntiCheat_Setup.exe [install, uninstall, factoryreset] ... run without args will show help
uninstall will clean registry and delete EAC folder in %USERPROFILE%
 
ceghey said:
yes run \StarCitizen\LIVE\EasyAntiCheat\EasyAntiCheat_Setup.exe [install, uninstall, factoryreset] ... run without args will show help
uninstall will clean registry and delete EAC folder in %USERPROFILE%
Click to expand...
Could you DM me your whole VM's config? lol. If so feel free to scrub MACs/UUIDs. Game crash is the issue now. It worked ages ago.
 
branpurn said:
Could you DM me your whole VM's config? lol. If so feel free to scrub MACs/UUIDs. Game crash is the issue now. It worked ages ago.
Click to expand...
The game crashes on my gaming laptop with a 3080 GPU and 16 Gigs of RAM, that's why I play on a virtual machine on my homelab server :)
Code: 
args: -cpu host,-hypervisor
bios: ovmf
boot: order=scsi0;ide2;ide0;net0
cores: 30
cpu: host
efidisk0: local-lvm:vm-105-disk-0,efitype=4m,ms-cert=2023,pre-enrolled-keys=1,size=4M
hostpci0: 0000:03:00,pcie=1
machine: pc-q35-10.1
memory: 32768
meta: creation-qemu=10.1.2,ctime=1769011637
name: win25
net0: virtio=D8:BB:C1:A0:51:84,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win11
parent: fresh
scsi0: local-lvm:vm-105-disk-1,iothread=1,size=200G,ssd=1
scsi1: satadisk2t:vm-105-disk-0,iothread=1,size=500G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=03000200-0400-0500-0006-000700080009,manufacturer=QkVTU1RBUiBURUNIIExJTUlURUQ=,product=SE04MA==,version=NS4xNg==,serial=RGVmYXVsdCBzdHJpbmc=,sku=RGVmYXVsdCBzdHJpbmc=,family=RGVmYXVsdCBzdHJpbmc=,base64=1
sockets: 1
tpmstate0: local-lvm:vm-105-disk-2,size=4M,version=v2.0
usb0: host=03f0:0024,usb3=1
usb1: host=25a7:fa49,usb3=1
usb2: host=0951:1625,usb3=1
usb3: host=231d:0200
usb4: host=231d:0201
usb5: host=0b05:1bef
vga: none
vmgenid: 6af8e786-fa2f-4858-82d7-ef918cf1b450
 
You must log in or register to reply here.
Top Bottom
Back