[PVE-User] VM startup fails ("got timeout")

[Michael Doerner | TechnologyWise]

Hi Daniel

thanks for your help with that pointer to the startup delay. I had not 
noticed that setting before (how bad).

We have applied a 60 second delay on that host and hope this will solve 
the issue. In parallel we will also look into the hardware RAID 
controller set up whether there is any indication for the delay.

Thanks again,
Michael


On 27/09/22 00:42, Daniel Tschlatscher wrote:
> 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 at lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>