I currently have a mostly-functional PoC hypervisor (e.g. EPTs, CR, etc). However when I add support for DR access I can no longer debug my hypervisor. I've been doing my testing and debugging in VMWare with windbg/VirtualKD. I haven't been doing anything fancy with segmented memory spaces etc.
However as the title says when I add the support for vmexits on DR accesses, I can no longer use debug breaks. I've checked my DR access handler (just a passthrough atm) by running mov dr, <reg> commands and I can see the debug messages from my VMM but if I insert an int3 or try to pause the VM it just hangs.
I haven't done anything with exceptions or etc passing-through to the Hypervisor, and as I said before adding vmexits for DR access I've been able to freely debug both my hypervisor and the managed code. Am I missing something obvious?