mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-02-09 21:21:28 +00:00
27cd763500
Linux still defaults to a 1024 open file handle limit. This causes scalability problems for libvirtd / virtlockd / virtlogd on large hosts which might want > 1024 guest to be running. In fact if each guest needs > 1 FD, we can't even get to 500 guests. This is not good enough when we see machines with 100's of physical cores and TBs of RAM. In comparison to other memory requirements of libvirtd & related daemons, the resource usage associated with open file handles is essentially line noise. It is thus reasonable to increase the limits unconditionally for all installs. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
24 lines
727 B
SYSTEMD
24 lines
727 B
SYSTEMD
[Unit]
|
|
Description=Virtual machine log manager
|
|
Requires=virtlogd.socket
|
|
Before=libvirtd.service
|
|
Documentation=man:virtlogd(8)
|
|
Documentation=http://libvirt.org
|
|
|
|
[Service]
|
|
EnvironmentFile=-/etc/sysconfig/virtlogd
|
|
ExecStart=@sbindir@/virtlogd $VIRTLOGD_ARGS
|
|
ExecReload=/bin/kill -USR1 $MAINPID
|
|
# Loosing the logs is a really bad thing that will
|
|
# cause the machine to be fenced (rebooted), so make
|
|
# sure we discourage OOM killer
|
|
OOMScoreAdjust=-900
|
|
# Need to have at least one file open per guest (eg QEMU
|
|
# stdio log), but might be more (eg serial console logs)
|
|
# libvirtd.service written to expect 4096 guests, so if we
|
|
# guess at 2 log files per guest here (stdio + 1 serial):
|
|
LimitNOFILE=8192
|
|
|
|
[Install]
|
|
Also=virtlogd.socket
|