[PATCH] qemu.conf: spaces correction

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



libvirt/qemu.conf: spaces correction

---
 src/qemu/qemu.conf | 42 +++++++++++++++++++++---------------------
 1 file changed, 21 insertions(+), 21 deletions(-)

diff --git a/src/qemu/qemu.conf b/src/qemu/qemu.conf
index 4fa5e8a..5cf4599 100644
--- a/src/qemu/qemu.conf
+++ b/src/qemu/qemu.conf
@@ -38,7 +38,7 @@
 #
 #  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
+#  server-key.pem - the server private key
 #
 # This option allows the certificate directory to be changed
 #
@@ -123,7 +123,7 @@
 #
 #  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
+#  server-key.pem - the server private key
 #
 # This option allows the certificate directory to be changed.
 #
@@ -179,7 +179,7 @@
 #remote_display_port_max = 65535
 
 # VNC WebSocket port policies, same rules apply as with remote display
-# ports.  VNC WebSockets use similar display <-> port mappings, with
+# ports. VNC WebSockets use similar display <-> port mappings, with
 # the exception being that ports start from 5700 instead of 5900.
 #
 #remote_websocket_port_min = 5700
@@ -196,7 +196,7 @@
 #       security_driver = [ "selinux", "apparmor" ]
 #
 # Notes: The DAC security driver is always enabled; as a result, the
-# value of security_driver cannot contain "dac".  The value "none" is
+# value of security_driver cannot contain "dac". The value "none" is
 # a special value; security_driver can be set to that value in
 # isolation, but it cannot appear in a list of drivers.
 #
@@ -272,7 +272,7 @@
 #    "/dev/null", "/dev/full", "/dev/zero",
 #    "/dev/random", "/dev/urandom",
 #    "/dev/ptmx", "/dev/kvm", "/dev/kqemu",
-#    "/dev/rtc","/dev/hpet", "/dev/vfio/vfio"
+#    "/dev/rtc", "/dev/hpet", "/dev/vfio/vfio"
 #]
 #
 # RDMA migration requires the following extra files to be added to the list:
@@ -285,11 +285,11 @@
 
 
 # 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
+# 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
+# a bit of space. If you would like to compress the images while they
 # 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
+# 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.
 #
@@ -319,7 +319,7 @@
 
 # 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
+# virDomainCoreDump API. That is, the system will avoid using the
 # file system cache while writing the dump file, but may cause
 # slower operation.
 #
@@ -327,17 +327,17 @@
 
 # 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
+# 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.
 #
 #auto_start_bypass_cache = 0
 
 # If provided by the host and a hugetlbfs mount point is configured,
-# a guest may request huge page backing.  When this mount point is
+# 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
+# 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. If desired, multiple mount points can
 # be specified at once, separated by comma and enclosed in square
 # brackets, for example:
@@ -353,9 +353,9 @@
 #hugetlbfs_mount = "/dev/hugepages"
 
 
-# Path to the setuid helper for creating tap devices.  This executable
+# Path to the setuid helper for creating tap devices. This executable
 # is used to create <source type='bridge'> interfaces when libvirtd is
-# running unprivileged.  libvirt invokes the helper directly, instead
+# running unprivileged. libvirt invokes the helper directly, instead
 # of using "-netdev bridge", for security reasons.
 #bridge_helper = "/usr/libexec/qemu-bridge-helper"
 
@@ -411,7 +411,7 @@
 #
 # 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'/>
+# guest XML <disk> elements to include <driver type='XXXX'/>
 # elements instead of enabling this option.
 #
 #allow_disk_format_probing = 1
@@ -437,18 +437,18 @@
 ###################################################################
 # Keepalive protocol:
 # This allows qemu driver to detect broken connections to remote
-# libvirtd during peer-to-peer migration.  A keepalive message is
+# libvirtd during peer-to-peer migration. A keepalive message is
 # sent to the daemon after keepalive_interval seconds of inactivity
 # to check if the daemon is still responding; keepalive_count is a
 # maximum number of keepalive messages that are allowed to be sent
 # to the daemon without getting any response before the connection
-# is considered broken.  In other words, the connection is
+# 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 daemon.  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
+# 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.
@@ -471,9 +471,9 @@
 
 
 # The default hostname or IP address which will be used by a migration
-# source for transferring migration data to this host.  The migration
+# source for transferring migration data to this host. The migration
 # source has to be able to resolve this hostname and connect to it so
-# setting "localhost" will not work.  By default, the host's configured
+# setting "localhost" will not work. By default, the host's configured
 # hostname is used.
 #migration_host = "host.example.com"
 
-- 
2.4.11

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list



[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]