** Changed in: cloud-archive
Status: Fix Committed => Fix Released
** Tags removed: sts-sru-needed
** Tags added: sts-sru-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708305
Title:
This bug was fixed in the package libvirt - 2.5.0-3ubuntu5.5~cloud0
---
libvirt (2.5.0-3ubuntu5.5~cloud0) xenial-ocata; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
libvirt (2.5.0-3ubuntu5.5) zesty; urgency=medium
.
*
This bug was fixed in the package libvirt - 1.3.1-1ubuntu10.14~cloud0
---
libvirt (1.3.1-1ubuntu10.14~cloud0) trusty-mitaka; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
libvirt (1.3.1-1ubuntu10.14) xenial; urgency=medium
.
*
This bug was fixed in the package libvirt - 2.5.0-3ubuntu5.5~cloud0
---
libvirt (2.5.0-3ubuntu5.5~cloud0) xenial-ocata; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
libvirt (2.5.0-3ubuntu5.5) zesty; urgency=medium
.
*
This bug was fixed in the package libvirt - 1.3.1-1ubuntu10.14~cloud0
---
libvirt (1.3.1-1ubuntu10.14~cloud0) trusty-mitaka; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
libvirt (1.3.1-1ubuntu10.14) xenial; urgency=medium
.
*
Verified on mitaka cloud http://pastebin.ubuntu.com/25621886/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708305
Title:
Realtime feature mlockall: Cannot allocate memory
To manage notifications
Verified on ocata cloud http://pastebin.ubuntu.com/25621949/
** Tags removed: verification-mitaka-needed verification-ocata-needed
** Tags added: verification-mitaka-done verification-ocata-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This bug was fixed in the package libvirt - 1.3.1-1ubuntu10.14
---
libvirt (1.3.1-1ubuntu10.14) xenial; urgency=medium
* d/p/bug-1708305-qemu-Fix-memory-locking-limit-calculation.patch:
Remove memlock limit when using .
(LP: #1708305).
-- Jorge Niedbalski
This bug was fixed in the package libvirt - 2.5.0-3ubuntu5.5
---
libvirt (2.5.0-3ubuntu5.5) zesty; urgency=medium
* d/p/bug-1708305-qemu-Fix-memory-locking-limit-calculation.patch:
Remove memlock limit when using .
(LP: #1708305).
-- Jorge Niedbalski
** Tags removed: verification-needed verification-needed-zesty
** Tags added: verification-done verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708305
Title:
Realtime feature
Repeated the previous attempt with a zesty machine, same results.
root@zesty:/home/ubuntu# stap -e 'probe kernel.function("sys_setrlimit") {
printf("locked: %d -> %s\n", pid(), sprintf("%s, %s",
_rlimit_resource_str($resource), _struct_rlimit_u($rlim))) }' -kv -g
--suppress-time-limits
Pass
OK, I commented out the memtune section of the guest
without a hard_limit set and started it, checking with the following
stap script:
root@buneary:/home/ubuntu# stap -e 'probe kernel.function("sys_setrlimit") {
printf("locked: %d -> %s\n", pid(), sprintf("%s, %s",
Hello Jorge, 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.14 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
The former SRU now completed, could one on the SRU Team move the Xenial
from unapproved to proposed 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/1708305
Title:
Realtime feature mlockall:
just for clarity i'm nominating for newton and it will be marked as
invalid since there is no libvirt in newton uca
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708305
Title:
Realtime feature
Hello Jorge, or anyone else affected,
Accepted libvirt into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/2.5.0-3ubuntu5.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Attached is the patch for Z/O UCA.
** Patch added: "fix-1708305-ocata.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+attachment/4930779/+files/fix-1708305-ocata.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Attached is the patch for T/M UCA.
** Patch added: "fix-1708305-trusty-mitaka.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+attachment/4930778/+files/fix-1708305-trusty-mitaka.debdiff
** Changed in: cloud-archive/mitaka
Status: Triaged => In Progress
**
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/mitaka
Importance: Undecided
Status: New
** Also affects: cloud-archive/ocata
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Fix
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/mitaka
Importance: Undecided
Status: New
** Also affects: cloud-archive/ocata
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Fix
Changes are in git, and pushed for SRU acceptance.
@SRU Team:
1. currently there is one libvirt SRU ongoing (on T/X - bug 1707400)
2. it is known and clear that acceptance of this SRU here prereqs that the
referenced one has completed
=> So please accept this once the other completed (which
** Description changed:
+ [Impact]
+
+ * Guest definitions that uses locked memory + hugepages fail to spawn
+
+ * Backport upstream fix to solve that issue
+
+
[Environment]
root@buneary:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:
Umm one thing - I checked qemu on the SRU queue, but while killing qemu
due to limits it is obviously a libvirt change.
That said there is an ongoing libvirt SRU already.
It is all green on tests and verifications, but needs some time to complete
following the SRU policy. That time this upload
Hi Jorge,
thanks for your prep work on this.
Checking prereqs.
#1 fixed in Dev?
I read the "there is a patch" before as "there is a -new- patch", but checked
now.
This is in since version 3.2 which makes it fix released in Artful already.
While I work on 3.6 we don't need it to go on with this
Attaching the patch for Zesty, please look the previous comment for
all the context.
Package for testing is available on this PPA
https://launchpad.net/~niedbalski/+archive/ubuntu/lp1708305/+packages
** Description changed:
[Environment]
root@buneary:~# lsb_release -a
No LSB modules
The attachment "fix-1708305-xenial.debdiff" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch"
Hello Christian,
Attached you can find a xenial SRU patch based on commit
(https://github.com/libvirt/libvirt/commit/7e667664d28f90bf6916604a55ebad7e2d85305b).
Here is the guest definition used on my testing
(http://paste.ubuntu.com/25288141/)
Without the patch, the error is reproduced.
** Changed in: libvirt (Ubuntu Xenial)
Status: New => In Progress
** Changed in: libvirt (Ubuntu Zesty)
Status: New => In Progress
** Changed in: libvirt (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: libvirt (Ubuntu Xenial)
Importance: High => Medium
**
Hello Christian,
- Could you please check if is feasible to include
https://github.com/libvirt/libvirt/commit/7e667664d28f90bf6916604a55ebad7e2d85305b
in the
current artful release as a patch?
The commit seems quite portable (and applies cleanly) and this would allow us
to fix the issue
** Changed in: libvirt (Ubuntu Artful)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708305
Title:
Realtime feature mlockall: Cannot allocate memory
To
** Changed in: libvirt (Ubuntu Artful)
Assignee: Jorge Niedbalski (niedbalski) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708305
Title:
Realtime feature mlockall: Cannot
** Changed in: libvirt (Ubuntu Artful)
Status: Confirmed => In Progress
** Changed in: libvirt (Ubuntu Artful)
Importance: Low => High
** Changed in: libvirt (Ubuntu Artful)
Importance: High => Medium
** Changed in: libvirt (Ubuntu Artful)
Assignee: (unassigned) => Jorge
** Changed in: libvirt (Ubuntu Artful)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708305
Title:
Realtime feature mlockall: Cannot allocate memory
To manage
With the workaround available to globally set the memtune/hard_limit
this is prio low, but certainly sounds like a valid issue.
Depending if we merge libvirt 3.6 this will be part of that merge or a
backport for artful and then consider SRUs from there.
FYI: I put this onto my tracking list, but
** Also affects: libvirt (Ubuntu Artful)
Importance: Undecided
Status: Confirmed
** Also affects: libvirt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Zesty)
Importance: Undecided
Status: New
--
You received this bug
Just to confirm that I can see this issue as well, and also that
configuring memtune/hard_limit to $LARGE_VALUE makes it go away
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708305
Title:
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708305
Title:
Realtime feature mlockall: Cannot allocate memory
To manage notifications about this bug go to:
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/1708305
Title:
38 matches
Mail list logo
