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

    Posts

    Recent Best Controversial
    • RE: French government initiative to support

      Thank you for this constructive argument ❀

      Have a nice day.

      posted in News
      julien-fJ
      julien-f
    • RE: Is there a way to proxy the xe command?

      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!

      posted in Compute
      julien-fJ
      julien-f
    • RE: xoce INTERNAL_ERROR while trying to create VM

      Thank you all, this is now fixed.

      https://github.com/vatesfr/xen-orchestra/commit/07bd9cadd4732554c57e441cd9d860b63f73fe02

      posted in Xen Orchestra
      julien-fJ
      julien-f
    • RE: XO tree view

      @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. πŸ™‚

      posted in Xen Orchestra
      julien-fJ
      julien-f
    • RE: Backups to SMB remote failing

      @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 πŸ˜‰

      posted in Xen Orchestra
      julien-fJ
      julien-f
    • [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: Group Query

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

      posted in REST API
      julien-fJ
      julien-f
    • RE: Group Query

      @M92 Hello, no, groups are not exposed at this time, will do it ASAP.

      posted in REST API
      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: Unable to convert VM to Template in Xen Orchestra ( VBD_IS_EMPTY )

      @josh383451 The bug was fixed 3 days ago: https://github.com/vatesfr/xen-orchestra/commit/73d88cc5f1a5458c68e6935a9d5a9240616007b1

      posted in Xen Orchestra
      julien-fJ
      julien-f
    • RE: CD drive not completely installed in XOA

      @olivierlambert Done: https://github.com/vatesfr/xen-orchestra/commit/33b45d2eda2ce6d8071541da246bdcfd06b133b8

      It's not perfect but that should help πŸ™‚

      Example:

      vm.start
      {
        "id": "123e4f2b-498e-d0af-15ae-f835a1e9f59f",
        "bypassMacAddressesCheck": false,
        "force": false
      }
      {
        "errors": [
          "R620-L3: VM_REQUIRES_SR(OpaqueRef:21fa00fc-62ce-4694-8b49-fcecd600a89e, OpaqueRef:4dd615a7-9a8c-4698-aceb-c10f782321c8)",
          "R620-L1: HOST_NOT_ENOUGH_FREE_MEMORY(216430280704, 18778341376)",
          "R620-L2: VM_REQUIRES_SR(OpaqueRef:21fa00fc-62ce-4694-8b49-fcecd600a89e, OpaqueRef:4dd615a7-9a8c-4698-aceb-c10f782321c8)"
        ],
        "message": "",
        "name": "Error",
        "stack": "Error: 
          at Xapi._startVm (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xapi/index.mjs:1358:15)
          at Xapi.startVm (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xapi/index.mjs:1393:7)
          at Api.callApiMethod (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:307:20)"
      }
      
      posted in Xen Orchestra
      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: [BUG]? If you don't have a disk attached, snapshots don't get cleaned up automatically

      @florent It was working before, this is likely something that has been broken when the handling of snapshots has been moved from VMs to VDIs.

      We need to fix this.

      posted in Backup
      julien-fJ
      julien-f
    • RE: [Suggestion] Don't try to attach passthrough devices when doing Healthchecks

      @probain Noted in backlog

      posted in Backup
      julien-fJ
      julien-f
    • RE: Migration doesn't work in XCP-ng Centar after successful backup with Xen Orchestra

      Hello all!

      It should be fixed https://github.com/vatesfr/xen-orchestra/commit/72592a54d2225d5368a3410e4b3c19039f8e5df1 πŸ™‚

      posted in Backup
      julien-fJ
      julien-f
    • RE: Export to ova from command line

      @Dude417 Hello, you need to use the format param for that:

      xo-cli vm.export vm=a01667e0-8e29-49fc-a550-17be4226783c format=ova @=vm.ova
      

      I've also just added OVA support for VM export in the REST API: https://github.com/vatesfr/xen-orchestra/blob/master/packages/xo-server/docs/rest-api.md#vm-export

      posted in Backup
      julien-fJ
      julien-f
    • RE: XO Backup Advanced Backup Schedules

      @olivierlambert It's a limitation of CRON patterns, to support this we need to implement it separately and design a dedicated UI.

      posted in Backup
      julien-fJ
      julien-f
    • RE: Latest commit smoked NFS remotes

      @fataugie Should be fixed, let me know if there are any issues left!

      https://github.com/vatesfr/xen-orchestra/commit/194db8d0dd28ccfd058c97e8c16b32d853b26cf8

      posted in Backup
      julien-fJ
      julien-f
    • RE: XO VM Export Fails With Unknown Error

      @XCP-ng-JustGreat Thank you for your report, it should be fixed πŸ™‚

      https://github.com/vatesfr/xen-orchestra/commit/0794a63

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

      @dj423 It's because the cloud-init configs in XO are template and some entries are replaced:

      • {name} with the name of the VM
      • % the index of the VM starting from 0, only useful when the advanced setting Multiple VMs is enabled, always 0 otherwise

      Would it fix your problem if we change the behavior so that % is simply removed when Multiple VMs is not enabled?

      posted in Infrastructure as Code
      julien-fJ
      julien-f