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.

Sign up for GitHub

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

Jump to bottom

Memory range fragmentation bug ("Failed to get Memory Geometry") [Hyper-V bug] #10

Open
vivianezw opened this issue Oct 12, 2020 · 0 comments
Open

Memory range fragmentation bug ("Failed to get Memory Geometry") [Hyper-V bug] #10

vivianezw opened this issue Oct 12, 2020 · 0 comments

Comments

@vivianezw
Copy link
Collaborator

vivianezw commented Oct 12, 2020 •
edited
Loading

This is an unfixable Hyper-V bug.

It happens only on Hyper-V VMs with "Dynamic Memory" enabled.
The memory ranges will fragment after a while leading to thousands of memory ranges. (reported: up to 8000!)
It's not only bad for memory dumping, it's generally bad.

Can be avoided by making sure the "Dynamic Memory" setting is disabled. It can be disabled at any time, but the machine needs to be powered down.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vivianezw