XCP-ng and Xen Orchestra Operators: hosts and VMs on XCP-ng and XenServer

2501 works on XCP-ng and XenServer in two ways: the XCP-ng CLI Operator from the host's control layer, or the Xen Orchestra API Operator through Xen Orchestra's API from a management host, without logging in to the hypervisor itself. Diagnosis runs on its own, and changes to a running guest are proposed for a person to approve.

A host looks saturated, a VM shows as halted, a storage repository is nearly full. On Xen, the first question is which layer is at fault: the host's control layer is itself a virtual machine with a slice of the host, and a busy guest does not show in its load.

What 2501 does

The XCP-ng specialties handle busy hosts, halted or hung VMs, full storage repositories and a full disk in the control layer, and trace each problem to the right layer: the control layer, the host or a guest. Through Xen Orchestra, anything its account is not allowed to do is reported, not worked around. Either way, the agent may start a halted VM a ticket asks for, while stopping, rebooting, reconfiguring or migrating a guest, or deleting anything, is set out for a person to approve. Management appliances, Xen Orchestra included, are never its target.

You stay in control

• You choose the level, per specialty: investigate only, act after a person confirms, or act on its own within your rules.
• Through Xen Orchestra, the access key is the hard limit: give the agent its own account, with rights only on the objects it looks after.
• Your rules decide which pools, hosts and guests are in scope, and destructive commands can be blacklisted outright.
• On-prem, cloud or hybrid: 2501 runs wherever you do. On-prem, no data leaves your network.

Frequently asked

Will it restart the host's management software to bring the web interface back? Not on its own. A restart leaves guests running but interrupts the web interface and API and aborts running tasks, so it is a person's decision.

Does it work with XenServer as well as XCP-ng? Yes. Both specialties cover XCP-ng and XenServer.

Related

• Read-only AI investigation
• Guardrails: what an agent may never touch
• Proxmox VE Operators: VMs, containers and cluster health
• VMware Datastore Operator: datastore space, snapshots and orphaned files