-
Notifications
You must be signed in to change notification settings - Fork 310
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
The VM loses control from windbg. #21
Comments
Hi, |
Thanks for your reply, there is such a situation from part 6 code. |
Can you confirm the same problem in part 8 too? Because a lot of changes have been made to Windows (and of course hypervisor itself), so if I wanna update part 6, it will break the codes and previous explanations. But, part 8 should be fine. |
There are 2 .gif images below, the first one is compiling part 8 in VS2019; the second one is after running the driver and app the VM freezes and loses control from windbg. |
Hi, SinaKarvandi :
Thank you very much for the tutorial, it helped me a lot.
But there is a problem that has been bothering me for a long time(OS: Windows 10 x64,19044, Disabled VBS). Without enabling EPT, the GUEST_RIP was able to execute every time the VMLAUNCH instruction was executed, but when I go (g) in windbg, the VM gets stuck and loses control from windbg and cannot enter the VM-exit handler, I tried the following method to try to find the reason: Before VMLANCH execution, I promoted IRQL > =DISPATCH_LEVEL to successfully enter the VM-exit handler every time the preset conditions in the control area are triggered. But as you know, the wrong IRQL will cause BSOD, but at least it will hit the VM-exit handler. I can't find a good solution, if you know, please help me correct it, thank you very much.
The text was updated successfully, but these errors were encountered: