blob: 90401577087928796314eefdd123725ffcdf3e25 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
|
# /etc/conf.d/libvirtd
# LIBVIRTD_OPTS
# You may want to add '--listen' to have libvirtd listen for tcp/ip connections
# if you want to use libvirt for remote control
# Please consult 'libvirtd --help' for more options
#LIBVIRTD_OPTS="--listen"
# LIBVIRTD_KVM_SHUTDOWN
# Valid options:
# * shutdown - Sends an ACPI shutdown (think when you tap the power button
# on your machine and it begins a graceful shutdown). If your
# VM ignores this, it will have the power yanked out from under
# it in LIBVIRTD_KVM_SHUTDOWN_MAXWAIT seconds.
# * managedsave - Performs a state save external to the VM. qemu-kvm will stop
# stop the CPU and save off all state to a separate file. When
# the machine is started again, it will resume like nothing ever
# happened. This is guarenteed to always successfully stop your
# machine and restart it. However it may take some time to finish.
# * none - No attempts will be made to stop any VMs. If you are restarting your
# machine the qemu-kvm process will be simply killed, which may result
# in your VMs having disk corruption.
LIBVIRTD_KVM_SHUTDOWN="managedsave"
# LIBVIRTD_KVM_SHUTDOWN_MAXWAIT
# Timeout in seconds until stopping libvirtd and "pulling the plug" on the
# remaining VM's still in a running state
#LIBVIRTD_KVM_SHUTDOWN_MAXWAIT="500"
# LIBVIRTD_NET_SHUTDOWN
# If libvirtd created networks for you (e.g. NATed networks) then this init
# script will shut them down for you if this is set to 'yes'. Otherwise,
# the networks will be left running once libvirt is shutdown. For this
# option to be useful you must have enabled the 'virt-network' USE flag and
# have had libvirt create a NATed network for you.
# Valid values: 'yes' or 'no'
#LIBVIRTD_NET_SHUTDOWN="yes"
|
GitWeb
