[pve-devel] [PATCH docs] qm: improve auto start/stop section

[Thomas Lamprecht]

For VMs we wait 180 seconds (CT sxtill 60, so no need to correct
there) for stop to succeed. Reword and add a few details while
touching this.

Signed-off-by: Thomas Lamprecht <t.lamprecht at proxmox.com>
---
 qm.adoc | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/qm.adoc b/qm.adoc
index 1c7373e..7aadf60 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -602,15 +602,17 @@ parameters:
 * *Start/Shutdown order*: Defines the start order priority. E.g. set it to 1 if
 you want the VM to be the first to be started. (We use the reverse startup
 order for shutdown, so a machine with a start order of 1 would be the last to
-be shut down)
+be shut down). If multiple VMs have the same order defined on a host, they will
+additionally get ordered by 'VMID' in ascending order.
 * *Startup delay*: Defines the interval between this VM start and subsequent
 VMs starts . E.g. set it to 240 if you want to wait 240 seconds before starting
 other VMs.
 * *Shutdown timeout*: Defines the duration in seconds {pve} should wait
 for the VM to be offline after issuing a shutdown command.
-By default this value is set to 60, which means that {pve} will issue a
-shutdown request, wait 60s for the machine to be offline, and if after 60s
-the machine is still online will notify that the shutdown action failed.
+By default this value is set to 180, which means that {pve} will issue a
+shutdown request, wait 180 seconds for the machine to be offline. If, after
+this timeout, the machine is still online it will be tried to forcefully stop
+it.
 
 NOTE: VMs managed by the HA stack do not follow the 'start on boot' and
 'boot order' options currently. Those VMs will be skipped by the startup and
@@ -618,8 +620,8 @@ shutdown algorithm as the HA manager itself ensures that VMs get started and
 stopped.
 
 Please note that machines without a Start/Shutdown order parameter will always
-start after those where the parameter is set, and this parameter only
-makes sense between the machines running locally on a host, and not
+start after those where the parameter is set. Further, this parameter can only
+be enforced between virtual machines, running locally on a host, but not
 cluster-wide.
 
 
-- 
2.11.0