Subcategories

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

    439 Topics
    3k Posts
    P
    @Danp if no one else complains, I have a problem ping OK, no TCP 443. strange.
  • 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...

    451 Topics
    4k Posts
    florentF
    @jsajous26 AFAIK this is not possible to call a script inside the VM through the guest tools. Maybe on veeam side there are other way to do this ( throug ssh / powershell) ?
  • 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
    443 Posts
    Mang0MusztardaM
    @mpiton thanks for sharing docs, the crucial part was openssl rand -hex 32 my password was too simple and that's why i got :"Query authentication does not match server setting" error after setting 32 characters password i got my metrics, in both http://localhost:9004/metrics and http://<xo-ip>/openmetrics/metrics
  • Building from source fails with commit cb96de6

    Solved
    12
    1
    0 Votes
    12 Posts
    950 Views
    J
    @Andrew many thanks. As do I. See my OP. A failed build doesn't break XO. It leaves the previous successful build in place. My post wasn't to ask how to fix my problem, but to point out the issue to others who might care to know (see my last post). Cheers.
  • Unknown error - this pool is already connected

    15
    0 Votes
    15 Posts
    5k Views
    P
    This is an old thread, but I ran into this myself recently. While there is a link to deleting the entire XO configuration, I think I fixed it with a less drastic solution. Remember: I'm just a random dude on the internet posting dangerous commands to try. It worked for me, but your mileage might vary. I run Xen Orchestra in a container (Xen Orchestra, commit e8733 at the time of writing). So I got a command line in the container with: docker exec -it xoa bash Then I ran redis-cli to get a redis command prompt. I typed KEYS * to get a list of keys. One key I saw was: 7) xo:server_host:172.30.0.214". That's the IP of the host I was trying to join (the master of a single-host pool). So I ran: del xo:server_host:172.30.0.214 Then I restarted my container with docker restart xoa. After that, I was able to successfully add the host to Xen Orchestra. Maybe this will help someone else. It got me working again.
  • freepbx import from esxi wont boot correctly

    12
    0 Votes
    12 Posts
    2k Views
    J
    @jsox79 No I did not. Disclaimer - I inherited this FreePBX system and don't know a whole lot about it. Once I got it to boot, I tested by calling my cell from a desk phone and making a page, and both worked as expected so I'm considering everything to be working. Didn't realize re-registering modules was something I may have needed to do.
  • Nordic languages AltGr+<key>

    3
    0 Votes
    3 Posts
    238 Views
    K
    OK, thanks for the quick response
  • The emulator required to run this VM failed to start..?

    14
    0 Votes
    14 Posts
    11k Views
    M
    Bit of a necro-post, but we're mid migration of storage/VM hosts/pools. I have a single win11 VM that's UEFI (not secure boot). It runs just fine on our old 8.1 server that we're migrating off of. If I provision a new UEFI VM on the new pool and point it at the shared storage VHD, it refuses to boot with the same "The emulator required to run this VM..." error OP posted. I've tried restarting the toolstack and "updating the Secure Boot certs" on the host server. Any guidance very much welcomed, I was unaware that this VM wasn't booting on the new pool (the VM is off a lot of the time), and we're a couple weeks from this project completing (and the old server being WEEEd).
  • XOA w/ secure boot and uefi mode

    4
    1
    0 Votes
    4 Posts
    440 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
    687 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
    439 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
    138 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
    747 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
    543 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
    897 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
    752 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
    388 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
    700 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
    907 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.