Subcategories

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

    473 Topics
    4k Posts
    olivierlambertO
    Hi, IP conflict?
  • 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...

    511 Topics
    5k Posts
    itservicesI
    Evening @pierrebrunet My bad. I am now on commit b440f and the issue persist. I have written you a message with the link to the file. Regards, Marc
  • 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
  • VM Backup failure

    Solved
    9
    1
    0 Votes
    9 Posts
    2k Views
    olivierlambertO
    Don't worry: if there's stuff to correct in the PR, the review process is made for that
  • VM migration stuck at 100%

    3
    0 Votes
    3 Posts
    3k Views
    J
    I ended up restarting the toolstack, which caused all of the migrating VMs to be in an error state, as they were halted but the system thought they should be running. I couldn't perform any actions on them. VM_BAD_POWER_STATE(OpaqueRef:f1f14751-cbc8-4a86-b98f-9e980b2b0d00, Running, Halted) After restarting the toolstack on all the hosts in the pool, they finally showed up as powered off and I was able to get them back up and could migrate them. Is there anywhere I can look to see why the migration got right to the doorstep and stopped?
  • Feature request: Cloud-config common parameters

    2
    0 Votes
    2 Posts
    519 Views
    olivierlambertO
    Why not. Double check there's not already an opened issue for this in XO bugtracker, otherwise, create it there
  • Increase simultaneous snapshot download from 2

    7
    0 Votes
    7 Posts
    2k Views
    olivierlambertO
    Yes, they are
  • notifications

    7
    0 Votes
    7 Posts
    1k Views
    pdoniasP
    @hoberion This should be fixed since XO 5.48 (xo-web 5.61.1) @hoberion said in notifications: @pdonias said in notifications: Hi @hoberion, what version are you using? xo-server 5.60.0 xo-server 5.60.0 was shipped with XO 5.47. Could you update your XOA and confirm that it fixes it? It should happen once more after the update and then it shouldn't happen any more.
  • Cannot figure out how to past INTO VM

    clipboard
    7
    0 Votes
    7 Posts
    5k Views
    DanpD
    https://xcp-ng.org/forum/topic/1846/guest-console-copy-paste
  • Which Template for Fedora Server & Workstation?

    5
    0 Votes
    5 Posts
    1k Views
    G
    See Citrix documentation, here and here. or be inspired, use command line or create your own script, like this.
  • Import CD ISO image via XOA?

    2
    0 Votes
    2 Posts
    1k Views
    olivierlambertO
    No, because SR ISO is read only in XCP-ng (so we can't ask XCP-ng to import a VDI there) sadly. There's 2 options: Modify XAPI code to allow VDI upload (and not mount ISO SR in read only). Then in Xen Orchestra, it would be trivial. Modify Xen Orchestra to mount the SR itself to upload it there. It's a bit complicated but doable.
  • ssh management

    Solved
    3
    0 Votes
    3 Posts
    2k Views
    kirovtomeK
    @olivierlambert Thanks!
  • xoa slow export speed - peak 30MB/s

    10
    1
    0 Votes
    10 Posts
    2k Views
    olivierlambertO
    Personally, I wouldn't touch anything regarding XVA generation, it's deep into XAPI code. Rely on delta backup in general, it's better.
  • Issues with XO

    3
    0 Votes
    3 Posts
    572 Views
    M
    thank you @olivierlambert !
  • Adding NFS as remote

    nfs
    4
    0 Votes
    4 Posts
    6k Views
    nikadeN
    @jedimarcus said in Adding NFS as remote: https://github.com/xcp-ng/xcp/wiki/FreeNAS-as-Storage-Repository-(SR) Did you: Check the All dirs option This is probably it, pretty common mistake.
  • Backup handler.outputStream is not a function

    Solved
    4
    0 Votes
    4 Posts
    559 Views
    M
    As confirmation, it's all OK after today re-rebuild. xo-web 5.67.0 bumped from xo-web 5.64.0
  • XO tasks can't be cleared

    4
    0 Votes
    4 Posts
    3k Views
    olivierlambertO
    Disconnect and reconnect the server in Settings/server of XO.
  • I am trying to install XOCE from a script

    3
    0 Votes
    3 Posts
    916 Views
    olivierlambertO
    @jharl said in I am trying to install XOCE from a script: so now I want a 20% discount on the next time I compile my free software Haha nice joke Also, just following the official doc might be easier sometimes, you actually know what you are doing
  • OpenStack.

    4
    0 Votes
    4 Posts
    689 Views
    olivierlambertO
    It depends on what you need, only you is able to answer that.
  • XO CE migrate fails for VM - "Internal Error"

    13
    0 Votes
    13 Posts
    3k Views
    olivierlambertO
    @vmpr Please create an issue on Xen Orchestra GitHub repo, this way XO dev will see it
  • XO Backups and location of XO VM

    7
    0 Votes
    7 Posts
    2k Views
    julien-fJ
    @RKENS Good question, during the replication, a new VM is created with the same settings as the original one, and this at every run. Therefore that's perfectly normal that this property reappears. I don't see how that's a problem because, as you said it yourself, the start operation is disabled by the replication job. I think it makes sense that the auto start is set like on the original VM so you can simply start the replication when necessary without having to think about enabling it.
  • Continuous Replication, are delta's automatic?

    Solved
    2
    0 Votes
    2 Posts
    535 Views
    R
    I answered my own question. For continuous replication, delta's are automatic. I was thrown by a backup job where I mistakenly selected disaster recovery instead of continuous replication and didn't realize it.
  • XO Sources - yarn build - javascript heap out of memory

    5
    0 Votes
    5 Posts
    3k Views
    H
    You do need a lot of virtual memory for build but you can get by with 2GB ram + 4 GB swap if you tell nodejs to limit it self, by setting export NODE_OPTIONS='--max-old-space-size=3072' before starting the build process