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.ehrha...@canonical.com> --- src/locking/virtlockd.service.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/locking/virtlockd.service.in b/src/locking/virtlockd.service.in index 928bf63..07e4847 100644 --- 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 -- 2.7.4 -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
