mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-23 21:34:54 +03:00
4ac265173c
The comment that > For instance, qemu-ga doesn't support guest time synchronization on > Windows guests, but Linux ones. Was correct at the time, but has since been addressed by qemu/qemu@105fad6bb2, which added support for set-time without a time argument, as used by `virsh domtime --sync` by libvirt-guests.sh. I can confirm that `virsh domtime --sync` works correctly on a Windows 10 guest, as does `SYNC_TIME=1`. (Note that there can be a significant delay between when the command completes and when the guest time finishes synchronizing due to QEMU GA calling `w32tm` with `/nowait`, which complicates testing.) Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
51 lines
2.2 KiB
Plaintext
51 lines
2.2 KiB
Plaintext
# Customizations for the libvirt-guests.service systemd unit
|
|
|
|
# URIs to check for running guests
|
|
# example: URIS='default xen:///system vbox+tcp://host/system lxc:///system'
|
|
#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
|
|
|
|
# Number of seconds to wait between each guest start. Set to 0 to allow
|
|
# parallel startup.
|
|
#START_DELAY=0
|
|
|
|
# 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
|
|
|
|
# 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.
|
|
#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
|
|
|
|
# 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
|
|
|
|
# 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. By default, this functionality is turned off.
|
|
#SYNC_TIME=1
|