-
Notifications
You must be signed in to change notification settings - Fork 52
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
E_INVALID_ARG for WHvMapGpaRange #2
Comments
@steffengy @ionescu007 I had the same problem. I fixed it by adjusting s_TcbRegionAddress and s_Pml4PhysicalAddress to lower values according to the maximum RAM supported by my CPU model. I think the TCB boundary of 256Gb and PML4 boundary of 512Gb are the maximum values by the architect but the hypervisor limits them based on the actual CPU model installed on the system. for me the maximum value seems to be 64Gb on an intel-i7-3612qm (the maximum supported ram is 32Gb actually!) but as soon as I run the simpleator I get the Unhandled Exit reason 4 which is WHvRunVpExitReasonUnrecoverableException. |
Building the binaries and starting
simpleator.exe N:\path\to\testapp.exe
yielded an E_INVALID_ARG in the debug console so I tried to look into it:SemVmCreatePartition
.For bigger sizes, we get E_INVALID_ARG again.
Any idea whats going on there?
Are some kind of limits put onto the guest address space?
Running Win10 Pro 1903 x64, HyperV Platform and HyperV enabled.
The text was updated successfully, but these errors were encountered: