search

zhaodice / qemu-anti-detection

A patch to hide qemu itself, bypass mhyprot,EAC,nProtect / VMProtect,VProtect, Themida, Enigma Protector,Safegine Shielden
744 stars 113 forks source link

vio driver issue #57

Open aamaanaa opened 6 months ago

aamaanaa commented 6 months ago

hi i compiled with the patch like so

../qemu/configure --target-list=x86_64-softmmu,x86_64-linux-user --enable-werror --enable-xen --enable-virtfs --enable-kvm --enable-libusb --enable-libudev --enable-spice --enable-usb-redir --prefix=/usr

then i set the drive to vio and the nic aswell

i then booted up windows 10, load the vio drivers from the attached vio iso image from fedora poeple, and i can not load it. when i uncheck the box hide unsupported drivers, i see the files from the virtio disk, but i cant install

what is going on here?

zhaodice commented 6 months ago

you can restore the virto modifying from patch

aamaanaa commented 6 months ago

you can restore the virto modifying from patch

do i need to remove all virtio stuff from the pach? so search for virtio and remove it all

aamaanaa commented 6 months ago

Virtio does seem to work when installing sudo dnf install @virtualization, but i gues it is not using my own compiled qemu in /opt

zhaodice commented 6 months ago

actually,I doesn't support virtio, because it is virtual machine device that can be detection, if you want to use virtio,please don't hide and anti-detection.

aamaanaa commented 6 months ago

okay i see. for now i just use spice and spice guest tools

JoaGamo commented 6 months ago

Hello. I've seen you need network and disk. I'm on proxmox so I hope you can adapt this to your configuration. I use Intel E1000 as my network card and for the disk I use SATA mode with cache disabled and aio=native (and discard=on of course). I get a good performance out of it

aamaanaa commented 6 months ago

ye i have it to. with spice and qxl with this patch i do get very laggy performance tho

Samuil1337 commented 5 months ago

I assume that the VirtIO driver doesn't work, because this patch renames the virtual devices in a way that cannot be detected by anti-cheat and the driver alike. You may need to recompile the drivers with the new identifiers, but this goes beyond the scope and purpose of this project. We want the virtual hardware to look as real as possible, so your VM isn't detected, and unfortunately, the VirtIO driver is a dead giveaway for any software. The performance issues can instead be mitigated by using VFIO to give your VM direct access to your graphics card. How you do this depends on your hardware configuration, but this is a good tutorial, if you only have one GPU: https://gitlab.com/risingprismtv/single-gpu-passthrough/-/wikis/home

caoshuai619 commented 2 months ago

okay i see. for now i just use spice and spice guest tools

hey, how do you do that ,not use vio? can you give me a tutorial.