Evan, from your screenshots, I can see that the memory demand values and the /proc/meminfo values do match closely to each other.
On the 16.04.01 VM, /proc/meminfo shows Committed_AS value is ~1800MB. The balloon driver then adds a buffer of ~300MB (this buffer is calculated according to how much total memory is assigned to the VM). So ~1800MB + ~300MB = 2100MB matches closely with the 2088 MB memory demand that you're seeing from the host. A similar calculation on the 15.10 VM also shows that the meminfo values match closely with the reported memory demand. (~2900MB committed + ~500MB buffer = 3400MB compared to 3600MB) The main culprit in both cases appears to be the large amount of committed memory. Would be worth investigating what the cause of this memory usage is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584597 Title: Hyper-V Memory Ballooning re-broken in 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584597/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
