zcN1fSQf

1# Master configuration file for the QEMU driver.
2# All settings described here are optional - if omitted, sensible
3# defaults are used.
4
5# Use of TLS requires that x509 certificates be issued. The default is
6# to keep them in /etc/pki/qemu. This directory must contain
7#
8#  ca-cert.pem - the CA master certificate
9#  server-cert.pem - the server certificate signed with ca-cert.pem
10#  server-key.pem  - the server private key
11#
12# and optionally may contain
13#
14#  dh-params.pem - the DH params configuration file
15#
16# If the directory does not exist, libvirtd will fail to start. If the
17# directory doesn't contain the necessary files, QEMU domains will fail
18# to start if they are configured to use TLS.
19#
20# In order to overwrite the default path alter the following. This path
21# definition will be used as the default path for other *_tls_x509_cert_dir
22# configuration settings if their default path does not exist or is not
23# specifically set.
24#
25#default_tls_x509_cert_dir = "/etc/pki/qemu"
26
27
28# The default TLS configuration only uses certificates for the server
29# allowing the client to verify the server's identity and establish
30# an encrypted channel.
31#
32# It is possible to use x509 certificates for authentication too, by
33# issuing an x509 certificate to every client who needs to connect.
34#
35# Enabling this option will reject any client who does not have a
36# certificate signed by the CA in /etc/pki/qemu/ca-cert.pem
37#
38# The default_tls_x509_cert_dir directory must also contain
39#
40#  client-cert.pem - the client certificate signed with the ca-cert.pem
41#  client-key.pem - the client private key
42#
43#default_tls_x509_verify = 1
44
45#
46# Libvirt assumes the server-key.pem file is unencrypted by default.
47# To use an encrypted server-key.pem file, the password to decrypt
48# the PEM file is required. This can be provided by creating a secret
49# object in libvirt and then to uncomment this setting to set the UUID
50# of the secret.
51#
52# NB This default all-zeros UUID will not work. Replace it with the
53# output from the UUID for the TLS secret from a 'virsh secret-list'
54# command and then uncomment the entry
55#
56#default_tls_x509_secret_uuid = "00000000-0000-0000-0000-000000000000"
57
58
59# VNC is configured to listen on 127.0.0.1 by default.
60# To make it listen on all public interfaces, uncomment
61# this next option.
62#
63# NB, strong recommendation to enable TLS + x509 certificate
64# verification when allowing public access
65#
66#vnc_listen = "0.0.0.0"
67
68# Enable this option to have VNC served over an automatically created
69# unix socket. This prevents unprivileged access from users on the
70# host machine, though most VNC clients do not support it.
71#
72# This will only be enabled for VNC configurations that have listen
73# type=address but without any address specified. This setting takes
74# preference over vnc_listen.
75#
76#vnc_auto_unix_socket = 1
77
78# Enable use of TLS encryption on the VNC server. This requires
79# a VNC client which supports the VeNCrypt protocol extension.
80# Examples include vinagre, virt-viewer, virt-manager and vencrypt
81# itself. UltraVNC, RealVNC, TightVNC do not support this
82#
83# It is necessary to setup CA and issue a server certificate
84# before enabling this.
85#
86#vnc_tls = 1
87
88
89# In order to override the default TLS certificate location for
90# vnc certificates, supply a valid path to the certificate directory.
91# If the provided path does not exist, libvirtd will fail to start.
92# If the path is not provided, but vnc_tls = 1, then the
93# default_tls_x509_cert_dir path will be used.
94#
95#vnc_tls_x509_cert_dir = "/etc/pki/libvirt-vnc"
96
97
98# Uncomment and use the following option to override the default secret
99# UUID provided in the default_tls_x509_secret_uuid parameter.
100#
101#vnc_tls_x509_secret_uuid = "00000000-0000-0000-0000-000000000000"
102
103
104# The default TLS configuration only uses certificates for the server
105# allowing the client to verify the server's identity and establish
106# an encrypted channel.
107#
108# It is possible to use x509 certificates for authentication too, by
109# issuing an x509 certificate to every client who needs to connect.
110#
111# Enabling this option will reject any client that does not have a
112# ca-cert.pem certificate signed by the CA in the vnc_tls_x509_cert_dir
113# (or default_tls_x509_cert_dir) as well as the corresponding client-*.pem
114# files described in default_tls_x509_cert_dir.
115#
116# If this option is not supplied, it will be set to the value of
117# "default_tls_x509_verify".
118#
119#vnc_tls_x509_verify = 1
120
121
122# The default VNC password. Only 8 bytes are significant for
123# VNC passwords. This parameter is only used if the per-domain
124# XML config does not already provide a password. To allow
125# access without passwords, leave this commented out. An empty
126# string will still enable passwords, but be rejected by QEMU,
127# effectively preventing any use of VNC. Obviously change this
128# example here before you set this.
129#
130#vnc_password = "XYZ12345"
131
132
133# Enable use of SASL encryption on the VNC server. This requires
134# a VNC client which supports the SASL protocol extension.
135# Examples include vinagre, virt-viewer and virt-manager
136# itself. UltraVNC, RealVNC, TightVNC do not support this
137#
138# It is necessary to configure /etc/sasl2/qemu.conf to choose
139# the desired SASL plugin (eg, GSSPI for Kerberos)
140#
141#vnc_sasl = 1
142
143
144# The default SASL configuration file is located in /etc/sasl2/
145# When running libvirtd unprivileged, it may be desirable to
146# override the configs in this location. Set this parameter to
147# point to the directory, and create a qemu.conf in that location
148#
149#vnc_sasl_dir = "/some/directory/sasl2"
150
151
152# QEMU implements an extension for providing audio over a VNC connection,
153# though if your VNC client does not support it, your only chance for getting
154# sound output is through regular audio backends. By default, libvirt will
155# disable all QEMU sound backends if using VNC, since they can cause
156# permissions issues. Enabling this option will make libvirtd honor the
157# QEMU_AUDIO_DRV environment variable when using VNC.
158#
159#vnc_allow_host_audio = 0
160
161
162
163# SPICE is configured to listen on 127.0.0.1 by default.
164# To make it listen on all public interfaces, uncomment
165# this next option.
166#
167# NB, strong recommendation to enable TLS + x509 certificate
168# verification when allowing public access
169#
170#spice_listen = "0.0.0.0"
171
172
173# Enable use of TLS encryption on the SPICE server.
174#
175# It is necessary to setup CA and issue a server certificate
176# before enabling this.
177#
178#spice_tls = 1
179
180
181# In order to override the default TLS certificate location for
182# spice certificates, supply a valid path to the certificate directory.
183# If the provided path does not exist, libvirtd will fail to start.
184# If the path is not provided, but spice_tls = 1, then the
185# default_tls_x509_cert_dir path will be used.
186#
187#spice_tls_x509_cert_dir = "/etc/pki/libvirt-spice"
188
189
190# Enable this option to have SPICE served over an automatically created
191# unix socket. This prevents unprivileged access from users on the
192# host machine.
193#
194# This will only be enabled for SPICE configurations that have listen
195# type=address but without any address specified. This setting takes
196# preference over spice_listen.
197#
198#spice_auto_unix_socket = 1
199
200
201# The default SPICE password. This parameter is only used if the
202# per-domain XML config does not already provide a password. To
203# allow access without passwords, leave this commented out. An
204# empty string will still enable passwords, but be rejected by
205# QEMU, effectively preventing any use of SPICE. Obviously change
206# this example here before you set this.
207#
208#spice_password = "XYZ12345"
209
210
211# Enable use of SASL encryption on the SPICE server. This requires
212# a SPICE client which supports the SASL protocol extension.
213#
214# It is necessary to configure /etc/sasl2/qemu.conf to choose
215# the desired SASL plugin (eg, GSSPI for Kerberos)
216#
217#spice_sasl = 1
218
219# The default SASL configuration file is located in /etc/sasl2/
220# When running libvirtd unprivileged, it may be desirable to
221# override the configs in this location. Set this parameter to
222# point to the directory, and create a qemu.conf in that location
223#
224#spice_sasl_dir = "/some/directory/sasl2"
225
226# Enable use of TLS encryption on the chardev TCP transports.
227#
228# It is necessary to setup CA and issue a server certificate
229# before enabling this.
230#
231#chardev_tls = 1
232
233
234# In order to override the default TLS certificate location for character
235# device TCP certificates, supply a valid path to the certificate directory.
236# If the provided path does not exist, libvirtd will fail to start.
237# If the path is not provided, but chardev_tls = 1, then the
238# default_tls_x509_cert_dir path will be used.
239#
240#chardev_tls_x509_cert_dir = "/etc/pki/libvirt-chardev"
241
242
243# The default TLS configuration only uses certificates for the server
244# allowing the client to verify the server's identity and establish
245# an encrypted channel.
246#
247# It is possible to use x509 certificates for authentication too, by
248# issuing an x509 certificate to every client who needs to connect.
249#
250# Enabling this option will reject any client that does not have a
251# ca-cert.pem certificate signed by the CA in the chardev_tls_x509_cert_dir
252# (or default_tls_x509_cert_dir) as well as the corresponding client-*.pem
253# files described in default_tls_x509_cert_dir.
254#
255# If this option is not supplied, it will be set to the value of
256# "default_tls_x509_verify".
257#
258#chardev_tls_x509_verify = 1
259
260
261# Uncomment and use the following option to override the default secret
262# UUID provided in the default_tls_x509_secret_uuid parameter.
263#
264# NB This default all-zeros UUID will not work. Replace it with the
265# output from the UUID for the TLS secret from a 'virsh secret-list'
266# command and then uncomment the entry
267#
268#chardev_tls_x509_secret_uuid = "00000000-0000-0000-0000-000000000000"
269
270
271# Enable use of TLS encryption for all VxHS network block devices that
272# don't specifically disable.
273#
274# When the VxHS network block device server is set up appropriately,
275# x509 certificates are required for authentication between the clients
276# (qemu processes) and the remote VxHS server.
277#
278# It is necessary to setup CA and issue the client certificate before
279# enabling this.
280#
281#vxhs_tls = 1
282
283
284# In order to override the default TLS certificate location for VxHS
285# backed storage, supply a valid path to the certificate directory.
286# This is used to authenticate the VxHS block device clients to the VxHS
287# server.
288#
289# If the provided path does not exist, libvirtd will fail to start.
290# If the path is not provided, but vxhs_tls = 1, then the
291# default_tls_x509_cert_dir path will be used.
292#
293# VxHS block device clients expect the client certificate and key to be
294# present in the certificate directory along with the CA master certificate.
295# If using the default environment, default_tls_x509_verify must be configured.
296# Since this is only a client the server-key.pem certificate is not needed.
297# Thus a VxHS directory must contain the following:
298#
299#  ca-cert.pem - the CA master certificate
300#  client-cert.pem - the client certificate signed with the ca-cert.pem
301#  client-key.pem - the client private key
302#
303#vxhs_tls_x509_cert_dir = "/etc/pki/libvirt-vxhs"
304
305
306
307# Enable use of TLS encryption for all NBD disk devices that don't
308# specifically disable it.
309#
310# When the NBD server is set up appropriately, x509 certificates are required
311# for authentication between the client and the remote NBD server.
312#
313# It is necessary to setup CA and issue the client certificate before
314# enabling this.
315#
316#nbd_tls = 1
317
318
319# In order to override the default TLS certificate location for NBD
320# backed storage, supply a valid path to the certificate directory.
321# This is used to authenticate the NBD block device clients to the NBD
322# server.
323#
324# If the provided path does not exist, libvirtd will fail to start.
325# If the path is not provided, but nbd_tls = 1, then the
326# default_tls_x509_cert_dir path will be used.
327#
328# NBD block device clients expect the client certificate and key to be
329# present in the certificate directory along with the CA certificate.
330# Since this is only a client the server-key.pem certificate is not needed.
331# Thus a NBD directory must contain the following:
332#
333#  ca-cert.pem - the CA master certificate
334#  client-cert.pem - the client certificate signed with the ca-cert.pem
335#  client-key.pem - the client private key
336#
337#nbd_tls_x509_cert_dir = "/etc/pki/libvirt-nbd"
338
339
340# In order to override the default TLS certificate location for migration
341# certificates, supply a valid path to the certificate directory. If the
342# provided path does not exist, libvirtd will fail to start. If the path is
343# not provided, but migrate_tls = 1, then the default_tls_x509_cert_dir path
344# will be used. Once/if a default certificate is enabled/defined, migration
345# will then be able to use the certificate via migration API flags.
346#
347#migrate_tls_x509_cert_dir = "/etc/pki/libvirt-migrate"
348
349
350# The default TLS configuration only uses certificates for the server
351# allowing the client to verify the server's identity and establish
352# an encrypted channel.
353#
354# It is possible to use x509 certificates for authentication too, by
355# issuing an x509 certificate to every client who needs to connect.
356#
357# Enabling this option will reject any client that does not have a
358# ca-cert.pem certificate signed by the CA in the migrate_tls_x509_cert_dir
359# (or default_tls_x509_cert_dir) as well as the corresponding client-*.pem
360# files described in default_tls_x509_cert_dir.
361#
362# If this option is not supplied, it will be set to the value of
363# "default_tls_x509_verify".
364#
365#migrate_tls_x509_verify = 1
366
367
368# Uncomment and use the following option to override the default secret
369# UUID provided in the default_tls_x509_secret_uuid parameter.
370#
371# NB This default all-zeros UUID will not work. Replace it with the
372# output from the UUID for the TLS secret from a 'virsh secret-list'
373# command and then uncomment the entry
374#
375#migrate_tls_x509_secret_uuid = "00000000-0000-0000-0000-000000000000"
376
377
378# By default, if no graphical front end is configured, libvirt will disable
379# QEMU audio output since directly talking to alsa/pulseaudio may not work
380# with various security settings. If you know what you're doing, enable
381# the setting below and libvirt will passthrough the QEMU_AUDIO_DRV
382# environment variable when using nographics.
383#
384nographics_allow_host_audio = 1
385
386
387# Override the port for creating both VNC and SPICE sessions (min).
388# This defaults to 5900 and increases for consecutive sessions
389# or when ports are occupied, until it hits the maximum.
390#
391# Minimum must be greater than or equal to 5900 as lower number would
392# result into negative vnc display number.
393#
394# Maximum must be less than 65536, because higher numbers do not make
395# sense as a port number.
396#
397#remote_display_port_min = 5900
398#remote_display_port_max = 65535
399
400# VNC WebSocket port policies, same rules apply as with remote display
401# ports.  VNC WebSockets use similar display <-> port mappings, with
402# the exception being that ports start from 5700 instead of 5900.
403#
404#remote_websocket_port_min = 5700
405#remote_websocket_port_max = 65535
406
407# The default security driver is SELinux. If SELinux is disabled
408# on the host, then the security driver will automatically disable
409# itself. If you wish to disable QEMU SELinux security driver while
410# leaving SELinux enabled for the host in general, then set this
411# to 'none' instead. It's also possible to use more than one security
412# driver at the same time, for this use a list of names separated by
413# comma and delimited by square brackets. For example:
414#
415#       security_driver = [ "selinux", "apparmor" ]
416#
417# Notes: The DAC security driver is always enabled; as a result, the
418# value of security_driver cannot contain "dac".  The value "none" is
419# a special value; security_driver can be set to that value in
420# isolation, but it cannot appear in a list of drivers.
421#
422#security_driver = "selinux"
423
424# If set to non-zero, then the default security labeling
425# will make guests confined. If set to zero, then guests
426# will be unconfined by default. Defaults to 1.
427#security_default_confined = 1
428
429# If set to non-zero, then attempts to create unconfined
430# guests will be blocked. Defaults to 0.
431#security_require_confined = 1
432
433# The user for QEMU processes run by the system instance. It can be
434# specified as a user name or as a user id. The qemu driver will try to
435# parse this value first as a name and then, if the name doesn't exist,
436# as a user id.
437#
438# Since a sequence of digits is a valid user name, a leading plus sign
439# can be used to ensure that a user id will not be interpreted as a user
440# name.
441#
442# Some examples of valid values are:
443#
444#       user = "qemu"   # A user named "qemu"
445#       user = "+0"     # Super user (uid=0)
446#       user = "100"    # A user named "100" or a user with uid=100
447#
448user = "mickael"
449
450# The group for QEMU processes run by the system instance. It can be
451# specified in a similar way to user.
452group = "mickael"
453
454# Whether libvirt should dynamically change file ownership
455# to match the configured user/group above. Defaults to 1.
456# Set to 0 to disable file ownership changes.
457#dynamic_ownership = 1
458
459# What cgroup controllers to make use of with QEMU guests
460#
461#  - 'cpu' - use for scheduler tunables
462#  - 'devices' - use for device whitelisting
463#  - 'memory' - use for memory tunables
464#  - 'blkio' - use for block devices I/O tunables
465#  - 'cpuset' - use for CPUs and memory nodes
466#  - 'cpuacct' - use for CPUs statistics.
467#
468# NB, even if configured here, they won't be used unless
469# the administrator has mounted cgroups, e.g.:
470#
471#  mkdir /dev/cgroup
472#  mount -t cgroup -o devices,cpu,memory,blkio,cpuset none /dev/cgroup
473#
474# They can be mounted anywhere, and different controllers
475# can be mounted in different locations. libvirt will detect
476# where they are located.
477#
478cgroup_controllers = [ "cpu", "devices", "memory", "blkio", "cpuset", "cpuacct" ]
479
480# This is the basic set of devices allowed / required by
481# all virtual machines.
482#
483# As well as this, any configured block backed disks,
484# all sound device, and all PTY devices are allowed.
485#
486# This will only need setting if newer QEMU suddenly
487# wants some device we don't already know about.
488#
489cgroup_device_acl = [
490    "/dev/null", "/dev/full", "/dev/zero",
491    "/dev/random", "/dev/urandom",
492    "/dev/ptmx", "/dev/kvm",
493    "/dev/rtc","/dev/hpet",
494    "/dev/input/event3",
495    "/dev/input/mouse1"
496]
497
498# RDMA migration requires the following extra files to be added to the list:
499#   "/dev/infiniband/rdma_cm",
500#   "/dev/infiniband/issm0",
501#   "/dev/infiniband/issm1",
502#   "/dev/infiniband/umad0",
503#   "/dev/infiniband/umad1",
504#   "/dev/infiniband/uverbs0"
505
506
507# The default format for QEMU/KVM guest save images is raw; that is, the
508# memory from the domain is dumped out directly to a file.  If you have
509# guests with a large amount of memory, however, this can take up quite
510# a bit of space.  If you would like to compress the images while they
511# are being saved to disk, you can also set "lzop", "gzip", "bzip2", or "xz"
512# for save_image_format.  Note that this means you slow down the process of
513# saving a domain in order to save disk space; the list above is in descending
514# order by performance and ascending order by compression ratio.
515#
516# save_image_format is used when you use 'virsh save' or 'virsh managedsave'
517# at scheduled saving, and it is an error if the specified save_image_format
518# is not valid, or the requested compression program can't be found.
519#
520# dump_image_format is used when you use 'virsh dump' at emergency
521# crashdump, and if the specified dump_image_format is not valid, or
522# the requested compression program can't be found, this falls
523# back to "raw" compression.
524#
525# snapshot_image_format specifies the compression algorithm of the memory save
526# image when an external snapshot of a domain is taken. This does not apply
527# on disk image format. It is an error if the specified format isn't valid,
528# or the requested compression program can't be found.
529#
530#save_image_format = "raw"
531#dump_image_format = "raw"
532#snapshot_image_format = "raw"
533
534# When a domain is configured to be auto-dumped when libvirtd receives a
535# watchdog event from qemu guest, libvirtd will save dump files in directory
536# specified by auto_dump_path. Default value is /var/lib/libvirt/qemu/dump
537#
538#auto_dump_path = "/var/lib/libvirt/qemu/dump"
539
540# When a domain is configured to be auto-dumped, enabling this flag
541# has the same effect as using the VIR_DUMP_BYPASS_CACHE flag with the
542# virDomainCoreDump API.  That is, the system will avoid using the
543# file system cache while writing the dump file, but may cause
544# slower operation.
545#
546#auto_dump_bypass_cache = 0
547
548# When a domain is configured to be auto-started, enabling this flag
549# has the same effect as using the VIR_DOMAIN_START_BYPASS_CACHE flag
550# with the virDomainCreateWithFlags API.  That is, the system will
551# avoid using the file system cache when restoring any managed state
552# file, but may cause slower operation.
553#
554#auto_start_bypass_cache = 0
555
556# If provided by the host and a hugetlbfs mount point is configured,
557# a guest may request huge page backing.  When this mount point is
558# unspecified here, determination of a host mount point in /proc/mounts
559# will be attempted.  Specifying an explicit mount overrides detection
560# of the same in /proc/mounts.  Setting the mount point to "" will
561# disable guest hugepage backing. If desired, multiple mount points can
562# be specified at once, separated by comma and enclosed in square
563# brackets, for example:
564#
565#     hugetlbfs_mount = ["/dev/hugepages2M", "/dev/hugepages1G"]
566#
567# The size of huge page served by specific mount point is determined by
568# libvirt at the daemon startup.
569#
570# NB, within these mount points, guests will create memory backing
571# files in a location of $MOUNTPOINT/libvirt/qemu
572#
573#hugetlbfs_mount = "/dev/hugepages"
574
575
576# Path to the setuid helper for creating tap devices.  This executable
577# is used to create <source type='bridge'> interfaces when libvirtd is
578# running unprivileged.  libvirt invokes the helper directly, instead
579# of using "-netdev bridge", for security reasons.
580#bridge_helper = "/usr/lib/qemu/qemu-bridge-helper"
581
582
583
584# If clear_emulator_capabilities is enabled, libvirt will drop all
585# privileged capabilities of the QEMU/KVM emulator. This is enabled by
586# default.
587#
588# Warning: Disabling this option means that a compromised guest can
589# exploit the privileges and possibly do damage to the host.
590#
591#clear_emulator_capabilities = 1
592
593
594# If enabled, libvirt will have QEMU set its process name to
595# "qemu:VM_NAME", where VM_NAME is the name of the VM. The QEMU
596# process will appear as "qemu:VM_NAME" in process listings and
597# other system monitoring tools. By default, QEMU does not set
598# its process title, so the complete QEMU command (emulator and
599# its arguments) appear in process listings.
600#
601#set_process_name = 1
602
603
604# If max_processes is set to a positive integer, libvirt will use
605# it to set the maximum number of processes that can be run by qemu
606# user. This can be used to override default value set by host OS.
607# The same applies to max_files which sets the limit on the maximum
608# number of opened files.
609#
610#max_processes = 0
611#max_files = 0
612
613# If max_core is set to a non-zero integer, then QEMU will be
614# permitted to create core dumps when it crashes, provided its
615# RAM size is smaller than the limit set.
616#
617# Be warned that the core dump will include a full copy of the
618# guest RAM, if the 'dump_guest_core' setting has been enabled,
619# or if the guest XML contains
620#
621#   <memory dumpcore="on">...guest ram...</memory>
622#
623# If guest RAM is to be included, ensure the max_core limit
624# is set to at least the size of the largest expected guest
625# plus another 1GB for any QEMU host side memory mappings.
626#
627# As a special case it can be set to the string "unlimited" to
628# to allow arbitrarily sized core dumps.
629#
630# By default the core dump size is set to 0 disabling all dumps
631#
632# Size is a positive integer specifying bytes or the
633# string "unlimited"
634#
635#max_core = "unlimited"
636
637# Determine if guest RAM is included in QEMU core dumps. By
638# default guest RAM will be excluded if a new enough QEMU is
639# present. Setting this to '1' will force guest RAM to always
640# be included in QEMU core dumps.
641#
642# This setting will be ignored if the guest XML has set the
643# dumpcore attribute on the <memory> element.
644#
645#dump_guest_core = 1
646
647# mac_filter enables MAC addressed based filtering on bridge ports.
648# This currently requires ebtables to be installed.
649#
650#mac_filter = 1
651
652
653# By default, PCI devices below non-ACS switch are not allowed to be assigned
654# to guests. By setting relaxed_acs_check to 1 such devices will be allowed to
655# be assigned to guests.
656#
657#relaxed_acs_check = 1
658
659
660# In order to prevent accidentally starting two domains that
661# share one writable disk, libvirt offers two approaches for
662# locking files. The first one is sanlock, the other one,
663# virtlockd, is then our own implementation. Accepted values
664# are "sanlock" and "lockd".
665#
666#lock_manager = "lockd"
667
668
669# Set limit of maximum APIs queued on one domain. All other APIs
670# over this threshold will fail on acquiring job lock. Specially,
671# setting to zero turns this feature off.
672# Note, that job lock is per domain.
673#
674#max_queued = 0
675
676###################################################################
677# Keepalive protocol:
678# This allows qemu driver to detect broken connections to remote
679# libvirtd during peer-to-peer migration.  A keepalive message is
680# sent to the daemon after keepalive_interval seconds of inactivity
681# to check if the daemon is still responding; keepalive_count is a
682# maximum number of keepalive messages that are allowed to be sent
683# to the daemon without getting any response before the connection
684# is considered broken.  In other words, the connection is
685# automatically closed approximately after
686# keepalive_interval * (keepalive_count + 1) seconds since the last
687# message received from the daemon.  If keepalive_interval is set to
688# -1, qemu driver will not send keepalive requests during
689# peer-to-peer migration; however, the remote libvirtd can still
690# send them and source libvirtd will send responses.  When
691# keepalive_count is set to 0, connections will be automatically
692# closed after keepalive_interval seconds of inactivity without
693# sending any keepalive messages.
694#
695#keepalive_interval = 5
696#keepalive_count = 5
697
698
699
700# Use seccomp syscall sandbox in QEMU.
701# 1 == seccomp enabled, 0 == seccomp disabled
702#
703# If it is unset (or -1), then seccomp will be enabled
704# only if QEMU >= 2.11.0 is detected, otherwise it is
705# left disabled. This ensures the default config gets
706# protection for new QEMU using the blacklist approach.
707#
708#seccomp_sandbox = 1
709
710
711# Override the listen address for all incoming migrations. Defaults to
712# 0.0.0.0, or :: if both host and qemu are capable of IPv6.
713#migration_address = "0.0.0.0"
714
715
716# The default hostname or IP address which will be used by a migration
717# source for transferring migration data to this host.  The migration
718# source has to be able to resolve this hostname and connect to it so
719# setting "localhost" will not work.  By default, the host's configured
720# hostname is used.
721#migration_host = "host.example.com"
722
723
724# Override the port range used for incoming migrations.
725#
726# Minimum must be greater than 0, however when QEMU is not running as root,
727# setting the minimum to be lower than 1024 will not work.
728#
729# Maximum must not be greater than 65535.
730#
731#migration_port_min = 49152
732#migration_port_max = 49215
733
734
735
736# Timestamp QEMU's log messages (if QEMU supports it)
737#
738# Defaults to 1.
739#
740#log_timestamp = 0
741
742
743# Location of master nvram file
744#
745# When a domain is configured to use UEFI instead of standard
746# BIOS it may use a separate storage for UEFI variables. If
747# that's the case libvirt creates the variable store per domain
748# using this master file as image. Each UEFI firmware can,
749# however, have different variables store. Therefore the nvram is
750# a list of strings when a single item is in form of:
751#   ${PATH_TO_UEFI_FW}:${PATH_TO_UEFI_VARS}.
752# Later, when libvirt creates per domain variable store, this list is
753# searched for the master image. The UEFI firmware can be called
754# differently for different guest architectures. For instance, it's OVMF
755# for x86_64 and i686, but it's AAVMF for aarch64. The libvirt default
756# follows this scheme.
757#nvram = [
758#   "/usr/share/OVMF/OVMF_CODE.fd:/usr/share/OVMF/OVMF_VARS.fd",
759#   "/usr/share/OVMF/OVMF_CODE.secboot.fd:/usr/share/OVMF/OVMF_VARS.fd",
760#   "/usr/share/AAVMF/AAVMF_CODE.fd:/usr/share/AAVMF/AAVMF_VARS.fd",
761#   "/usr/share/AAVMF/AAVMF32_CODE.fd:/usr/share/AAVMF/AAVMF32_VARS.fd"
762#]
763
764nvram = [
765	"/usr/share/ovmf/x64/OVMF_CODE.fd:/usr/share/ovmf/x64/OVMF_VARS.fd"
766]
767
768# The backend to use for handling stdout/stderr output from
769# QEMU processes.
770#
771#  'file': QEMU writes directly to a plain file. This is the
772#          historical default, but allows QEMU to inflict a
773#          denial of service attack on the host by exhausting
774#          filesystem space
775#
776#  'logd': QEMU writes to a pipe provided by virtlogd daemon.
777#          This is the current default, providing protection
778#          against denial of service by performing log file
779#          rollover when a size limit is hit.
780#
781#stdio_handler = "logd"
782
783# QEMU gluster libgfapi log level, debug levels are 0-9, with 9 being the
784# most verbose, and 0 representing no debugging output.
785#
786# The current logging levels defined in the gluster GFAPI are:
787#
788#    0 - None
789#    1 - Emergency
790#    2 - Alert
791#    3 - Critical
792#    4 - Error
793#    5 - Warning
794#    6 - Notice
795#    7 - Info
796#    8 - Debug
797#    9 - Trace
798#
799# Defaults to 4
800#
801#gluster_debug_level = 9
802
803# To enhance security, QEMU driver is capable of creating private namespaces
804# for each domain started. Well, so far only "mount" namespace is supported. If
805# enabled it means qemu process is unable to see all the devices on the system,
806# only those configured for the domain in question. Libvirt then manages
807# devices entries throughout the domain lifetime. This namespace is turned on
808# by default.
809#namespaces = [ "mount" ]
810
811# This directory is used for memoryBacking source if configured as file.
812# NOTE: big files will be stored here
813#memory_backing_dir = "/var/lib/libvirt/qemu/ram"
814
815# Path to the SCSI persistent reservations helper. This helper is
816# used whenever <reservations/> are enabled for SCSI LUN devices.
817#pr_helper = "/usr/bin/qemu-pr-helper"
818
819# User for the swtpm TPM Emulator
820#
821# Default is 'tss'; this is the same user that tcsd (TrouSerS) installs
822# and uses; alternative is 'root'
823#
824#swtpm_user = "tss"
825#swtpm_group = "tss"