OK, I commented out the memtune section of the guest
<!--<memtune> <hard_limit unit='GiB'>128</hard_limit> </memtune>--> 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