Subcategories

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

    446 Topics
    3k Posts
    gskgerG
    I am running NVIDIA P40s on a DELL R720/R730 and a NVIDIA A2000 12GB on a DELL Optiplex 9010 in my playlab. Getting the GPUs to be accessible for VMs was quite easy: shutdown the XCP-ng host, install the GPUs, start the host again, activate the GPU in the advanced settings of the host in the PCI Devices section (“Passthrough enabled”). The host will restart at this point after displaying a warning. That's it – the GPU can now be assigned to a VM in the VMs advanced settings. I do use the GPUs for AI workloads under Debian though, so your use case might vary.
  • ACLs, Self-service, Cloud-init, Load balancing...

    98 Topics
    825 Posts
    D
    @bleader Hopefully the palm print on my forehead isn't visible from where you are sitting. Of course the interface needs an IP address. In my defense, normally for something like this, I wouldn't put it on the bonded interface with all the trunked VLAN's for guest traffic (we don't give that one an IP) and it would go on the other bonded interface that isn't trunked and does get an IP, but these are test hosts and I didn't set up the other bond, so it is pulling double duty. I was able to set the IP's and get SDN working. Thanks!
  • All XO backup features: full and incremental, replication, mirrors...

    459 Topics
    5k Posts
    P
    Having the flag "Protect from accidental deletion" has since yesterday left me with plenty of restored VMs. In the backup logs, it indicates that this happens during the healthcheck. This has happened on 3 out of 6 VMs Update: The other 3 VMs were opt-out from Healthchecks. So that is why this didn't affect them. [image: 1770237677335-23a84083-7aa0-4405-81f2-30e630b5edd5-image.png] commit: dd5f0cdaa9993fae25469bd1cb1d01d4f2123f44 transfer Start: 2026-02-04 12:16 End: 2026-02-04 12:16 Duration: a few seconds Size: 2.01 GiB Speed: 81.14 MiB/s health check transfer Start: 2026-02-04 12:16 End: 2026-02-04 12:35 Duration: 19 minutes vmstart Start: 2026-02-04 12:35 End: 2026-02-04 12:35 Start: 2026-02-04 12:16 End: 2026-02-04 12:35 Error: forbidden operation: destroy is blocked: protected from accidental deletion Start: 2026-02-04 12:15 End: 2026-02-04 12:35 Duration: 20 minutes Error: forbidden operation: destroy is blocked: protected from accidental deletion Clean VM directory cleanVm: incorrect backup size in metadata merge Start: 2026-02-04 12:40 End: 2026-02-04 12:41 Duration: a minute Start: 2026-02-04 12:40 End: 2026-02-04 12:41 Snapshot Start: 2026-02-04 12:41 End: 2026-02-04 12:41
  • Everything related to Xen Orchestra's REST API

    76 Topics
    578 Posts
    R
    @Pilow tags can work and the path to them is much more succinct. Thanks!
  • Terraform, Packer or any tool to do IaC

    48 Topics
    444 Posts
    CyrilleC
    Kubernetes CCM for Xen Orchestra v1.0.0-rc.1 We’re shipping v1.0.0-rc.1, our first release candidate on the road to a stable 1.0.0! This RC is feature-complete and ready for real-world use. Please try it out and share any feedback—bugs, regressions, or usability notes—so we can polish the final release. Thank you for testing and helping us! https://github.com/vatesfr/xenorchestra-cloud-controller-manager/releases/tag/v1.0.0-rc.1 Golang SDK for Xen Orchestra v1.11.0 SDK v2: VM and Task services now match the latest REST API. Host service has been added for host data retrieval. Integration tests have also been strengthened to boost reliability. The v2 SDK is gradually becoming our main library for all the other DevOps tools (Kubernetes drivers, Terraform provider…). There are BREAKING CAHNGES in the v2 SDK, so please read the release notes carefully. Remember that the v2 SDK is a beta version and can be subject to significant changes. The current semantic versioning we use is mostly for the v1 SDK. When the v2 SDK becomes stable, the major version number will increase. https://github.com/vatesfr/xenorchestra-go-sdk/releases/tag/v1.11.0
  • How to add plugins like sdn-controller etc. to my XOA

    5
    1
    0 Votes
    5 Posts
    929 Views
    P
    ok thank you!
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    6 Views
    No one has replied
  • Reset/Update statistics page fields

    3
    1
    0 Votes
    3 Posts
    504 Views
    S
    ah ok, thanks for the information.
  • Problems mounting NFS share

    13
    0 Votes
    13 Posts
    2k Views
    DanpD
    @rongage I don't know if anyone else has it working correctly on CentOS Stream 9. I know that it works on recent versions of Debian and Ubuntu, so why not try one of those?
  • Continue (vs restart) an interrupted backup

    7
    0 Votes
    7 Posts
    1k Views
    olivierlambertO
    With classical export (ie VHD and without NBD) you cannot "resume" a backup. Now it's possible (technically with NBD) but it's not done (yet). But we improved a lot the retry vs the original backups in VHD.
  • Deployment of XOA

    4
    0 Votes
    4 Posts
    1k Views
    J
    I don't "need" to deploy with xo-lite I just wanted to report it in case it was a bug with static ip configuration.
  • Replicating bare metal to VM

    6
    0 Votes
    6 Posts
    768 Views
    olivierlambertO
    In theory, like thinking on top of my head, an agent in the physical machine that will be able to replicate the VM files in the same format than the XO backup, with also the "machine metadata" (CPU, RAM etc.). Then, if something goes wrong, you could restore a backup as a VM from the real machine.
  • Windows template sysprep with cloudinit

    3
    0 Votes
    3 Posts
    691 Views
    J
    @olivierlambert thanks for the quick reply Olivier, We have cloudinit working for Linux as that is working like a charm, hopefully a MS cloudinit god will reply and will be able to help me out
  • Windows VM gets apipa from tagged network interface, no issues on Linux

    Solved
    3
    2
    0 Votes
    3 Posts
    358 Views
    J
    @Andrew it was related to a switch configuration mistake, thanks anyways.
  • Set Static Memory for VM in XOA

    9
    2
    0 Votes
    9 Posts
    1k Views
    olivierlambertO
    Yes, you can ignore static min, 99% of the time it's not relevant.
  • Ran XOA updater, got 'CANNOT GET /', web UI has stopped working.

    7
    0 Votes
    7 Posts
    2k Views
    W
    My apologies @Danp , I had misunderstood the comments on the other commands in that KB article. Good news, things are working, but it didn't seem like they would be. xoa run npm i -g --unsafe-perm https://xen-orchestra.com/xoa-updater.tgz Seemed to work. I was then able to run systemctl restart xoa-updater and xoa-updater --upgrade. After the upgrade command, this is the feedback: xoa:xoa$ xoa-updater --upgrade stable channel selected Downloading packages... xen-orchestra 5.95.2 . ok ✔ xo-server-telemetry 0.5.0 ...................................... ok ✔ xen-orchestra-web 0.0.3 ................................................... ok ✔ xo-server-xoa 0.29.0 .................................................................................................................. ok ✔ xo-web-free 5.147.0 ................................................................................................................................................................................................................................................................................................................................................................................................................................. ok ✔ xoa-cli 0.38.2 ...................................................................................................................................................................................................................... ok ✔ xen-orchestra-upload-ova 0.1.6 ........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ ok ✔ xo-server 5.145.0 ......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... ok ✔ Following packages will be removed: xoa-updater 0.50.0 Removing packages... Saving current updater version in /usr/local/lib/node_modules/xoa-updater-previous ...ok ✔ xoa-updater ✔ New versions available: node 18.20.2 (18.19.1 installed) npm 10.5.0 (10.2.4 installed) Downloading packages... node 18.20.2 ...... ok ✔ npm 10.5.0 .................................................................................................................................................................. ok ✔ Installing packages... Upgrading Node/npm failed, re-installing old packages Command failed with exit code 1: npm i -g --unsafe-perm --quiet /tmp/xoa-updater/node-18.20.2.tgz npm ERR! code 1 npm ERR! path /usr/local/lib/node_modules/node npm ERR! command failed npm ERR! command sh -c ./installer npm ERR! installing : node-v18.20.2 npm ERR! curl: (28) Failed to connect to nodejs.org port 443 after 261014 ms: Couldn't connect to server npm ERR! npm ERR! Error: download preflight failed for '18.20.2' (https://nodejs.org/dist/v18.20.2/node-v18.20.2-linux-x64.tar.xz) npm ERR! A complete log of this run can be found in: /tmp/.npm/_logs/2024-09-01T16_42_27_685Z-debug-0.log New packages available: xoa-updater 0.50.0 Downloading packages... Installing packages... xoa-updater ✔ xoa-updater ✔ ✖ { message: 'Command failed with exit code 1: npm i -g --unsafe-perm --quiet /tmp/xoa-updater/node-18.20.2.tgz\n' + 'npm ERR! code 1\n' + 'npm ERR! path /usr/local/lib/node_modules/node\n' + 'npm ERR! command failed\n' + 'npm ERR! command sh -c ./installer\n' + 'npm ERR! installing : node-v18.20.2\n' + "npm ERR! curl: (28) Failed to connect to nodejs.org port 443 after 261014 ms: Couldn't connect to server\n" + 'npm ERR! \n' + "npm ERR! Error: download preflight failed for '18.20.2' (https://nodejs.org/dist/v18.20.2/node-v18.20.2-linux-x64.tar.xz)\n" + '\n' + 'npm ERR! A complete log of this run can be found in: /tmp/.npm/_logs/2024-09-01T16_42_27_685Z-debug-0.log' } At this point I thought there was a failure - but then I was able to run systemctl restart xo-server.service and access both the current web UI and the v6 UI. I'm interested in trying the newer v6 features, so I just changed from the stable channel to latest using the web UI and ran upgrade - but it gave me an error: 9/1/2024, 1:02:48 PM: New versions available: 9/1/2024, 1:02:48 PM: xoa-updater 0.50.1 (0.50.0 installed) 9/1/2024, 1:02:48 PM: Downloading packages... 9/1/2024, 1:02:49 PM: xoa-updater 0.50.1 ....................................................................................................................................................................................... ok ✔ 9/1/2024, 1:02:49 PM: Installing packages... 9/1/2024, 1:03:02 PM: Saving current updater version in /usr/local/lib/node_modules/xoa-updater-previous ...ok ✔ 9/1/2024, 1:03:03 PM: xoa-updater ✔ 9/1/2024, 1:03:14 PM: xoa-updater ✔ 9/1/2024, 1:03:14 PM: Lost connection with xoa-updater 9/1/2024, 1:03:14 PM: xoa-updater could not be reached Using ssh I went back to the command line and ran xoa-updater --upgrade again and this time it is proceeding forward. And now it all works! Very weird. I think I'm in good shape now.
  • Health alerts/alarms

    14
    1 Votes
    14 Posts
    4k Views
    J
    @billcouper I 100% agree with you. I will add to this that it would be amazing if RX and TX nic/SFP errors could be made visible in the interface as well. reason why i mention this is we recently had a problem on one of our hosts storage links where due to a dirty fiber we had some problems (vm's going to read only, crashes, very poor IO). Due to how dom0 sits as a VM we could not get stats off a nic using ethtool or snmp. It took WAY to much trouble shooting to figure out that our issues was caused by a dirty fiber on the servers side. the more native/local self monitoring/alerting xcp-ng and XOA can do, the better.
  • Best Practices XO Location

    5
    0 Votes
    5 Posts
    1k Views
    J
    I do run XOA on its own dedicated host/dedicated pool, so the xcp-ng cpu scheduler does not cause issues with other busy production VM's while backup tasks are happening. this also allows XOA to use 100% of cpu cores making backups (especially with compression on) faster. xoa does DR back up to the primary pool in case something happens to the host its running on.
  • Full backup restore error: Stream_vdi.Invalid_checksum

    14
    0 Votes
    14 Posts
    2k Views
    olivierlambertO
    Yes, you can always export/import the config on a working install. So it's a problem on your build, it's really hard to tell where's the culprit (because you built it, you see why we distribute it via XOA for production/professional usage )
  • XOA Pricing Concerns

    3
    0 Votes
    3 Posts
    740 Views
    Marc.pezinM
    Hello @someone2b, Marc here, CMO of Vates. I wanted to provide some clarity on our new pricing structure and the reasoning behind these changes. Here are a few key points that led to our decision: In 2022, half of the support requests from Xen Orchestra customers were actually related to issues with the hypervisor layer, which aren't covered by standalone Xen Orchestra support. We've seen an increase in requests for XCP-ng support from users who only seek help after encountering issues in their infrastructure. XCP-ng and Xen Orchestra have become deeply integrated, making it increasingly challenging for our team to effectively support Xen Orchestra without also addressing the virtualization platform. We’ve also redesigned our business model to be more equitable, particularly for smaller infrastructures. For those with 10 hosts or fewer, the new pricing is actually lower than the previous cost of purchasing XCP-ng and Xen Orchestra separately. That being said, we didn't forgot as well all the remaining XenServer users out there and we are currently working on to have a secure and affordable path forward for them as well. If you have any questions or would like to discuss this further, please don’t hesitate to reach out to our sales team at sales@vates.tech. Marc
  • Auth LDAP "unable to get local issuer certificate"?

    2
    0 Votes
    2 Posts
    479 Views
    O
    @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.
  • Xenserver 8 Support

    Solved
    4
    0 Votes
    4 Posts
    622 Views
    olivierlambertO
    The doc is now updated: https://xen-orchestra.com/docs/supported_hosts.html
  • Autostart VMs doesn't work

    6
    0 Votes
    6 Posts
    767 Views
    krakenredseaK
    what about xcp center v20, after enabling the checkbox, it can't work like if we enable power_on:true via command line? is xcp center not patched?
  • after a major crash and reload sr introduce

    2
    0 Votes
    2 Posts
    313 Views
    olivierlambertO
    The SR won't store the metadata. Maybe you have a metadata backup saved for this pool?
  • Automatic startup and shutdows VMs at the specified time

    Solved
    10
    0 Votes
    10 Posts
    1k Views
    julien-fJ
    @abudef Indeed, the delay is in milliseconds.