qemu.conf 12.6 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11
# Master configuration file for the QEMU driver.
# All settings described here are optional - if omitted, sensible
# defaults are used.

# VNC is configured to listen on 127.0.0.1 by default.
# To make it listen on all public interfaces, uncomment
# this next option.
#
# NB, strong recommendation to enable TLS + x509 certificate
# verification when allowing public access
#
12
#vnc_listen = "0.0.0.0"
13

14 15 16 17 18
# Enable this option to have VNC served over an automatically created
# unix socket. This prevents unprivileged access from users on the
# host machine, though most VNC clients do not support it.
#
# This will only be enabled for VNC configurations that do not have
19 20
# a hardcoded 'listen' or 'socket' value. This setting takes preference
# over vnc_listen.
21
#
22
#vnc_auto_unix_socket = 1
23 24 25 26 27 28

# Enable use of TLS encryption on the VNC server. This requires
# a VNC client which supports the VeNCrypt protocol extension.
# Examples include vinagre, virt-viewer, virt-manager and vencrypt
# itself. UltraVNC, RealVNC, TightVNC do not support this
#
29
# It is necessary to setup CA and issue a server certificate
30 31
# before enabling this.
#
32
#vnc_tls = 1
33 34 35 36 37 38 39 40 41 42 43 44


# Use of TLS requires that x509 certificates be issued. The
# default it to keep them in /etc/pki/libvirt-vnc. This directory
# must contain
#
#  ca-cert.pem - the CA master certificate
#  server-cert.pem - the server certificate signed with ca-cert.pem
#  server-key.pem  - the server private key
#
# This option allows the certificate directory to be changed
#
45
#vnc_tls_x509_cert_dir = "/etc/pki/libvirt-vnc"
46 47 48 49


# The default TLS configuration only uses certificates for the server
# allowing the client to verify the server's identity and establish
E
Eric Blake 已提交
50
# an encrypted channel.
51 52 53
#
# It is possible to use x509 certificates for authentication too, by
# issuing a x509 certificate to every client who needs to connect.
54
#
55 56 57
# Enabling this option will reject any client who does not have a
# certificate signed by the CA in /etc/pki/libvirt-vnc/ca-cert.pem
#
58
#vnc_tls_x509_verify = 1
59 60 61 62 63 64


# The default VNC password. Only 8 letters are significant for
# VNC passwords. This parameter is only used if the per-domain
# XML config does not already provide a password. To allow
# access without passwords, leave this commented out. An empty
E
Eric Blake 已提交
65
# string will still enable passwords, but be rejected by QEMU,
66
# effectively preventing any use of VNC. Obviously change this
E
Eric Blake 已提交
67
# example here before you set this.
68
#
69
#vnc_password = "XYZ12345"
70 71


72 73 74 75 76 77 78 79
# Enable use of SASL encryption on the VNC server. This requires
# a VNC client which supports the SASL protocol extension.
# Examples include vinagre, virt-viewer and virt-manager
# itself. UltraVNC, RealVNC, TightVNC do not support this
#
# It is necessary to configure /etc/sasl2/qemu.conf to choose
# the desired SASL plugin (eg, GSSPI for Kerberos)
#
80
#vnc_sasl = 1
81 82 83 84 85 86 87


# The default SASL configuration file is located in /etc/sasl2/
# When running libvirtd unprivileged, it may be desirable to
# override the configs in this location. Set this parameter to
# point to the directory, and create a qemu.conf in that location
#
88
#vnc_sasl_dir = "/some/directory/sasl2"
89 90 91



92 93 94 95 96 97 98
# SPICE is configured to listen on 127.0.0.1 by default.
# To make it listen on all public interfaces, uncomment
# this next option.
#
# NB, strong recommendation to enable TLS + x509 certificate
# verification when allowing public access
#
99
#spice_listen = "0.0.0.0"
100 101 102 103 104 105 106


# Enable use of TLS encryption on the SPICE server.
#
# It is necessary to setup CA and issue a server certificate
# before enabling this.
#
107
#spice_tls = 1
108 109 110 111 112 113 114 115 116 117


# Use of TLS requires that x509 certificates be issued. The
# default it to keep them in /etc/pki/libvirt-spice. This directory
# must contain
#
#  ca-cert.pem - the CA master certificate
#  server-cert.pem - the server certificate signed with ca-cert.pem
#  server-key.pem  - the server private key
#
E
Eric Blake 已提交
118
# This option allows the certificate directory to be changed.
119
#
120
#spice_tls_x509_cert_dir = "/etc/pki/libvirt-spice"
121 122 123 124 125 126


# The default SPICE password. This parameter is only used if the
# per-domain XML config does not already provide a password. To
# allow access without passwords, leave this commented out. An
# empty string will still enable passwords, but be rejected by
E
Eric Blake 已提交
127 128
# QEMU, effectively preventing any use of SPICE. Obviously change
# this example here before you set this.
129
#
130
#spice_password = "XYZ12345"
131

132

133 134 135 136
# The default security driver is SELinux. If SELinux is disabled
# on the host, then the security driver will automatically disable
# itself. If you wish to disable QEMU SELinux security driver while
# leaving SELinux enabled for the host in general, then set this
E
Eric Blake 已提交
137
# to 'none' instead.
138
#
139
#security_driver = "selinux"
140

141 142 143
# If set to non-zero, then the default security labeling
# will make guests confined. If set to zero, then guests
# will be unconfined by default. Defaults to 1.
144
#security_default_confined = 1
145 146 147

# If set to non-zero, then attempts to create unconfined
# guests will be blocked. Defaults to 0.
148
#security_require_confined = 1
149

E
Eric Blake 已提交
150
# The user ID for QEMU processes run by the system instance.
151 152
#user = "root"

E
Eric Blake 已提交
153
# The group ID for QEMU processes run by the system instance.
154
#group = "root"
155

156 157 158 159 160
# Whether libvirt should dynamically change file ownership
# to match the configured user/group above. Defaults to 1.
# Set to 0 to disable file ownership changes.
#dynamic_ownership = 1

161 162 163 164 165

# What cgroup controllers to make use of with QEMU guests
#
#  - 'cpu' - use for schedular tunables
#  - 'devices' - use for device whitelisting
E
Eric Blake 已提交
166
#  - 'memory' - use for memory tunables
A
Alex Jia 已提交
167
#  - 'blkio' - use for block devices I/O tunables
H
Hu Tao 已提交
168
#  - 'cpuset' - use for CPUs and memory nodes
169
#  - 'cpuacct' - use for CPUs statistics.
170 171
#
# NB, even if configured here, they won't be used unless
E
Eric Blake 已提交
172
# the administrator has mounted cgroups, e.g.:
173 174
#
#  mkdir /dev/cgroup
H
Hu Tao 已提交
175
#  mount -t cgroup -o devices,cpu,memory,blkio,cpuset none /dev/cgroup
176
#
E
Eric Blake 已提交
177
# They can be mounted anywhere, and different controllers
178 179 180
# can be mounted in different locations. libvirt will detect
# where they are located.
#
181
#cgroup_controllers = [ "cpu", "devices", "memory", "blkio", "cpuset", "cpuacct" ]
182 183 184 185 186 187 188 189

# This is the basic set of devices allowed / required by
# all virtual machines.
#
# As well as this, any configured block backed disks,
# all sound device, and all PTY devices are allowed.
#
# This will only need setting if newer QEMU suddenly
E
Eric Blake 已提交
190
# wants some device we don't already know about.
191 192 193 194 195
#
#cgroup_device_acl = [
#    "/dev/null", "/dev/full", "/dev/zero",
#    "/dev/random", "/dev/urandom",
#    "/dev/ptmx", "/dev/kvm", "/dev/kqemu",
196
#    "/dev/rtc","/dev/hpet"
197
#]
198

199

200 201 202 203
# The default format for Qemu/KVM guest save images is raw; that is, the
# memory from the domain is dumped out directly to a file.  If you have
# guests with a large amount of memory, however, this can take up quite
# a bit of space.  If you would like to compress the images while they
204 205 206 207
# are being saved to disk, you can also set "lzop", "gzip", "bzip2", or "xz"
# for save_image_format.  Note that this means you slow down the process of
# saving a domain in order to save disk space; the list above is in descending
# order by performance and ascending order by compression ratio.
208
#
209 210 211 212 213 214 215 216
# save_image_format is used when you use 'virsh save' at scheduled
# saving, and it is an error if the specified save_image_format is
# not valid, or the requested compression program can't be found.
#
# dump_image_format is used when you use 'virsh dump' at emergency
# crashdump, and if the specified dump_image_format is not valid, or
# the requested compression program can't be found, this falls
# back to "raw" compression.
217
#
218 219
#save_image_format = "raw"
#dump_image_format = "raw"
220

H
Hu Tao 已提交
221 222 223 224
# When a domain is configured to be auto-dumped when libvirtd receives a
# watchdog event from qemu guest, libvirtd will save dump files in directory
# specified by auto_dump_path. Default value is /var/lib/libvirt/qemu/dump
#
225
#auto_dump_path = "/var/lib/libvirt/qemu/dump"
226

227 228 229 230 231 232
# When a domain is configured to be auto-dumped, enabling this flag
# has the same effect as using the VIR_DUMP_BYPASS_CACHE flag with the
# virDomainCoreDump API.  That is, the system will avoid using the
# file system cache while writing the dump file, but may cause
# slower operation.
#
233
#auto_dump_bypass_cache = 0
234 235 236 237 238 239 240

# When a domain is configured to be auto-started, enabling this flag
# has the same effect as using the VIR_DOMAIN_START_BYPASS_CACHE flag
# with the virDomainCreateWithFlags API.  That is, the system will
# avoid using the file system cache when restoring any managed state
# file, but may cause slower operation.
#
241
#auto_start_bypass_cache = 0
242

243 244 245 246 247 248 249 250 251
# If provided by the host and a hugetlbfs mount point is configured,
# a guest may request huge page backing.  When this mount point is
# unspecified here, determination of a host mount point in /proc/mounts
# will be attempted.  Specifying an explicit mount overrides detection
# of the same in /proc/mounts.  Setting the mount point to "" will
# disable guest hugepage backing.
#
# NB, within this mount point, guests will create memory backing files
# in a location of  $MOUNTPOINT/libvirt/qemu
252
#
253
#hugetlbfs_mount = "/dev/hugepages"
254

255

256 257 258
# mac_filter enables MAC addressed based filtering on bridge ports.
# This currently requires ebtables to be installed.
#
259
#mac_filter = 1
260

261

262 263 264 265
# By default, PCI devices below non-ACS switch are not allowed to be assigned
# to guests. By setting relaxed_acs_check to 1 such devices will be allowed to
# be assigned to guests.
#
266
#relaxed_acs_check = 1
267 268 269 270 271 272 273 274 275


# QEMU implements an extension for providing audio over a VNC connection,
# though if your VNC client does not support it, your only chance for getting
# sound output is through regular audio backends. By default, libvirt will
# disable all QEMU sound backends if using VNC, since they can cause
# permissions issues. Enabling this option will make libvirtd honor the
# QEMU_AUDIO_DRV environment variable when using VNC.
#
276
#vnc_allow_host_audio = 0
277

278

279 280 281 282 283 284 285
# If clear_emulator_capabilities is enabled, libvirt will drop all
# privileged capabilities of the QEmu/KVM emulator. This is enabled by
# default.
#
# Warning: Disabling this option means that a compromised guest can
# exploit the privileges and possibly do damage to the host.
#
286
#clear_emulator_capabilities = 1
287 288 289 290 291 292 293 294 295 296


# If allow_disk_format_probing is enabled, libvirt will probe disk
# images to attempt to identify their format, when not otherwise
# specified in the XML. This is disabled by default.
#
# WARNING: Enabling probing is a security hole in almost all
# deployments. It is strongly recommended that users update their
# guest XML <disk> elements to include  <driver type='XXXX'/>
# elements instead of enabling this option.
297
#
298
#allow_disk_format_probing = 1
299 300 301 302 303 304 305 306 307


# If enabled, libvirt will have QEMU set its process name to
# "qemu:VM_NAME", where VM_NAME is the name of the VM. The QEMU
# process will appear as "qemu:VM_NAME" in process listings and
# other system monitoring tools. By default, QEMU does not set
# its process title, so the complete QEMU command (emulator and
# its arguments) appear in process listings.
#
308
#set_process_name = 1
309 310


311 312 313 314 315
# If max_processes is set to a positive integer, libvirt will use
# it to set the maximum number of processes that can be run by qemu
# user. This can be used to override default value set by host OS.
# The same applies to max_files which sets the limit on the maximum
# number of opened files.
316
#
317 318
#max_processes = 0
#max_files = 0
319

320
# To enable 'Sanlock' project based locking of the file
321
# content (to prevent two VMs writing to the same
322
# disk), uncomment this
323
#
324
#lock_manager = "sanlock"
325 326 327 328 329 330

# Set limit of maximum APIs queued on one domain. All other APIs
# over this threshold will fail on acquiring job lock. Specially,
# setting to zero turns this feature off.
# Note, that job lock is per domain.
#
331
#max_queued = 0
332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353

###################################################################
# Keepalive protocol:
# This allows qemu driver to detect broken connections to remote
# libvirtd during peer-to-peer migration.  A keepalive message is
# sent to the deamon after keepalive_interval seconds of inactivity
# to check if the deamon is still responding; keepalive_count is a
# maximum number of keepalive messages that are allowed to be sent
# to the deamon without getting any response before the connection
# is considered broken.  In other words, the connection is
# automatically closed approximately after
# keepalive_interval * (keepalive_count + 1) seconds since the last
# message received from the deamon.  If keepalive_interval is set to
# -1, qemu driver will not send keepalive requests during
# peer-to-peer migration; however, the remote libvirtd can still
# send them and source libvirtd will send responses.  When
# keepalive_count is set to 0, connections will be automatically
# closed after keepalive_interval seconds of inactivity without
# sending any keepalive messages.
#
#keepalive_interval = 5
#keepalive_count = 5