Subcategories

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

    476 Topics
    4k Posts
    poddingueP
    I had a look at your screenshots. The Topology dropdown is greyed out with a tooltip saying Requires admin permissions, so this looks deliberate rather than broken: the field seems gated on being a full XO admin, not on being admin of your own resource set. I couldn't find an existing report asking for it to respect resource-set admin instead, so feedback.vates.tech is probably the right place to raise it. It would carry more weight coming from you, with those screenshots, than from me. I don't know whether the ACL rework changes any of this, so I wouldn't count on it until someone who works on it says so. Might be worth a mention to @Team-XO-Backend, since where that permission gate lives is really their call.
  • 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
    J
    Any solution?
  • 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
  • XOA Error when installing

    Solved
    107
    1
    0 Votes
    107 Posts
    57k Views
    G
    I did the manual installation via the XVA. It worked for me.
  • Nag-Screens

    30
    0 Votes
    30 Posts
    12k Views
    olivierlambertO
    Thanks for the suggestion, but don't you think we never thought to that before? I start to think you are considering us as 2 people in a garage. We are crunching numbers on a regular basis, and it never computes with those models. Proxmox is here since a long time, with a strong and "large" use base allowing to use this model. This is not the case for us now. So on short term, this is not doable. But be assured we are continuously working on testing various models to see what's the best fit.
  • XOA Backup/Restore Screen - enhancement suggestions

    2
    2 Votes
    2 Posts
    757 Views
    olivierlambertO
    You should use GitHub and create an issue. This will be taken into account for XO 6 web UI
  • Question about live migration and a few others...

    3
    0 Votes
    3 Posts
    2k Views
    B
    @rkelley You nailed it for item 2. Was driving me crazy! Ok, that does make sense for item #1 and was kinda what I was thinking. But it does lead one to believe you can't live migrate anything with a single host even if you have shared/remote storage available unless you poke around and experiment with different buttons like i did.
  • Get an 'Disconnected' Information under the 'XOA' Icon

    3
    1
    0 Votes
    3 Posts
    981 Views
    DanpD
    That's "normal" if you are running XO (from the sources) and not XOA (the pre-built appliance)
  • Install Plugins XO from sources

    4
    0 Votes
    4 Posts
    2k Views
    F
    @Danp Thanks for pointing me in the right direction. I was following an older howto where --global was not specified. That was my first problem - now fixed! Second problem was that I had installed into the root directory of Centos7 so the paths for creating the links were different. Once I had found the correct paths and created the links all was good. Thanks again. Frank.
  • Tasks Page: Hard to read / Hard to use

    3
    0 Votes
    3 Posts
    1k Views
    D
    @fx991 the SR scans can and have been helpful in detecting storage issues for me. Sometimes when my ISO library goes offline but XCP-ng has not detected the failure and still shows it as connected I usually notice it from the long running SR scans that get stuck. The "Connection to VM console..." task is when you have a console window open to a VM or Host...hence the reason why you can't cancel/end it...if you want to get rid of it then close all open console windows
  • Missing SMLog file on XCP-NG 8.0 /var/log directory

    1
    2
    0 Votes
    1 Posts
    660 Views
    No one has replied
  • multiple network cards in VM

    12
    1
    0 Votes
    12 Posts
    3k Views
    pdoniasP
    I already opened one: https://github.com/vatesfr/xen-orchestra/issues/4882. pdonias created this issue in vatesfr/xen-orchestra closed [VM] Network: show IP addresses in front of their VIFs #4882
  • Jobs not running error: no value for `user_ip`

    7
    0 Votes
    7 Posts
    2k Views
    C
    I can already confirm that I could trigger 2 Jobs manually in XO and it run successfully. Thanks! The scheduled ones I will see tomorrow and report if it would fail, but it is not expected.
  • Change boot order

    Solved
    3
    0 Votes
    3 Posts
    3k Views
    ForzaF
    Thanks! Found it.
  • host.call_plugin Running

    6
    0 Votes
    6 Posts
    1k Views
    olivierlambertO
    It could, I don't know what XCP-ng Center can do in details. But again, this is NOT a problem. I said it 3 times, why do you think it's still related to your coalesce problems?
  • XOA VM creation with static memory

    2
    0 Votes
    2 Posts
    1k Views
    olivierlambertO
    It's the default parameter of your template. XCP-ng Center is probably forcing fixed memory, XO is just doing template recommendation. You can change values at creation in "Advanced" section.
  • first attemp with XOCE

    12
    0 Votes
    12 Posts
    3k Views
    olivierlambertO
    Exactly like how it's displayed in the documentation.
  • Backup Interupted

    3
    0 Votes
    3 Posts
    723 Views
    olivierlambertO
    Try to switch to NFS and report if you have the same issue.
  • Building Xen Orchestra from Source: FreeBSD xo-web:build _ Error: null

    Solved
    3
    0 Votes
    3 Posts
    920 Views
    P
    @Danp As soon as I read that, I thought "I think I've been down this road before." Sure enough. I gave it 2G of RAM and it wouldn't build. I gave it 4G of RAM and I watched using systat and that final step went to about 52% of RAM usage. It has completed. I routinely run Xen Orchestra on a 1G VM because it's rarely used and it runs fine that way. But building it clearly takes a lot more RAM. I'll update my internal notes. It might be worth it to update the building from source docs to mention having enough RAM. Thanks for hitting the nail on the head with that advice!
  • Backup jobs run twice after upgrade to 5.76.2

    35
    0 Votes
    35 Posts
    12k Views
    olivierlambertO
    XOA got its own numbering, unrelated to xo-server or xo-web: it'a all a matter of a coherent "whole", including dependencies etc. Thing we can't provide when built on sources. Please test and report You can switch to latest too, doesn't matter.
  • XO from source: webui lockout recover-account not working

    8
    0 Votes
    8 Posts
    2k Views
    G
    Hi Julien, i already did that. localadmin is the user i also use for the xo-server. did not elaborate that further on a test system.
  • HUB Templates

    Solved
    29
    0 Votes
    29 Posts
    20k Views
    luiscamaralL
    @luiscamaral Let me reply to myself. If you update xoa it will show user and password as in bellow description: Template for Alpine Linux 3.10, with 'root' username and 'xohub' password, DHCP enabled
  • XOce "Still Loading"

    3
    1
    0 Votes
    3 Posts
    1k Views
    mpyuskoM
    @olivierlambert Yes, direct access is fine.