Thank you for this constructive argument 
Have a nice day.
Thank you for this constructive argument 
Have a nice day.
This should work:
xe vm-param-set uuid="$uuid" \
xenstore-data:vm-data/ip="$ip" \
xenstore-data:vm-data/netmask="$netmask" \
xenstore-data:vm-data/gateway="$gateway"
Optionally the default DNS server can be replaced as well:
xe vm-param-set uuid="$uuid" xenstore-data:vm-data/dns="$dns"
Don't forget to restart the XOA afterward!
@markhewitt1978 Hi, thank you for your feedbacks!
We are aware that this limitation bothers a lot of users and we have plan to address that in the next major version of XO.
XO 5 was already a major improvement over its predecessor because it allows viewing and handling a much bigger infra.
XO 6 will go further in this direction by introducing a tree view and the possibility to edit and handle many objects at the same time. 
@Danp That may not be directly to script but to the external environment: SMB works much better if cifs-utils is installed on the system, something that is present on our doc but might be missing in some install scripts.
We have no animosity whatsoever regarding these scripts but we prefer our appliances (or even manual installs from our documentation) because we understand much better what's going on and it's easier to replicate and fix the issues 
Regarding your idea of including the commit identifier for the source version, that's not a bad idea, a (as simple as possible) implementation in a PR would be welcome 
Hello everyone,
In today’s cybersecurity landscape, vulnerabilities are an ongoing reality for all software vendors, and open source projects are no exception. We take our responsibility to identify, address and communicate security issues very seriously, including towards our community.
We were recently made aware that a vulnerability affecting Xen Orchestra (VSA-2026-062) was being actively exploited by a threat actor. Our teams mobilized immediately. The vulnerability was under embargo; the embargo has now been lifted, and we fast-tracked a patch in line with our vulnerability handling process. The vulnerability is now fixed.
Most Xen Orchestra deployments are not exposed to the public Internet, which greatly reduces the likelihood of exploitation. If your Xen Orchestra is reachable from the public Internet, however, urgent action is strongly advised.
If you run Xen Orchestra from sources
master, which includes the fix from pull request #10748, then rebuild and restart xo-server as usual.If you use a Xen Orchestra Appliance (XOA): update to 6.10.1 (latest channel) or 6.9.2 (stable channel). In XO 5, go to XOA > Updates and click Upgrade.
All instructions are centralized in the advisory, which will be updated as new information becomes available:
https://docs.vates.tech/security-advisories/advisories/2026/vates-sa-2026-062/
A reminder that applies to any product: a virtualization management plane should never be exposed to the whole Internet, however up to date it is. A VPN and a dedicated management network remain the best protection against the next unknown vulnerability.
If you have questions, feel free to ask in this thread. Please don’t post logs or details that could expose your infrastructure publicly.
@M92 There is now a /groups collection which lists all the groups and two new collections, /groups/:id/users and /users/:id/groups which list respectively all users in a group and all groups a user belongs to.
These new collections have the same behaviours than the others, which means they accept the fields, filter and limit parameters.
And yes the limit parameter should work correctly, let me know if you have any issue.
@M92 Hello, no, groups are not exposed at this time, will do it ASAP.
@Davidj-0 You can list VMs without a management agent with the following filter: power_state:running !managementAgentDetected?.
XO does not support this for halted VMs but that could be added indeed.
Hello everyone,
In today’s cybersecurity landscape, vulnerabilities are an ongoing reality for all software vendors, and open source projects are no exception. We take our responsibility to identify, address and communicate security issues very seriously, including towards our community.
We were recently made aware that a vulnerability affecting Xen Orchestra (VSA-2026-062) was being actively exploited by a threat actor. Our teams mobilized immediately. The vulnerability was under embargo; the embargo has now been lifted, and we fast-tracked a patch in line with our vulnerability handling process. The vulnerability is now fixed.
Most Xen Orchestra deployments are not exposed to the public Internet, which greatly reduces the likelihood of exploitation. If your Xen Orchestra is reachable from the public Internet, however, urgent action is strongly advised.
If you run Xen Orchestra from sources
master, which includes the fix from pull request #10748, then rebuild and restart xo-server as usual.If you use a Xen Orchestra Appliance (XOA): update to 6.10.1 (latest channel) or 6.9.2 (stable channel). In XO 5, go to XOA > Updates and click Upgrade.
All instructions are centralized in the advisory, which will be updated as new information becomes available:
https://docs.vates.tech/security-advisories/advisories/2026/vates-sa-2026-062/
A reminder that applies to any product: a virtualization management plane should never be exposed to the whole Internet, however up to date it is. A VPN and a dedicated management network remain the best protection against the next unknown vulnerability.
If you have questions, feel free to ask in this thread. Please don’t post logs or details that could expose your infrastructure publicly.
@Byte0 The json: makes the rest of the value interpreted as JSON, otherwise it is interpreted as a plain string. It is therefore required for all non-string values.
Some method params (like memory for vm.set) accept both integers and strings, that's why it was working.
xoa network static supports setting IPv6 addresses but do not allow setting multiple gateways for a single interface at this time.
And indeed, it's also not possible to set XOA's network config from the UI.
@McHenry You can ask for the JSON format instead of a human readable excerpt:
xo-cli backupNg.getLogs --json
@Davidj-0 You can list VMs without a management agent with the following filter: power_state:running !managementAgentDetected?.
XO does not support this for halted VMs but that could be added indeed.
@nickdsl This is a known limitation: at the moment, xo-server doesn’t filter objects based on permissions: permissions are currently applied during actions.
We’re actively working on resolving this in XO6 and the new REST API to improve overall functionality.
@chr1st0ph9 Local remotes are disabled by default for XO Proxies because they can be confusing: they are local to the XO Proxy itself and not the XOA they are defined in.
You can enable them by creating a config file on the XO Proxy Appliance, /etc/xo-proxy/config.toml:
[remotes]
disableFileRemotes = false
@ewoudstra Simply updating the git repo and rebuilding should be enough, but it depends a lot of how your previous XO.
The data should be kept across version as they are stored in Redis and in a LevelDB database as long as you are using the same ones.
And, as @olivierlambert said, if you cannot figure out the problem, simply export the config of your previous XO and import it into the new one.
@Bambos A timeout error means that the host did not reply in the expected delay, which, if I'm remembering correctly is 5 minutes.
I suspect a problem on your host but we will take a look further on your support ticket.
Yes, you can use JSON-RPC et REST APIs together for now 
We will try to add support for CPU settings soon.
Also, expect things to accelerate in 2025 regarding the REST API.