bump version to 4.2-11

[pve-docs.git] / pvecm.adoc

diff --git a/pvecm.adoc b/pvecm.adoc
index 6f8b3826c63dd38a9a38593258552a4c6cd0d699..e6e2058d73ed813d272d2a91dbe692eb6b51a2ec 100644 (file)
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -311,18 +311,13 @@ NOTE: It is always a good idea to use an uninterruptible power supply
 ('UPS', also called 'battery backup') to avoid this state. Especially if
 you want HA.
 
-On node startup, service 'pve-manager' waits up to 60 seconds to reach
-quorum, and then starts all guests. If it fails to get quorum, that
-service simply aborts, and you need to start your guest manually once
-you have quorum.
-
-If you start all nodes at the same time (for example when power comes
-back), it is likely that you reach quorum within above timeout. But
-startup can fail if some nodes starts much faster than others, so you
-need to start your guest manually after reaching quorum. You can do
-that on the GUI, or on the command line with:
-
- systemctl start pve-manager
+On node startup, service 'pve-manager' is started and waits for
+quorum. Once quorate, it starts all guests which have the 'onboot'
+flag set.
+
+When you turn on nodes, or when power comes back after power failure,
+it is likely that some nodes boots faster than others. Please keep in
+mind that guest startup is delayed until you reach quorum.
 
 
 ifdef::manvolnum[]