Subcategories

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

    499 Topics
    4k Posts
    I
    @tjkreidl everything looks normal. I also shared SOS report with @goulven I hope I'll get a feedback on slowness.
  • ACLs, Self-service, Cloud-init, Load balancing...

    107 Topics
    877 Posts
    Bastien NolletB
    Hello @ludalm13, Thanks for your contribution and sorry for not giving an answer earlier. We initially planned to review your PR while doing some additional work on the audit plugin, but our planning evolved and that work was postponed. We'll review your PR in the following days.
  • All XO backup features: full and incremental, replication, mirrors...

    550 Topics
    6k Posts
    poddingueP
    @blueh2o I think the two things you saw fit together, at least going by what I see in the mirror code. The 1 differencing tag only says that this one backup's disk is a delta, which is normal for an incremental; the key sits further back in the chain, which I think is why the health check could still rebuild the whole ~280 GiB disk. And as I wrote a few posts up, the mirror reads the parent of each delta on Ark and then asks each target whether it already has it, so last night's error would mean the Synology is missing d08f1acc for that one VM (fb7fca7d), not that Ark is broken. That brings us back to Florent's suggestion from the older thread, deleting that VM's most recent backups on the Synology so they get sent again, though I can't tell you why the Synology lost that base in the first place. At least it's down to one VM out of 56 last night, against 16 in October.
  • Everything related to Xen Orchestra's REST API

    89 Topics
    656 Posts
    P
    Hi, This was fixed in Latest. But if you need to stay on Stable, you can open a ticket to have a patch.
  • Terraform, Packer or any tool to do IaC

    54 Topics
    508 Posts
    poddingueP
    @enkaskal I need to correct my reply above, I got two things wrong. The plugin is ours after all: ddelnano/packer-plugin-xenserver is the repo's old address, it moved to vatesfr/packer-plugin-xenserver (where you filed #212), and GitHub just redirects the old link, which I read on our IaC docs page and jumped to the wrong conclusion. The key isn't missing either, I just didn't look in the right place: it's the signing key the Terraform Registry lists for vatesfr/xenorchestra, so you can fetch it from there. curl -s https://registry.terraform.io/v1/providers/vatesfr/xenorchestra/0.41.2/download/linux/amd64 \ | jq -r '.signing_keys.gpg_public_keys[0].ascii_armor' > xenorchestra-signing.asc gpg --import xenorchestra-signing.asc gpg --verify packer-plugin-xenserver_v0.12.0_SHA256SUMS.sig packer-plugin-xenserver_v0.12.0_SHA256SUMS On my machine the last command reports a good signature from 0DD2E92A7A0F682BC29F87073084D82948625D89, still a key in Dom Delnano's name from before the move. I'm honestly not sure how much trust that gives you beyond "the registry vouches for the same key", so I'd leave that part to the folks on #212 who know the release side better than me. Sorry for the detour.
  • Lost connection to ISO Repository

    10
    2
    0 Votes
    10 Posts
    2k 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.
  • Managing vAPPs with XOA

    11
    0 Votes
    11 Posts
    4k 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 ?
  • Ignition and creating a SUSE MicroOS VM

    11
    0 Votes
    11 Posts
    5k 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.
  • libfuse.so: error adding symbols: File in wrong format

    48
    0 Votes
    48 Posts
    32k 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
  • Auth LDAP "unable to get local issuer certificate"?

    3
    0 Votes
    3 Posts
    1k 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.
  • How do I apply host patches in XO-6?

    3
    0 Votes
    3 Posts
    709 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.
  • Axios NPM attack

    4
    0 Votes
    4 Posts
    690 Views
    olivierlambertO
    I think I added it after the video ^^ (between the recording and the official release)
  • Loss of connection during an action BUG

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

    6
    5
    0 Votes
    6 Posts
    1k Views
    U
    @Danp Okay thanks you
  • Removed VM - Now have unhealthy VDI

    Unsolved
    2
    0 Votes
    2 Posts
    357 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.
  • cant create a private cross pool network

    4
    0 Votes
    4 Posts
    1k 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: 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.
  • XOSTOR

    Solved
    12
    1
    0 Votes
    12 Posts
    2k Views
    U
    But thank you for your time all the same.
  • Migrations after updates

    13
    2
    0 Votes
    13 Posts
    2k Views
    Bastien NolletB
    Hi @acebmxer, I've made some tests with a small infrastructure, which helped me understand the behaviour you encounter. With the performance plan, the load balancer can trigger migrations in the following cases: to better satisfy affinity or anti-affinity constraints if a host has a memory or CPU usage exceeds a threshold (85% of the CPU critical threshold, of 1.2 times the free memory critical threshold) with vCPU balancing behaviour, if the vCPU/CPU ratio differs too much from one host to another AND at least one host has more vCPUs than CPUs with preventive behaviour, if CPU usage differs too much from one host to another AND at least one host has more than 25% CPU usage After a host restart, your VMs will be unevenly distributed, but this will not trigger a migration if there are no anti-affinity constraints to satisfy, if no memory or CPU usage thresholds are exceeded, and if no host has more CPUs than vCPUs. If you want migrations to happen after a host restart, you should probably try using the "preventive" behaviour, which can trigger migrations even if thresholds are not reached. However it's based on CPU usage, so if your VMs use a lot of memory but don't use much CPU, this might not be ideal as well. We've received very few feedback about the "preventive" behaviour, so we'd be happy to have yours. As we said before, lowering the critical thresholds might also be a solution, but I think it will make the load balancer less effective if you encounter heavy load a some point.
  • S3 Backup - maximum number of parts

    11
    0 Votes
    11 Posts
    2k Views
    D
    @florent That would be great. Thanks again!
  • Created VM from Fast Clone, Now How to Separate

    5
    0 Votes
    5 Posts
    935 Views
    bvitnikB
    @hawkpro I believe it will be worse with continuous replication because your replica will be in a shut down state. When you decide to start it, you will have to shut down the original VM and start the replica. You will have a downtime during shut down and start up sequence. Downtime during VM migration is a necessity so there is nothing unexpected there. All types of migrations require a VM to be suspended for some time (usually seconds) during the switchover from one host or SR to the other host or SR. If you have extended downtimes of your VM migrations, then something is not quite right with your setup.
  • IPMI Info Outlet Air temp missing.

    10
    2
    0 Votes
    10 Posts
    2k Views
    J
    @acebmxer I’m sorry to say that if those Dells are at your workplace, the wrong edition of iDRAC was purchased. You see with at the very least iDRAC 9 access to the full granular IPMI sensor data, was placed behind an edition paywall by Dell Technologies. Outlet temperature is just one of the feeds, missing from the Enterprise or lower edition of iDRAC 9. You’ll get the temperature readings from the Dell iDRAC web browser based interface, but not IPMI with iDRAC 9 Enterprise. To obtain the full IPMI sensor data you need the Datacenter edition.
  • Unable to connect to V5

    3
    0 Votes
    3 Posts
    583 Views
    J
    @olivierlambert said: I think it was fixed since, are you sure you are using an uptodate XO? Commit 0be23 Anyway was directing attention to the GitHub issue, which was opened. The issue has another reference to it.
  • Commit 109e376 Implications

    5
    0 Votes
    5 Posts
    1k Views
    rzrR
    Latest XO can be new tested along XCP-ng (with OpenSSL 3): https://xcp-ng.org/forum/topic/9964/xcp-ng-8-3-updates-announcements-and-testing/363 Feedback welcome
  • VDIS not showing in XO5, but are in XO6 and on the VM itself ?

    4
    2
    0 Votes
    4 Posts
    882 Views
    P
    @kent you would have to rollback to early december 2025 XO/XOA (before the 10 of december) quite a long way I'm just waiting the devs to eventually fix it as we have other way to manage VDIs (API calls)
  • XOA SocketError: Other side Closed

    1
    0 Votes
    1 Posts
    272 Views
    No one has replied