External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-01-06 04:55:22 +00:00
Code Issues Packages Projects Releases Wiki Activity
a3f8abb003
libvirt/src/logging/virtlogd.service.in

27 lines
836 B
SYSTEMD
Raw Normal View History

Import stripped down virtlockd code as basis of virtlogd Copy the virtlockd codebase across to form the initial virlogd code. Simple search & replace of s/lock/log/ and gut the remote protocol & dispatcher. This gives us a daemon that starts up and listens for connections, but does nothing with them. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2015-02-09 16:35:05 +00:00
[Unit]
Description=Virtual machine log manager
Requires=virtlogd.socket
logd: add support for admin protocol in virtlogd Add a virtlogd-admin-sock can serves the admin protocol for the virtlogd daemon and define a virtlogd:///{system,session} URI scheme for connecting to it. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2018-01-19 14:54:00 +00:00
Requires=virtlogd-admin.socket
virtlogd.socket: Tie lifecycle to libvirtd.service We already guarantee that virtlogd.socket is enabled/disabled along with libvirtd.service, but if libvirtd.service has just been installed and is started before rebooting, then virtlogd.socket will not be running and guest startup will fail. Add Requires=virtlogd.socket to libvirtd.service to make sure virtlogd.socket is always started along with libvirtd.service, and add Before=libvirtd.service to both virtlogd.socket and virtlogd.service so that virtlogd never disappears before libvirtd has exited. Also add PartOf=libvirtd.service to both virtlogd.socket and virtlogd.service, so that virtlogd can be shut down when not needed. Resolves: https://bugzilla.redhat.com/1372576
2016-09-06 13:16:24 +00:00
Before=libvirtd.service
Import stripped down virtlockd code as basis of virtlogd Copy the virtlockd codebase across to form the initial virlogd code. Simple search & replace of s/lock/log/ and gut the remote protocol & dispatcher. This gives us a daemon that starts up and listens for connections, but does nothing with them. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2015-02-09 16:35:05 +00:00
Documentation=man:virtlogd(8)
Use https:// links for most sites This adds a rule to require https links for the libvirt, qemu and kvm websites. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2017-10-13 15:30:41 +00:00
Documentation=https://libvirt.org
Import stripped down virtlockd code as basis of virtlogd Copy the virtlockd codebase across to form the initial virlogd code. Simple search & replace of s/lock/log/ and gut the remote protocol & dispatcher. This gives us a daemon that starts up and listens for connections, but does nothing with them. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2015-02-09 16:35:05 +00:00
[Service]
build: don't hardcode /etc in the config related files Substitute in the @sysconfigdir@ value instead of /etc. Reviewed-by: Christophe de Dinechin <dinechin@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2019-07-18 15:17:07 +00:00
EnvironmentFile=-@sysconfdir@/sysconfig/virtlogd
Import stripped down virtlockd code as basis of virtlogd Copy the virtlockd codebase across to form the initial virlogd code. Simple search & replace of s/lock/log/ and gut the remote protocol & dispatcher. This gives us a daemon that starts up and listens for connections, but does nothing with them. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2015-02-09 16:35:05 +00:00
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
Increase default file handle limits for daemons 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>
2017-03-15 16:51:51 +00:00
# Need to have at least one file open per guest (eg QEMU
# stdio log), but might be more (eg serial console logs)
Increase default file handle limits for virtlogd The initial assumption was ~2 files per guest, but some common setups like Openstack drive up to 4 files per guest. E.g. on Arm where the following XML leads to 4 file handles: <serial type='file'> <source path='/var/lib/nova/instances/7c0dcd78-.../console.log'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='file'> <source path='/var/lib/nova/instances/7c0dcd78-.../console.log'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> With that in mind and the target to support 4k guests by default we should raise the limit to 16k. Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
2017-10-18 09:19:29 +00:00
# A common case is OpenStack which often has up to 4 file
# handles per guest.
Increase default file handle limits for daemons 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>
2017-03-15 16:51:51 +00:00
# libvirtd.service written to expect 4096 guests, so if we
Increase default file handle limits for virtlogd The initial assumption was ~2 files per guest, but some common setups like Openstack drive up to 4 files per guest. E.g. on Arm where the following XML leads to 4 file handles: <serial type='file'> <source path='/var/lib/nova/instances/7c0dcd78-.../console.log'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='file'> <source path='/var/lib/nova/instances/7c0dcd78-.../console.log'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> With that in mind and the target to support 4k guests by default we should raise the limit to 16k. Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
2017-10-18 09:19:29 +00:00
# guess at 4 files per guest here that is 16k:
LimitNOFILE=16384
Import stripped down virtlockd code as basis of virtlogd Copy the virtlockd codebase across to form the initial virlogd code. Simple search & replace of s/lock/log/ and gut the remote protocol & dispatcher. This gives us a daemon that starts up and listens for connections, but does nothing with them. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2015-02-09 16:35:05 +00:00
[Install]
Also=virtlogd.socket
Reference in New Issue Copy Permalink