[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu Xenial) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Summary changed:
- Hyper-V Memory Ballooning re-broken in 16.04
+ [Hyper-V] Memory Ballooning re-broken in 16.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584597
Title:
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
Bernhard(galmok), the memory corruption you're seeing is likely a known
issue that happens when Linux guests are running on Windows Server 2012.
This was fixed recently in the upstream Linux kernels, so hopefully a
future update will have these patches.
--
You received this bug notification
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
Sorry, second screen shot didn't get attached. Here it is. See post #38
for details.
** Attachment added: "Ubuntu Mate Desktop 16.04.1 /proc/meminfo"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584597/+attachment/4738365/+files/ubuntu_mate_16..04.1_proc_mem_info_hyperv.png
--
You
OP seems to be MIA, but I'm also seeing higher than expected memory
usage. This is actually showing up in both Ubuntu 15.10 and 16.04. I've
attached screenshots of `cat proc/meminfo` from both an Ubuntu 15.10
Desktop and Ubuntu Mate 16.04.1 Desktop install.
The 15.10 VM has dynamic memory set to
OP seems to be MIA, but I'm also seeing higher than expected memory
usage. This is actually showing up in both Ubuntu 15.10 and 16.04. I've
attached screenshots of `cat proc/meminfo` from both an Ubuntu 15.10
Desktop and Ubuntu Mate 16.04.1 Desktop install.
The 15.10 VM has dynamic memory set to
I had same issue because my memory parameters didn't divide by 128mb
see official Hyper-V documentation Note 8 and 9:
https://technet.microsoft.com/ru-ru/windows-server-docs/compute/hyper-v/supported-ubuntu-virtual-machines-on-hyper-v
--
You received this bug notification because you are a
> Committed_AS: 7291440 kB
The amount of committed memory reported by meminfo is about 7GB. So it
shouldn't be surprising to see that the demand as seen by Hyper-V is
also high.
In general, the Hyper-V demand is calculated as Committed_AS value plus
some buffer(roughly 700MB if you have 8GB of
Here you go
root@ContainerHost1:~# cat /proc/meminfo
MemTotal:8328584 kB
MemFree: 130152 kB
MemAvailable:3530108 kB
Buffers: 273056 kB
Cached: 3071076 kB
SwapCached: 598656 kB
Active: 3785684 kB
Inactive:3125476 kB
Active(anon):
The hv_balloon driver hasn't changed between 15.10 and 16.04, so there
shouldn't be any difference in the way the driver reports demand to
Hyper-V.
To provide a further breakdown of the memory usage, can you show the
output of "cat /proc/meminfo"?
Might help to compare this info between 16.04
So both VM's are still sitting at the same memory usage according to hyper-v.
Memory demand hasn't seemed to budge either.
I tried this on a 15.10 box we had, and got very different results. I
logged in (Server needs a GUI for some tools) and memory went from 2gb
to 6gb. I did a few things, did a
One other caveat I should mention:
Even if the VM has reduced its memory consumption, Hyper-V does not
necessarily reclaim the unused memory from that VM.
Generally, Hyper-V reclaims unused memory from a VM if it's seeing
memory pressure from other VMs or if the Hyper-V host itself is seeing
Thanks. In both VMs, it looks like the buff/cached memory dropped by
2GB. After some time, did the Hyper-V host eventually reclaim this
memory? Can you check if the Hyper-V host's assigned memory also drops
after some time?
Also, can you tell us if you tried this on an older build where it
This machine didn't have any impact, but the other one dropped about 1g
of ram when I did that, less than should have been reclaimed, but some
reclamation at least.
** Attachment added: "Bug1584597-4.png"
Screenshot of VM that dropped some ram.
** Attachment added: "Bug1584597-5.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584597/+attachment/4692476/+files/Bug1584597-5.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
In both screenshots, it appears that the "buff/cache" value is very
high.
Perhaps the balloon driver is reporting the "buff/cache" as in use to
the host. Can you try running following commands to flush write buffers
and free page cache?
1) sync
2) echo 3 > /proc/sys/vm/drop_caches
After running
My apologies for so many separate comments, I'll try to keep the noise
down.
I should add that these boxes run redis, and the amount of data in redis
is fairly static. It's a devtest environment. Memory demand peaks at
boot and then falls off to a constant usage. So it's safe to assume that
the
This is the first time i've seen "free" drop down low as it should, but
the memory still hasn't been reclaimed by hyper-v. This particular VM
has been up 19 days. am I wrong in thinking that dynamic mem should have
scaled back to maybe... 2.2-ish GB? Roughly?
I tried looking at hv_balloon.c, but
Here's another screenshot from a different VM, same thing as previous
screenshot.
Demand should be roughly 3.6ish, but instead it's 7ish.
This box has been running for 7 days, I think this is the machine from
the original screenshot.
** Attachment added: "Bug1584597-3.png"
** Attachment added: "Bug1584597-2.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584597/+attachment/4692231/+files/Bug1584597-2.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Jason,
As Josh mentioned, the screenshot shows that demand as seen by Hyper-V
is still quite high compared to what is displayed inside the guest. If
this number doesn't settle, then Hyper-V would have no reason to reclaim
memory. Does the Hyper-V memory demand number ever settle after some
Thanks for all the additional information, we'll take a look.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584597
Title:
Hyper-V Memory Ballooning re-broken in 16.04
Status in linux
In your screenshot, memory demand reported by Hyper-V is quite a bit
higher than within the guest. How soon after the peak memory demand was
the screenshot taken?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Screenshot of hyper-v settings, and VM state, next to VM
** Attachment added: "Bug1584597.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584597/+attachment/4687972/+files/Bug1584597.png
--
You received this bug notification because you are a member of Kernel
Packages, which is
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jun 21 09:43 seq
crw-rw 1 root audio 116, 33 Jun 21 09:43 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
This bug is causing some serious issues for us with the 16.04 rollout.
We oversubscribe which is admittedly our problem, and our 16.04 VM's
spike to 8gb during boot, but then settle at a reasonable 2gb, but the
VM continues to hog 8gb to itself. We have 5 total, so that's a grand
total of 30GB
@l-ububtu-3 What was the procedure on the reinstall?
Based on my results, I will add some more checks to our long-term
testing efforts to see if ballooning messages are being dropped.
An explanation of Hyper-V dynamic memory in general is here:
I just reinstalled a VM and, on that VM, it doesn't work.
It would be really nice to have some visibility into the inner workings
of the hv_balloon module to figure out what's going on with it.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Oddly, the issue seems to have fixed itself. It's quite unclear how it
managed to do so though.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584597
Title:
Hyper-V Memory Ballooning
** Tags added: kernel-da-key kernel-hyper-v
** Tags added: xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584597
Title:
Hyper-V Memory Ballooning re-broken in 16.04
Status in
Per https://technet.microsoft.com/en-us/library/dn531029.aspx the
recommended kernel and tools to load is as follows:
# apt-get update
# apt-get install --install-recommends linux-virtual-lts-xenial
# apt-get install --install-recommends linux-tools-virtual-lts-xenial
I have tried a number of different reproduction scenarios at this point
on 4.4.0-21 and 4.4.0-22 and am not getting 100% except on a fresh
install.
Why are you modprobing hv_balloon? It should always be present and
should never need to be loaded manually.
--
You received this bug notification
I have verified that 4.4.0-22 does not balloon memory back to Hyper-V
and 4.4.0-21 does. We are investigating, but there doesn't seem to be a
lot of Hyper-V changes that relate to memory between these two kernels.
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Triaged
** Changed in:
I'd like to post the output of lspci -vnvn, but it doesn't return
anything on Hyper-V.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1584597
Title:
Hyper-V Memory Ballooning re-broken
39 matches
Mail list logo
