Subcategories

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

    475 Topics
    4k Posts
    olivierlambertO
    Great! I think this is really the best possible approach to make it clean
  • ACLs, Self-service, Cloud-init, Load balancing...

    104 Topics
    863 Posts
    laszlobortelL
    @florent Thanks for your reply! We have started to migrate thousands of VMs, so disk transfer speed is important for us.. We will also do our detailed tests soon with different threads setting and publish it here. I think threads=1 is a good and logical default, but not efficient. Others might complain if you set it to a higher value. Configuration option would be a real good solution.
  • All XO backup features: full and incremental, replication, mirrors...

    514 Topics
    5k Posts
    poddingueP
    Sorry it's back. Just to line things up for whoever picks this up: the original full-backup Body Timeout was tracked in https://github.com/xapi-project/xen-api/pull/6786 and shipped with the March 2026 8.3 updates, so what you're seeing on metadata backups might be a cousin rather than the same bug. From Olivier's earlier note the error just means XO got nothing from the pool master for 5 minutes mid-transfer, so the useful question is what the master was doing during that silence. The fact that a toolstack restart clears it for a while and then it returns is probably itself a clue. Could you grab the complete logs from one failed metadata run (the ask pierrebrunet made earlier), plus a rough note of whether it lines up with the master being busy or briefly unreachable? I'm out of my depth on the internals, but that's the piece the team will want. last-genius opened this pull request in xapi-project/xen-api closed stream_vdi: Only process allocated clusters for VHD and QCOW on XVA export #6786
  • 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
  • Unable to mount NFS share in XOA

    4
    3
    0 Votes
    4 Posts
    5k Views
    H
    @olivierlambert could this error be more verbose? I think this error should say: Cannot write file .keeper_uygbivt5lv on remote <whatever the remote name/address> NFS is mounted but XOA cannot write to mounted dir. This happens in NFSv4 as default when sec=sys on NFS server (that is the default).
  • OVA import failing

    48
    0 Votes
    48 Posts
    24k Views
    G
    @olivierlambert @olivierlambert said in OVA import failing: Keep in mind the file has to flow from your browser toward your XOA, then to your XOA to your host, which might use another network share itself. If your XOA could mount the place where you have your OVA directly, you could use upload-ova utility (see https://github.com/vatesfr/xen-orchestra/tree/master/%40xen-orchestra/upload-ova#usage ) to send them directly. Going to look into that, thank you.
  • 0 Votes
    6 Posts
    8k Views
    julien-fJ
    Yep, that's the best solution Have a nice day.
  • 0 Votes
    7 Posts
    1k Views
    olivierlambertO
    @julien-f is aware of the problem, he's working on getting proxy fully independent on the network connection. Can you check why the connection between XOA and your proxy is interrupted? Is there any reason you have in mind?
  • Can't deploy XOA

    Solved
    10
    0 Votes
    10 Posts
    4k Views
    olivierlambertO
    I said that for both statements: It's not Xen fault if it doesn't work on top of KVM, but Xen accessing some virt features that aren't correctly exposed by KVM. I'm not blaming them, nested virt is a mess to properly code and test. Consider this as experimental everywhere. I missed the "for me". But it's also vague, I don't know your constraints/what do you want. Also, I think I heard that some users made it work with Virtualbox, but it might also depends on your hardware. As I said, nested virt is a mess, and sometimes, some hardware works better than others (or even some VBox versions).
  • Old snapshot listing

    6
    0 Votes
    6 Posts
    1k Views
    olivierlambertO
    Can you create a GitHub issue gathering our elements here to get a simple but complete "specification"? https://github.com/vatesfr/xen-orchestra/issues/new
  • Backup Continuous Replication hängt!

    Solved
    47
    1
    0 Votes
    47 Posts
    23k Views
    olivierlambertO
    We don't have any other report of this issue elsewhere. Double check you are on the completely latest XO version, and alternatively, try with XOA on latest channel.
  • XOA hangs when trying to show SR in webbrowser..

    11
    0 Votes
    11 Posts
    3k Views
    olivierlambertO
    There's an small update you should see now in your XOA. Install it, and you'll be able to bind the license to this new XOA
  • Enhancement: Show background coalesce and cleanup activities

    18
    0 Votes
    18 Posts
    3k Views
    olivierlambertO
    Yep, there's basically nothing. It's more SMAPI related than XAPI in the end.
  • Phantom Vif in the Stats tab

    3
    2
    0 Votes
    3 Posts
    894 Views
    A
    @olivierlambert Thanks for the response. It does make sense since I made some changes to the network a few days back.
  • Wrong timestamp on snaphot

    Solved
    15
    0 Votes
    15 Posts
    2k Views
    olivierlambertO
    @akurzawa said in Wrong timestamp on snaphot: Hi It'a an important to know exact time of vm and snapshot - eg when recovering for an example a Active Directory or sql database. When doing so, someone can believe that restores the data from {the time visible in name}, because can be unaware of possible offset of zulu time. You already have the exact time If you aren't aware of an ISO standard format date, it's another story. But this is really standard and universal way. I suppose you meant "misinterpreting the snapshot time" which has NOT the same meaning than "incorrect time".
  • 2 Votes
    11 Posts
    4k Views
    akurzawaA
    https://github.com/vatesfr/xen-orchestra/issues/4472 akurzawa created this issue in vatesfr/xen-orchestra closed encrypt xcp-ng root user password in config file #4472
  • Continuous Replication Manual initial seed

    Solved
    7
    0 Votes
    7 Posts
    1k Views
    julien-fJ
    FYI, an extremely basic command line to encode passwords: > node -e 'process.stdin.on("data", _ => {console.log(encodeURIComponent(_.toString().trim())); process.exit()}); process.stdout.write("Password: ")' Password: foo@bar foo%40bar
  • Remotes - NFS - Disk (Used / Total) blank after update

    8
    0 Votes
    8 Posts
    2k Views
    C
    @badrAZ w00t! Thank you! I look forward to the update. BTW, I went ahead and threw my updated XO CE into "production" here at home where it runs 10 VMs. So far no other issues seen by me. XCP-NG/XO.
  • NFS Backups and Xen Orchestra

    9
    0 Votes
    9 Posts
    5k Views
    olivierlambertO
    Doc now updated with 2 pictures here: https://xen-orchestra.com/docs/proxy.html#architecture
  • 0 Votes
    29 Posts
    7k Views
    olivierlambertO
    Have you read https://xen-orchestra.com/docs/delta_backups.html ? Use normal backup it will work. Or stick with delta and advanced option, a full every 1 backup.
  • Xen Orchestra editions

    Solved
    6
    0 Votes
    6 Posts
    4k Views
    olivierlambertO
    You are welcome
  • Delta backup always full for running VMs

    14
    0 Votes
    14 Posts
    3k Views
    J
    @julien-f Thank you and @olivierlambert for the quick and outstanding support!
  • sexilog ova import... causes xoa to drop import task

    10
    0 Votes
    10 Posts
    2k Views
    nraynaudN
    you can follow the fix is in this pull request: https://github.com/vatesfr/xen-orchestra/pull/5085 nraynaud opened this pull request in vatesfr/xen-orchestra closed feat(import/ova) allow import of gzipped vmdk disks. #5085
  • Unable to register XOA

    Solved
    7
    0 Votes
    7 Posts
    5k Views
    olivierlambertO
    Did it for you