1. Home
  2. Xen Orchestra

Subcategories

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

    463 Topics
    4k Posts
    P
    @delacosta456 said: the pool host maximum limit is 3200% right right

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

    102 Topics
    853 Posts
    I
    @simonp - Can you reshare the dashboards. The link says json is not available for any of these dashboards,

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

    498 Topics
    5k Posts
    olivierlambertO
    Question for @Team-XO-Backend

  • Everything related to Xen Orchestra's REST API

    84 Topics
    630 Posts
    K
    @olivierlambert & @mathieura thanks for the speedy response. Duly noted, very much appreciated.

  • Terraform, Packer or any tool to do IaC

    49 Topics
    463 Posts
    dalemD
    Version 1.4.0 is released: https://codeberg.org/NiXOA/system/releases/tag/v1.4.0 It includes significant changes and improvements, including: dedicated getting started section, migration to valkey, only needing to clone system, and helper scripts. the xen-orchestra-ce nixpkg now references the libvhdi nixpkg, and the core flake now references and pulls from the xen-orchestra-ce repo as an overlay. System (the user input flake) now uses the Core repo as an overlay, reducing the need to clone both locally AND allowing system to pull new updates and releases from core. XO, and libvhdi as needed. The next goal is: Make an xsconsole-like TUI Automate package updates for libvhdi and xen-orchestra-ce using CI/CD pipelines Submit libvhdi and xen-orchestra-ce as official nixpkgs
Log in to post
Load new posts
  • olivierlambertO

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

    Pinned
    179
    7 Votes
    179 Posts
    23k Views
    olivierlambertO
    Thank you for the great feedback @escape222 Likely a bug indeed
  • U

    load-balancer : Affinity to Host groups

    6
    0 Votes
    6 Posts
    193 Views
    Mitchel-APDM
    @olivierlambert In my understanding, Anti affinity tags only looks for the tags that are attached to the VM. For example: Datacenter 1 Host 1 VM1-1 Host 2 VM1-2 Datacenter 2 Host 3 VM2-1 Host 4 VM2-2 VM1-1 and VM1-2 should be able to migrate to Host 1 and Host 2. VM2-1 and VM2-2 should be able to migrate to Host 3 and Host 4. But VM1-1 and VM1-2 should never be able to migrate to Host 3 and Host 4. VM2-1 and VM2-2 should never be able to migrate to Host 1 and Host 2. With the current (Anti) Affinity tags, it will only look to the tags attached to the VM, so in the example it would be possible for VM1-1 to go to Host 4, if VM2-2 would be at Host 3 together with VM2-1. But if we could tag the hosts, it would not be possible for VM1-1 and VM1-2 to be on Host 3 and Host 4
  • A

    Lost connection to ISO Repository

    10
    2
    0 Votes
    10 Posts
    130 Views
    A
    @Pilow Apologies for the late reply. Thank you for sharing the work around. I have tried it and confirmed that the work around works. I hope they can find a solution for this issue.
  • A

    XOA - Memory Usage

    37
    2
    0 Votes
    37 Posts
    1k Views
    florentF
    @MajorP93 said: @florent Thanks! I did not have time (yet) to look into the heap export due to weekend being in between. I will update to current master and provide you with the heap export in the following days. Best regards no problem , the sooner we'll have these exports, the sooner we will be able to indentify what is leaking in your usage, since we already plugged the leaks we reproduced in our labs
  • A

    Managing vAPPs with XOA

    11
    0 Votes
    11 Posts
    2k Views
    G
    @olivierlambert +1 For creating vApps GUI in XO Reason: I recently had this configuration: VM1 - Delay 90 Seconds VM2 - Delay 100 Seconds VM3 - Delay 0 Seconds The VM3 instead of starting first, always starts last without fail. One difference I noticed is that VM3 is UEFI vs VM1 & 2 being in BIOS mode. I read elsewhere in the forum that vApps is the only reliable way to have an order. Maybe if we can somehow ensure that delay works, vApps will become less significant ?
  • P

    Ignition and creating a SUSE MicroOS VM

    11
    0 Votes
    11 Posts
    3k Views
    G
    @Bytevenidos That's an interesting way of doing this, I'll have to remember it. I think the Fuel Ignition tool has a vhd output, it also produces both ignition and combustion parts for you. Worked pretty good on one test machine, but I need to go deeper into some of the other choices you can type in.
  • M

    libfuse.so: error adding symbols: File in wrong format

    48
    0 Votes
    48 Posts
    23k Views
    florentF
    @Mark-C this is not forgotten, but file level restore has been under priorised, so it didn't get much work it is now quite high on our backlog , so expect good news in the next months
  • O

    Auth LDAP "unable to get local issuer certificate"?

    3
    0 Votes
    3 Posts
    628 Views
    D
    @omatsei said: @omatsei I figured out the problem. There appears to be a bug in XO that requires you to check "Check Certificate" and/or "Start TLS", save the configuration, then uncheck them, then save again. Then it should work. The bug is that they're unchecked by default, but apparently they're enabled in the background. Thanks for that, I was stump on this one trying to reconfigure a new instance. This is defintely the case even with the latest auth-ldap (v0.10.11) plugin.
  • BrantleyHobbsB

    How do I apply host patches in XO-6?

    3
    0 Votes
    3 Posts
    107 Views
    BrantleyHobbsB
    @DustinB thank you! I suspected as much, but as my wife points out all the time, I am terrible at finding things, so I figured I would ask.
  • E

    After Update XO wont start

    5
    1
    1 Votes
    5 Posts
    276 Views
    O
    @geometry game 2 This usually happens when dependencies are out of sync after pulling updates. Did you try removing node_modules and the lock file and then running yarn install again before starting XO?
  • jerry1333J

    XOA Unable to connect xo server every 30s

    3
    0 Votes
    3 Posts
    116 Views
    jerry1333J
    Support tunnel is active but I have troubles to access support "Oops, something went wrong! Don't worry, our team is already on it". I'll keep trying, thanks.
  • M

    Axios NPM attack

    4
    0 Votes
    4 Posts
    152 Views
    olivierlambertO
    I think I added it after the video ^^ (between the recording and the official release)
  • U

    Loss of connection during an action BUG

    18
    3
    0 Votes
    18 Posts
    563 Views
    P
    @User-cxs peut etre un clnflit IP ou la VM prenait l'IP du master... courage pour la suite !
  • U

    HOST_NOT_ENOUGH_FREE_MEMORY

    6
    5
    0 Votes
    6 Posts
    295 Views
    U
    @Danp Okay thanks you
  • MathieuRAM

    ACL V2 is coming soon and we need your feedbacks!

    1
    4 Votes
    1 Posts
    209 Views
    No one has replied
  • A

    Install XO from sources.

    21
    3 Votes
    21 Posts
    2k Views
    G
    @AlexanderK The ronivay script requires you to select an option (#2 to update). I look at things this way, it's good to have more people working on scripts like this.
  • S

    cleanVm: incorrect backup size in metadata

    18
    1
    0 Votes
    18 Posts
    4k Views
    M
    @hoh This is SOOO long in the tooth........... Always was annoying. Thx for findinf a fix, looking forward to it.
  • Z

    Removed VM - Now have unhealthy VDI

    Unsolved
    2
    0 Votes
    2 Posts
    115 Views
    Z
    UPDATE: its been 2 days and as I suspected the VDI is still waiting to coalesce at a length of 1, The GC does not seem to be cleaning it up. Does anyone have suggestions for how to remove this orphaned VDI and base copy. I'm not interested in saving the VM just cleaning up the remnants of the botched migration and removal.
  • B

    cant create a private cross pool network

    4
    0 Votes
    4 Posts
    539 Views
    M
    I am trying to setup the same VxLAN Private Network between two pools. I have been running XO from sources (commit 813514821) for a while now and encountered the same error "No PIF found in center". Therefore I updated to the latest commit 60ba5070c (still using XO v5) and now I was able to create a VxLAN private network that spans two pools without an error. I checked the networks for both pools and noticed that two networks were created per pool, so I was able to create it despite the error from the older XO version. However, using either VxLAN to connect two VMs in different pools doesn't work. Pinging a VM over that VxLAN in the same pool and host works, but pinging a VM from another Pool doesn't work. This is also the case when using GRE, Looking at the ARP Table, it seems that the VMs from different pool do show up, but as incomplete: [image: 1774432891674-screenshot-from-2026-03-25-10-59-34.png] 172.30.0.10 is the VM in the same pool as work (172.30.0.30), 172.30.0.20 is the VM from a different pool. I manually set the MTU size in each VM to 1450 just to be sure. I have two pools with one server each. This is due to CPU feature mismatch. Each host is connected via a bond of two SFP+ Ports (which have default MTU 1500) to a switch that allows all VLANs. Using normal VLAN Networks does work with multiple pools.
  • U

    XOSTOR

    Solved
    12
    1
    0 Votes
    12 Posts
    439 Views
    U
    But thank you for your time all the same.