Start VM/CTs in parallel at boot rather than one at a time?

[owldown]

I'm able to set certain containers and VMs to boot 1st, 3nd, etc, and those unspecified appear to then start in numerical order by ID. This still takes longer (10 minutes!) than it seems that it should take. Is there a way for PVE to start multiple VMs or CTs at the same time, rather than waiting for #105 to finish before starting #106?

I've looked in the docs, and I thought that maybe Datacenter / Options / Maximal Workers bulk action would help, but it seems to only affect bulk shutdowns, and has no effect on starting containers.

 

[reinob]

How often do you reboot your server?
I mean, perhaps it would be nice to have such control over the VM/container startup, but it's probably irrelevant (for most), as you normally only need to reboot if there's a kernel/major update, and this doesn't happen that often!

 

[owldown]

How often do you reboot your server?
I mean, perhaps it would be nice to have such control over the VM/container startup, but it's probably irrelevant (for most), as you normally only need to reboot if there's a kernel/major update, and this doesn't happen that often!

Not super often, but it's a used tower, I'm still figuring out how to set the fans in the bios, I bought some used RAM that turned out to fail MEMTEST, I bought a new drive, I bought a SATA controller, I don't have a UPS for it, etc. As I learn, I'm not needing to reboot frequently. I don't reboot daily, but it just seems suboptimal that when I manually start an LXC, it takes seconds, but when I'm looking at the web interface after a reboot (which is ready quickly, in about 20 seconds), it takes 10 minutes to start 2 VMs and 12 LXCs. I don't need clustered HA, but I'd like things to automatically be started at least as fast as I can do it manually.