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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id A83699122A for ; Mon, 26 Sep 2022 13:52:00 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8B3B839BF for ; Mon, 26 Sep 2022 13:51: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 for ; Mon, 26 Sep 2022 13:51:28 +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 3978F424C7; Mon, 26 Sep 2022 13:42:35 +0200 (CEST) Message-ID: <9dcdbf08-6651-af97-eb3d-6416f8fd06a8@proxmox.com> Date: Mon, 26 Sep 2022 13:42:33 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0 Content-Language: en-US To: Proxmox VE user list References: From: Daniel Tschlatscher In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 1.643 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 NICE_REPLY_A -3.766 Looks like a legit reply (A) POISEN_SPAM_PILL 0.1 Meta: its spam POISEN_SPAM_PILL_1 0.1 random spam to be learned in bayes POISEN_SPAM_PILL_3 0.1 random spam to be learned in bayes SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record X-Mailman-Approved-At: Tue, 27 Sep 2022 10:19:47 +0200 Subject: Re: [PVE-User] VM startup fails ("got timeout") X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Sep 2022 11:52:00 -0000 Hello Michael, The startup-order settings apply to the next VM in the sequence. Therefore, (Start at boot, order=1, up=120) means that the first VM will start immediately, with VM #2 waiting for 2 minutes before starting. However, you can configure a startup delay for your first VM simply via the setting "startall-onboot-delay". Setting this e.g. to 60 will make VM #1 start after one minute, with subsequent VMs starting according to the startup-order delay configurations. You can find this setting under Node > System > Options > Start on boot delay in the GUI or under /nodes/{node}/config in the API. As to why your storage takes so long until it becomes ready, I unfortunately don't know what the cause could be. Best regards, Daniel On 9/24/22 23:36, Michael Doerner | TechnologyWise via pve-user wrote: > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user