1. Home
  2. Xen Orchestra

Subcategories

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

    437 Topics
    3k Posts
    florentF
    @Pilow the rrd ( the stats ) use the same code path as the backup . I am not sure if it's a feature or a bug, but at least it's a good canary the data volume of stats can be quite huge and have an impact on management. So it's a little justifiable to use the same network for backup and stats, at least until we can separate things more clealy . At least it helps a lot to check if the network is really reachable (sometimes because of third party filtering or ip configuration error , other to the xoa missing some network), and the downside is not to dangerous.

  • ACLs, Self-service, Cloud-init, Load balancing...

    97 Topics
    821 Posts
    pdoniasP
    @DaleDibbadel Are you running XOA or XO from the sources? Are you up-to-date?

  • All XO backup features: full and incremental, replication, mirrors...

    450 Topics
    4k Posts
    rizaemet 0R
    @olivierlambert Ceph. There are a few configuration examples. That's how I learned it's Ceph. Edit: When I asked the AI ​​some questions, it said something like this: "If the chunk size is too small → the risk of a 502 increase". Seeing this, I ran a few tests. A backup of a virtual machine with 80 GB of disk space (backup size: 70 GB) went through without any problems. However, a backup of a virtual machine with 16 GB of disk space (backup size: 3 GB) resulted in a failure. It seems the 502 error occurred during the clean-vm phase of the backup. However, the backup appears to have been created and it was working when I restored. I was backing up virtual machines with large disk sizes and had never encountered this error before. This section in the log exists both before the snapshot and after the export: ... { "id": "1768672615028", "message": "clean-vm", "start": 1768672615028, "status": "failure", "end": 1768673350279, "result": { "$metadata": { "httpStatusCode": 502, "clockSkewCorrected": true, "attempts": 3, "totalRetryDelay": 112 }, "message": "Expected closing tag 'hr' (opened in line 9, col 1) instead of closing tag 'body'.:11:1 Deserialization error: to see the raw response, inspect the hidden field {error}.$response on this object.", "name": "Error", "stack": "Error: Expected closing tag 'hr' (opened in line 9, col 1) instead of closing tag 'body'.:11:1 Deserialization error: to see the raw response, inspect the hidden field {error}.$response on this object. at st.parse (/opt/xo/xo-builds/xen-orchestra-202601171930/node_modules/fast-xml-parser/lib/fxp.cjs:1:20727) at parseXML (/opt/xo/xo-builds/xen-orchestra-202601171930/node_modules/@aws-sdk/xml-builder/dist-cjs/xml-parser.js:17:19) at /opt/xo/xo-builds/xen-orchestra-202601171930/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:1454:52 at process.processTicksAndRejections (node:internal/process/task_queues:103:5) at async parseXmlErrorBody (/opt/xo/xo-builds/xen-orchestra-202601171930/node_modules/@aws-sdk/core/dist-cjs/submodules/protocols/index.js:1475:17) at async de_CommandError (/opt/xo/xo-builds/xen-orchestra-202601171930/node_modules/@aws-sdk/client-s3/dist-cjs/index.js:5154:11) at async /opt/xo/xo-builds/xen-orchestra-202601171930/node_modules/@smithy/middleware-serde/dist-cjs/index.js:8:24 at async /opt/xo/xo-builds/xen-orchestra-202601171930/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:488:18 at async /opt/xo/xo-builds/xen-orchestra-202601171930/node_modules/@smithy/middleware-retry/dist-cjs/index.js:254:46 at async /opt/xo/xo-builds/xen-orchestra-202601171930/node_modules/@aws-sdk/middleware-flexible-checksums/dist-cjs/index.js:318:18" } } ...

  • Everything related to Xen Orchestra's REST API

    75 Topics
    572 Posts
    L
    @florent, I had to do the same for Xen Orchestra Community Edition. In my case, config.toml already contained the [authentication] section, so adding a separate config.tokenValidity.toml file did not work. Instead, I had to modify the existing config.toml located at /opt/xo/xo-server. In my opinion, it is best to keep defaultTokenValidity set to 30 days as a fallback in case no value is specified. You can then simply increase maxTokenValidity to the duration you prefer. [authentication] defaultTokenValidity = '30 days' # default value of 0.5 years # comment out and increase to 5 years #maxTokenValidity = ' 0.5 year' maxTokenValidity = '5 year'

  • Terraform, Packer or any tool to do IaC

    48 Topics
    438 Posts
    CyrilleC
    XO CCM v0.2.0 This update make it working with Talos. What's Changed Feat: record event when region zone changed Refactor: make xoClient and xoConfig available outside package scope (to be used by the CSI) Workaround for the SystemUUID sometimes in little-endian https://github.com/vatesfr/xenorchestra-cloud-controller-manager/releases/tag/v0.2.0 Terraform Provider v0.37.2 What's Changed Fix xenorchestra_vdi data source: you can now filter VDI/ISO with the same name label using tags. https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.37.2
Log in to post
Load new posts
  • olivierlambertO

    🛰️ XO 6: dedicated thread for all your feedback!

    Pinned
    90
    5 Votes
    90 Posts
    5k Views
    G
    I was having similar focus issues with a Debian 12 VM today, switched to XO5 to get the work done. Every few seconds the green border would vanish, but when it came back nothing had reset so it was less painful, but still annoying enough to switch back to 5.
  • N

    XO 6 backup job missing VM info on failure.

    1
    2
    0 Votes
    1 Posts
    27 Views
    No one has replied
  • W

    Orphan VDIs in XO show health problem

    15
    4
    0 Votes
    15 Posts
    364 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.
  • J

    Power Management (Power Efficiencies) Plugin Idea

    power managment efficiencies savings costs budgeting xenorchestra xcp-ng xenserver
    7
    0 Votes
    7 Posts
    1k 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.
  • K

    ISO won't show since XO6 Default

    5
    2
    0 Votes
    5 Posts
    222 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 spacotte-vates opened this pull request in vatesfr/xen-orchestra closed fix(xo-server): improve handling of xapi snapshots #9231
  • D

    XO 6 Official Release (for community)

    xo6 community life-cycle feedback
    4
    0 Votes
    4 Posts
    161 Views
    D
    I provided some feedback.
  • V

    Can't designate new master on XO source pool

    8
    0 Votes
    8 Posts
    256 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.
  • snk33S

    XOA gets disconnected very often

    6
    0 Votes
    6 Posts
    185 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.
  • W

    Staring up a shutdown VM in XO 6

    4
    0 Votes
    4 Posts
    216 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.
  • P

    2FA doesn't load graphics properly after XO6 went default (XO from source)

    Solved
    5
    1
    0 Votes
    5 Posts
    212 Views
    olivierlambertO
    Excellent news
  • P

    Failed unmounting remotes at XO/XOA shutdown

    4
    1
    0 Votes
    4 Posts
    402 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.
  • M

    Xen Orchestra Node 24 compatibility

    7
    0 Votes
    7 Posts
    501 Views
    M
    @olivierlambert said in Xen Orchestra Node 24 compatibility: Can you reproduce the issue on XOA? Or it's only on the sources + your current OS? We do not have a XOA license (yet) which is why I am currently solely using XO from sources. Therefore currently not able to reproduce on XOA. OS is Debian 13.
  • P

    XO5 breaks after defaulting to XO6 (from source)

    53
    1
    0 Votes
    53 Posts
    2k 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!
  • K

    Plugins in XO6?

    6
    0 Votes
    6 Posts
    211 Views
    olivierlambertO
    It won't disappear tomorrow, but I'd like to phase it out sooner than later (before 2027? who knows)
  • A

    Xen Orchestra from source ignores config.toml from /etc/xo-server/

    2
    0 Votes
    2 Posts
    158 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.
  • M

    LUKS Secured VM via Cloud Config

    1
    0 Votes
    1 Posts
    68 Views
    No one has replied
  • ForzaF

    Retention for log files and audit logs

    6
    0 Votes
    6 Posts
    699 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
  • ditzy-oliveD

    This topic is deleted!

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

    HOST_NOT_ENOUGH_FREE_MEMORY

    4
    0 Votes
    4 Posts
    188 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
  • D

    SAML Auth with Azure AD

    Solved
    37
    1 Votes
    37 Posts
    6k Views
    D
    @olivierlambert Just to add another weird case of this situation I tell you my SAML-auth-adventures. I have just migrated a week ago from XOCE to XOA paid support this week and all the process was fine except the auth with the saml plugin. The commit I had in XOCE was [XO 5d92f - Master 3f604]. I compiled it the first week of this november so it wasn't very outdated. We use the MSEntraID SAML authentication and it was working fine in XOCE since at least one year ago. Mi process was like this: First, I installed XOA and imported the configuration from my old XOCE. Everything was fine and all was imported succesfully (backups, users, acls, etc.), including my plugin configurations. Note that I reused the https server certificate/private key and used the same IP and the same DNS (beacuse I turned off my XOCE before starting XOA). Everything was working fine except the saml auth plugin. I had the same "Internal server error" problem. I looked at the xo-server logs and the error was "invalid document signature" so, as Olivier said, we changed the configuration in MSEntraID to set the "Sign SAML response and assertion" on. Once we changed the configuration I thought the plugin would work again, but surprisingly not. If I try again SAML validation i still got the "Internal server error". When i checked again the xo-server logs I saw ahother exception, this time with the error "SAML assertion audience mismatch" and a reference to the issuer configuration of the plugin. The exact error I got from xo-server logs using "journalctl -u xo-server -f -n 50" was: "xoa xo-server[2370]: Error: SAML assertion audience mismatch. Expected: <id-of-MSEntraID-xo-validation> Received: spn:<id-of-MSEntraID-xo-validation>"I didn't understand this, because the configuration was exactly the same as I had in XOCE. In fact, I turned off XOA and turned on again XOCE just to test the plugin. The result was that in XOCE the plugin worked well. After many tries and some time of impostor syndrome we found the solution: I don't know why, but in XOCE compiled at the beginning of november you have to configure the issuer field of the plugin with the <id-of-MSEntraID-xo-validation> (8digit-4digit-4digit-4digit-12digit). Instead, in XOA deployed also this november, you have to set the issuer field to you XOA URL: https://<xo.company.net>/ I hope this will help, because it was a pain in the neck for us this week. BTW: @olivierlambert this "Internal server error" coming from an uncatched exception in the plugin was not very descriptive. Even a generic try-catch block just to show in the web interface the error would help... P.D.: I'm from Spain, so I do my best with my english P.D. 2: Great job with all the Vates virtualization stack! You are the best! Dani