When reporting a bug, please follow the template provided, otherwise the report will be declined. The information requested is vital to allow us to correctly reproduce and then fix what you are reporting.
Visit the Kill Switch Master List for more information on this and other current known issues: https://forums.bhvr.com/dead-by-daylight/kb/articles/299-kill-switch-master-list
Launch Error , Cannot run under Virtual Machine.
Hello, been playing DBD for almost 2 years now in a virtual machine via windows 10 and steam.
Tried to load DBD today (2022-08-23) and got greeted with this. Please address!
Comments
-
Same thing here -
I *really* don't want to put Windows on bare metal as I severely distrust it and am a longtime Linux user. This issue wouldn't matter to me whatsoever if BHVR finally implemented Proton support in EAC. The lack of it is the only reason I used a KVM.
0 -
Hello fellow linux user, I did a bit of experimenting last night, and I may have a solution, hopefully it sticks, but it worked for me. Im using libvirt, for me I had to add <smbios mode="host"/> in the <os> section of the configuration. I hope this helps. Let me know!
1 -
Works for me too. Thank you :).
0 -
Consider me a curious Beaver, are you having an issue with the latest 6.3.2 bugfix patch where you are consistently disconnected from the host, showing you and the killer as having disconnected?
1 -
You are a curious beaver indeed, I have been 100% disconnecting from host either in lobby or 30 seconds into the game. Going to try loading the game without the fix and see if that works.
2 -
rip
0 -
looks like undoing the fix leads to the original issue. guess we are screwed for now. Would be nice to get some dev response or something.
0 -
This fix seems to have let me play again, without having any disconnection from host problems.
Under the hyperv block you must add this.
<vendor_id state="on" value="123456789123"/>
the original fix is still necessary as well. cheers.
0 -
working for me with the following changes:
<smbios mode="host"/> under <os> <vendor_id state="on" value="123456789123"/> under <features> <hyperv> <hidden state="on"/> under <features> <kvm> <hint-dedicated state="on"/> under <features> <kvm> <qemu:arg value="-cpu"/> and <qemu:arg value="host,-hypervisor,+kvm_pv_unhalt,+kvm_pv_eoi,+topoext,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,kvm=off,hv_vendor_id=amd"/> under <qemu:commandline> <qemu:commandline> has to be added manually, add xmlns:qemu="http://libvirt.org/schemas/domain/qemu/1.0" to domain opening tag
0 -
Also update to the latest gpu drivers on your guest, weirdly enough that made a difference for me
0 -
ive done a lot of testing, the only things that seem to be needed are the smbios, and vendor_id blocks. also you dont need to have any qemu args specifying hypervisor features, this can be done using the hyperv block. the solution looks more like this.
<os> ... <smbios mode="host"/> </os> <features> ... <hyperv mode="custom"> ... <vendor_id state="on" value="123456789123"/> </hyperv> </features>
Post edited by soalokin on0 -
You're correct, I've mainly added the cpu flags for other Anticheats, but it might help later down the line when EAC becomes more strict.
0
