Subcategories

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

    452 Topics
    3k Posts
    andrewperryA
    We have been quietly suffering without the time to try and resolve it for the past couple of months. I have now spent the day trying to resolve it in our environment, as we have one SR having this problem with some hundreds! of vdi. I am having the same problem whether running the docker container version of XO CE or the local install on a VM we've been using for ages. It seems that the api call from the VDIs tab in v6 (Disks in v5) may be triggering a call to the wrong url, without the /rest/v0 prefix: sudo journalctl -u xo-server -n 300 --no-pager 2026-02-26T06:01:57.169Z xo:rest-api:error-handler INFO [GET] /vms/[[UUID]]/vdis (404) I had the same experience as some others for a while, a couple of months ago, where it would not show up in the v5 UI but was showing in v6, but very quickly after that it stopped working in either. I know that these are VDIs with a snapshot in the chain, for example a parent VDI that may have two snapshots from it. I had thought the issue may have been had something to do with https://github.com/vatesfr/xen-orchestra/pull/9381 as it was around this time that I saw the problem in v5 before it also trickled through to v6 - but now I see that this topic was started just before Christmas so there must have been something else too. If I run curl with the /rest/v0 prefix to the url I don't get the 404. I hope this helps to track it down! MathieuRA opened this pull request in vatesfr/xen-orchestra closed fix(rest-api): fix getVmVdis and enhance the type #9381
  • ACLs, Self-service, Cloud-init, Load balancing...

    100 Topics
    832 Posts
    Tristis OrisT
    Ok, my syntax is oudated. resize_rootfs: true growpart: mode: auto devices: ['/dev/xvda3'] ignore_growroot_disabled: false runcmd: - pvresize /dev/xvda3 - lvextend -r -l +100%FREE /dev/ubuntu-vg/ubuntu-lv || true this one works. final_message. doesn't support any macro like %(uptime) %(UPTIME)
  • All XO backup features: full and incremental, replication, mirrors...

    467 Topics
    5k Posts
    A
    @Pa3docypris I also had this problem with one single Debian VM. I would delete the snapshot and they would just keep adding every backup. I have lots of the same VMs and lots of other VMs on the pool. Three VMs were basically exactly the same but only one had an issue. I tried deleting all snapshots on the VM. Changing the CBT state. Doing a full backup up of the VM.... same problem. Snapshots just built up. I found a CD in the VM drive and it would not eject (with a XCP error). So there was something strange with the VM state. I shutdown the VM, cleared the CD, and restarted the VM. After that, backups worked normally for that VM. So I won't blame XCP or XO, it seems the VM was just in a random strange state that caused problems.
  • Everything related to Xen Orchestra's REST API

    79 Topics
    597 Posts
    H
    Aha! I will move to prometheus in the future, but at the moment it is more basic. Thank you!
  • Terraform, Packer or any tool to do IaC

    49 Topics
    461 Posts
    jmaraJ
    @Cyrille
  • XOA w/ secure boot and uefi mode

    4
    1
    0 Votes
    4 Posts
    491 Views
    olivierlambertO
    Not with XOA then (yet). We might switch XOA to UEFI in the future for that. If you are using XO from the source, sure, you can do that
  • [Request] Improve XO6 tags display functionality

    8
    2
    1 Votes
    8 Posts
    776 Views
    tc-atworkT
    @lsouai-vates those look great! @Pilow hey I’m just happy that @olivierlambert officially 100% promised and fully committed to a December 2025 initial release of XO6 on the monthly blog
  • Update Templates

    13
    1 Votes
    13 Posts
    1k Views
    G
    @olivierlambert The only thing I can think of from newer kernels is NFS options like nconnect=xx for hopefully more speed in the day to day range of duties. As of the pre-LTS, this still wasn't in 8.3. I haven't checked after LTS.
  • ECONNREFUSED when creating SDN network

    5
    0 Votes
    5 Posts
    499 Views
    K
    @bleader Hi, After a restart of the entire host, port 6640 is now listed when I trigger ss. But, unfortunatly, tunnels are not working, every VM on this host loose connection to other in the same sdn network. Exemple with an ping between two hosts : 2025-10-09T12:22:54.781Z|00026|tunnel(handler1)|WARN|receive tunnel port not found (arp,tun_id=0x1f1,tun_src=192.0.0.1,tun_dst=192.0.0.3,tun_ipv6_src=::,tun_ipv6_dst=::,tun_gbp_id=0,tun_gbp_flags=0,tun_tos=0,tun_ttl=64,tun_erspan_ver=0,gtpu_flags=0,gtpu_msgtype=0,tun_flags=key,in_port=33,vlan_tci=0x0000,dl_src=56:30:10:5c:4d:ad,dl_dst=ff:ff:ff:ff:ff:ff,arp_spa=192.168.10.10,arp_tpa=192.168.10.20,arp_op=1,arp_sha=56:30:10:5c:4d:ad,arp_tha=00:00:00:00:00:00) 2025-10-09T12:22:54.781Z|00027|ofproto_dpif_upcall(handler1)|INFO|Dropped 61 log messages in last 59 seconds (most recently, 1 seconds ago) due to excessive rate 2025-10-09T12:22:54.781Z|00028|ofproto_dpif_upcall(handler1)|INFO|received packet on unassociated datapath port 33 If I migrate the VM on the third host to another, network came back. This is very strange, because the network I've choose to test it is one of firt of all created, not last one, so it have worked before, and not now. I don't understand why and what to do...
  • XCP-NG & XOA Trial extend

    2
    1
    0 Votes
    2 Posts
    153 Views
    olivierlambertO
    Hi, As the message said, please reach out to us, you can use the contact form https://vates.tech/contact We'll be happy to discuss and assist in your evaluation
  • Feature request add open in new tab to XO GUI

    9
    2
    0 Votes
    9 Posts
    870 Views
    marcoiM
    @tc-atwork thanks for post, i wasnt able to get xo6 setup as i havent had time to play with it. I look forward to when it released. For now I just keep using xo-lite to open the console window.
  • [VDDK V2V] Migration of VM that had more than 1 snapshot creates multiple VHDs

    Solved
    6
    1
    0 Votes
    6 Posts
    632 Views
    P
    @MajorP93 stress of VM migration XD good luck with your V2Vs !
  • ldap user auth doesn't work after update to actual version

    8
    1
    0 Votes
    8 Posts
    992 Views
    lsouai-vatesL
    @vmpr hello, to be able to address the problem more clearly can you give me the version of your XO please? and if you are on stable or latest? XO v5.111.0 has been publicly released in latest channel yesterday.
  • CPU radio buttons on usage graph

    15
    1
    0 Votes
    15 Posts
    1k Views
    P
    @DustinB with Easyvirt integrated in the stack
  • Build failure in XO v6

    8
    0 Votes
    8 Posts
    843 Views
    D
    The same issue was reported here, but seems its been fixed already. https://github.com/Jarli01/xenorchestra_installer/issues/137 nickali created this issue in Jarli01/xenorchestra_installer closed v6 build error: Scale is not exported by #137
  • Default resources not showing on template

    Solved
    3
    2
    0 Votes
    3 Posts
    424 Views
    K
    Ah... so I missed the fix by one commit and two hours... I can confirm it resolve it. Thanks!
  • VMware importer using Proxy

    4
    0 Votes
    4 Posts
    738 Views
    florentF
    @hitechhillbilly Hi, For now the import tool does not use the proxy. Not that the full import tool also work from source if you need additional XOA , but we won't be able to connect to them for support
  • VDI is not available

    6
    0 Votes
    6 Posts
    995 Views
    TheLittleDukeT
    @Danp the issue is "resolved" only because we got the host back online so it released the lock. Yes I did try Start on which is method that produced the "The VDI is not available" error no the offline host was not the pool master Yes the VDI's are on shared iSCSI storage (truenas) And I want to note that OTHER VM's that were not on that failed host were able to restart and on any other node without an issue. I was even able to delete old snapshots without an issue so clearly the storage was online and available. It is deeply concerning that we were unable to get the VMs running again and only coincidental that were were able to re-seat the ram module and get it back online -- once it rejoined the pool the locked VM started without any issues on another host, so something was clearly locking it down even though it was fully stopped and visible.
  • Update XOA OS via apt update?

    12
    0 Votes
    12 Posts
    2k Views
    olivierlambertO
    @thomas-dkmt we might need to make sure XO docs tell how system updates are handled and proxy config
  • Migrating logs and history between XOA instances?

    8
    0 Votes
    8 Posts
    1k Views
    ForzaF
    @olivierlambert said in Migrating logs and history between XOA instances?: Hi, VM stats aren't store on XOA but on your pools, and they should be there with the same history as the old one Can you tell exactly what kind of logs are you talking about? Thanks. I had looked on the wrong VM. The stats are indeed retained. Originally I was thinking of audit logs, but I realized they can be exported and imported. So for m point of view it is enough for now. Other logs that are missing is for example backup logs.
  • New proxy giving unauthorized error

    1
    0 Votes
    1 Posts
    135 Views
    No one has replied
  • XO logs to external syslog

    19
    0 Votes
    19 Posts
    5k Views
    P
    @Forza I didn't try, as my default Graylog Input was UDP and worked with the hosts... But guys, that was it. In TCP mode, it's working. Rapidly set up a TCP input, and voila. [image: 1758137911306-42411fc9-af86-4838-a870-ca9ca6307234-image.png]
  • DUPLICATE_MAC_SEED

    8
    0 Votes
    8 Posts
    1k Views
    I
    @KPS Unfortunate, no. I just replicate and avoid moving live VM on the same host, target for replication.
  • XOA deploy from XO lite

    Solved
    8
    3
    0 Votes
    8 Posts
    2k Views
    olivierlambertO
    Excellent news!
  • 0 Votes
    17 Posts
    2k Views
    M
    @Andrw0830 I am using paid version of ESXi / vSphere. The free version of ESXi has so many limitations that I consider it pretty much unusable / only usable for very limited basic tests. It would not suprise me if your issue is due to the license limitations within ESXi.