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
  • X

    Xen Orchestra reporting high disk usage (thin provisioned VDI)

    4
    2
    0 Votes
    4 Posts
    1k Views
    X
    @olivierlambert I have assigned 1.9TiB to a VM and XOA is saying the VM is using 1.07TiB, but df -h on the VM is saying that I'm using 418GB. So according to XOA I should have about 800GiB left but according to my VM I should have 1.4TB left, there's a pretty big 600GB difference here.
  • A

    Enable VGA Graphics in Xcp-ng Center for a particular VM.

    1
    0 Votes
    1 Posts
    520 Views
    No one has replied
  • S

    LDAP extract user from specified field?

    4
    0 Votes
    4 Posts
    856 Views
    D
    I actually like the current implementation. I am currently using this setup to allow an admin user to have 2 accounts managed by one authentication back-end. One account is a typical self-service user to consume resources according to ACL/Self-service rule sets The other account is used to manage Admin features like backups and XO settings (environment with multiple admins who also consume resources from a shared pool with other departments/teams) I use separate accounts so when admin users create VMs it can go to the appropriate self-service container. I hope any fixes to address the above concern doesn't completely remote this capability or at least adds another method of achieving this.
  • A

    uninstall xen orchestra in ubuntu 18.04.

    1
    0 Votes
    1 Posts
    424 Views
    No one has replied
  • C

    Monitor XOA Disk Space

    Solved
    17
    0 Votes
    17 Posts
    4k Views
    C
    easy as that Thanks for you help.
  • S

    building from source - yarn fetch error

    Solved
    6
    0 Votes
    6 Posts
    1k Views
    S
    guys, it is solved, but thats something i will file again under technological harrassment. it was a DNS Problem. the dns-servers at my hosting provider woudnt resolve properly, only when I forced googles DNS servers onto it did it work. thanks for the push
  • A

    Kubernetes cluster recipe?

    8
    0 Votes
    8 Posts
    2k Views
    olivierlambertO
    Indeed, it's using our cloudinit ready templates hosted on xen-orchestra.com, so you need a XOA.
  • J

    Problem creating Quiesced snapshots

    4
    0 Votes
    4 Posts
    919 Views
    olivierlambertO
    VSS agent will disappear, so yes, quiesce snapshots will disappear too. But fear not, we have plans to introduce a new feature, called "RAM backups".
  • V

    daily Continuous Replication backup in XO

    37
    2
    0 Votes
    37 Posts
    12k Views
    M
    Hi I had exatly the same problem when I upgrade one of my four server from xenserver 7.1 to xcp-ng 8.0, one backup failed with error: job already running and the other finish normaly later! I upgrade Xo from 5.51 to 5.54 and it's Ok for this problem BUT I have a new problem, the cold backup to NFS and the Continuous replication to a Xcp-ng 8 server are REALLY slow !! One exemple: Start time: Thursday, December 19th 2019, 7:20:00 am End time: Thursday, December 19th 2019, 7:58:54 am Duration: 39 minutes Snapshot Start time: Thursday, December 19th 2019, 7:20:00 am End time: Thursday, December 19th 2019, 7:20:05 am Duration: a few seconds SRs Local storage (a70a93c4-4951-9bec-54ab-d45bb5039b44) ✔ Start time: Thursday, December 19th 2019, 7:20:05 am End time: Thursday, December 19th 2019, 7:58:52 am Duration: 39 minutes transfer ✔ Start time: Thursday, December 19th 2019, 7:20:06 am End time: Thursday, December 19th 2019, 7:58:50 am Duration: 39 minutes Size: 1.34 GiB Speed: 605.55 KiB/s I try to upgrade debian OS, upgrade VM (4cpus 3Go ram) but same problem for the moment Thanks in advance Edit: I do a manual test by copy an iso of 2G locally on the virtual machine Xen orchestra, to the same connected NFS for backup, and the performance is normal, 10 seconds for 2Go, it seems to be a problem with Xen orchestra system backup?
  • E

    Cold Backup in XO

    5
    0 Votes
    5 Posts
    1k Views
    olivierlambertO
    It's supported in XOA since 5.40 and all more recent releases. Just tick the checkbox and that's it
  • B

    Build from source question

    8
    0 Votes
    8 Posts
    2k Views
    B
    @ruskofd said in Build from source question: Why not using a systemd unit instead of forever ? This is exactly what I did. Created a service file in etc/systemd/system that points back to the xo-server bin file.
  • T

    [CLOUDINIT] network config is being saved in the config drive but its not being applied.

    6
    0 Votes
    6 Posts
    3k Views
    fohdeeshaF
    I'm not sure, I have not used cloud-init in centos. I'd imagine it's similar, you need to find the cloud-init config file in your centos template install, and edit it to prefer the nocloud datasource
  • ForzaF

    XOA Updater not working?

    4
    0 Votes
    4 Posts
    865 Views
    olivierlambertO
    Ping @pdonias
  • J

    Can not restore files from delta backup

    11
    1
    0 Votes
    11 Posts
    2k Views
    olivierlambertO
    Restoring the whole VM is OK, because XO doesn't "look" inside the disk.
  • F

    Cloud like services

    6
    0 Votes
    6 Posts
    1k Views
    olivierlambertO
    I'm pretty fine that anyone build a WHMCS connector to XO API
  • A

    Problems getting containers to show in CoreOS on XO.

    5
    0 Votes
    5 Posts
    1k Views
    A
    Thank you. Yes, I have installed the xscontainer though it does nothing.
  • G

    XO CE Backup remote: no right to make /run/xo-server when xo not running as root

    1
    2 Votes
    1 Posts
    976 Views
    No one has replied
  • P

    Moving VMs from one Pool to another

    6
    2
    1 Votes
    6 Posts
    4k Views
    P
    Next thing I tried was Exporting the affected VM, delete it and import it again. This fails because after deleting the VM both VDIs / VHDs are still there. Also I can not delete them. The error says: [image: 1576141485072-f6ff6ad4-8a59-4424-9bb5-ff498f87989f-image.png]
  • Z

    XOA and SAML (keycloak)

    5
    0 Votes
    5 Posts
    2k Views
    julien-fJ
    I'm not overly familiar with SAML, but our plugin is based on this: https://github.com/bergie/passport-saml Let us know if you find something relevant.
  • J

    Open Console of VM in new dedicated Window

    11
    0 Votes
    11 Posts
    6k Views
    DanpD
    @Jarvar You install them in each VM. See here for more details.