VM Startup Delay Setup

[Guillaume Soucy]

Hello,

I just want to confirm if my setup is correctly configured.

For the first VM in Startup delay field I'd put nothing, the second one I'd put 60, the third one 120, the fourth one 180 till I reach the last one whom is set to 900.

I red the documentation but it is not clear to me.

Best regards,

Guillaume

 

[Dunuin]

I would work with Start/Shutdown order too. Start/Shutdown order 1 + delay 60, Start/Shutdown order 2 + delay 60, Start/Shutdown order 3 + delay 60, ...
That way also a guest should be started every 60 seconds but shutting down the node will shutdown guests in the reverse order.

 

[Guillaume Soucy]

Hello,

If I'd setup a start/shutdown order, is that mean the value for the delay could be 60 everywhere instead of 60, 120, 180?

Guillaume

 

[Dunuin]

Didn't used delay for a long time. But as far as I remember, yes.
With...
pfsense VM: start/shutdown order 1; delay 60
NAS VM: start/shutdown order 2; delay 60
Webserver VM: start/shutdown order 3; delay 60
...it should start pfsense VM -> NAS VM -> Webserver VM with a delay of 60 seconds between each start.
And when you shutdown the node it will shutdown the VMs in reverse order so Webserver VM -> NAS VM -> pfsense VM. That way you won't run into problems where NAS couldn't be accessed because pfsense might be shutdown first or webserver couldn't flush writes because NAS isn't accessible anymore.

 

[Guillaume Soucy]

Okay, that good, I will give this a try.

However, I rarely need to reboot hosts, the only time I do need to do so is when I'm making hardware upgrades. Even power outages aren't affecting the servers because I do have standby generators.

Startup order/delays will be very useful in my case, if I need to reboot an host, everything will start smoothly. I find myself in situations where some web servers didn't start as resources was all tied... This as example. ;-)

Best regards,

Guillaume