This bug was fixed in the package netcf - 0.1.9-2ubuntu3.1
---
netcf (0.1.9-2ubuntu3.1) precise-proposed; urgency=low
* netcf-debian-memleak.patch: prevent a memory leak when listing
interfaces (LP: #1201938)
-- Serge Hallyn serge.hal...@ubuntu.com Wed, 14 Aug 2013 15:32:11
This bug was fixed in the package netcf - 1:0.2.3-1ubuntu0.1
---
netcf (1:0.2.3-1ubuntu0.1) raring-proposed; urgency=low
* netcf-debian-memleak.patch: prevent a memory leak when listing
interfaces (LP: #1201938)
-- Serge Hallyn serge.hal...@ubuntu.com Tue, 13 Aug 2013
This bug was fixed in the package netcf - 0.2.0-1ubuntu1.1
---
netcf (0.2.0-1ubuntu1.1) quantal-proposed; urgency=low
* netcf-debian-memleak.patch: prevent a memory leak when listing
interfaces (LP: #1201938)
-- Serge Hallyn serge.hal...@ubuntu.com Wed, 14 Aug 2013 10:14:50
This bug was fixed in the package netcf - 0.2.0-1ubuntu1.1
---
netcf (0.2.0-1ubuntu1.1) quantal-proposed; urgency=low
* netcf-debian-memleak.patch: prevent a memory leak when listing
interfaces (LP: #1201938)
-- Serge Hallyn serge.hal...@ubuntu.com Wed, 14 Aug 2013 10:14:50
This bug was fixed in the package netcf - 1:0.2.3-1ubuntu0.1
---
netcf (1:0.2.3-1ubuntu0.1) raring-proposed; urgency=low
* netcf-debian-memleak.patch: prevent a memory leak when listing
interfaces (LP: #1201938)
-- Serge Hallyn serge.hal...@ubuntu.com Tue, 13 Aug 2013
This bug was fixed in the package netcf - 0.1.9-2ubuntu3.1
---
netcf (0.1.9-2ubuntu3.1) precise-proposed; urgency=low
* netcf-debian-memleak.patch: prevent a memory leak when listing
interfaces (LP: #1201938)
-- Serge Hallyn serge.hal...@ubuntu.com Wed, 14 Aug 2013 15:32:11
Confirmed for raring.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to netcf in Ubuntu.
https://bugs.launchpad.net/bugs/1201938
Title:
excessive memory use from libvirtd
To manage notifications about this bug go to:
Verified in quantal.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to netcf in Ubuntu.
https://bugs.launchpad.net/bugs/1201938
Title:
excessive memory use from libvirtd
To manage notifications about this bug go to:
Actually the precise libvirt isn't linked against netcf (as netcf isn't
in main there).
confirmed that 'ncftool list' in precise still works.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server
Confirmed for raring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201938
Title:
excessive memory use from libvirtd
To manage notifications about this bug go to:
Verified in quantal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201938
Title:
excessive memory use from libvirtd
To manage notifications about this bug go to:
Actually the precise libvirt isn't linked against netcf (as netcf isn't
in main there).
confirmed that 'ncftool list' in precise still works.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Stable memory use after three days. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to netcf in Ubuntu.
https://bugs.launchpad.net/bugs/1201938
Title:
excessive memory use from libvirtd
To manage notifications about this bug
Stable memory use after three days. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201938
Title:
excessive memory use from libvirtd
To manage notifications about this bug go to:
Hello Robert, or anyone else affected,
Accepted netcf into raring-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/netcf/1:0.2.3-1ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Robert, or anyone else affected,
Accepted netcf into raring-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/netcf/1:0.2.3-1ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
This is much better for me, but I have seen an increase of 1M over 5
hours so far - so there may be another lower-frequency leak. I will
file a new bug if I find that to be the case.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
This is much better for me, but I have seen an increase of 1M over 5
hours so far - so there may be another lower-frequency leak. I will
file a new bug if I find that to be the case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: netcf (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netcf (Ubuntu)
Importance: Undecided = High
** Changed in: netcf (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Also affects: libvirt (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: netcf (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: netcf (Ubuntu Quantal)
This bug was fixed in the package netcf - 1:0.2.3-3ubuntu1
---
netcf (1:0.2.3-3ubuntu1) saucy; urgency=low
* netcf-debian-memleak.patch: prevent a memory leak when listing
interfaces (LP: #1201938)
-- Serge Hallyn serge.hal...@ubuntu.com Wed, 14 Aug 2013 00:29:13 +
**
** No longer affects: libvirt (Ubuntu Precise)
** No longer affects: libvirt (Ubuntu Quantal)
** No longer affects: libvirt (Ubuntu)
** No longer affects: libvirt (Ubuntu Raring)
** Description changed:
+ ==
+ SRU Justification
+ 1. Impact: libvirt over time consumes excessive
Note the raring debdiff (which I don't have perms to push) is at
http://people.canonical.com/~serge/netcf-raring.debdiff.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to netcf in Ubuntu.
https://bugs.launchpad.net/bugs/1201938
Title:
The leak was in libnetcf. Eric Blake has pushed a patch upstream to fix
it. I will push packages today and tomorrow with the fix.
** Changed in: libvirt (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: netcf (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netcf (Ubuntu)
Importance: Undecided = High
** Changed in: netcf (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: libvirt (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: netcf (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: netcf (Ubuntu Quantal)
This bug was fixed in the package netcf - 1:0.2.3-3ubuntu1
---
netcf (1:0.2.3-3ubuntu1) saucy; urgency=low
* netcf-debian-memleak.patch: prevent a memory leak when listing
interfaces (LP: #1201938)
-- Serge Hallyn serge.hal...@ubuntu.com Wed, 14 Aug 2013 00:29:13 +
**
** No longer affects: libvirt (Ubuntu Precise)
** No longer affects: libvirt (Ubuntu Quantal)
** No longer affects: libvirt (Ubuntu)
** No longer affects: libvirt (Ubuntu Raring)
** Description changed:
+ ==
+ SRU Justification
+ 1. Impact: libvirt over time consumes excessive
Note the raring debdiff (which I don't have perms to push) is at
http://people.canonical.com/~serge/netcf-raring.debdiff.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201938
Title:
excessive
I had previously reproduced this with a ppa build from an hourly
upstream snapshot. I reported this upstream at
https://www.redhat.com/archives/libvir-list/2013-July/msg01751.html
Today I can't reproduce this even in stock saucy.
libvirt hasn't been updated in the archive in the meantime.
Ok, very slow leak appears to still be in saucy. will re-try with a
fresh fedora install (local so i'm not in a hurry :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201938
Title:
excessive
Reproduced in saucy (1.0.6 libvirt) as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201938
Title:
excessive memory use from libvirtd
To manage notifications about this bug go to:
I can reproduce it - albeit slowly - even without any vms running.
I'll try with saucy next, then try to narrow it down to a few commits.
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Triaged
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
Running vms:
$ virsh list
IdName State
1 seed running
6 baremetal_2running
I have virt-manager connected showing both cpu usage and host cpu usage.
With
https://github.com/tripleo/incubator/blob/master/devtest.md
shows the relevant workflow
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201938
Title:
excessive memory use from libvirtd
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201938
Title:
Not using rbd at all.
We're using libvirt to host the tripleo dev/test story (rather than
requiring developers to have multiple physical machines).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
To reproduce - run something like virt-manager and a couple of vms for
an extended period (days). Eventually libvirtd will use a lot of ram and
then if you push it long enough get OOM killed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Tags added: apport-collected
** Description changed:
libvirtd is using excessive amounts of memory after a week or so of uptime:
uptime
07:47:15 up 9 days, 21:49, 16 users, load average: 1.06, 2.20, 1.70
from top (sorry for the truncated line, window got
** Changed in: libvirt (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201938
Title:
excessive memory use from libvirtd
To manage notifications about this
40 matches
Mail list logo
