1. Home
  2. Xen Orchestra

Subcategories

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

    476 Topics
    4k Posts
    dvdwxD
    @john.c my XO is compiled from sources... on future i will try config the v.6 to use the RBAC ACL for this case. @poddingue Thanks for your response, i will look this in a near future... My Cluster here is used only by the Tech/NOC team for tests/homologation purposes , beside that we are studying other virtualization systems because we will decrease our dependency on VMware on next year. Soon i will try change a few configurations and overview the v.6 to try fix this issue.

  • ACLs, Self-service, Cloud-init, Load balancing...

    105 Topics
    864 Posts
    M
    Is a centralized XOA server "managing" two remote Proxy-fronted XCP clusters supported with the SDN Controller Plugin? We are looking to deploy an architecture similar to this blog post from 2022: https://xen-orchestra.com/blog/xo-proxy-a-concrete-guide/

  • All XO backup features: full and incremental, replication, mirrors...

    515 Topics
    5k Posts
    P
    @poddingue Hi! Unfortunately, another error came up on the larger vms. The job also seems to be painfully slow. Slower than usual I mean. Also, it seems that job changes are not being commited. I've changed the job so it wouldn't retry in case of failure and the log shows it still trying 3 times (that was the old setting, and probably explains the job taking longer than usual). [image: 1784017759119-a917295e-ea92-4173-bc5a-7c9652a8d2ad-image.jpeg] { "id": "0mrjahr8e-ssawlbveq5", "start": 1783951215134, "status": "failure", "tasks": [ { "id": "0mrjahs3e-dbfaqajeze", "start": 1783951216250, "status": "failure", "tasks": [ { "id": "0mrjahs8s-2yb6i3fny6f", "start": 1783951216444, "status": "failure", "end": 1783959266484, "result": { "$fault": "server", "$metadata": { "httpStatusCode": 500, "requestId": "c0a9f30190109f99", "extendedRequestId": "aMJgyljkPZEdiEDW0Nk9lTmbINpI1FGIP", "attempts": 3, "totalRetryDelay": 197 }, "name": "InternalError", "Code": "InternalError", "message": "internal incident", "stack": "InternalError: internal incident\n at ProtocolLib.getErrorSchemaOrThrowBaseException (/opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:70:67)\n at S3RestXmlProtocol.handleError (/opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:1856:65)\n at S3RestXmlProtocol.deserializeResponse (/opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@smithy/core/dist-cjs/submodules/protocols/index.js:341:24)\n at process.processTicksAndRejections (node:internal/process/task_queues:104:5)\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@smithy/core/dist-cjs/submodules/schema/index.js:25:24\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/submodules/s3/index.js:367:20\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@smithy/core/dist-cjs/submodules/retry/index.js:172:50\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/checksums/dist-cjs/index.js:337:24\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/submodules/s3/index.js:64:28\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/submodules/s3/index.js:91:20" }, "message": "transfer", "data": { "progress": 40 } } ], "end": 1783959266485, "result": { "$fault": "server", "$metadata": { "httpStatusCode": 500, "requestId": "c0a9f30190109f99", "extendedRequestId": "aMJgyljkPZEdiEDW0Nk9lTmbINpI1FGIP", "attempts": 3, "totalRetryDelay": 197 }, "name": "InternalError", "Code": "InternalError", "message": "internal incident", "stack": "InternalError: internal incident\n at ProtocolLib.getErrorSchemaOrThrowBaseException (/opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:70:67)\n at S3RestXmlProtocol.handleError (/opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:1856:65)\n at S3RestXmlProtocol.deserializeResponse (/opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@smithy/core/dist-cjs/submodules/protocols/index.js:341:24)\n at process.processTicksAndRejections (node:internal/process/task_queues:104:5)\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@smithy/core/dist-cjs/submodules/schema/index.js:25:24\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/submodules/s3/index.js:367:20\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@smithy/core/dist-cjs/submodules/retry/index.js:172:50\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/checksums/dist-cjs/index.js:337:24\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/submodules/s3/index.js:64:28\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/submodules/s3/index.js:91:20" }, "message": "export", "data": { "id": "14b59f44-4517-411e-9e39-4eb7136928d0", "type": "remote", "isFull": true } }, { "id": "0mrjfabp3-c8mf2pnq8yf", "start": 1783959266487, "status": "success", "warnings": [ { "data": { "path": "xo-vm-backups/60b4d2a7-3f91-f0f9-b0a0-f834df3ff9ee/cache.json.gz", "actual": 0, "expected": 1 }, "message": "unexpected number of entries in backup cache" } ], "end": 1783959266989, "result": { "merge": false, "size": 0 }, "message": "clean-vm" } ], "end": 1783959266989, "result": { "$fault": "server", "$metadata": { "httpStatusCode": 500, "requestId": "c0a9f30190109f99", "extendedRequestId": "aMJgyljkPZEdiEDW0Nk9lTmbINpI1FGIP", "attempts": 3, "totalRetryDelay": 197 }, "name": "InternalError", "Code": "InternalError", "message": "internal incident", "stack": "InternalError: internal incident\n at ProtocolLib.getErrorSchemaOrThrowBaseException (/opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:70:67)\n at S3RestXmlProtocol.handleError (/opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:1856:65)\n at S3RestXmlProtocol.deserializeResponse (/opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@smithy/core/dist-cjs/submodules/protocols/index.js:341:24)\n at process.processTicksAndRejections (node:internal/process/task_queues:104:5)\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@smithy/core/dist-cjs/submodules/schema/index.js:25:24\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/submodules/s3/index.js:367:20\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@smithy/core/dist-cjs/submodules/retry/index.js:172:50\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/checksums/dist-cjs/index.js:337:24\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/submodules/s3/index.js:64:28\n at async /opt/xo/xo-builds/xen-orchestra-202607120728/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/submodules/s3/index.js:91:20" }, "message": "backup VM", "data": { "id": "60b4d2a7-3f91-f0f9-b0a0-f834df3ff9ee", "type": "VM", "progress": 0 } },

  • Everything related to Xen Orchestra's REST API

    86 Topics
    645 Posts
    J
    Hello I'm pulling stats for all VMs to understand CPU usage. We're a bit behind the curve in terms of XO versions, but these questions hopefully are still relevant. If using a granularity of days, the interval is set to 86400 (understandably) but the endTimestamp varies. Running this on June 9th @ ~1740 we get timestamps for both Mon Jun 8 01:00:00 AM BST 2026 and Tues Jun 9 01:00:00 AM BST 2026. Does this average across the day? Why is the timestamp 0100? Why would there be different timestamps between VMs (all are running) and does that mean that the figures are misaligned in the results? These are retrieved via curl and a bash script, a bit hacky, but for clarity the request is: ++ curl -X GET -s -H accept:application/json -b authenticationToken=[[REDACTED]] -o [[REDACTED]] 'https://[[REDACTED]]/rest/v0/vms/[[REDACTED]]/stats?granularity=days' Really keen to know if we can control the start and endtime, as well as provide a manual interval, as well as the aggregation strategy (min, max, average). Are any of these possible? Lastly, is cpuUsage the percentage as per the dashboard, but averaged over all CPUs? Thanks so much in advance. James

  • Terraform, Packer or any tool to do IaC

    51 Topics
    471 Posts
    poddingueP
    The Kubernetes CSI driver for Xen Orchestra just hit v0.4.0, and we want it on more real clusters before it reaches a stable release candidate. If you run Kubernetes on XCP-ng VMs, this is a good time to give it a proper workout. What's new in v0.4.0: Local-storage support Automatic pool-discovery fallback Kubernetes metadata now lives in Xen Orchestra VDI tags instead of the deprecated other_config. That change also drops the old requirement for Xen Orchestra 6.4 or newer, so the driver runs on more deployments now. ️ Read this before you upgrade. v0.4.0 is a breaking change. The Kubernetes metadata moved from other_config to VDI tags, so you must migrate before upgrading from v0.3.0. Do not upgrade in place: follow the v0.3.0 to v0.4.0 migration guide in the release notes, then move to v0.4.0. What helps us most is hearing how it behaves on your own setup: what works, what breaks, which storage backend you use, and which flavour of Kubernetes you run (k3s, full k8s, or something else). Edge cases on real clusters are the ones we don't see in our own testing. Where to report: start right here in this thread. It keeps everything visible to the community and lets others on the same setup jump in. If something turns out to be a reproducible bug, we'll move it to a GitHub issue on the repo so the team can track it to a fix. Release notes and migration guide: https://github.com/vatesfr/xenorchestra-csi-driver/releases/tag/v0.4.0
Log in to post
Load new posts
  • K

    Workload Balancing

    8
    0 Votes
    8 Posts
    2k Views
    K
    So is there anyone who would be so kind to tell me whether it is worth it trying XOA instead of XOCE regarding workload balancing? Anyone who knows if there are differences?
  • K

    XO logs have repeating [load_balancer]Execute plans statement. Is this a problem?

    2
    0 Votes
    2 Posts
    448 Views
    DanpD
    I think this is normal behavior when you have the Load Balancer plugin loaded. If you don't intend to use it, then unload it.
  • akurzawaA

    xoa automated tasks [workflow feature request]

    7
    0 Votes
    7 Posts
    1k Views
    pdoniasP
    Hi @akurzawa, this would be quite a big feature, please open an issue if you have something precise in mind (a list of possible actions, what could trigger a workflow, ideally some use cases that couldn't be done without it, etc.). Also, a lot can probably already be done with XO's Web Hooks, xo-cli and a third party workflow tool in between.
  • G

    VM migration between hosts fails

    3
    0 Votes
    3 Posts
    760 Views
    G
    thank you, that did it. i got the container plugin installed, shows the containers in the VM fine in XO, testing migration of that VM now
  • G

    XoError: no such host & Firefox crashing at Logs

    2
    0 Votes
    2 Posts
    483 Views
    G
    Tested with Chrome now, on chrome it works. So it seems only a firefox problem. I switched off the extensions ( https everywhere, ublock origin and privacy badger ) but still crashes. Had htop running on my client while crashing, no unusual increase in RAM usage while going to crash. Rebooted XO VM, now it is ok again with firefox. so for me the issue is closed, if somebody is bored and wants to look into some logs for bug hunting i am glad to provide them. i also restarted the toolstack on one of the pool members ( not master ) and the "no such host" error is gone.
  • J

    How does Xen Orchestra work.

    12
    0 Votes
    12 Posts
    4k Views
    olivierlambertO
    xe CLI. Type xe --help.
  • S

    http authentication

    5
    0 Votes
    5 Posts
    1k Views
    julien-fJ
    @sborrill I have a work-in-progress branch with a plugin for this: https://github.com/vatesfr/xen-orchestra/pull/4701 To test, you will need to checkout this branch, add a symlink to the packages/xo-server-auth-http plugin into the directory xo-server/node_modules and then to configure and unable the plugin from XO. This will make basic authentication available with the path /signin/basic, note that you can make it the default authentication by overriding authentication.defaultSignInPage in your configuration file. julien-f opened this pull request in vatesfr/xen-orchestra open WiP: feat(xo-server): support HTTP basic auth #4701
  • bpbB

    Command failed: npm uninstall -g --silent xoa-updater

    3
    0 Votes
    3 Posts
    686 Views
    bpbB
    Will do. I've got an installation of it in two locations and neither are behind a proxy. In a moment of early-onset senility/dementia I confused npm with dnf - somehow! So there's obviously a chance I'm doing something incorrectly.
  • A

    Xen Orchestra CE not show home section in web interface

    18
    1
    0 Votes
    18 Posts
    3k Views
    DanpD
    @AgentZoy Sorry, but I don't understand your current issue. Please restate.
  • B

    [SOLVED] XO From source restore backup fails with VDI_IO_ERROR

    Solved
    16
    0 Votes
    16 Posts
    5k Views
    olivierlambertO
    This is not related to the original, feel free to create a new one regarding this issue. You can't "manually" move a VM, there's always a client to do that (XO, xe, XCP-ng Center etc.). So you need to understand why it's failing first.
  • H

    XOA on Xenserver 6.5

    2
    0 Votes
    2 Posts
    442 Views
    olivierlambertO
    It should work on XS 6.5, yes. Feel free to create a ticket if you need assistance
  • C

    Little bug or better error handling?

    1
    0 Votes
    1 Posts
    487 Views
    No one has replied
  • D

    XO from source & Netdata

    Solved
    3
    0 Votes
    3 Posts
    2k Views
    D
    @Biggen Ahh gotcha. I’ll check that out
  • D

    Backups to SMB remote failing

    19
    1
    0 Votes
    19 Posts
    6k Views
    julien-fJ
    @Danp The implementation would be very different
  • akurzawaA

    xoa - repair iso SR after host restart

    2
    1
    0 Votes
    2 Posts
    397 Views
    olivierlambertO
    Repair is just replug the pbd. Of course you can do that with XO
  • D

    XO Delta Backup failure

    Solved
    4
    0 Votes
    4 Posts
    820 Views
    olivierlambertO
    Okay thanks for the feedback
  • C

    Problem with restore through XenOrchestra

    Solved
    5
    0 Votes
    5 Posts
    1k Views
    A
    But now release xo-server 5.53.0 backup export concurrency >2 didn't apply. Setting concurrency to 4 or 6. but only 2 tasks works at the same time. Reverted to release xo-server 5.52.1 then 4 and 6 concurrency tasks are shown as expected.
  • bill.gertzB

    XOA won't start HTTPS listen on configured port

    29
    0 Votes
    29 Posts
    13k Views
    julien-fJ
    @bill-gertz It depends of how you install it, but it look ok. In our appliances we install and run xo-server as a global service, and there is only /etc/xo-server/config.toml which is used for user customization (you could remove it and it would still work).
  • akurzawaA

    can we run simple bash sript in cron in xoa?

    5
    0 Votes
    5 Posts
    1k Views
    akurzawaA
    I can put the script everywhere - but I want to avoid non standard config. In case of failure of {system} I'm reinstalling it, and restoring config from file. I don't need to remember that I've put some fancy staff somewhere on the lan.
  • D

    This topic is deleted!

    2
    1
    0 Votes
    2 Posts
    31 Views