buheratorLook at this gem I just found:<br><br>Using WinDbg Over KDNet on QEMU-KVM<br><br><a href="https://www.osr.com/blog/2021/10/05/using-windbg-over-kdnet-on-qemu-kvm/" rel="nofollow noopener" target="_blank">https://www.osr.com/blog/2021/10/05/using-windbg-over-kdnet-on-qemu-kvm/</a><br><br>"The enlightenments that are enabled by default include setting the hypervisor ID to the same ID that’s reported by Microsoft Hyper-V (which is “Microsoft Hv”). [...] when the KDNet transport initializes, it checks the hypervisor ID, and if it discovers it is running under Microsoft Hyper-V [...] it attempts to open a debugger connection using an undocumented protocol over a synthetic hypervisor-owned debug device that Hyper-V provides." <br><br>I'll give this a shot tomorrow on Proxmox and I'll drink something strong if modifying the hypervisor ID actually solves my issues! :D<br><br><a class="hashtag" href="https://infosec.place/tag/windbg" rel="nofollow noopener" target="_blank">#windbg</a> <a class="hashtag" href="https://infosec.place/tag/reverseengineering" rel="nofollow noopener" target="_blank">#reverseengineering</a> <a class="hashtag" href="https://infosec.place/tag/proxmox" rel="nofollow noopener" target="_blank">#proxmox</a> <a class="hashtag" href="https://infosec.place/tag/kvm" rel="nofollow noopener" target="_blank">#kvm</a>