XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    • Profile
    • Following 0
    • Followers 3
    • Topics 2
    • Shares 0
    • Posts 696
    • Groups 4
    julien-fJ Offline
    1. Home
    2. julien-f
    3. Posts

    Posts

    Recent Best Controversial
    • [Security] VSA-2026-062: critical Xen Orchestra vulnerability fixed, please update

      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

      1. Update to the latest master, which includes the fix from pull request #10748, then rebuild and restart xo-server as usual.
      2. Restrict access right away if Xen Orchestra is reachable from the Internet: VPN, dedicated management network or IP allow-list.
      3. Revoke all active sessions and API tokens, then rotate the secrets used in your stack: the root password of every XCP-ng host, XO proxy credentials, backup remotes (NFS, S3, etc.), XO user passwords and OTP secrets.
      4. Check for compromise: watch for unexpected VMs, imports or sessions, check the indicators of compromise listed in the advisory, and implement the blocking countermeasures it describes.

      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.

      posted in Xen Orchestra
      julien-fJ
      julien-f
    • RE: Location of xo-cli reference

      @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.

      posted in Management
      julien-fJ
      julien-f
    • RE: How to change IP of XOA & XCP-ng?

      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.

      posted in Management
      julien-fJ
      julien-f
    • RE: Export backup reports

      @McHenry You can ask for the JSON format instead of a human readable excerpt:

      xo-cli backupNg.getLogs --json
      
      posted in Backup
      julien-fJ
      julien-f
    • RE: Enhancement suggestion: Filter showing VMs that don't have the agent installed

      @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.

      posted in Xen Orchestra
      julien-fJ
      julien-f
    • RE: ACL security issue with ansible

      @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.

      posted in Infrastructure as Code
      julien-fJ
      julien-f
    • RE: XO Proxy: Local remotes are disabled in proxies

      @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
      
      posted in Backup
      julien-fJ
      julien-f
    • RE: Migrating configured backup jobs between XO from sources

      @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.

      posted in Backup
      julien-fJ
      julien-f
    • RE: Backup fails with "Body Timeout Error", "all targets have failed, step: writer.run()"

      @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.

      posted in XCP-ng
      julien-fJ
      julien-f
    • RE: XO Rest API

      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.

      posted in REST API
      julien-fJ
      julien-f
    • RE: XO Rest API

      @irtaza9 As explained in the documentation, the method is a POST (cf. https://github.com/vatesfr/xen-orchestra/blob/master/packages/xo-server/docs/rest-api.md#start-an-action).

      As explained in the documentation, you can list the available actions at /rest/v0/pools/_/actions and see the list of available params for a specific action by checking out its endpoint (/rest/v0/pools/_/create_vm for create_vm).

      To create/alter disks, you need to use the vdis param, if you do not see it on your instance, it means it is not up-to-date.

      CPU settings are not available at this time.

      posted in REST API
      julien-fJ
      julien-f
    • RE: XO Rest API

      @irtaza9 Creating a VM is an action on a pool.

      Check out the /rest/v0/pools/_/actions endpoint for the available actions and expected params.

      posted in REST API
      julien-fJ
      julien-f
    • RE: Dynamic cloudinit network config [FEATURE REQUEST]

      @olivierlambert It's still possible to use the VM number in the cloud-init template: {index} since XO 5.100 (% before)

      See the changelog.

      posted in Xen Orchestra
      julien-fJ
      julien-f
    • RE: Clarification on Creating ResourceSet via xo-cli

      @samuelolavo Shell only handles string values, to pass other types to xo-cli you need to encode them in JSON and use the json: prefix:

      xo-cli resourceSet.create name=test-resource subjects=json:'["d301d9ea-9e22-4480-bf40-111111111111"]' objects=json:'["8fb06362-d8fe-598b-f819-11111111111111"]' shareByDefault=json:true
      
      posted in REST API
      julien-fJ
      julien-f
    • RE: VMs Showing as "Not Backed Up" and "Unknown Job" When Using Sequences Only

      @cirosantos0 Indeed, our detection is wrong in this case, I will put this in our backlog, but don't expect it to be fixed soon.

      PRs are welcome though 🙂

      posted in Backup
      julien-fJ
      julien-f
    • RE: % characters in cloud-init configs render as 0 in instance

      @dj423 It should be fixed in the master branch: https://github.com/vatesfr/xen-orchestra/commit/30e6d4b4f14ddbb6ee34cd456e4ca707486df2db

      • {index} is now used in place of %
      • % is still working when Multiple VMs is enabled
      • % and \% will be replaced by % when Multiple VMs is disabled
      posted in Infrastructure as Code
      julien-fJ
      julien-f
    • RE: xo-cli user.create issues

      @samuelolavo No, users management and self service are not in the REST API yet.

      posted in REST API
      julien-fJ
      julien-f
    • RE: Running xo-cli command returns Unhandled Error

      @nick-lloyd Yes, you can filter collection using the same syntax of XO's Home page as explained in the REST API documentation:

      xo-cli rest get plugins/audit/records filter=data:method:vm.snapshot
      
      posted in Management
      julien-fJ
      julien-f
    • RE: % characters in cloud-init configs render as 0 in instance

      @dj423 Then my solution would not work as it would break all your tags.

      But indeed, maybe we should not replace % at all when Multiple VMs is disabled.

      I know it's a bit cumbersome but in the meantime, you can escape the problematic character: \%.

      posted in Infrastructure as Code
      julien-fJ
      julien-f
    • RE: Running xo-cli command returns Unhandled Error

      @olivierlambert Never heard of invalid code lengths set.

      Also, it's strange that this command is not working but others are… Maybe it's related to the size of the response…

      You can try to use the REST API:

      xo-cli rest get -o records.ndjson plugins/audit/records fields=data,event,subject,time,id ndjson
      
      posted in Management
      julien-fJ
      julien-f