Subcategories

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

    476 Topics
    4k Posts
    A
    @pkgw Planning an RPU as a whole is a nice idea in theory, but it's inherently designed to co-exist with normal pool management operations (you should still be able to migrate VMs between hosts B and C during it, or start new ones), we are not "pre-booking" memory and other resources for groups of VMs, otherwise it can quickly make the rest of the pool hard to manage while some VM migrations could still be far away. Regarding the narrower case - I'll note this down and see if we can improve things, thank you!
  • 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
    poddingueP
    Thanks for checking. That's useful, even if it points away from where I was looking. Clocks within a second of each other means drift probably isn't your problem, and I'd guess the MST/UTC difference is just how dom0 displays it, though I'm not sure. What I keep coming back to is that your full backups fail while the delta jobs on the same hosts never do. That's the same split in https://github.com/vatesfr/xen-orchestra/issues/9181, where full backups hit BodyTimeoutError on VMs with big disks or a lot of free space and the deltas are fine. If your failing VMs look like that, your dates and the MST/UTC detail would do more good on that issue than buried in here. MajorP93 created this issue in vatesfr/xen-orchestra open Full backup fails on large VMs / VMs with lots of free disk space #9181
  • 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
  • 0 Votes
    10 Posts
    2k Views
    D
    @julien-f said in Enhancement suggestion: Filter showing VMs that don't have the agent installed: XO does not support this for halted VMs but that could be added indeed. Can you change the title of my thread to "Enhancement suggestion: Update 'ManagementAgentDetected?' to support halted VMs" ?
  • XO High Availability

    6
    0 Votes
    6 Posts
    1k Views
    DanpD
    @irtaza9 You should be able to login with the default credentials after you restart the xo-server service with systemctl restart xo-server.service.
  • Web Hook plugin

    2
    0 Votes
    2 Posts
    418 Views
    olivierlambertO
    Hi, Before enabling the plugin, you need to configure it in the Plugin view.
  • XOA on a vSphere VM

    4
    0 Votes
    4 Posts
    781 Views
    DanpD
    @yzgulec You will likely need to install the fix given in the following post for XOA to function correctly on vSphere -- https://xcp-ng.org/forum/post/50279
  • Difference between "pool", "host" and "server".

    Solved
    6
    0 Votes
    6 Posts
    3k Views
    pdoniasP
    @andrewperry Exactly
  • Lots of performance alerts after upgrading XO to commit aa490

    28
    0 Votes
    28 Posts
    10k Views
    Bastien NolletB
    @ph7 Some of the errors you encountered are intended. We don't allow values in the "Virtual Machines" field if "Exclude VMs" is disabled and "All running VMs" is enabled, because it would make the plugin configuration confusing. However you're right, there seems to be an issue when the VMs are selected and then removed. The value becomes an empty list instead of being undefined, which causes the validation to fail when we try to turn off the "Exclude VMs" option. I'm going to create a task on our side so that we can plan to resolve this problem. In the meantime you can work around the problem by deleting the monitor and recreating a new one with the same parameters.
  • How to update to the latest version of XOA?

    2
    1
    0 Votes
    2 Posts
    1k Views
    DanpD
    Hi, This is explained in this KB article -- https://help.vates.tech/kb/en-us/30/21 Regards, Dan
  • Guide : XOA OIDC authentication with Fortiauthenticator

    1
    0 Votes
    1 Posts
    598 Views
    No one has replied
  • Rolling pool update failed to migrate VMs back

    14
    0 Votes
    14 Posts
    3k Views
    N
    @BenjiReis HA is automatically disabled by the RPU when it starts, then enabled at the end. - I see the task for that in the task log. We do have about 5 VMs that do not have HA enabled, but they are very small (~4GB each) so should not make any difference regardless of which hosts they were on. Also all VMs successfully evacuate from the host for the updates, its only when VMs are migrated back after all hosts are upgraded that I see a problem. I've raised a support ticket, if anything relevant comes out of it I'll try and report back here for future readers. Thanks for the suggestions, Neal.
  • Acl setting not clear, how to

    4
    0 Votes
    4 Posts
    779 Views
    I
    @Chico008 ACLs are used to assign rights to the guest users. As you said you have an admin who can do anything. In case you want to go with acl then your guest can get no leverage by using ACL create vm You as an admin will create VMs and manage other stuff but you then have ability to give three type of rights to the guest user. admin, operator, viewer In case of VMs when you give the admin right to a user then it means that user can have ability to anything with that VM. Delete, Reboot, etc But from you query you said that you want to give a right to guest user to create/run the vms to achieve this you have to look Self Service feature which is supported in XO from sources and in Premium XOA In self service you have ability to create resource sets which are pools, storage, networks, templates etc, and assign a user or group to it.
  • 0 Votes
    16 Posts
    4k Views
    M
    @florent Sorry for the delay. I was able to make it work with the change you posted. Thank You.
  • All drop-down options are empty

    Solved
    18
    3
    0 Votes
    18 Posts
    4k Views
    TS79T
    @Andrew said in All drop-down options are empty: XO install video thanks Andrew - 100% agree Tom's video is the exact one that introduced me to the ronivay script, which is what I've used for all XO-from-source installs without problems.
  • OIDC issue with Microsoft Entra ID

    3
    0 Votes
    3 Posts
    1k Views
    J
    I'm expericing the same/similar behaviour with SAML, and submitted a Feature Request that it should be looked at. https://xcp-ng.org/forum/topic/10430/feature-request-if-authenticated-don-t-stop-at-the-xo.company.net-signin-page
  • This topic is deleted!

    17
    1
    0 Votes
    17 Posts
    41 Views
  • Is there any way to cleanup or reset xo config db

    Solved
    4
    0 Votes
    4 Posts
    843 Views
    A
    @Danp Thanks a million dear. much appreciated
  • $getFrom Understanding

    1
    3
    0 Votes
    1 Posts
    201 Views
    No one has replied
  • 0 Votes
    5 Posts
    3k Views
    D
    I'm starting to think that something is wrong. Everywhere I check, I can see that the SAML request from the SP should have a signature of some sort. It doesn't seem that there is anything of the sort in our case. We are using the opensource for preproduction and are waiting for a pro license (paperwork on it's way) so maybe there is something wrong in the implementation ?
  • LDAP fails with error "Code: -32000 Message: Code: 0x3"

    Solved
    7
    0 Votes
    7 Posts
    1k Views
    Y
    @dinhngtu said in LDAP fails with error "Code: -32000 Message: Code: 0x3": sAMAccountName Thank you. (userPrincipalName={{name}}) filter made the trick. When I use (userPrincipalName={{name}}), it works for me either I set certificate check ON or not. (Actually I was expecting to check AD root cert as this connection is using LDAPS) And also test only works when I do it using UPN but not with username@domain format. Other filter options did not work at all.
  • Transfer Pool Master / only partial success

    Solved xoa master designate
    6
    1 Votes
    6 Posts
    2k Views
    X
    positive Update: today I wanted to continue with this problem, but when I logged Into XOA today, Master status was Green / enabled. Since no one execpt me has credentials to the Testcluster, I am sure that no one else had done something. So the master host seemed to recovered itself from grey to green within the last 8 Hours. There were at least 1-2 hours yesterday between execution of "pool-emergency-transition-to-master" and still beeing grey dot / Halted. xe pool-emergency-reset-master master-address=... then added the remaining hosts to the new master.
  • windows 11 : "windows 11 installation has failed"

    2
    3
    0 Votes
    2 Posts
    389 Views
    No one has replied