** Changed in: cloud-archive/mitaka
Status: Fix Committed => Fix Released
** Changed in: cloud-archive
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package libvirt - 4.0.0-1ubuntu8.15~cloud0
---
libvirt (4.0.0-1ubuntu8.15~cloud0) xenial-queens; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
libvirt (4.0.0-1ubuntu8.15) bionic; urgency=medium
.
*
This bug was fixed in the package libvirt - 4.0.0-1ubuntu8.15~cloud0
---
libvirt (4.0.0-1ubuntu8.15~cloud0) xenial-queens; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
libvirt (4.0.0-1ubuntu8.15) bionic; urgency=medium
.
*
This bug was fixed in the package libvirt - 1.3.1-1ubuntu10.30
---
libvirt (1.3.1-1ubuntu10.30) xenial; urgency=medium
* d/p/lp-1844455-node_device_conf-Don-t-leak-physical_function.patch:
fix memory-leak from PCI-related structure. (LP: #1844455)
*
This bug was fixed in the package libvirt - 4.0.0-1ubuntu8.15
---
libvirt (4.0.0-1ubuntu8.15) bionic; urgency=medium
* d/p/lp-1844455-node_device_conf-Don-t-leak-physical_function.patch:
fix memory-leak from PCI-related structure. (LP: #1844455)
-- gpicc...@canonical.com
This bug was fixed in the package libvirt - 5.4.0-0ubuntu5.1
---
libvirt (5.4.0-0ubuntu5.1) eoan; urgency=medium
* d/p/lp-1844455-node_device_conf-Don-t-leak-physical_function.patch:
fix memory-leak from PCI-related structure. (LP: #1844455)
-- gpicc...@canonical.com
I've managed to verify the following proposed versions of libvirt:
* Eoan: 5.4.0-0ubuntu5.1
* Bionic: 4.0.0-1ubuntu8.15
* Xenial/Queens: 4.0.0-1ubuntu8.15~cloud0
* Xenial: 1.3.1-1ubuntu10.30
* Trusty/Mitaka: 1.3.1-1ubuntu10.30~cloud0
In all cases, Valgrind approach was used to verify the leak
** Changed in: cloud-archive/queens
Status: In Progress => Fix Committed
** Changed in: cloud-archive/mitaka
Status: In Progress => Fix Committed
** Changed in: cloud-archive
Status: In Progress => Fix Committed
--
You received this bug notification because you are a
** Changed in: cloud-archive/mitaka
Status: Confirmed => In Progress
** Changed in: cloud-archive/queens
Status: Fix Committed => In Progress
** Changed in: cloud-archive
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of
** Also affects: cloud-archive/queens
Importance: Undecided
Status: New
** Changed in: cloud-archive/queens
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: cloud-archive/queens
Status: New => Confirmed
--
You received this bug notification because
Hello Guilherme, or anyone else affected,
Accepted libvirt into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/1.3.1-1ubuntu10.30 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Guilherme, or anyone else affected,
Accepted libvirt into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/5.4.0-0ubuntu5.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Patch added: "lp1844455-bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1844455/+attachment/5332043/+files/lp1844455-bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1844455-eoan.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1844455/+attachment/5332044/+files/lp1844455-eoan.debdiff
** Changed in: libvirt (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: libvirt (Ubuntu Bionic)
Status:
The patch for LP #1864918 (Xenial-only) is being also uploaded here, in the
Xenial debdiff.
Thanks Dariusz for sponsoring this one!
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- It was reported that libvirt 1.3.1 running on Trusty (through
- UCA/Mitaka) is getting OOM'ed after a while - in our reports took 2
- years for the leak to trigger an out-of-memory situation, but this may
- change according to the user available memory.
+ [Impact]
+ *
Formatting was severely impaired on last comment, so here's a more
'visual" diagram set: https://pastebin.ubuntu.com/p/Qps5g2gmsv
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The function that allocates the structure _virPCIDeviceAddress is:
virPCIGetDeviceAddressFromSysfsLink().
This function is called in the following path, specifically in
virPCIGetPhysicalFunction(), which is itself called from
nodeDeviceSysfsGetPCISRIOVCaps().
[0] [1][2]
** Summary changed:
- Memory leak on libvirt 1.3.1
+ Memory leak of struct _virPCIDeviceAddress on libvirt
** Changed in: libvirt (Ubuntu Focal)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
19 matches
Mail list logo
