Skip to content
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 computer freezes after starting hv #32

Open
LYingSiMon opened this issue Aug 2, 2023 · 3 comments
Open

The computer freezes after starting hv #32

LYingSiMon opened this issue Aug 2, 2023 · 3 comments

Comments

@LYingSiMon
Copy link

LYingSiMon commented Aug 2, 2023

Hi, I am having a problem when I use vmware, after installing hv, the system is stuck(windbg not working either)。Soon after, vmware automatically rebooted the system, I cannot provide dump files because there is no bsod。

This is my environment:
cpu:i9 13900k
system:win10 1903

I also tested it on 1909, and it jammed the system, but the phenomenon was slightly different, the 1909 phenomenon was the system black screen and kept flashing.

this is hv's log:

行 1016: [hv] Driver loaded.
行 1018: hv!driver_entry+0x32:
行 1022: [hv] Allocated 2 VCPUs (0x16A000 bytes).
行 1023: [hv] System EPROCESS = 0xFFFFCC0F8BC71300.
行 1024: [hv] EPROCESS::UniqueProcessId offset = 0x2E8.
行 1025: [hv] EPROCESS::ImageFileName offset = 0x450.
行 1026: [hv] System CR3 = 0x1AD000.
行 1027: [hv] Mapped all of physical memory to address 0x7F8000000000.
行 1028: [hv] Cached VCPU data.
行 1029: [hv] Enabled VMX operation.
行 1030: [hv] Entered VMX operation.
行 1031: [hv] Loaded VMCS pointer.
行 1032: [hv] Initialized external structures.
行 1033: [hv] Wrote VMCS fields.
行 1035: [hv] Launched VM on VCPU#1.
行 1036: [hv] Successfully pinged the hypervisor.
行 1037: [hv] Measured VM-exit overhead (TSC = 20664).
行 1038: [hv] Measured VM-exit overhead (MPERF = 0).
行 1039: [hv] Measured VM-exit overhead (CPU_CLK_UNHALTED.REF_TSC = 0).
行 1040: [hv] Cached VCPU data.
行 1041: [hv] Enabled VMX operation.
行 1042: [hv] Entered VMX operation.
行 1043: [hv] Loaded VMCS pointer.
行 1044: [hv] Initialized external structures.
行 1045: [hv] Wrote VMCS fields.
行 1047: [hv] Launched VM on VCPU#2.
行 1048: [hv] Successfully pinged the hypervisor.
行 1049: [hv] Measured VM-exit overhead (TSC = 20674).
行 1050: [hv] Measured VM-exit overhead (MPERF = 0).
行 1051: [hv] Measured VM-exit overhead (CPU_CLK_UNHALTED.REF_TSC = 0).

This is all the information I can provide. I hope you can help me,thank you.

Supplement: I found a physical machine with i5 8400 win10 1909 and hv works fine.

@jonomango
Copy link
Owner

Have you tried this? #13 (comment)

@LYingSiMon
Copy link
Author

LYingSiMon commented Aug 3, 2023

yes.

hv/hv/vmcs.cpp

Line 51 in 86ca9f5

exit_ctrl.flags = 0;

The latest code, it's 0 here, so I didn't change it

hv/hv/ept.h

Line 10 in 86ca9f5

inline constexpr size_t ept_pd_count = 64;

Here I changed it to 512

But problems still arise

ScreenCAP.mp4

@untyper
Copy link

untyper commented Sep 20, 2023

Happened to me when I had other hypervisors running. Turn off your virtual machines and HyperV

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants