[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Edward Hope-Morley]

** 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:
  Realtime feature mlockall: Cannot allocate memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[James Page]

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
 .
   * d/p/bug-1708305-qemu-Fix-memory-locking-limit-calculation.patch:
 Remove memlock limit when using .
 (LP: #1708305).


** Changed in: cloud-archive/ocata
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1708305

Title:
  Realtime feature mlockall: Cannot allocate memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[James Page]

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
 .
   * d/p/bug-1708305-qemu-Fix-memory-locking-limit-calculation.patch:
 Remove memlock limit when using .
 (LP: #1708305).


** Changed in: cloud-archive/mitaka
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1708305

Title:
  Realtime feature mlockall: Cannot allocate memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[James Page]

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
 .
   * d/p/bug-1708305-qemu-Fix-memory-locking-limit-calculation.patch:
 Remove memlock limit when using .
 (LP: #1708305).


** Changed in: cloud-archive/ocata
   Status: Fix Committed => Fix Released

-- 
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:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[James Page]

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
 .
   * d/p/bug-1708305-qemu-Fix-memory-locking-limit-calculation.patch:
 Remove memlock limit when using .
 (LP: #1708305).


** Changed in: cloud-archive/mitaka
   Status: Fix Committed => Fix Released

-- 
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:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Jorge Niedbalski]

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 about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Jorge Niedbalski]

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 to Ubuntu.
https://bugs.launchpad.net/bugs/1708305

Title:
  Realtime feature mlockall: Cannot allocate memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Launchpad Bug Tracker]

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   Thu, 10 Aug 2017
22:50:46 -0400

** Changed in: libvirt (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
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:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Launchpad Bug Tracker]

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   Fri, 11 Aug 2017
00:34:01 -0400

** Changed in: libvirt (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

-- 
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:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[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 mlockall: Cannot allocate memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Jorge Niedbalski]

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 1: parsed user script and 465 library scripts using 
112796virt/48420res/6644shr/42136data kb, in 140usr/50sys/318real ms.
Pass 2: analyzed script: 1 probe, 5 functions, 100 embeds, 0 globals using 
164772virt/101816res/7956shr/94112data kb, in 750usr/290sys/3419real ms.
Pass 3: translated to C into "/tmp/stap2amlcj/stap_54795_src.c" using 
164772virt/102008res/8148shr/94112data kb, in 0usr/0sys/5real ms.
Pass 4: compiled C into "stap_54795.ko" in 2180usr/530sys/3318real ms.
Pass 5: starting run.
locked: 55222 -> RLIMIT_MEMLOCK, [9007199254740991,9007199254740991]

Marking the zesty verification as 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:
  Realtime feature mlockall: Cannot allocate memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Jorge Niedbalski]

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", 
_rlimit_resource_str($resource), _struct_rlimit_u($rlim))) }' -kv  -g 
--suppress-time-limits 
Pass 1: parsed user script and 465 library scripts using 
112804virt/48432res/6652shr/42144data kb, in 160usr/20sys/176real ms.
Pass 2: analyzed script: 1 probe, 5 functions, 100 embeds, 0 globals using 
164780virt/101832res/7968shr/94120data kb, in 740usr/140sys/2122real ms.
Pass 3: translated to C into "/tmp/stapXqZhh3/stap_54310_src.c" using 
164780virt/102024res/8160shr/94120data kb, in 10usr/0sys/13real ms.
Pass 4: compiled C into "stap_54310.ko" in 2040usr/540sys/4985real ms.
Pass 5: starting run.

It looks like the process limit has been applied correctly and the guest
starts:

locked: 54734 -> RLIMIT_MEMLOCK, [9007199254740991,9007199254740991]

Marking the xenial verification as done.

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
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:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Chris J Arges]

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
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libvirt (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-xenial

-- 
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:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[ChristianEhrhardt]

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: Cannot allocate memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Edward Hope-Morley]

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 mlockall: Cannot allocate memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Brian Murray]

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
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libvirt (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-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 mlockall: Cannot allocate memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Jorge Niedbalski]

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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708305

Title:
  Realtime feature mlockall: Cannot allocate memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Jorge Niedbalski]

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

** Changed in: cloud-archive/ocata
   Status: Triaged => In Progress

-- 
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:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Corey Bryant]

** 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 Committed

** Changed in: cloud-archive
   Importance: Undecided => Medium

** Changed in: cloud-archive/mitaka
   Importance: Undecided => Medium

** Changed in: cloud-archive/ocata
   Importance: Undecided => Medium

** Changed in: cloud-archive/ocata
 Assignee: (unassigned) => Jorge Niedbalski (niedbalski)

** Changed in: cloud-archive/mitaka
 Assignee: (unassigned) => Jorge Niedbalski (niedbalski)

** Changed in: cloud-archive/mitaka
   Status: New => Triaged

** Changed in: cloud-archive/ocata
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1708305

Title:
  Realtime feature mlockall: Cannot allocate memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Corey Bryant]

** 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 Committed

** Changed in: cloud-archive
   Importance: Undecided => Medium

** Changed in: cloud-archive/mitaka
   Importance: Undecided => Medium

** Changed in: cloud-archive/ocata
   Importance: Undecided => Medium

** Changed in: cloud-archive/ocata
 Assignee: (unassigned) => Jorge Niedbalski (niedbalski)

** Changed in: cloud-archive/mitaka
 Assignee: (unassigned) => Jorge Niedbalski (niedbalski)

** Changed in: cloud-archive/mitaka
   Status: New => Triaged

** Changed in: cloud-archive/ocata
   Status: New => Triaged

-- 
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:
https://bugs.launchpad.net/cloud-archive/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[ChristianEhrhardt]

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 looks good other than 
waiting the few days the process defines).

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[ChristianEhrhardt]

** 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:  Ubuntu 16.04.2 LTS
  Release:  16.04
  Codename: xenial
  
  root@buneary:~# uname -r
  4.10.0-29-generic
  
  Reproducible also with the 4.4 kernel.
  
- [Description]
+ [Detailed Description]
  
  When a guest memory backing stanza is defined using the  stanza + 
hugepages,
  as follows:
  
    
  
    
    
  
  
  
    
  
  (Full guest definition: http://paste.ubuntu.com/25229162/)
  
  The guest fails to start due to the following error:
  
  2017-08-02 20:25:03.714+: starting up libvirt version: 1.3.1, package: 
1ubuntu10.12 (Christian Ehrhardt  Wed, 19 Jul 
2017 08:28:14 +0200), qemu version: 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.14), 
hostname: buneary.seg
  LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 
QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name reproducer2 -S -machine 
pc-i440fx-2.5,accel=kvm,usb=off -cpu host -m 124928 -realtime mlock=on -smp 
32,sockets=16,cores=1,threads=2 -object 
memory-backend-file,id=ram-node0,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,share=yes,size=64424509440,host-nodes=0,policy=bind
 -numa node,nodeid=0,cpus=0-15,memdev=ram-node0 -object 
memory-backend-file,id=ram-node1,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,share=yes,size=66571993088,host-nodes=1,policy=bind
 -numa node,nodeid=1,cpus=16-31,memdev=ram-node1 -uuid 
2460778d-979b-4024-9a13-0c3ca04b18ec -no-user-config -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-reproducer2/monitor.sock,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive 
file=/var/lib/uvtool/libvirt/images/test-ds.qcow,format=qcow2,if=none,id=drive-virtio-disk0,cache=none
 -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-vnc 127.0.0.1:0 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  Domain id=14 is tainted: host-cpu
  char device redirected to /dev/pts/1 (label charserial0)
  
  mlockall: Cannot allocate memory
  
  2017-08-02T20:25:37.732772Z qemu-system-x86_64: locking memory failed
  2017-08-02 20:25:37.811+: shutting down
  
  This seems to be due to the setrlimit for RLIMIT_MEMLOCK is too low for 
mlockall
  to work given the large amount of memory.
  
  There is a libvirt upstream patch that enforces the existence of the
  hard_limit stanza when using with  in the memory backing settings.
  
  
https://github.com/libvirt/libvirt/commit/c2e60ad0e5124482942164e5fec088157f5e716a
  
  Memory locking can only work properly if the memory locking limit
  for the QEMU process has been raised appropriately: the default one
  is extremely low, so there's no way the guest will fit in there.
  
  The commit
  
https://github.com/libvirt/libvirt/commit/7e667664d28f90bf6916604a55ebad7e2d85305b
  is also required when using hugepages and the locked stanza.
  
- [Test Case] 
-  * Define a guest that uses the following stanzas (See for a full guest 
reference: http://paste.ubuntu.com/25288141/)
+ [Test Case]
+  * Define a guest that uses the following stanzas (See for a full guest 
reference: http://paste.ubuntu.com/25288141/)
  
-   120
-   120
+   120
+   120
  
-   
- 
-   
-   
- 
- 
- 
-   
+   
+ 
+   
+   
+ 
+ 
+ 
+   
  
  * virsh define guest.xml
  * virsh start guest.xml
  * Without the fix, the following error will be raised and the guest
  will not start.
  
  root@buneary:/home/ubuntu# virsh start reproducer2
  error: Failed to start domain reproducer2
  error: internal error: process exited while connecting to monitor: mlockall: 
Cannot allocate memory
  2017-08-11T03:59:54.936275Z qemu-system-x86_64: locking memory failed
  
  * With the fix, the error shouldn't be displayed and the guest started
  
- 
  [Suggested Fix]
  
  *
  
https://github.com/libvirt/libvirt/commit/7e667664d28f90bf6916604a55ebad7e2d85305b
  (Proposed)
+ 
+ 
+ [Regression Potential] 
+ 
+  * There is one (theoretical) thing to think of - the change increases  
+the lock resource limits for the spawned qemu. Maybe that could be 
+used as an attack. Fortunately  the defnition does have neither 
+locked nor hugepages by default so opt-in, and while the guest can 
+do all kind of things when exploited it can only hardly change it's 
+(virtual) physical memory to increase what the host might be locking. 
+Yet worth to mention IMHO
+ 
+  * 

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[ChristianEhrhardt]

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 will have to wait until being 
considered and accepted by the SRU Team.
As I outlined below when I set low prio (I understand it is more for some 
people) I don't think it is overall urgent enough to override the other SRU 
that is already almost complete.

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[ChristianEhrhardt]

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 as a fix in the dev 
version is a prereq.

#2 Patch?
I reviewed your changes and I'm ok with the patch, headers and backport.
Also in general while I'm not so sure on unlimited in general I see why they 
can't set a better value int his case - and since this is as-upstream this is 
good.

#3 SRU Queue?
Last SRU just complete, I think we are good adding a new one to the queue.

#4 Regressions
Thanks for pre-testing on your side already, gives some extra confidence.
I also checked via a (very basic) sniff test, full tests will have to be done 
on proposed but that we always do.
Therefore ok for now to go on.

#5 SRU Template
You already provided half of it, it misses a few things like regression 
considerations.
I can add those, but then nothing seems to block us from sponsoring this for 
SRU review IMO.

** Changed in: libvirt (Ubuntu Artful)
   Status: Fix Committed => Fix Released

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Jorge Niedbalski]

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 are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  Codename: xenial
  
  root@buneary:~# uname -r
  4.10.0-29-generic
  
  Reproducible also with the 4.4 kernel.
  
  [Description]
  
  When a guest memory backing stanza is defined using the  stanza + 
hugepages,
  as follows:
  
    
  
    
    
  
  
  
    
  
  (Full guest definition: http://paste.ubuntu.com/25229162/)
  
  The guest fails to start due to the following error:
  
  2017-08-02 20:25:03.714+: starting up libvirt version: 1.3.1, package: 
1ubuntu10.12 (Christian Ehrhardt  Wed, 19 Jul 
2017 08:28:14 +0200), qemu version: 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.14), 
hostname: buneary.seg
  LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 
QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name reproducer2 -S -machine 
pc-i440fx-2.5,accel=kvm,usb=off -cpu host -m 124928 -realtime mlock=on -smp 
32,sockets=16,cores=1,threads=2 -object 
memory-backend-file,id=ram-node0,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,share=yes,size=64424509440,host-nodes=0,policy=bind
 -numa node,nodeid=0,cpus=0-15,memdev=ram-node0 -object 
memory-backend-file,id=ram-node1,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,share=yes,size=66571993088,host-nodes=1,policy=bind
 -numa node,nodeid=1,cpus=16-31,memdev=ram-node1 -uuid 
2460778d-979b-4024-9a13-0c3ca04b18ec -no-user-config -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-reproducer2/monitor.sock,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive 
file=/var/lib/uvtool/libvirt/images/test-ds.qcow,format=qcow2,if=none,id=drive-virtio-disk0,cache=none
 -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-vnc 127.0.0.1:0 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  Domain id=14 is tainted: host-cpu
  char device redirected to /dev/pts/1 (label charserial0)
  
  mlockall: Cannot allocate memory
  
  2017-08-02T20:25:37.732772Z qemu-system-x86_64: locking memory failed
  2017-08-02 20:25:37.811+: shutting down
  
  This seems to be due to the setrlimit for RLIMIT_MEMLOCK is too low for 
mlockall
  to work given the large amount of memory.
  
  There is a libvirt upstream patch that enforces the existence of the
  hard_limit stanza when using with  in the memory backing settings.
  
  
https://github.com/libvirt/libvirt/commit/c2e60ad0e5124482942164e5fec088157f5e716a
  
  Memory locking can only work properly if the memory locking limit
  for the QEMU process has been raised appropriately: the default one
  is extremely low, so there's no way the guest will fit in there.
  
  The commit
  
https://github.com/libvirt/libvirt/commit/7e667664d28f90bf6916604a55ebad7e2d85305b
  is also required when using hugepages and the locked stanza.
  
+ [Test Case] 
+  * Define a guest that uses the following stanzas (See for a full guest 
reference: http://paste.ubuntu.com/25288141/)
+ 
+   120
+   120
+ 
+   
+ 
+   
+   
+ 
+ 
+ 
+   
+ 
+ * virsh define guest.xml
+ * virsh start guest.xml
+ * Without the fix, the following error will be raised and the guest
+ will not start.
+ 
+ root@buneary:/home/ubuntu# virsh start reproducer2
+ error: Failed to start domain reproducer2
+ error: internal error: process exited while connecting to monitor: mlockall: 
Cannot allocate memory
+ 2017-08-11T03:59:54.936275Z qemu-system-x86_64: locking memory failed
+ 
+ * With the fix, the error shouldn't be displayed and the guest started
+ 
  
  [Suggested Fix]
  
  *
- 
https://github.com/libvirt/libvirt/commit/c2e60ad0e5124482942164e5fec088157f5e716a
- 
- *
  
https://github.com/libvirt/libvirt/commit/7e667664d28f90bf6916604a55ebad7e2d85305b
+ (Proposed)

** Tags added: sts-sru-needed

** Patch added: "fix-1708305-zesty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+attachment/4930472/+files/fix-1708305-zesty.debdiff

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Ubuntu Foundations Team Bug Bot]

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" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Jorge Niedbalski]

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.

root@buneary:/home/ubuntu# virsh start reproducer2
error: Failed to start domain reproducer2
error: internal error: process exited while connecting to monitor: mlockall: 
Cannot allocate memory
2017-08-11T03:59:54.936275Z qemu-system-x86_64: locking memory failed

With the patch the guest is initialized correctly.

root@buneary:/var/lib/uvtool/libvirt/images# virsh start reproducer2
Domain reproducer2 started

I ran the following systemtap probe (probe
kernel.function("sys_setrlimit") { printf("locked: %d -> %s\n", pid(),
sprintf("%s, %s", _rlimit_resource_str($resource),
_struct_rlimit_u($rlim))) } )

And the output shows that the RLIMIT_MEMLOCK process limit is set to
9007199254740991 (VIR_DOMAIN_MEMORY_PARAM_UNLIMITED)

root@buneary:/home/ubuntu# stap -g qemu_probe.stap -kv  -g 
--suppress-time-limits 
Pass 1: parsed user script and 465 library scripts using 
112796virt/48440res/6664shr/42136data kb, in 130usr/40sys/164real ms.
Pass 2: analyzed script: 1 probe, 5 functions, 100 embeds, 0 globals using 
164772virt/101848res/7988shr/94112data kb, in 660usr/120sys/776real ms.
Pass 3: translated to C into "/tmp/stapVXuoMi/stap_30601_src.c" using 
164772virt/102040res/8180shr/94112data kb, in 10usr/0sys/5real ms.
Pass 4: compiled C into "stap_30601.ko" in 2160usr/540sys/3231real ms.
Pass 5: starting run.
locked: 31028 -> RLIMIT_MEMLOCK, [9007199254740991,9007199254740991]


** Changed in: libvirt (Ubuntu Artful)
   Status: Confirmed => Fix Released

** Changed in: libvirt (Ubuntu Artful)
   Status: Fix Released => Fix Committed

** Patch added: "fix-1708305-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+attachment/4930463/+files/fix-1708305-xenial.debdiff

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Jorge Niedbalski]

** 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

** Changed in: libvirt (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: libvirt (Ubuntu Xenial)
 Assignee: (unassigned) => Jorge Niedbalski (niedbalski)

** Changed in: libvirt (Ubuntu Zesty)
 Assignee: (unassigned) => Jorge Niedbalski (niedbalski)

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Jorge Niedbalski]

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
without the need of a further patch in nova. 

I am currently testing it with different memory sizes w/without hugepages and 
the locked
stanza enabled. I will be posting the entire test results soon.

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Jorge Niedbalski]

** 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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Jorge Niedbalski]

** 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 allocate memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Jorge Niedbalski]

** 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 Niedbalski (niedbalski)

** Description changed:

  [Environment]
  
  root@buneary:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  Codename: xenial
  
  root@buneary:~# uname -r
  4.10.0-29-generic
  
  Reproducible also with the 4.4 kernel.
  
  [Description]
  
  When a guest memory backing stanza is defined using the  stanza + 
hugepages,
  as follows:
  
-   
- 
-   
-   
- 
- 
- 
-   
+   
+ 
+   
+   
+ 
+ 
+ 
+   
  
  (Full guest definition: http://paste.ubuntu.com/25229162/)
  
  The guest fails to start due to the following error:
  
  2017-08-02 20:25:03.714+: starting up libvirt version: 1.3.1, package: 
1ubuntu10.12 (Christian Ehrhardt  Wed, 19 Jul 
2017 08:28:14 +0200), qemu version: 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.14), 
hostname: buneary.seg
  LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 
QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name reproducer2 -S -machine 
pc-i440fx-2.5,accel=kvm,usb=off -cpu host -m 124928 -realtime mlock=on -smp 
32,sockets=16,cores=1,threads=2 -object 
memory-backend-file,id=ram-node0,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,share=yes,size=64424509440,host-nodes=0,policy=bind
 -numa node,nodeid=0,cpus=0-15,memdev=ram-node0 -object 
memory-backend-file,id=ram-node1,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,share=yes,size=66571993088,host-nodes=1,policy=bind
 -numa node,nodeid=1,cpus=16-31,memdev=ram-node1 -uuid 
2460778d-979b-4024-9a13-0c3ca04b18ec -no-user-config -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-reproducer2/monitor.sock,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive 
file=/var/lib/uvtool/libvirt/images/test-ds.qcow,format=qcow2,if=none,id=drive-virtio-disk0,cache=none
 -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-vnc 127.0.0.1:0 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  Domain id=14 is tainted: host-cpu
  char device redirected to /dev/pts/1 (label charserial0)
  
  mlockall: Cannot allocate memory
  
  2017-08-02T20:25:37.732772Z qemu-system-x86_64: locking memory failed
  2017-08-02 20:25:37.811+: shutting down
  
- This seems to be due to the setrlimit for RLIMIT_MEMLOCK is too low for 
mlockall 
+ This seems to be due to the setrlimit for RLIMIT_MEMLOCK is too low for 
mlockall
  to work given the large amount of memory.
  
- There is a libvirt upstream patch that enforces the existence of the 
+ There is a libvirt upstream patch that enforces the existence of the
  hard_limit stanza when using with  in the memory backing settings.
  
  
https://github.com/libvirt/libvirt/commit/c2e60ad0e5124482942164e5fec088157f5e716a
  
  Memory locking can only work properly if the memory locking limit
  for the QEMU process has been raised appropriately: the default one
  is extremely low, so there's no way the guest will fit in there.
  
+ The commit
+ 
https://github.com/libvirt/libvirt/commit/7e667664d28f90bf6916604a55ebad7e2d85305b
+ is also required when using hugepages and the locked stanza.
+ 
+ 
  [Suggested Fix]
  
  *
  
https://github.com/libvirt/libvirt/commit/c2e60ad0e5124482942164e5fec088157f5e716a
+ 
+ *
+ 
https://github.com/libvirt/libvirt/commit/7e667664d28f90bf6916604a55ebad7e2d85305b

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[ChristianEhrhardt]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[ChristianEhrhardt]

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 will need a while to get back
to that.

** Tags added: libvirt-3.6

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Eric Desrochers]

** 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 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:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Peter Sabaini]

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:
  Realtime feature mlockall: Cannot allocate memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Peter Sabaini]

** 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:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Launchpad Bug Tracker]

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:
  Realtime feature mlockall: Cannot allocate memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1708305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs