guardmon driver locking the virtual machine and not working correctly #9
Description
i used guardmon inside of vmware and hyper-v machines, both build 1809. when kernel debugging the loading of the guardmon driver on both machines with drvloader as the loader and windbg as the debugger, after a few seconds and exactly 2 prints every time i try it the machine stops working. not as shutting down/restarting, but as if i hit a breakpoint in the kernel debugger and now the executing context of the machine is solely debugging the kernel. an example for the output given by the debugger is the following:
KDTARGET: Refreshing KD connection
17:36:01.443 INF #2 4 3028 System Log has been initialized.
17:36:01.505 INF #0 4 3028 System Initializing VMX for the processor 0.
the number in the first print after the "INF #" changes each time but other than that the output is exactly the same.
it would help if someone could help me figure out the problem or even detect where its going wrong so i could try to fix it, thank you!