Subcategories

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

    477 Topics
    4k Posts
    B
    Hello all, I was looking at the code for the perf-alert plugin because I wasn't sure if it followed the same workflow as the backup-reports plugin where it sends emails and delivers to multiple transports. As it turns out, it only sends emails that are configured in the plugin, but I would love it to use the other transports available if they're set up like transport-slack, etc. As a user who is interested in expanding my monitoring footprint in my infrastructure, I think the perf-alert plugin should follow the same reporting/alerting mechanisms as the backup-report plugin and notify to transport-slack along with others. In my case I use Discord, but Mattermost, etc. users would all benefit based on the format the transport-slack plugin already provides. Reading the code it seems like the Plugin system would benefit from having a singular "alerting" layer that you send messages to within each plugin and then the transport plugins just relay the messages to their appropriate APIs (this would likely require rethinking the plugin archictecture however, so not an actionable item), similar to a job queue. I would probably be able to file a PR to add this functionality, but I'm not confident enough to give it a go at the moment as I'd like to understand the implications of adding said code first. For now, I'll leave this as a feature request as I think most people would find this a welcome addition.
  • 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...

    517 Topics
    5k Posts
    P
    @pierrebrunet said: Another thing to check is the exact time between your XO and your host. I installed the host with NTP from "static" DHCP (OK according to https://docs.xcp-ng.org/installation/requirements/) not made any manual changes/configs After I did a RTC adjustment in BIOS 3 days ago, the time now is ~1s ahead This is the output from timedatectl [22:04 x2 ~]# timedatectl status Local time: tor 2026-07-16 22:06:45 CEST Universal time: tor 2026-07-16 20:06:45 UTC RTC time: tor 2026-07-16 20:06:42 Time zone: Europe/Stockholm (CEST, +0200) NTP enabled: yes NTP synchronized: no RTC in local TZ: no DST active: yes Last DST change: DST began at sön 2026-03-29 01:59:59 CET sön 2026-03-29 03:00:00 CEST Next DST change: DST ends (the clock jumps one hour backwards) at sön 2026-10-25 02:59:59 CEST sön 2026-10-25 02:00:00 CET NTP synchronized: no I thought that the time would be adjusted automatically at reboot The first NTP sync should allow a bigger step than when it's already synced. @pierrebrunet said: do you make these backup regularly? They run once a day @ 03:04 before the normal backup that starts @ 03:10 and they have all run OK since July 8, the failed one reported 8 days ago ( post ~85 ) Maybe you should resync your clock NTP is enabled but not synced, I don't know the correct way to sync it In xsconsole/ I tried Use DHCP NTP Servers It changed the RTC clock to the same as UTC time but time was still 1s ahead and NTP not synced. I rebooted the host and I got this: [23:36 x2 ~]# timedatectl status Local time: tor 2026-07-16 23:37:17 CEST Universal time: tor 2026-07-16 21:37:17 UTC RTC time: tor 2026-07-16 21:37:16 Time zone: Europe/Stockholm (CEST, +0200) NTP enabled: yes NTP synchronized: no RTC in local TZ: no DST active: yes Last DST change: DST began at sön 2026-03-29 01:59:59 CET sön 2026-03-29 03:00:00 CEST Next DST change: DST ends (the clock jumps one hour backwards) at sön 2026-10-25 02:59:59 CEST sön 2026-10-25 02:00:00 CET NTP still not synced, Local time 2s ahead, RTC 1s ahead, I don't know, If not someone can show me the proper way to manually resync, maybe I should try to reinstall the host
  • 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
  • Xen Orchestra Node 24 compatibility

    9
    0 Votes
    9 Posts
    2k Views
    olivierlambertO
    Nice find! Is there's any plan for Debian to backport that patch?
  • Yarn gpg key expired/ xo bfs on debian 12

    Moved
    1
    0 Votes
    1 Posts
    639 Views
    No one has replied
  • Kubernetes Recipe VM failed to start - Raise Network Interfaces

    12
    1
    0 Votes
    12 Posts
    3k Views
    CyrilleC
    Hi @jacob.becker, We identified the issue last weekend, and we're currently working on a solution. We plan to include a fix in the next XO release.
  • XO 6 backup job missing VM info on failure.

    1
    2
    0 Votes
    1 Posts
    185 Views
    No one has replied
  • Orphan VDIs in XO show health problem

    15
    4
    0 Votes
    15 Posts
    2k Views
    W
    @Pilow Does disk show up after you do the snapshot? If it is able to do the snapshot there is a high chance it can boot up. So try booting up (and check for disk) and shut it down and do the snapshot at that time if the disk show up. It helps to boot up on the old v5 commit and check from that side too if you have both copy before the commit update. Yep I can confirm that snapshot doesn't always work. But using the older v5 that used to work before the update does get it showing up on the newer v5 commit if I go through whole snapshot, revert, etc. one of those case work.
  • 0 Votes
    7 Posts
    2k Views
    olivierlambertO
    We are not energy efficiency experts, while EasyVirt people are. I think they already have some stuff and it might be just a matter of plumbing.
  • ISO won't show since XO6 Default

    5
    2
    0 Votes
    5 Posts
    673 Views
    MathieuRAM
    Hi @Kptainflintt, I don't think this is related to XO6, but probably to this PR: https://github.com/vatesfr/xen-orchestra/pull/9231 VDIs with snapshot_of: <something> are now recognized as snapshots
  • XO 6 Official Release (for community)

    xo6 community life-cycle feedback
    4
    0 Votes
    4 Posts
    901 Views
    D
    I provided some feedback.
  • Can't designate new master on XO source pool

    8
    0 Votes
    8 Posts
    990 Views
    V
    Tracked it down to it thinking there was a pool version mismatch... then when I tried to transition to a new master it would fail with Xmlrpc_client.Connection_reset ... digging deeper it was complaining that it couldn't restore from the wrong version. Lots of head banging later... I setup a backup for the pool metadata and forced the backup immediately. TADA... I can now change the master with no issues at all.
  • XOA gets disconnected very often

    6
    0 Votes
    6 Posts
    931 Views
    olivierlambertO
    Yes, there's a possible weird combo between XOSTOR and HA in some situations. Let me add @ronan-a or @dthenot in the loop. It's likely that XOA disconnection is just a visible symptom of something else. It's not ultra trivial to reproduce though.
  • Staring up a shutdown VM in XO 6

    4
    0 Votes
    4 Posts
    730 Views
    W
    @olivierlambert Thank you. I thought maybe I was losing my mind/eye sight, especially after reading that google search indicating there was a start button in 6.
  • 2FA doesn't load graphics properly after XO6 went default (XO from source)

    Solved
    5
    1
    0 Votes
    5 Posts
    623 Views
    olivierlambertO
    Excellent news
  • Failed unmounting remotes at XO/XOA shutdown

    4
    1
    0 Votes
    4 Posts
    813 Views
    P
    No idea if anyone have "fixed" anything No, the XO commit 5fcb6 hang for ~3 min at reboot today. edit: I disabled the sceduled reboot yesterday.
  • XO5 breaks after defaulting to XO6 (from source)

    53
    1
    0 Votes
    53 Posts
    9k Views
    M
    @MathieuRA I disabled Traefik and reverted to my old XO config (port 443, ssl encryption, http to https redirection), rebuild the docker container using your branch and tested: it is working fine on my end now Thank you very much! I did not expect this to get fixed so fast!
  • Plugins in XO6?

    6
    0 Votes
    6 Posts
    611 Views
    olivierlambertO
    It won't disappear tomorrow, but I'd like to phase it out sooner than later (before 2027? who knows)
  • Xen Orchestra from source ignores config.toml from /etc/xo-server/

    2
    0 Votes
    2 Posts
    388 Views
    A
    Ok I've figured out root cause. My config override has only one option: ignoreVmSnapshotResources = true And I had to change it with adding [selfService] on a line below Also I found out that override config for XO5 interface needs to have absolute paths to xo-web and @XenOrchestra in it. With relative paths it didn't work.
  • LUKS Secured VM via Cloud Config

    1
    0 Votes
    1 Posts
    203 Views
    No one has replied
  • Retention for log files and audit logs

    6
    0 Votes
    6 Posts
    1k Views
    eveaneE
    I would like to suggest to configure a remote syslog server. it centralizes all the log s and give you full control over the retention. It would also avoid situation where a disk full would impact your logging as well XCP-ng or XOA host operations. For your XCP-NG host go to you POOl, select Advanced tab and configure the Remote syslog host section to point to your syslog server. For XOA, you can follow the instruction here : https://docs.xen-orchestra.com/backups#send-xo-logs-to-an-external-syslog-server
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    4 Views
    No one has replied
  • HOST_NOT_ENOUGH_FREE_MEMORY

    4
    0 Votes
    4 Posts
    560 Views
    P
    @ideal perhaps you could use advantage of dynamic memory https://docs.xcp-ng.org/vms/#dynamic-memory to oversubscribe memory and have all 4 VMs up at once... or reduce the allocated memory of your VMs, you seem to have a pretty big VM in terms of memory in comparison to the 2 others on your screenshot