https://forums.veeam.com/kvm-rhv-olvm-pve-schc-f62/xcp-ng-not-showing-as-virtualization-source-after-restore-t101040.html

Et voilà suffit de demander

@olivierlambert Hello Olivier same thread is already open at Veeam

Hello everyone,

We have use now XCP-ng Standalone (paid version) with a single host and about 8 VMs.

After opening a ticket with support, I received confirmation that there is currently no built-in feature in XCP-ng or XOA (even Premium) to control VM boot order or per-VM startup delays.

XOA’s Auto-Power-On option does not offer sequencing or delays.
The documentation mentions “appliances”, but even after reviewing that I don't understand how It can help me.

What I need is very simple:
1 Host 1 pool, around 8 VMs.
I need them to auto-start after a host reboot in a specific order, with a delay between each VM (e.g., XOA → Domain Controller → other servers, with 30 seconds delay).

If this cannot be done natively for now, I’ll create a startup script, but before doing that I would really appreciate feedback from others in the community who may have solved this.

Thanks in advance for any advice or ideas!

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:

1. XOA
2. Domain Controller
3. Application servers, etc.

⸻

What I have verified so far

I 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 community

Before 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 ?

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 far

I 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 community

Before 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!

https://forums.veeam.com/kvm-rhv-olvm-pve-schc-f62/xcp-ng-not-showing-as-virtualization-source-after-restore-t101040.html

Et voilà suffit de demander

@olivierlambert Hello Olivier same thread is already open at Veeam

Hi everyone,

I’m currently testing Veeam Backup & Replication 13.3.2 Beta 2, which includes the new plugin for XCP-ng. I’m running the beta on a physical Windows Server.

Here’s the situation:
1. I had an existing Veeam installation on this server.
2. I uninstalled it completely, then installed the 13.3.2 Beta 2 version.
3. The installation went fine, the license was accepted, everything looked normal.
4. However, when I tried to add XCP-ng as a virtualization source, it was not available in the list.
5. I tried troubleshooting but couldn’t find anything obvious.

To rule out any leftovers from the previous installation, I:
6. Reformatted the entire physical server.
7. Performed a clean installation of Windows Server (fresh OS).
8. Installed Veeam 13.3.2 Beta 2 again — clean environment.
9. At this point, before restoring anything, the option to add XCP-ng as a virtualization source was visible.

But then:
10. I restored my Veeam configuration backup.
11. The restore went smoothly.
12. After the restore, XCP-ng disappeared again from the list of available virtualization sources when trying to add a new one.

So now I’m stuck:
• Fresh install = XCP-ng option appears.
• After restoring configuration = option disappears.
• I’m out of ideas.

Has anyone seen this behavior, or is there anything I might be missing? Any help would be greatly appreciated.

Thanks!

@DustinB please this thread : https://xcp-ng.org/forum/topic/10036/zabbix-on-xcp-ng

@DustinB

yum update && yum install -y pcre2 --enablerepo=epel,base,updates
rpm -Uvh https://repo.zabbix.com/zabbix/7.0/rhel/7/x86_64/zabbix-release-7.0-1.el7.noarch.rpm
yum update && yum install -y zabbix-agent2 zabbix-agent2-plugin-*

Connection is now ok i need to allow iptable to grant the connection.

I need to go deeper.

With Nedata can you monitor the host and receive all the informations on the vm hosted on it ?

because with Zabbix I think this is not possible to get this data.

Any idea ?

Re: Zabbix on xcp-ng

Hello,

i just followed the instruction to install the Zabbix agent on XCPNG 8.3.

Install is ok but this is impossible for me to receive the data to Zabbix.

No connection between the host and the zabbix server.

Is there anything special to specify when you add the host to Zabbix ?

Thanks

Hi everyone,

I’m facing an issue in my XCP-ng environment and would really appreciate some advice or best practices.

I have a pool with 3 XCP-ng hosts, and I’m running Xen Orchestra (XOA) as a VM on the second host (not the master). Everything runs fine under normal conditions.

However, if I reboot the master host, I temporarily lose all control of the pool through XOA. Even though XOA is still up and running on the second host, it can’t see any hosts, VMs, or storage — it’s like the entire pool becomes unmanageable until the master comes back online.

My setup:
• 3-host XCP-ng pool
• XOA is a VM on host 2 (not the master)
• When the master is rebooted, XOA loses access to the infrastructure
• When the master is back online, everything works again

My questions:
1. Is this behavior expected in a multi-host pool?
2. Is there a safe way to promote another host to master automatically or manually during planned or unplanned downtime?
3. Would it be better to run XOA outside of the pool, on a dedicated device (e.g., a NUC, VM on another hypervisor)?
4. Are there best practices for ensuring high availability of the management layer (XAPI + XOA)?

Thanks a lot for your help!