1# default xenstored config 2 3# Where the pid file is stored 4pid-file = @XEN_RUN_DIR@/xenstored.pid 5 6# Randomly failed a transaction with EAGAIN. Used for testing Xs user 7test-eagain = false 8 9# Activate transaction merge support 10merge-activate = true 11 12# Limits applied to domains whose writes cause other domains' transaction 13# commits to fail. Must include decimal point. 14 15# The burst limit is the number of conflicts a domain can cause to 16# fail in a short period; this value is used for both the initial and 17# the maximum value of each domain's conflict-credit, which falls by 18# one point for each conflict caused, and when it reaches zero the 19# domain's requests are ignored. 20conflict-burst-limit = 5.0 21 22# The conflict-credit is replenished over time: 23# one point is issued after each conflict-max-history-seconds, so this 24# is the minimum pause-time during which a domain will be ignored. 25conflict-max-history-seconds = 0.05 26 27# If the conflict-rate-limit-is-aggregate flag is true then after each 28# tick one point of conflict-credit is given to just one domain: the 29# one at the front of the queue. If false, then after each tick each 30# domain gets a point of conflict-credit. 31# 32# In environments where it is known that every transaction will 33# involve a set of nodes that is writable by at most one other domain, 34# then it is safe to set this aggregate-limit flag to false for better 35# performance. (This can be determined by considering the layout of 36# the xenstore tree and permissions, together with the content of the 37# transactions that require protection.) 38# 39# A transaction which involves a set of nodes which can be modified by 40# multiple other domains can suffer conflicts caused by any of those 41# domains, so the flag must be set to true. 42conflict-rate-limit-is-aggregate = true 43 44# Activate node permission system 45perms-activate = true 46 47# Activate the watch permission system 48# When this is enabled unprivileged guests can only get watch events 49# for xenstore entries that they would've been able to read. 50# 51# When this is disabled unprivileged guests may get watch events 52# for xenstore entries that they cannot read. The watch event contains 53# only the entry name, not the value. 54# This restores behaviour prior to XSA-115. 55perms-watch-activate = true 56 57# Activate quota 58quota-activate = true 59quota-maxentity = 1000 60quota-maxsize = 2048 61quota-maxwatch = 100 62quota-transaction = 10 63quota-maxrequests = 1024 64quota-path-max = 1024 65 66# Activate filed base backend 67persistent = false 68 69# Xenstored logs 70# xenstored-log-file = @XEN_LOG_DIR@/xenstored.log 71# xenstored-log-level = null 72# xenstored-log-nb-files = 10 73 74# Xenstored access logs 75# access-log-file = @XEN_LOG_DIR@/xenstored-access.log 76# access-log-nb-lines = 13215 77# acesss-log-nb-chars = 180 78# access-log-special-ops = false 79 80# Perodically scanning all the rings as a safenet for lazy clients. 81# Define the interval in seconds, set to negative to disable. 82# ring-scan-interval = 20 83 84xenstored-kva = @XENSTORED_KVA@ 85xenstored-port = @XENSTORED_PORT@ 86