1# Master virtlockd daemon configuration file 2# 3 4################################################################# 5# 6# Logging controls 7# 8 9# Logging level: 4 errors, 3 warnings, 2 information, 1 debug 10# basically 1 will log everything possible 11# 12# WARNING: USE OF THIS IS STRONGLY DISCOURAGED. 13# 14# WARNING: It outputs too much information to practically read. 15# WARNING: The "log_filters" setting is recommended instead. 16# 17# WARNING: Journald applies rate limiting of messages and so libvirt 18# WARNING: will limit "log_level" to only allow values 3 or 4 if 19# WARNING: journald is the current output. 20# 21# WARNING: USE OF THIS IS STRONGLY DISCOURAGED. 22#log_level = 3 23 24# Logging filters: 25# A filter allows to select a different logging level for a given category 26# of logs. The format for a filter is: 27# 28# level:match 29# 30# where 'match' is a string which is matched against the category 31# given in the VIR_LOG_INIT() at the top of each libvirt source 32# file, e.g., "remote", "qemu", or "util.json". The 'match' in the 33# filter matches using shell wildcard syntax (see 'man glob(7)'). 34# The 'match' is always treated as a substring match. IOW a match 35# string 'foo' is equivalent to '*foo*'. 36# 37# 'level' is the minimal level where matching messages should 38# be logged: 39# 40# 1: DEBUG 41# 2: INFO 42# 3: WARNING 43# 4: ERROR 44# 45# Multiple filters can be defined in a single @log_filters, they just need 46# to be separated by spaces. Note that libvirt performs "first" match, i.e. 47# if there are concurrent filters, the first one that matches will be applied, 48# given the order in @log_filters. 49# 50# For the virtlockd daemon, a typical need is to capture information 51# from the locking code and some of the utility code. Some utility 52# code is very verbose and is generally not desired. A suitable filter 53# string for debugging might be to turn off object, json & event logging, 54# but enable the rest of the util and the locking code: 55# 56#log_filters="1:locking 4:object 4:json 4:event 1:util" 57 58# Logging outputs: 59# An output is one of the places to save logging information 60# The format for an output can be: 61# level:stderr 62# output goes to stderr 63# level:syslog:name 64# use syslog for the output and use the given name as the ident 65# level:file:file_path 66# output to a file, with the given filepath 67# level:journald 68# output to journald logging system 69# In all cases 'level' is the minimal priority, acting as a filter 70# 1: DEBUG 71# 2: INFO 72# 3: WARNING 73# 4: ERROR 74# 75# Multiple outputs can be defined, they just need to be separated by spaces. 76# e.g. to log all warnings and errors to syslog under the virtlockd ident: 77#log_outputs="3:syslog:virtlockd" 78# 79 80# The maximum number of concurrent client connections to allow 81# on primary socket 82# Each running virtual machine will require one open connection 83# to virtlockd. So 'max_clients' will affect how many VMs can 84# be run on a host 85#max_clients = 1024 86 87# The maximum number of concurrent client connections to allow 88# on administrative socket 89#admin_max_clients = 5 90