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 [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
  • Commit Number Not Updating?

    5
    2
    0 Votes
    5 Posts
    596 Views
    A
    @Danp Sorry for the delay, in the end I waited for a nother commit to come out and update to it, once I'd done so the issue was fixed. Thanks for your help either way.
  • "Xenserver 8" with PVS Accelerator showing Full Orphan VDIs

    Solved
    7
    0 Votes
    7 Posts
    1k Views
    M
    Hi @infecticide, the fix for this issue has been been merged and will be available in the next release (5.100.1)
  • xoa not show host patch?

    1
    1
    0 Votes
    1 Posts
    145 Views
    No one has replied
  • Storage Bar Graph Misinformation

    Unsolved
    9
    1
    0 Votes
    9 Posts
    1k Views
    T
    I have another weird one. The numeric representative is correct, but the bar graph is unintuitive. [image: 1730944307575-aa347240-cb22-4cde-acb0-ac741e44151a-image.png]
  • Encrypt Server Passwords

    13
    0 Votes
    13 Posts
    3k Views
    J
    @olivierlambert said in Encrypt Server Passwords: I'm not saying it's not possible, I'm saying this will be at the huge expense of usability. One such software implementation of a KMIP protocol server, which is in software form is an open source fork of HashiCorp Vault. This open source fork is called OpenBao (https://openbao.org/).
  • XOA / XCP-ng NTP?

    4
    0 Votes
    4 Posts
    1k Views
    olivierlambertO
    I think on recent XOA we even switched to systemd-timesyncd. Pinging @thomas-dkmt so he can update the doc to fix it (only the new doc directly! oh and you can ask @julien-f for details if needed, thanks!).
  • Is it possible to do this with VM list filters?

    Solved
    6
    0 Votes
    6 Posts
    696 Views
    J
    @Danp You're right, I missed the question mark on it when I tried it before. With the question mark, it works. Thank you for your help.
  • Logs Partition Full

    59
    0 Votes
    59 Posts
    37k Views
    X
    How can I determine which VM is causing this problem? Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830066:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830198:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830311:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830458:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830605:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830712:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830797:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830885:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831006:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831094:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831185:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831260:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831333:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831407:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831478:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831551:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.884264:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.884519:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.884615:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.884721:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.923891:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924054:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924207:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924319:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924505:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924675:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924803:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924913:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927026:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927185:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927303:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927436:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927657:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927772:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927903:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927993:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.928136:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.928255:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.928396:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.928479:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.932786:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.932906:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017)
  • Bug?? Tree view XO v6

    Solved
    3
    1
    0 Votes
    3 Posts
    372 Views
    P
    @Danp Yes of course You are correct I moved it to local storage a few weeks ago My bad
  • Filtering multiple hosts by name

    Solved
    5
    0 Votes
    5 Posts
    690 Views
    olivierlambertO
    That's the right way, yes Enjoy!
  • Building Xen Orchestra 6 from scratch

    2
    0 Votes
    2 Posts
    469 Views
    olivierlambertO
    Hi, From the XO root folder, just do a yarn run turbo run build --filter @xen-orchestra/web and then access the XO URL with /v6 in the end.
  • [SOLVED] Missing Plugins

    2
    0 Votes
    2 Posts
    360 Views
    L
    @llabtaem This issue has been resolved. I just needed to rebuild Xen Orchestra after adding the symbolic links. Then the plugins registered and I can now see them in the console.
  • Error restore backup

    7
    0 Votes
    7 Posts
    816 Views
    humitoH
    @olivierlambert said in Error restore backup: No I mean the file level restore feature from XO. If it all worked, I'm curious to understand why you had this issue in the first place. Did you restore the entire chain? We had to restore the entire VM as a new instance from Xen Orchestra using the delta backup. However, the same error occurred with each restore point. So, we manually copied the backup files from XOA and imported them.
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    5 Views
    No one has replied
  • Forgot password for the webgui

    11
    0 Votes
    11 Posts
    3k Views
    J
    @peder Thanks, it works
  • Free Xen Orchestra?

    15
    0 Votes
    15 Posts
    18k Views
    olivierlambertO
    Thanks for your feedback, we'll improve the doc.
  • XOA says not up to date after 8.3 upgrade

    4
    0 Votes
    4 Posts
    618 Views
    olivierlambertO
    Check your NTP is correctly configured. For the rest, it works then
  • XCP-ng Tools Storage contains VDIs I’m unable to Destroy

    Solved
    9
    0 Votes
    9 Posts
    1k Views
    M
    @gduperrey said in XCP-ng Tools Storage contains VDIs I’m unable to Destroy: It seems that it is possible to clean old isos manually, via the command line, as explained in this forum post: https://xcp-ng.org/forum/post/15703 Wau!!! That actually works like charm! Thank you sooooo much!
  • Xen Orchestra has stopped updating commits

    26
    0 Votes
    26 Posts
    8k Views
    A
    That happens to me about once every six weeks on one of the XO installs. For what its worth, if I just kill the XO vm and let it reboot, as long as its not out of disk space, it always works the second time.
  • Project Pyrgos

    12
    0 Votes
    12 Posts
    4k Views
    olivierlambertO
    We had to reorg a bit the team, with the creation of an internal devops team. We hope to get some cool news in the following months