Proxmox/pve-docs
5
0
Fork 0
mirror of git://git.proxmox.com/git/pve-docs.git synced 2025-01-06 13:17:48 +03:00
Code Releases Activity

qm: improve auto start/stop section

Browse Source 
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@proxmox.com>
This commit is contained in:
Thomas Lamprecht 2018-01-17 09:25:40 +01:00 committed by Wolfgang Bumiller
parent 82445c4eec
commit 7eed72d845
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
qm.adoc
View File

@ -629,15 +629,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
@ -645,8 +647,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.