I seem to experience a kernel crash (or application crash in early
moments of this bug) due to Hyper-V ballooning (or at least dynamic
memory). I am using Xenial on Hyper-V on Windows Server 2012 64bit. I
started using dynamic memory (1024 Kb start memory, allowed growing to
3072 Kb). Apparently this worked fine; I saw memory rise during demand
and memory was released back to the host when not needed. But the
releasing of memory apparently causes memory corruption. I noticed this
my using the stress tool that was called like this:

bme@zabbix:~$ stress --vm-bytes $(awk '/MemFree/{printf "%d\n", $2 * 0.9;}' < 
/proc/meminfo)k --vm-keep -m 1
stress: info: [3698] dispatching hogs: 0 cpu, 0 io, 1 vm, 0 hdd
stress: FAIL: [3699] (522) memory corruption at: 0x7fd801e00010
stress: FAIL: [3698] (394) <-- worker 3699 returned error 1
stress: WARN: [3698] (396) now reaping child worker processes
stress: FAIL: [3698] (451) failed run completed in 0s

The memory corruption only occured when Hyper-V had reclaimed memory
(balloning). Disabling dynamic memory has removed the memory

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  Hyper-V Memory Ballooning re-broken in 16.04

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to