]> git.ipfire.org Git - thirdparty/libvirt.git/commit
projects / thirdparty / libvirt.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: c256813) | patch
Revert "qemu: Forbid <memoryBacking><locked> without <memtune><hard_limit>"
authorAndrea Bolognani <abologna@redhat.com>
Thu, 16 Mar 2017 17:23:56 +0000 (18:23 +0100)
committerAndrea Bolognani <abologna@redhat.com>
Tue, 28 Mar 2017 08:44:25 +0000 (10:44 +0200)
commit4b67e7a3779a695ad4460874ff6848e086ba08f3
treee7dc1666609dbb77a56c9ad2c9e54f5e77e2fac3tree | snapshot
parentc2568133bb3565ea605ddfff359c5da2ec5d55b7commit | diff
Revert "qemu: Forbid <memoryBacking><locked> without <memtune><hard_limit>"

This reverts commit c2e60ad0e5124482942164e5fec088157f5e716a.

Turns out this check is excessively strict: there are ways
other than <memtune><hard_limit> to raise the memory locking
limit for QEMU processes, one prominent example being
tweaking /etc/security/limits.conf.

Partially-resolves: https://bugzilla.redhat.com/1431793
src/qemu/qemu_domain.c diff | blob | blame | history
tests/qemuxml2argvdata/qemuxml2argv-mlock-on.xml diff | blob | blame | history
Mirror of https://github.com/libvirt/libvirt.git