[pve-devel] [PATCH docs 3/3] various wording improvement

Thomas Lamprecht t.lamprecht at proxmox.com
Fri Oct 13 13:00:43 CEST 2017


Signed-off-by: Thomas Lamprecht <t.lamprecht at proxmox.com>
---

had this still lying around, its not to much changes, just use
`git show --word-diff=color` to see the effective ones.

 ha-manager.adoc |  8 ++++----
 qm.adoc         | 15 +++++++--------
 2 files changed, 11 insertions(+), 12 deletions(-)

diff --git a/ha-manager.adoc b/ha-manager.adoc
index 07a2370..efa5646 100644
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -760,10 +760,10 @@ actions between the cluster and the local resource manager. For restarting,
 the LRM makes a request to the CRM to freeze all its services. This prevents
 that they get touched by the Cluster during the short time the LRM is restarting.
 After that the LRM may safely close the watchdog during a restart.
-Such a restart happens on a update and as already stated a active master
-CRM is needed to acknowledge the requests from the LRM, if this is not the case
-the update process can be too long which, in the worst case, may result in
-a watchdog reset.
+Such a restart happens normally during a package update and, as already stated,
+an active master CRM is needed to acknowledge the requests from the LRM. If
+this is not the case the update process can take to long which, in the worst
+case, may result in a reset triggered by he watchdog.
 
 
 Node Maintenance
diff --git a/qm.adoc b/qm.adoc
index eda85f8..8895044 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -230,14 +230,13 @@ virtual cpus, as for each virtual cpu you add, Qemu will create a new thread of
 execution on the host system. If you're not sure about the workload of your VM,
 it is usually a safe bet to set the number of *Total cores* to 2.
 
-NOTE: It is perfectly safe to set the _overall_ number of total cores in all
-your VMs to be greater than the number of of cores you have on your server (i.e.
-4 VMs with each 4 Total cores running in a 8 core machine is OK) In that case
-the host system will balance the Qemu execution threads between your server
-cores just like if you were running a standard multithreaded application.
-However {pve} will prevent you to allocate on a _single_ machine more vcpus than
-physically available, as this will only bring the performance down due to the
-cost of context switches.
+NOTE: It is perfectly safe if the _overall_ number of cores from all your VMs
+is greater than the number of cores on the server (e.g., 4 VMs with each 4
+cores on a machine with only 8 cores). In that case the host system will
+balance the Qemu execution threads between your server cores, just like if you
+were running a standard multithreaded application. However, {pve} will prevent
+you to assign more virtual CPU cores than physically available, as this will
+only bring the performance down due to the cost of context switches.
 
 [[qm_cpu_resource_limits]]
 Resource Limits
-- 
2.11.0




More information about the pve-devel mailing list