Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • Thanks - you are definitely onto something. lsmod | grep hv_ shows hv_balloon on the low memory machine but not on the other - so the balloon module is loaded on one and not the other. And the behaviour looks very much like this description. Commented Feb 11, 2016 at 5:06
  • Not sure what the equivalent to vmware-toolbox-cmd is on Hyper V though. Commented Feb 11, 2016 at 5:06
  • @assylias I know, sorry. I looked myself while writing this answer and came up empty. However, if you write a program that quickly allocates a lot of memory, that may convince the hypervisor that your VM needs the resources. Similar to disk cache eviction test case, but different root cause. Commented Feb 11, 2016 at 13:20
  • You can unset the dynamic ram feature in Hyper-V to solve this issue. Commented Aug 23, 2017 at 11:06
  • 3
    I don't really see the solution here I'm afraid. Commented Nov 2, 2018 at 11:51