proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-05-29 15:22:13 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

cleanup typos / phrasing

Browse Source
This commit is contained in:
Fabian Grünbichler 2017-10-13 13:19:30 +02:00
parent 7dd7a0b711
commit fb29acddf3
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ha-manager.adoc
View File

@ -321,7 +321,7 @@ node, or when we restart the LRM daemon
ignored:: ignored::
Act as the service is not managed by HA at all. Act as if the service were not managed by HA at all.
Useful, when full control over the service is desired temporarily, Useful, when full control over the service is desired temporarily,
without removing it from the HA configuration. without removing it from the HA configuration.
@ -762,8 +762,8 @@ 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 normally during a package update and, as already stated, 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 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 this is not the case the update process can take too long which, in the worst
case, may result in a reset triggered by he watchdog. case, may result in a reset triggered by the watchdog.
Node Maintenance Node Maintenance

4
qm.adoc
View File

@ -230,12 +230,12 @@ 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 if the _overall_ number of cores from all your VMs NOTE: It is perfectly safe if the _overall_ number of cores of all your VMs
is greater than the number of cores on the server (e.g., 4 VMs with each 4 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 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 balance the Qemu execution threads between your server cores, just like if you
were running a standard multithreaded application. However, {pve} will prevent were running a standard multithreaded application. However, {pve} will prevent
you to assign more virtual CPU cores than physically available, as this will you from assigning more virtual CPU cores than physically available, as this will
only bring the performance down due to the cost of context switches. only bring the performance down due to the cost of context switches.
[[qm_cpu_resource_limits]] [[qm_cpu_resource_limits]]