2020-04-02 16:20:08 +00:00
|
|
|
# Customizations for the libvirt-guests.service systemd unit
|
|
|
|
|
2010-05-14 13:37:55 +00:00
|
|
|
# URIs to check for running guests
|
2018-03-27 13:32:07 +00:00
|
|
|
# example: URIS='default xen:///system vbox+tcp://host/system lxc:///system'
|
2010-05-14 13:37:55 +00:00
|
|
|
#URIS=default
|
|
|
|
|
|
|
|
# action taken on host boot
|
|
|
|
# - start all guests which were running on shutdown are started on boot
|
|
|
|
# regardless on their autostart settings
|
|
|
|
# - ignore libvirt-guests init script won't start any guest on boot, however,
|
|
|
|
# guests marked as autostart will still be automatically started by
|
|
|
|
# libvirtd
|
|
|
|
#ON_BOOT=start
|
|
|
|
|
2012-02-28 15:09:42 +00:00
|
|
|
# Number of seconds to wait between each guest start. Set to 0 to allow
|
|
|
|
# parallel startup.
|
2011-04-15 08:57:06 +00:00
|
|
|
#START_DELAY=0
|
|
|
|
|
2010-05-14 13:37:55 +00:00
|
|
|
# action taken on host shutdown
|
|
|
|
# - suspend all running guests are suspended using virsh managedsave
|
|
|
|
# - shutdown all running guests are asked to shutdown. Please be careful with
|
|
|
|
# this settings since there is no way to distinguish between a
|
|
|
|
# guest which is stuck or ignores shutdown requests and a guest
|
|
|
|
# which just needs a long time to shutdown. When setting
|
|
|
|
# ON_SHUTDOWN=shutdown, you must also set SHUTDOWN_TIMEOUT to a
|
|
|
|
# value suitable for your guests.
|
|
|
|
#ON_SHUTDOWN=suspend
|
|
|
|
|
2017-08-14 16:39:36 +00:00
|
|
|
# Number of guests will be shutdown concurrently, taking effect when
|
|
|
|
# "ON_SHUTDOWN" is set to "shutdown". If Set to 0, guests will be shutdown one
|
|
|
|
# after another. Number of guests on shutdown at any time will not exceed number
|
|
|
|
# set in this variable.
|
2012-02-28 15:09:42 +00:00
|
|
|
#PARALLEL_SHUTDOWN=0
|
|
|
|
|
|
|
|
# Number of seconds we're willing to wait for a guest to shut down. If parallel
|
|
|
|
# shutdown is enabled, this timeout applies as a timeout for shutting down all
|
|
|
|
# guests on a single URI defined in the variable URIS. If this is 0, then there
|
|
|
|
# is no time out (use with caution, as guests might not respond to a shutdown
|
|
|
|
# request). The default value is 300 seconds (5 minutes).
|
|
|
|
#SHUTDOWN_TIMEOUT=300
|
2011-07-14 23:22:53 +00:00
|
|
|
|
|
|
|
# If non-zero, try to bypass the file system cache when saving and
|
|
|
|
# restoring guests, even though this may give slower operation for
|
|
|
|
# some file systems.
|
|
|
|
#BYPASS_CACHE=0
|
2015-02-18 10:59:22 +00:00
|
|
|
|
|
|
|
# If non-zero, try to sync guest time on domain resume. Be aware, that
|
|
|
|
# this requires guest agent with support for time synchronization
|
|
|
|
# running in the guest. For instance, qemu-ga doesn't support guest time
|
|
|
|
# synchronization on Windows guests, but Linux ones. By default, this
|
|
|
|
# functionality is turned off.
|
|
|
|
#SYNC_TIME=1
|