@poddingue said:
That second one is exactly what you saw: the delay lands on the next VM to start, not on the one you set it on. I quoted the confusing one and then said it explained your behaviour, which it does not really.
I am really puzzled by this because it makes absolutely no sense whatsoever. I mean why would you design it like that? When I open a VM's settings and find start delay in there, it makes perfect sense to assume it delays start of the one I am messing around with. It makes even less sense for the feature to even exist in the first place when you consider there is no way to set the order in which VMs start.
I am surprised noone ever brought this up and it wasn't changed. It's pretty basic functionality I took for granted when I moved over from ESXi. For example, I have TrueNAS VM and also a torrent seedbox, and the seedbox absolutely has to start after the NAS has fully booted up, otherwise the share it connects to is unavailable. Well it just doesn't work here and everytime I reboot the server (thankfully that doesn't happen often) I have to remember to restart the seedbox VM manually once.
