** Changed in: qemu-kvm (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/591610
Title:
memory leak
To manage notifications
Chris, could you confirm whether this is in fact fixed in
lucid-proposed?
--
memory leak
https://bugs.launchpad.net/bugs/591610
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
Serge: Yep, per the other bug, this is totally fixed for me.
--
memory leak
https://bugs.launchpad.net/bugs/591610
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
Note: I deleted the proposal for merge for
https://code.launchpad.net/~serge-hallyn/ubuntu/lucid/qemu-kvm/memleak-fix
because it is already in lucid-proposed.
** Changed in: qemu-kvm (Ubuntu)
Status: Triaged = Fix Committed
--
memory leak
https://bugs.launchpad.net/bugs/591610
You
I ran my test again overnight with the packages from -proposed and it's
not fixed the leak for me
--
memory leak
https://bugs.launchpad.net/bugs/591610
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Hrm, okay, thanks Chris.
Is this VM managed by libvirt? Is it possible the memory leak is in
libvirt, rather than kvm?
--
memory leak
https://bugs.launchpad.net/bugs/591610
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in
Dustin: yep, managed by libvirt.
I'm pretty sure the leak is kvm and not libvirt - the one remaining kvm process
this morning had a VIRT of ~7GB.
--
memory leak
https://bugs.launchpad.net/bugs/591610
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Dustin: It's certainly possible. It was easy enough to reproduce this
bug - I just ran one VM per CPU core, doing constant IO stress for about
8 hours and it entirely consumed the 8GB in the machine, so when that's
SRU'd we can test to see if it's fixed :)
--
memory leak
Chris-
Do you think this is a dupe of Bug #588293? There's a patch attached to
that one. Serge is going to apply that patch, and put up a package for
testing, and we'll try to get it SRU'd to Lucid.
** Package changed: kvm (Ubuntu) = qemu-kvm (Ubuntu)
--
memory leak
As I mentioned in comment #2, I re-ran my test with 0.12.4 (a simple
rebuild of the package from sid) and after almost 12 hours there was no
sign of memory leaking.
--
memory leak
https://bugs.launchpad.net/bugs/591610
You received this bug notification because you are a member of Ubuntu
Server
** Attachment added: syslog showing the OOM events
http://launchpadlibrarian.net/49996223/syslog-kvm-oom.txt
** Bug watch added: SourceForge.net Tracker #2989366
http://sourceforge.net/support/tracker.php?aid=2989366
** Also affects: kvm via
I've linked this bug to an upstream bug filed against 0.12.3 (the
version of KVM we have in Lucid) which describes a serious memory leak.
I am also repeating the test with 0.12.4 which claims to fix the leak.
--
memory leak
https://bugs.launchpad.net/bugs/591610
You received this bug
According to the upstream bug report, this is fixed in version 0.12.4
however I am unsure of the exact commit that resolved it. Although I
haven't encountered this issue yet, i'm going to mark it as triaged as
upstream, have essentially confirmed it with the version we ship.
** Changed in: kvm
13 matches
Mail list logo
