proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-08-05 16:45:09 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

various wording improvement

Browse Source 
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
Thomas Lamprecht 2017-10-13 13:00:43 +02:00 committed by Fabian Grünbichler
parent d9a27ee1c8
commit 7dd7a0b711
2 changed files with 11 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
ha-manager.adoc
View File

@ -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 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. 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. 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 Such a restart happens normally during a package update and, as already stated,
CRM is needed to acknowledge the requests from the LRM, if this is not the case an active master CRM is needed to acknowledge the requests from the LRM. If
the update process can be too long which, in the worst case, may result in this is not the case the update process can take to long which, in the worst
a watchdog reset. case, may result in a reset triggered by he watchdog.
Node Maintenance Node Maintenance

15
qm.adoc
View File

@ -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, 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. 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 NOTE: It is perfectly safe if the _overall_ number of cores from all your VMs
your VMs to be greater than the number of of cores you have on your server (i.e. is greater than the number of cores on the server (e.g., 4 VMs with each 4
4 VMs with each 4 Total cores running in a 8 core machine is OK) In that case cores on a machine with only 8 cores). In that case the host system will
the host system will balance the Qemu execution threads between your server balance the Qemu execution threads between your server cores, just like if you
cores just like if you were running a standard multithreaded application. were running a standard multithreaded application. However, {pve} will prevent
However {pve} will prevent you to allocate on a _single_ machine more vcpus than you to assign more virtual CPU cores than physically available, as this will
physically available, as this will only bring the performance down due to the only bring the performance down due to the cost of context switches.
cost of context switches.
[[qm_cpu_resource_limits]] [[qm_cpu_resource_limits]]
Resource Limits Resource Limits