Subcategories

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

    405 Topics
    3k Posts
    olivierlambertO
    Question for @lsouai-vates
  • ACLs, Self-service, Cloud-init, Load balancing...

    96 Topics
    811 Posts
    olivierlambertO
    Indeed, and it's clearly stated at https://docs.xen-orchestra.com/community
  • All XO backup features: full and incremental, replication, mirrors...

    413 Topics
    4k Posts
    M
    @olivierlambert Is it XO or xcp-ng that manages the coalescing? Can more resources be applied to assist?
  • Everything related to Xen Orchestra's REST API

    69 Topics
    545 Posts
    S
    I was curious if there had been any updates to mounting ISOs via the API? Thanks.
  • Terraform, Packer or any tool to do IaC

    39 Topics
    371 Posts
    C
    Update: I tried to create a vm using a basic terraform config and using another template. Still the same problem, vm created without a disk. tofu apply -var-file="carlo111.tfvars" OpenTofu used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: + create OpenTofu will perform the following actions: # module.vm.xenorchestra_vm.vm will be created + resource "xenorchestra_vm" "vm" { + auto_poweron = false + clone_type = "full" + core_os = false + cpu_cap = 0 + cpu_weight = 0 + cpus = 2 + destroy_cloud_config_vdi_after_boot = false + exp_nested_hvm = false + hvm_boot_firmware = "uefi" + id = (known after apply) + ipv4_addresses = (known after apply) + ipv6_addresses = (known after apply) + memory_max = 2126512128 + memory_min = (known after apply) + name_label = "carlo111" + power_state = "Running" + start_delay = 0 + template = "3dbf5448-0337-40e1-ebfc-f3f47e2cb0dd" + vga = "std" + videoram = 8 + disk { + name_label = "carlo111-osdisk" + position = (known after apply) + size = 32212254720 + sr_id = "589dad4d-2391-c2a9-589c-d34a9a7757ea" + vbd_id = (known after apply) + vdi_id = (known after apply) } + network { + device = (known after apply) + ipv4_addresses = (known after apply) + ipv6_addresses = (known after apply) + mac_address = (known after apply) + network_id = "d4ddcfb0-6d3e-d267-b200-d7d1fec1edc8" } } Plan: 1 to add, 0 to change, 0 to destroy. Do you want to perform these actions? OpenTofu will perform the actions described above. Only 'yes' will be accepted to approve. Enter a value: yes module.vm.xenorchestra_vm.vm: Creating... module.vm.xenorchestra_vm.vm: Still creating... [10s elapsed] module.vm.xenorchestra_vm.vm: Creation complete after 14s [id=95b3b0c6-ac8e-fe4b-2f55-ba0d8ff04005] [20:09 dacshyp002 ~]# xe vbd-list vm-uuid=95b3b0c6-ac8e-fe4b-2f55-ba0d8ff04005 [20:25 dacshyp002 ~]# main.tf resource "xenorchestra_vm" "vm" { name_label = var.vm_name template = var.template_uuid cpus = var.cpus memory_max = var.memory * 1024 * 1024 hvm_boot_firmware = "uefi" clone_type = "full" disk { sr_id = var.sr_uuid name_label = "${var.vm_name}-osdisk" size = var.disk_size * 1024 * 1024 * 1024 } network { network_id = var.network_id } } I don't know if it is related, I see the following errors during the creation of the vm: Oct 28 20:44:07 dacshyp002 xapi: [error||458 |xapi events D:20adbb444ff6|xenops] events_from_xapi: missing from the cache: [ 532cad38-f1ae-433b-b7ac-e0399613fe24 ] Oct 28 20:44:07 dacshyp002 xapi: [error||458 |xapi events D:20adbb444ff6|xenops] events_from_xapi: extra items in the cache: [ 95b3b0c6-ac8e-fe4b-2f55-ba0d8ff04005 ] [20:44 dacshyp002 log]# xe vm-list uuid=532cad38-f1ae-433b-b7ac-e0399613fe24 uuid ( RO) : 532cad38-f1ae-433b-b7ac-e0399613fe24 name-label ( RW): Control domain on host: dacshyp002 power-state ( RO): running [20:45 dacshyp002 log]# xe vm-list uuid=1c210250-1f89-b0e3-c1e6-f7bee976e94c uuid ( RO) : 95b3b0c6-ac8e-fe4b-2f55-ba0d8ff04005 name-label ( RW): carlo111 power-state ( RO): running Manually creating the vm using the same template is not a problem.
  • Building from source fails with commit cb96de6

    Solved
    10
    1
    0 Votes
    10 Posts
    76 Views
    J
    @Andrew For the record, that didn't fix it for me. To be specific, it >>did<< fix the error regarding bigint in QcowDisk.mts, but a new error popped up later in the build: yarn run v1.22.22 $ TURBO_TELEMETRY_DISABLED=1 turbo run build --filter xo-server --filter xo-server-'*' --filter xo-web turbo 2.5.8 • Packages in scope: xo-server, xo-server-audit, xo-server-auth-github, xo-server-auth-google, xo-server-auth-ldap, xo-server-auth-oidc, xo-server-auth-saml, xo-server-backup-reports, xo-server-load-balancer, xo-server-netbox, xo-server-perf-alert, xo-server-sdn-controller, xo-server-test-plugin, xo-server-transport-email, xo-server-transport-icinga2, xo-server-transport-nagios, xo-server-transport-slack, xo-server-transport-xmpp, xo-server-usage-report, xo-server-web-hooks, xo-web • Running build in 21 packages • Remote caching disabled x Internal errors encountered: external process killed a task error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. + rm -rf /opt/xo/xo-builds/xen-orchestra-202510281354 That was with commit 740fc03, the latest at the time of my build at 2025-10-28 17:54 UTC. It's unclear to me why the build failed exactly. Except that "Internal errors encountered: external process killed a task". I don't know know what that external process was. Unfortunately the 3rd party build script doesn't seem to preserve failed builds, only a slender log file. I tried again a little later, with commit 87471d9. That succeeded, but it's unclear to me why. Neither commit explains either the failure, nor the success. The only other difference is that with the success, nodejs was updated (automatically, as part of the 3rd party build script) from 22.20.0-1nodesource1 to 22.21.1-1nodesource1, whereas for the failed build it was still 22.20.0-1nodesource1. I don't know enough about the build process to untangle what happened... but I don't really need to. I can remain ignorant By the way, if my initial post was closer to static noise than useful feedback, please forgive, and please let me know. It was really just an FYI to those who may be both listening and desiring to know. I see things move fast with the repo, with ten or more commits some days, so maybe flooding the forums with 'my build failed!' posts isn't helpful.
  • Unknown error - this pool is already connected

    15
    0 Votes
    15 Posts
    4k 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.
  • SAML Auth with Azure AD

    Solved
    32
    1 Votes
    32 Posts
    4k Views
    TheNorthernLightT
    @pierrebrunet Are you aware if there is an official guide on how to use this with AzureAD ?
  • freepbx import from esxi wont boot correctly

    12
    0 Votes
    12 Posts
    1k 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
    32 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).
  • VM exports sometimes invalid / truncated

    2
    0 Votes
    2 Posts
    53 Views
    olivierlambertO
    Ping @florent
  • XOA w/ secure boot and uefi mode

    4
    1
    0 Votes
    4 Posts
    121 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
    245 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
    347 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
    192 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
    69 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
    264 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
    231 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
    477 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
    704 Views
    P
    @DustinB with Easyvirt integrated in the stack
  • Build failure in XO v6

    8
    0 Votes
    8 Posts
    355 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
    187 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
    528 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
    609 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.