- 01 June 2022 (18 messages)
-
Joined. -
Hey guys, thanks for your amazing work on hyperdbg. Are there currently known issues? Because it bluescreens in my VM
-
The reason it bluescreens is cause it calls LogPrepareAndSendMessageToQueue in the vmexit handler, which eventually requires IRQL lower than the one in vmexit. But the reason it actually logs is because it exits due to VMX_EXIT_REASON_ERROR_INVALID_GUEST_STATE
-
I have a few ideas in mind why this might be and I'm trying to debug that, but could it be that this is already a known issue?
-
Hi, thanks for using HyperDbg.
No, there is no known issues.
Would you please provide more information about how you get error and information regarding your system like Windows version and processor generation. -
No, it's not a known issue.
-
What's your testing environment? VMware or physical machine?
-
vmware with nested virtualization, windows version is the following:
-
If it's not known to you, I will try to debug it and fix it myself and create a PR on github, if that's fine for you. Because I guess it might be very hard for you to debug the issue remotely :D
-
Yes, that's fine, let me know if you need help or if you have any question
-
I will do. I probably won't have time to do anything anymore today, but i will get to it tomorrow
-
In case you didn't find the problem we can discuss more about it to find the solution together.
-
It's ok
-
👍
-
sounds good, thank you :D
- 02 June 2022 (5 messages)
-
Joined. -
I found the issue and created a PR on github: https://github.com/HyperDbg/HyperDbg/pull/177Properly clear reserved segment access rights fields by momo5502 · Pull Request #177 · HyperDbg/HyperDbg
The reserved fields in the segment access rights must be zero. Otherwise, an INVALID_GUEST_STATE vm exit is triggered which leads to a bluesceen.
-
Merged, thanks
-
Thank you too :D
-
Just in case others also need to debug invalid guest states, this is an insanely helpful snippet: https://twitter.com/standa_t/status/1363354500589740033?t=zKKdlATC0RPH1n92i2IoVQ&s=19Satoshi Tanda
You must know what VM-exit reason 33 (0x21) is if you ever wrote a hypervisor from scratch. Too much researchers' time was wasted to diagnose it I am sharing diagnostics code I have been using. This finds out why that VM-exit happened and saves your time gist.github.com/tandasat/4b0bc…
