Feature Request / Community Input – VM Boot Order & Delayed Startup
-
Hello everyone,
I’m currently deploying a complete infrastructure for a client who previously used Hyper-V, where we could easily configure a VM boot order as well as startup delays between VMs.
This ensured a clean sequence:
1. XOA
2. Domain Controller
3. Application servers, etc.⸻
What I have verified so farI contacted the official XCP-ng / XOA support, and they confirmed that this functionality does NOT currently exist, even on the paid (Premium) version of XOA.
They also confirmed that:
• There is no native way to set a boot priority in XCP-ng
• There is no parameter such as order= or delay= in xe vm-param-set
• XOA does not provide a UI for this either
• The orchestration engine does not currently support dependent startup⸻
What I’m asking the communityBefore I build something custom (scripts, hooks, cron jobs, etc.), I would like to know:
Has anyone implemented a reliable way to:
• Force a boot order for VMs
• Introduce a configurable delay between VM startups
• Ensure XOA starts first, then the Domain Controller, then other servers Is there perhaps:
• A community script
• A known workaround
• A XenAPI trick
• Or an unofficial feature hidden somewhere?⸻
Environment
• XCP-ng host
• XOA Premium
• ~5 VMs (DC, financial software, POS system, XOA itself, etc.)
• Need clean deterministic startup order after host reboot or power outage⸻
Any insight or community solutions would be greatly appreciated!
This is something my client relied on in Hyper-V, so I’m trying to replicate the behavior in XCP-ng as cleanly as possible.Thanks in advance!
-
Hi,
You can use vApp for that.
-
said in Feature Request / Community Input – VM Boot Order & Delayed Startup:
Hello everyone,
I’m currently deploying a complete infrastructure for a client who previously used Hyper-V, where we could easily configure a VM boot order as well as startup delays between VMs.
This ensured a clean sequence:- XOA
- Domain Controller
- Application servers, etc.
⸻
What I have verified so farI contacted the official XCP-ng / XOA support, and they confirmed that this functionality does NOT currently exist, even on the paid (Premium) version of XOA.
They also confirmed that:
• There is no native way to set a boot priority in XCP-ng
• There is no parameter such as order= or delay= in xe vm-param-set
• XOA does not provide a UI for this either
• The orchestration engine does not currently support dependent startup⸻
What I’m asking the communityBefore I build something custom (scripts, hooks, cron jobs, etc.), I would like to know:
Has anyone implemented a reliable way to:
• Force a boot order for VMs
• Introduce a configurable delay between VM startups
• Ensure XOA starts first, then the Domain Controller, then other servers Is there perhaps:
• A community script
• A known workaround
• A XenAPI trick
• Or an unofficial feature hidden somewhere?⸻
Environment
• XCP-ng host
• XOA Premium
• ~5 VMs (DC, financial software, POS system, XOA itself, etc.)
• Need clean deterministic startup order after host reboot or power outage⸻
Any insight or community solutions would be greatly appreciated!
This is something my client relied on in Hyper-V, so I’m trying to replicate the behavior in XCP-ng as cleanly as possible.Thanks in advance!
Hello Olivier, vApp ???
What do you mean ?
-
@Cygace in advanced settings of VMs
there is
I know at scale it is not easy with 100+ VMs but...
try to put 40s for all VMs, except 20s for domain controller, and 0 for XOA ?that will not change start order as you think it, but in case of a full restart should do the job ?
-
