--- Comment #3 from Marcel Moolenaar <> ---
It looks like AllocatePages() succeeded. Is that correct?

If yes, then it's possible that there's a Hyper-V bug. 

Try to obtain the memory map before the call to AllocatePages and then again
after the call to AllocatePages. The memory map should show a difference of
exactly the amount of pages being allocated. Some unused memory region should
be smaller by the same amount. Any discrepancy is an indication of a bug in
AllocatePages. If the memory map looks fine, then the problem may be later: at
the time the loader is ready to jump into the kernel. The loader calls
ExitBootServices around that time for example...


You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________ mailing list
To unsubscribe, send any mail to 

Reply via email to