Subcategories

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

    434 Topics
    3k Posts
    nikadeN
    Cool, thnx for the info!
  • ACLs, Self-service, Cloud-init, Load balancing...

    97 Topics
    818 Posts
    olivierlambertO
    October release fixed it
  • All XO backup features: full and incremental, replication, mirrors...

    445 Topics
    4k Posts
    olivierlambertO
    Hi! Thanks for the feedback. Can you be more specific? This might be helpful if others would have the same issue Thanks!
  • Everything related to Xen Orchestra's REST API

    75 Topics
    571 Posts
    F
    @MathieuRA Thank you, perfect Br,
  • Terraform, Packer or any tool to do IaC

    46 Topics
    428 Posts
    dalemD
    I have created two Nix flakes for running Xen Orchestra inside a NixOS virtual machine on XCP-ng. I am a strong supporter of Nix and NixOS, and I was interested in the idea of building Xen Orchestra from source in a fully declarative way. Requirements Before you begin, you need: • A virtual machine running NixOS • Flakes enabled (either in your system configuration or in your current shell) • The git package installed Flake Overview There are two flakes: NiXOA-VM This is the main flake of the project. It includes: A Xen Orchestra package built from source A libvhdi Nix module Update and maintenance modules System and user configuration modules Xen guest tools (via xen-guest-agent) Support for a separate user-config flake This flake is where the Xen Orchestra service and core functions are defined. It is not intended to be user editable when using it. User-config This flake contains your machine-specific settings. Editing configuration.nix is used for basic system settings such as: Hostname Username Time zone SSH keys hardware-configuration.nix You must copy this file from /etc/nixos/hardware-configuration.nix into the root of the user-config directory. While you're at it, go ahead and update hardware-configuration.nix to have a swap file (you can ignore this if you set a swap file in the NixOS installer) by adding the following lines to the config: swapDevices = [ { device = "/swapfile"; size = 4096; # in MB (4GB) } ]; Making Customizations There are helper scripts to simplify setup. In the future, these may be replaced with a text-based user interface (TUI). In most cases, you will only need to edit: configuration.nix – system-level settings home.nix (optional) – if you want more control using Home Manager config.nixoa.toml – only if you have custom Xen Orchestra server settings You usually do not need to edit config.nixoa.toml. If you do, avoid changing the Redis, sudo, or HTTPS mount settings unless you know exactly what you are doing, as this can break the system. Building the System After you finish editing your configuration: Go to the user-config directory Update inputs from nixoa-vm: nix flake update Add all changed files (including hardware-configuration.nix): git add * Commit your changes: git commit -m "Initial configuration" Rebuild the system: sudo nixos-rebuild switch --flake .#nixoa (Replace nixoa if you changed the hostname.) Installer The documentation mentions an installer that automates most of these steps. It exists, but it still needs more testing and should be considered experimental. Optional Shell Enhancements If you change the shell for the xoa user from bash to zsh in configuration.nix, the system will automatically install several quality-of-life tools, including: oh-my-posh fzf zoxide eza bat and other terminal enhancements This is a personal passion project that I built on my own. If you are interested, please take a look and share any feedback or suggestions: https://codeberg.org/NiXOA
  • 🛰️ XO 6: dedicated thread for all your feedback!

    Pinned
    82
    5 Votes
    82 Posts
    4k Views
    P
    Windows guests Console - Reloads every 5-10s. When trying to use the console for both my Windows 11 and Server 2025. The console reloads every 5-10s. This makes it borderline unusable. Since it resets the viewport/window scroll placement as well. Also the console seems to loose focus when this happens as well. Leading to have to click the console-section to get it in focus, to receive I am not seeing this behaviour in XO5 at all. I do not see the same behaviour on Linux (Ubuntu 24.04) guests. But they are cli-only. No X/Wayland Commit: b89c26459cfd301bb92adf0a98a0b2dbab57e487 node: 24.12.0 Management agent 9.1.100-59 on both VMs Windows 11 has GPU passthrough & bios Windows Server 2025 - no GPU passthrough , uses uefi
  • Can't designate new master on XO source pool

    8
    0 Votes
    8 Posts
    198 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
    94 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
    137 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
    150 Views
    olivierlambertO
    Excellent news
  • Failed unmounting remotes at XO/XOA shutdown

    4
    1
    0 Votes
    4 Posts
    331 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.
  • Xen Orchestra Node 24 compatibility

    7
    0 Votes
    7 Posts
    426 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.
  • XO5 breaks after defaulting to XO6 (from source)

    53
    1
    0 Votes
    53 Posts
    1k 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!
  • ISO won't show since XO6 Default

    1
    2
    0 Votes
    1 Posts
    64 Views
    No one has replied
  • Plugins in XO6?

    6
    0 Votes
    6 Posts
    147 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
    113 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
    47 Views
    No one has replied
  • Retention for log files and audit logs

    6
    0 Votes
    6 Posts
    642 Views
    E
    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
    141 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
  • 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
  • XOCE - ISO upload is renamed after upload to ISO SR

    18
    1 Votes
    18 Posts
    756 Views
    mxM
    We'd recently got a relevant experience regarding this weird renaming to uuids. We had one orchestra managing one pool. ISOs were in an ISO SR, with an nfs4 serving it underneath. All fine till then. We added one second pool to the orchestra. Just a single host by itself. One of the very next days we discovered that all names in the ISO SR had been replaced by uuids. Removing/readding the sr to the new pool helped temporarily. Usual names appeared again. But after a few more days, again uuids. Where uuids were appearing, we could not select anything from the dropdown list in the console's cdrom. The list per pool was unpopulated. We tried separate the shares by offering the new pool an nfs4 share from the NAS, actually sharing the same source dir. It did mount but now there was a uuid uniq constraint that was violated, so we could not see no files at all in this new SR. It would not be an illogical thought to have an 'iso sr' attached once to the orchestra and be offered by the orchestra to all managed pools, without uuids, without uniqs etc. There seems to be an unnecessary complication here I think.
  • Set default resolution for UEFI

    5
    0 Votes
    5 Posts
    2k Views
    G
    I haven't had too much difficulty hitting the esc key in time to get into the EFI config. Click the start VM button, quickly click away from the display area and click in the display area, then toggle the esc key until I see it take effect. I know I have a couple running at 1920x1080, but that's actually kind of a pain. I only did that to try and get a larger RDP window, RDP may be limited by the original "monitor" resolution, but this might also be fixed in later updates. This one VM has been up for a few years. (edit, yes this has been changed, VMs with a 4x3 monitor now RDP is whatever I have set).
  • cleanVm: incorrect backup size in metadata

    16
    1
    0 Votes
    16 Posts
    3k Views
    U
    @k11maris Same on my side. Delta backup for all VMs show this message. [image: 1763710321097-bildschirmfoto-2025-11-21-um-08.30.44.png]
  • License not working

    7
    0 Votes
    7 Posts
    278 Views
    DanpD
    Hi, I just responded to your ticket with the steps to update XOA to match your new license. Regards, Dan