From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id DA5EE6FD64 for ; Wed, 1 Sep 2021 16:17:00 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D01DA834E for ; Wed, 1 Sep 2021 16:16:30 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 390558336 for ; Wed, 1 Sep 2021 16:16:30 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 10DA5444AE for ; Wed, 1 Sep 2021 16:16:30 +0200 (CEST) From: Dylan Whyte To: pve-devel@lists.proxmox.com Date: Wed, 1 Sep 2021 16:16:13 +0200 Message-Id: <20210901141615.1832385-2-d.whyte@proxmox.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20210901141615.1832385-1-d.whyte@proxmox.com> References: <20210901141615.1832385-1-d.whyte@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.558 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH v3 pve-docs 2/4] fix #844: document first VM/CT start-up delay X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Sep 2021 14:17:00 -0000 adds subsection to the "PVE Node Management" section, discussing the initial VM/CT startup delay feature. also makes reference to this in the Qemu & LXC sections of the documentation. Signed-off-by: Dylan Whyte --- changes from v1: * Add section to PVE node management section and cross reference in pct.adoc and qm.adoc. changes from v2: * Use title-capitalisation for heading pct.adoc | 5 +++++ pvenode.adoc | 18 ++++++++++++++++++ qm.adoc | 3 +++ 3 files changed, 26 insertions(+) diff --git a/pct.adoc b/pct.adoc index b88569f..c5ed243 100644 --- a/pct.adoc +++ b/pct.adoc @@ -433,6 +433,11 @@ 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 cluster-wide. +If you require a delay between the host boot and the booting of the first +container, see the section on +xref:first_guest_boot_delay[Proxmox VE Node Management]. + + Hookscripts ~~~~~~~~~~~ diff --git a/pvenode.adoc b/pvenode.adoc index bace13c..7986fa0 100644 --- a/pvenode.adoc +++ b/pvenode.adoc @@ -83,6 +83,24 @@ of `` obtained from the `wakeonlan` property. The node specific pvenode config set -wakeonlan XX:XX:XX:XX:XX:XX ---- + +[[first_guest_boot_delay]] +First Guest Boot Delay +~~~~~~~~~~~~~~~~~~~~~~ + +In case your VMs/containers rely on slow-to-start external resources, for +example an NFS server, you can also set a per-node delay between the time {pve} +boots and the time the first VM/container that is configured to autostart boots +(see xref:qm_startup_and_shutdown[Automatic Start and Shutdown of Virtual Machines]). + +You can achieve this by setting the following (where `10` represents the delay +in seconds): + +---- +pvenode config set --startall-onboot-delay 10 +---- + + // TODO: extend and improve chapter! ifdef::manvolnum[] diff --git a/qm.adoc b/qm.adoc index c291cb0..80734e3 100644 --- a/qm.adoc +++ b/qm.adoc @@ -923,6 +923,9 @@ start after those where the parameter is set. Further, this parameter can only be enforced between virtual machines running on the same host, not cluster-wide. +If you require a delay between the host boot and the booting of the first VM, +see the section on xref:first_guest_boot_delay[Proxmox VE Node Management]. + [[qm_qemu_agent]] Qemu Guest Agent -- 2.30.2