• XOSTOR hyperconvergence preview

    Pinned Moved XOSTOR
    471
    1
    6 Votes
    471 Posts
    1m Views
    Maelstrom96M
    @dthenot For anyone stuck, here is what I ended up doing: I've manually hardcoded the controller_uri in /opt/xensource/sm/linstorvolumemanager.py on the new host, restarted the toolstack using xe-toolstack-restart and ran the xe host-call-plugin host-uuid=NEW_HOST_UUID plugin=linstor-manager fn=addHost args:groupName=linstor_group/thin_device command. def _get_controller_uri() -> str: # TODO: Check that an IP address from the current pool is returned. #addresses = _get_controller_addresses() return "linstor://10.25.254.100" #return "linstor://" + addresses[0] if addresses else "" After that, you should see the addHost command return True. It should be safe to revert the change to the _get_controller_uri() function and restart to make sure everything starts properly. [10:06 van3-pprod-xen01 ~]# linstor --controllers 10.25.254.100 node l ╭───────────────────────────────────────────────────────────────────╮ ┊ Node ┊ NodeType ┊ Addresses ┊ State ┊ ╞═══════════════════════════════════════════════════════════════════╡ ┊ van3-pprod-xen01 ┊ COMBINED ┊ 10.25.254.100:3366 (PLAIN) ┊ Online ┊ ┊ van3-pprod-xen02 ┊ COMBINED ┊ 10.25.254.101:3366 (PLAIN) ┊ Online ┊ ┊ van3-pprod-xen03 ┊ COMBINED ┊ 10.25.254.102:3366 (PLAIN) ┊ Online ┊ ┊ van3-pprod-xen04 ┊ COMBINED ┊ 10.25.254.103:3366 (PLAIN) ┊ Online ┊ ╰───────────────────────────────────────────────────────────────────╯ [10:06 van3-pprod-xen01 ~]# xe host-call-plugin host-uuid=f9d94f6c-e826-452f-b9b9-638550b209cf plugin=linstor-manager fn=addHost args:groupName=linstor_group/thin_device True [10:08 van3-pprod-xen01 ~]# linstor --controllers 10.25.254.100 node l ╭───────────────────────────────────────────────────────────────────╮ ┊ Node ┊ NodeType ┊ Addresses ┊ State ┊ ╞═══════════════════════════════════════════════════════════════════╡ ┊ van3-pprod-xen01 ┊ COMBINED ┊ 10.25.254.100:3366 (PLAIN) ┊ Online ┊ ┊ van3-pprod-xen02 ┊ COMBINED ┊ 10.25.254.101:3366 (PLAIN) ┊ Online ┊ ┊ van3-pprod-xen03 ┊ COMBINED ┊ 10.25.254.102:3366 (PLAIN) ┊ Online ┊ ┊ van3-pprod-xen04 ┊ COMBINED ┊ 10.25.254.103:3366 (PLAIN) ┊ Online ┊ ┊ van3-pprod-xen05 ┊ COMBINED ┊ 10.25.254.104:3366 (PLAIN) ┊ Online ┊ ╰───────────────────────────────────────────────────────────────────╯
  • 4 Votes
    1 Posts
    43 Views
    No one has replied
  • XO RBAC Granularity?

    Unsolved Management
    10
    0 Votes
    10 Posts
    158 Views
    julienXOvatesJ
    Thanks @ataxyanetwork I was about to answer the same...! (but was too busy this morning )
  • 🛰️ XO 6: dedicated thread for all your feedback!

    Pinned Xen Orchestra
    314
    7 Votes
    314 Posts
    211k Views
    acebmxerA
    @Greg_E said: @coolsport00 Not spinning, but the backups tab is gone, It was really only good to see the green check marks or red x, but gone as of the update I did about 24 hours. I didnt notice the backup tab missing at first but also for me. Edit - Found [image: Screenshot 2026-11-10 101330.png]
  • XCP-ng 8.3 updates announcements and testing

    Pinned News
    791
    1 Votes
    791 Posts
    995k Views
    F
    Installed on my test hosts, no issues.
  • 0 Votes
    4 Posts
    411 Views
    D
    Hello, The hang bug will be fixed in a future release of Xen, but Windows requires enabling all Viridian extensions (currently 6) to ensure optimal performance and reliability. Enabling Viridian extensions also fixes the hang bug via a different way. On Windows guests, please reenable all Viridian extensions using these instructions: https://docs.xcp-ng.org/vms/#enabling-viridian-extensions
  • Auth LDAP Plugin "Could Not Authenticate User"

    Unsolved Management
    3
    1 Votes
    3 Posts
    74 Views
    C
    Hi @poddingue ..yes, I have quite a few 'requests' I need to post in there...I just have yet to do so Thanks!
  • Rolling pool update

    Xen Orchestra
    10
    0 Votes
    10 Posts
    270 Views
    C
    @Octopuss Indeed! Looking to implement this in my org, so am testing out all kinds of things. Cheers!
  • 1 Votes
    2 Posts
    55 Views
    poddingueP
    For the partitioning part, the docs say NVIDIA vGPU isn't supported on XCP-ng, since it depends on a proprietary XenServer component that can't be redistributed: https://docs.xcp-ng.org/compute#vgpu. So as far as I can tell, the "20, 40 or 80 GB per VM" split won't work through vGPU. Passing a whole GPU to one VM is the documented path, on the same page. I haven't seen anyone report on H100 or H200 cards here, though, so I can't tell you if that class of card brings its own surprises. There's also a blog post doing LLM inference that way on a much smaller Tesla T4: https://xcp-ng.org/blog/2025/07/28/your-own-gpu-powered-llms-with-xcp-ng/. There's an open design discussion upstream in XAPI about GPU partitioning, MIG included (https://github.com/xapi-project/xen-api/pull/7260), but that's the XenServer side, and I don't know if or when it would reach XCP-ng. As GPU partitioning matters for your project, it might be worth opening a request on https://feedback.vates.tech/ with what you described here (H200s, LLM inference, several tenants per card, fixed VRAM per VM). From what I've seen, a concrete use case like yours carries more weight there than a plain "please support vGPU", and other people needing the same thing can vote on it.
  • 0 Votes
    19 Posts
    2k Views
    J
    @nathanael-h I know you're suuuper early in your process. But would it be possible to have podman be an alternative to Docker too?
  • XCP-ng Windows PV tools announcements

    Moved News
    117
    0 Votes
    117 Posts
    63k Views
    D
    Hello all, Version 9.2.445 of the XCP-ng Windows Guest Tools has been released. Download the latest release here: https://github.com/xcp-ng/win-pv-drivers/releases This release brings important bug fixes to the Windows drivers and installer. Important note for users upgrading from 9.2.350: You must first install the XenTools-fix-9.2.351.msp hotfix to upgrade to 9.2.351 before installing 9.2.445. Otherwise, upgrades from 9.2.350 will be blocked. Reboot is not required after installing the hotfix. The installer downloads include a copy of XenClean and XenBootFix. It is not necessary to run XenClean when upgrading from previous versions of the XCP-ng Windows guest tools, unless prompted by the installer. Remember to carefully read XenClean docs before use. Note: Always download the latest XenClean/XenBootFix from https://github.com/xcp-ng/win-pv-drivers/releases . You can find them in the latest release ZIP/ISO archives. Before installing Thank you for using our Windows PV tools. Please carefully read the instructions below. It is not necessary to run XenClean when upgrading from previous versions of the XCP-ng Windows guest tools, unless prompted by the installer. Not compatible with the "Manage Citrix PV drivers via Windows Update" option. You must disable this option before installing. Changes since 9.2.385 NEW: Group Policy support (see the extras/admx directory in the source code tree). Supported policies include: Hide the tray icon Disable all features that allow controlling the VM from the host Improved: Better network performance. Improved: System reliability improvements on driver upgrade failure. On an upgrade failure, the installer will remove all Xen drivers to ensure that the system will keep operating, and to allow you to safely uninstall the existing driver package. Improved: Remove obsolete Windows Update devices and don't block installation because of them. Fixed: Fix further data corruption bugs during memory snapshots and backups. This driver version significantly narrows the corruption window. However, fully fixing all known corruption issues requires further work in other XCP-ng components. Please keep an eye on the XCP-ng blog for updates. Fixed: Fix loss of VBD connection after storage migration. Fixed: Improve reliability of the clipboard service. Fixed: Improve reliability of the VIF IP configuration feature. Fixed: Reliability fixes on VMs with many vCPUs (>64). Fixed: Many other driver reliability fixes. Help / Community support If you encounter installation/uninstallation errors, please try again with one of the following commands: For installing: msiexec.exe /i XenTools-x64.msi /l*vx install.log For uninstalling: msiexec.exe /x XenTools-x64.msi /l*vx uninstall.log Please include this log along with the file C:\Windows\INF\setupapi.dev.log in your bug report. These files will help us troubleshoot any installation issues. Additionally, please report any errors or BSOD you encounter during testing of this release. Your feedback is very appreciated.
  • Bug in XO-Lite GUI / VM Creation

    Unsolved XO Lite
    3
    1
    0 Votes
    3 Posts
    119 Views
    C
    @poddingue Yes, reads pretty much like the same error / root cause.
  • 0 Votes
    8 Posts
    240 Views
    F
    @poddingue Taking the time to do this it's the bare minium! Here you go: https://github.com/vatesfr/xen-orchestra/issues/10741
  • Missing vdi which is a base for a delta

    Unsolved Backup
    11
    0 Votes
    11 Posts
    649 Views
    poddingueP
    Thanks, that helps. Some VMs fail to the Synology but pass to S3, and some the other way round. So I think the backups on Ark are probably fine (they pass health checks, as you said at the start) and it has more to do with what each target already holds, but I could be wrong. I'd also flag the several delta jobs with different retentions all feeding Ark, I just don't know the mirror code well enough to say whether that matters. @Team-XO-Backend, posts 6 and 10 have the log and the pattern if someone gets to this one.
  • 0 Votes
    4 Posts
    233 Views
    poddingueP
    @mdm thanks for checking Reconnect. If I'm reading the code right, both actions have the same mistake, so one fix should cover both. You already wrote the steps out in your first post, so if you're up for it, an issue on https://github.com/vatesfr/xen-orchestra/issues would put it where the frontend team tracks their work. Their bug form asks for the XO version (or commit if you're on sources) plus your Node and XCP-ng versions, which I don't know for your setup.
  • 0 Votes
    7 Posts
    673 Views
    Bastien NolletB
    Hello @ludalm13, Thanks for your contribution and sorry for not giving an answer earlier. We initially planned to review your PR while doing some additional work on the audit plugin, but our planning evolved and that work was postponed. We'll review your PR in the following days.
  • Backup failures with odd connection refused errors

    Unsolved Backup
    8
    0 Votes
    8 Posts
    840 Views
    C
    Just as an update on this. Did get the migrations working. Still haven't gotten the backups working. Pool is still stable otherwise. Have managed to get backups by using Veeam so it's not to much of a problem.
  • Version 9 already ;0)

    Xen Orchestra
    2
    1
    0 Votes
    2 Posts
    154 Views
    poddingueP
    Thanks for the information, @ph7 . That's a typo, for sure.
  • Native Ceph RBD SM driver for XCP-ng

    Development
    42
    3 Votes
    42 Posts
    11k Views
    dicode-nlD
    @nick.lloyd that's something out of this plugin, that's ceph native. most clusters should run on msgr2 native. which ceph versions are you running?
  • Veeam and XO backup CBT. How to avoid conflict?

    Unsolved Backup
    7
    0 Votes
    7 Posts
    420 Views
    poddingueP
    @zorro So with purge off, Veeam stayed clean for a few nights, which fits what I saw in the lab test. If I read the docs right, the cost is that XO's reference snapshot keeps its data on the SR again, which you'd notice more on thick-provisioned storage: https://docs.xen-orchestra.com/backups-and-dr/backup-types/incremental_backups#purge-snapshot-data-cbt. Storage hasn't said yet whether purge breaking another tool's chain is expected, so I'd still call this a workaround rather than the answer. If a CBT warning comes back when you add the other VMs, the Veeam task id and the time would probably help them. And keeping both makes sense to me, since Veeam doesn't do the cross-site replication you need XO for.