Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how to bypass virtual machine check #120

Open
nhamhuynh79 opened this issue Oct 29, 2023 · 3 comments
Open

how to bypass virtual machine check #120

nhamhuynh79 opened this issue Oct 29, 2023 · 3 comments

Comments

@nhamhuynh79
Copy link

Hello everyone, how to bypass intel graphic driver check "hide kvm"
When hide vm state get error code 43 :(

@michael-pptf
Copy link
Contributor

set your vm cpu type to host.

@liuran001
Copy link

I have the same problem. When I try to add the parameter args: -cpu host,hypervisor=off to pve's qemu config file, the device manager in my Windows VM says Windows has stopped this device due to a problem with it (code 43). I've tried a number of things, and it's apparently impossible to hide the VM without adding hypervisor=off, and once this parameter is added, the device manager frustratingly displays error code 43. I haven't tried this in Linux for now (and I don't have a need to hide the VM in Linux), but in Windows, a lot of the software and games detect the presence of a VM and refuse to start it once it is detected (e.g. Genshin Impact), while it is impractical to run these games without a GPU. I assume that Intel's driver detects the VM state or has a special adaptation for SR-IOV, and once the VM state is removed, the driver will not run in the correct state (maybe?). My CPU is an i7-12700H and this problem has been bothering me for a while, hopefully someone can fix it.

@michael-pptf
Copy link
Contributor

I have the same problem. When I try to add the parameter args: -cpu host,hypervisor=off to pve's qemu config file, the device manager in my Windows VM says Windows has stopped this device due to a problem with it (code 43). I've tried a number of things, and it's apparently impossible to hide the VM without adding hypervisor=off, and once this parameter is added, the device manager frustratingly displays error code 43. I haven't tried this in Linux for now (and I don't have a need to hide the VM in Linux), but in Windows, a lot of the software and games detect the presence of a VM and refuse to start it once it is detected (e.g. Genshin Impact), while it is impractical to run these games without a GPU. I assume that Intel's driver detects the VM state or has a special adaptation for SR-IOV, and once the VM state is removed, the driver will not run in the correct state (maybe?). My CPU is an i7-12700H and this problem has been bothering me for a while, hopefully someone can fix it.

Here's the thing - this is a kernel module developed by Intel, and its intention is to support SR-IOV. There should be no reason whatsoever to hide that the vGPU is used in a VM, because that's what it is for. This is the reason why you can't set the hypervisor=off and expect this vGPU to function correctly.

If you want to play games or what not, pass a real GPU to the VM might have better chance of success.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants