XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • stormiS

      XCP-ng 8.3 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      793
      1 Votes
      793 Posts
      997k Views
      acebmxerA
      @gduperrey ======================================================================================================================================================= Package Arch Version Repository Size ======================================================================================================================================================= Downgrading: kernel x86_64 4.19.19-8.0.46.16.xcpng8.3 xcp-ng-updates 29 M Transaction Summary ======================================================================================================================================================= Downgrade 1 Package Total download size: 29 M Is this ok [y/d/N]: y Downloading packages: kernel-4.19.19-8.0.46.16.xcpng8.3.x86_64.rpm | 29 MB 00:00:07 Running transaction check Running transaction test Transaction test succeeded Running transaction Installing : kernel-4.19.19-8.0.46.16.xcpng8.3.x86_64 1/2 depmod: WARNING: /lib/modules/4.19.0+1/kernel/crypto/authencesn.ko needs unknown symbol memcpy_sglist Cleanup : kernel-4.19.19-8.0.49.3.xcpng8.3.x86_64 2/2 Verifying : kernel-4.19.19-8.0.46.16.xcpng8.3.x86_64 1/2 Verifying : kernel-4.19.19-8.0.49.3.xcpng8.3.x86_64 2/2 Removed: kernel.x86_64 0:4.19.19-8.0.49.3.xcpng8.3 Installed: kernel.x86_64 0:4.19.19-8.0.46.16.xcpng8.3 Updated: forkexecd.x86_64 0:26.1.21-1.4.xcpng8.3 message-switch.x86_64 0:26.1.21-1.4.xcpng8.3 qcow-stream-tool.x86_64 0:26.1.21-1.4.xcpng8.3 rrdd-plugins.x86_64 0:26.1.21-1.4.xcpng8.3 sm-cli.x86_64 0:26.1.21-1.4.xcpng8.3 squeezed.x86_64 0:26.1.21-1.4.xcpng8.3 varstored-guard.x86_64 0:26.1.21-1.4.xcpng8.3 vhd-tool.x86_64 0:26.1.21-1.4.xcpng8.3 wsproxy.x86_64 0:26.1.21-1.4.xcpng8.3 xapi-core.x86_64 0:26.1.21-1.4.xcpng8.3 xapi-nbd.x86_64 0:26.1.21-1.4.xcpng8.3 xapi-rrd2csv.x86_64 0:26.1.21-1.4.xcpng8.3 xapi-storage-script.x86_64 0:26.1.21-1.4.xcpng8.3 xapi-tests.x86_64 0:26.1.21-1.4.xcpng8.3 xapi-xe.x86_64 0:26.1.21-1.4.xcpng8.3 xcp-networkd.x86_64 0:26.1.21-1.4.xcpng8.3 xcp-rrdd.x86_64 0:26.1.21-1.4.xcpng8.3 xenopsd.x86_64 0:26.1.21-1.4.xcpng8.3 xenopsd-cli.x86_64 0:26.1.21-1.4.xcpng8.3 xenopsd-xc.x86_64 0:26.1.21-1.4.xcpng8.3 Complete!
    • C

      XO RBAC Granularity?

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Management
      10
      0 Votes
      10 Posts
      160 Views
      julienXOvatesJ
      Thanks @ataxyanetwork I was about to answer the same...! (but was too busy this morning )
    • olivierlambertO

      šŸ›°ļø XO 6: dedicated thread for all your feedback!

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      315
      7 Votes
      315 Posts
      212k Views
      julienXOvatesJ
      right, we are moving all Backup pages in Administration tab (https://xen-orchestra.com/blog/xen-orchestra-6-10/), but we probably forgot to say we removed this "Backups" tab from the Site view...! Create/restore backup is in progress...!
    • I

      Windows Server 2025 VM randomly freezes/hangs (loss of VNC + RDP + console) on XCP-ng — reboot required

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      5
      0 Votes
      5 Posts
      427 Views
      I
      @gudge25 check these https://docs.xcp-ng.org/vms/#enabling-viridian-extensions and https://lazyadmin.nl/it/september-2026-update-break-rds-how-to-fix/
    • olivierlambertO

      XOSTOR hyperconvergence preview

      Watching Ignoring Scheduled Pinned Locked 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 ā”Š ╰───────────────────────────────────────────────────────────────────╯
    • C

      Auth LDAP Plugin "Could Not Authenticate User"

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Management
      3
      1 Votes
      3 Posts
      76 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!
    • O

      Rolling pool update

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      10
      0 Votes
      10 Posts
      279 Views
      C
      @Octopuss Indeed! Looking to implement this in my org, so am testing out all kinds of things. Cheers!
    • I

      NVIDIA H200 GPU Support on XCP-ng – PCI Passthrough, vGPU and VRAM Allocation

      Watching Ignoring Scheduled Pinned Locked Moved XCP-ng
      2
      1 Votes
      2 Posts
      56 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.
    • C

      Bringing container visibility back to XO - Docker experimental integration

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra docker container
      19
      1
      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?
    • C

      Booting Homeassistant (HAOS) Image breaks VM

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Compute
      3
      0 Votes
      3 Posts
      229 Views
      C
      Hey Poddingue! I very much assume to have found the troublemaker. I compared the outputs of xe vm-param-list and what triggered my eyes the most was: Debian: PV-drivers-version (MRO): HA: PV-drivers-version (MRO): major: @PRODUCT_MAJOR_VERSION@; minor: @PRODUCT_MINOR_VERSION@; micro: @PRODUCT_MICRO_VERSION@; build: @NUMERIC_BUILD_NUMBER@ Ofc what's reported after a HomeAssistant boot is completely nuts and should be "nothing"/empty. As the errorlog of Commvault says something about XenSDKWrapper, I'm unsure if the errorhandling of the SDK or Commault sucks (should I be happy that it was caught at all and didn't crash the whole application? ). The German translation, to me, indicateds Commvault at faul though. Neither XCP-ng nor the XenSDK will be able to speak english, nor is it likely that they translate a "try-catch"-errormessage, I assume. BUT: XCP-ng should never report back such nonsense and by that probably hit Commvault unexpected. So I also suggest to catch nonsense/unclear responses before XAPI (which is what xe triggers?) output/response.
    • julien-fJ

      [Security] VSA-2026-062: critical Xen Orchestra vulnerability fixed, please update

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      1
      4 Votes
      1 Posts
      130 Views
      No one has replied