Subcategories

  • VMs, hosts, pools, networks and all other usual management tasks.

    431 Topics
    3k Posts
    itservicesI
    Hi @McHenry . You should obfuscate the IP address in your first screenshot. Also check your profile and private chat Hope everyone had a joyful Christmas and I wish everyone the best for 2026. Regards, Marc
  • ACLs, Self-service, Cloud-init, Load balancing...

    97 Topics
    818 Posts
    olivierlambertO
    October release fixed it
  • All XO backup features: full and incremental, replication, mirrors...

    444 Topics
    4k Posts
    A
    I have opened a support ticket and tunnel is open - Ticket#7749796 here is a section of the error log. I have rebooted XOA and rebooted the Proxy but yet the job still remains hung. Maybe i didn't reboot them in the correct order? As stated support ticket and tunnel are open. { "id": "1766901730734", "message": "snapshot", "start": 1766901730734, "status": "success", "end": 1766901734483, "result": "a995b25e-ab77-a217-fccd-7e8a1d06df57" }, { "data": { "id": "3022703c-5029-4ac3-bda1-3a76c6634a39", "isFull": true, "type": "remote" }, "id": "1766901734494", "message": "export", "start": 1766901734494, "status": "interrupted", "tasks": [ { "id": "1766901737246", "message": "transfer", "start": 1766901737246, "status": "interrupted" } ] } ], "infos": [ { "message": "Transfer data using NBD" } ] } ], "end": 1766901871318, "result": { "url": "https://10.120.20.119/api/v1", "message": "HTTP connection has timed out", "name": "Error", "stack": "Error: HTTP connection has timed out\n at ClientRequest.<anonymous> (/usr/local/lib/node_modules/xo-server/node_modules/http-request-plus/index.js:61:25)\n at ClientRequest.emit (node:events:518:28)\n at ClientRequest.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17)\n at TLSSocket.emitRequestTimeout (node:_http_client:849:9)\n at Object.onceWrapper (node:events:632:28)\n at TLSSocket.emit (node:events:530:35)\n at TLSSocket.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17)\n at TLSSocket.Socket._onTimeout (node:net:595:8)\n at listOnTimeout (node:internal/timers:581:17)\n at processTimers (node:internal/timers:519:7)" schedule.runSequence { "schedules": [ "3a677031-4eb9-427a-99fc-22afa411b745", "cadef7b9-2541-4850-9bfd-871d9602c6bb", "599d9321-7081-4840-9617-d31762d4764c", "828b5e60-4302-455c-94f1-479a8001f955" ] } { "url": "https://10.120.20.119/api/v1", "message": "HTTP connection has timed out", "name": "Error", "stack": "Error: HTTP connection has timed out at ClientRequest.<anonymous> (/usr/local/lib/node_modules/xo-server/node_modules/http-request-plus/index.js:61:25) at ClientRequest.emit (node:events:518:28) at ClientRequest.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17) at TLSSocket.emitRequestTimeout (node:_http_client:849:9) at Object.onceWrapper (node:events:632:28) at TLSSocket.emit (node:events:530:35) at TLSSocket.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17) at TLSSocket.Socket._onTimeout (node:net:595:8) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)" backupNg.runJob { "id": "bb0adfc7-93b9-45c9-a90f-7aa327f95a05", "schedule": "3a677031-4eb9-427a-99fc-22afa411b745", "vms": [ "4c2fb974-f2d5-b0fb-7385-1683e0275ef2", "025f71ff-ecb2-9d0c-7692-f7005d22c659", "78aecc3d-4817-a11c-04b4-9d0f49f8736e", "9f36a8c5-c988-8546-b0f9-30ac9d0a5015", "db89c6f0-3330-7180-b5e4-7f2f36a241e6", "e5c656bb-8bb2-461e-a801-402ae150d022" ] } { "code": -32000, "data": { "jobId": "bb0adfc7-93b9-45c9-a90f-7aa327f95a05", "stack": "Error: job is already running at file:///usr/local/lib/node_modules/@xen-orchestra/proxy/app/mixins/backups.mjs:96:25 at file:///usr/local/lib/node_modules/@xen-orchestra/proxy/app/mixins/backups.mjs:114:20 at processTicksAndRejections (node:internal/process/task_queues:95:5)" },
  • Everything related to Xen Orchestra's REST API

    75 Topics
    571 Posts
    F
    @MathieuRA Thank you, perfect Br,
  • Terraform, Packer or any tool to do IaC

    45 Topics
    427 Posts
    CyrilleC
    Terraform provider release v0.37.0 Enables the secure boot parameter for the VM resource Terraform provider release: https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.37.0
  • 0 Votes
    27 Posts
    16k Views
    olivierlambertO
    Short answer: no. Long answer: I'm not sure on the "how" we could do that. You should probably ask a XAPI developer about this. I'll try to get one or two here
  • Memory Usage wouldn't be displayed in XOA

    Solved
    8
    4
    0 Votes
    8 Posts
    2k Views
    olivierlambertO
    So yes, it was the service not started properly, so we didn't get the info into XOA You are welcome, enjoy it!
  • LDAP Plugin with start_tls

    3
    0 Votes
    3 Posts
    546 Views
    olivierlambertO
    Linking the issue here: https://github.com/vatesfr/xen-orchestra/issues/4999 franc6 created this issue in vatesfr/xen-orchestra closed Feature Request to support TLS for auth-ldap plugin #4999
  • 0 Votes
    2 Posts
    357 Views
    olivierlambertO
    Hi! I suppose you mean XOA? And yes, you can, until we have a UUID bind per XOA.
  • centos 8 cloud image + not changing cloud config hostname

    10
    0 Votes
    10 Posts
    4k Views
    stormiS
    Thanks for sharing.
  • XOA build: unknown

    Solved
    10
    1
    0 Votes
    10 Posts
    1k Views
    olivierlambertO
    The information is visible in the build number you have in your XO section. The build number will be visible in the latest appliance once deployed. Because it's not mandatory to use the last one, we don't track it. As I said, it's not a problem to update it until we ask people to change it
  • Backup Retention Cleanup Issue

    4
    3
    0 Votes
    4 Posts
    569 Views
    olivierlambertO
    Good, keep us posted.
  • Feature request: VM low disk space perf-alert

    2
    0 Votes
    2 Posts
    276 Views
    olivierlambertO
    Right now there's no way to know what's happening inside a VM disk. So we can't know when a VM disk is full or not.
  • Kubernetes cluster recipe not starting kubernetes

    xoa-recipe k8s
    4
    0 Votes
    4 Posts
    1k Views
    D
    Thanks for the tip. Requested.
  • XOA create VM from snapshot makes VDI but VM is lost

    3
    0 Votes
    3 Posts
    1k Views
    olivierlambertO
    Ping @julien-f
  • Restoring VMs from a new instance XO?

    Solved
    7
    0 Votes
    7 Posts
    1k Views
    DanpD
    @Biggen Yeah... definitely easier to backup / restore the config file.
  • Building XO from sources on Fedora, anyone?

    fedora
    8
    0 Votes
    8 Posts
    1k Views
    olivierlambertO
    @m076162 I updated XO doc: https://xen-orchestra.com/docs/installation.html#packages
  • console is not possible

    2
    0 Votes
    2 Posts
    1k Views
    R
    I had similar problems in 8. Even though I had static leases set in DHCP, oftentimes services come up before the IP address has been obtained. The physical console and SSH worked, but not XOA nor XCP center. Set a static IP address and reboot. If that does not work, repeat the installation and set a static IP at install. Make sure your IP address has not changed and look at the lease time. Is it only leased out for a few minutes? Here is where we discussed it for version 8: Broken Host Consoles in fresh xcp-ng 8 installation. VM consoles work.
  • Import OVA silently fails

    23
    3
    0 Votes
    23 Posts
    8k Views
    B
    @olivierlambert Thanks!
  • Name of file backup

    Solved
    2
    0 Votes
    2 Posts
    489 Views
    olivierlambertO
    Hi, No. Using UUIDs is vital to have consistent files (if you change the VDI or VM name etc.) Any XO, even a fresh one, is able to connect to your remote and restore your backup. So there's no need to access files directly.
  • How to save Statistic from XOA when rebooting the XCP-NG Nodes?

    6
    0 Votes
    6 Posts
    703 Views
    olivierlambertO
    It should be the same result on XCP-ng Center: it uses RRDs files stored on the host. Why do you continue to talk about the after the reboot? You mean after the upgrade, right? RRDs are preserved after a reboot If you do a yum update, those stats should be in theory preserved. If it's not the case, try to diagnose why, by comparing behavior between XCP-ng Center and XO. If it's not the same, then it's a client issue. If it's the same, then it means a version upgrade (yum or ISO) won't preserve RRDs. If you really want long terms stats for "real production" usage on long term, I strongly suggest that you think to store them in a real time series database, like Prometheus or so.
  • Citrix Hypervisor 8.1 Snapshot / Backup problem

    Solved
    6
    0 Votes
    6 Posts
    1k Views
    dbeatoD
    @dbeato Update on this. Basically I needed to run the Updates on the XCP-ng hosts even though they were on 8.1 and upgraded 5 packages. Once I did that since I had an Updated XOA system, then I reboot the servers and XOA and now backups are running!
  • [Jobs] invalid parameters (old jobs)

    1
    0 Votes
    1 Posts
    279 Views
    No one has replied
  • No Statistics in XOA after Rebooting our XCP-NG Nodes

    6
    1
    0 Votes
    6 Posts
    1k Views
    olivierlambertO
    Nothing. You should have the stats visible in live (post-upgrade). That's it. If you don't, it might be because your nodes are behind a NAT.
  • XOA Proxy Console Log-In

    2
    0 Votes
    2 Posts
    561 Views
    olivierlambertO
    Hi, Please open a support ticket so we can assist you more efficiently https://support.vates.fr/