Increase default file handle limits for virtlockd

The assumption so far was an average of 4 disks per guest.
But some architectures, like s390x, still often use plenty of smaller disks.

To include those in the considerations an assumption of an average of 10
disks is more reasonable.

Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>

diff --git a/src/locking/virtlockd.service.in b/src/locking/virtlockd.service.in
index 928bf63fb2e6293b28ed39b4a54f78f88deb0688..07e48478b781d0ec4e6d3318c827411afdecbbd5 100644 (file)
--- a/src/locking/virtlockd.service.in
+++ b/src/locking/virtlockd.service.in
@@ -15,8 +15,8 @@ ExecReload=/bin/kill -USR1 $MAINPID
 OOMScoreAdjust=-900
 # Needs to allow for max guests * average disks per guest
 # libvirtd.service written to expect 4096 guests, so if we
-# allow for 4 disks per guest, we get:
-LimitNOFILE=16384
+# allow for 10 disks per guest, we get:
+LimitNOFILE=40960
 
 [Install]
 Also=virtlockd.socket