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
    • P

      XO5 breaks after defaulting to XO6 (from source)

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      36
      1
      0 Votes
      36 Posts
      348 Views
      A
      @mathieura Maybe this has something to do with the script i used to install xo but i can not get v6 to be the default. The links going from v6 to v5 work but just defaults to v5 and accessing. i use port 443 for xo and i do use a proxy. from the config.toml file [http.mounts] 164 # Uncomment to setup a default version. 165 # Otherwise, XO5 will be the default for stable channel and XO6 for latest and source 166 # '/' = '../xo-web/dist/' 167 168 '/' = '../xo-web/dist/' 169 '/v6' = '../../@xen-orchestra/web/dist/' 170 171 [http.proxies] 172 # [port] is used to reuse the same port declared in [http.listen.0] 173 '/v5/api' = '[protocol]//localhost:[port]/api' 174 '/v5/api/updater' = 'ws://localhost:9001' 175 '/v5/rest' = 'http://localhost:[port]/rest' [image: 1765927899950-screenshot-2025-12-16-183125.png] this config breaks everything. Nothing works. [http.mounts] 164 # Uncomment to setup a default version. 165 # Otherwise, XO5 will be the default for stable channel and XO6 for latest and source 166 # '/' = '../xo-web/dist/' 167 168 '/v6' = '../xo-web/dist/' 169 '/' = '../../@xen-orchestra/web/dist/' 170 171 [http.proxies] 172 # [port] is used to reuse the same port declared in [http.listen.0] 173 '/v5/api' = '[protocol]//localhost:[port]/api' 174 '/v5/api/updater' = 'ws://localhost:9001' 175 '/v5/rest' = 'http://localhost:[port]/rest' Original config [http.mounts] 164 # Uncomment to setup a default version. 165 # Otherwise, XO5 will be the default for stable channel and XO6 for latest and source 166 # '/' = '../xo-web/dist/' 167 168 '/v5' = '../xo-web/dist/' 169 '/v6' = '../../@xen-orchestra/web/dist/' 170 171 [http.proxies] 172 # [port] is used to reuse the same port declared in [http.listen.0] 173 '/v5/api' = '[protocol]//localhost:[port]/api' 174 '/v5/api/updater' = 'ws://localhost:9001' 175 '/v5/rest' = 'http://localhost:[port]/rest'
    • B

      New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client

      Watching Ignoring Scheduled Pinned Locked Moved News
      5
      1
      1 Votes
      5 Posts
      34 Views
      G
      @benapetr Pretty cool project, might be handy to learn to work with this. Question: Will it run on a raspberry pi with a 1280x720 display? Specifically a Clockwork Pi uConsole with CM4 Rpi module with 8gb or ram. That's my emergency computing device for when things fail, only thing it is missing is a kvm to USB module to look at BIOS on a server.
    • H

      Unable to MIgrate VDI when host is low on free memory

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      5
      0 Votes
      5 Posts
      33 Views
      nikadeN
      You say you're trying to migrate a vdi, where are you trying to migrate it? To a SR attached to your current host or to another host/pool? If you're trying to migrate it to another host/pool this is something that i've seen as well when dom0 is not assigned enough RAM, we usually gave them 16Gg which seemed to resolved these kind of issues back when we were running 8.2.0.
    • L

      XCP-ng 7.5 -> 8.3: Best VM Migration Path?

      Watching Ignoring Scheduled Pinned Locked Moved Migrate to XCP-ng
      3
      0 Votes
      3 Posts
      31 Views
      L
      @olivierlambert Thanks for the tip — it’s a very interesting mechanism. I’m going to read the docs now
    • olivierlambertO

      🛰️ XO 6: dedicated thread for all your feedback!

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      60
      5 Votes
      60 Posts
      2k Views
      P
      @olivierlambert nice, better than megathreads ! added my first TAG demand on it
    • V

      Can't designate new master on XO source pool

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      1
      0 Votes
      1 Posts
      6 Views
      No one has replied
    • P

      Ansible Role - Install XO from source - Now available

      Watching Ignoring Scheduled Pinned Locked Moved Infrastructure as Code
      5
      3 Votes
      5 Posts
      330 Views
      M
      @probain Your role seems to neither install or pin node js itself so it does not fully follow the official steps from Xen Orchestra docs. Xen Orchestra docs state to use LTS node js - installing it is something that the the ronivay XO script does. Due to this part missing in your role it can not be executed on a freshly provisioned VM, something that is not really best practice. A role that was made for the purpose of deploying a software should also install / manage it's dependencies. Other than that, thanks for sharing your role. Every contribution towards this community is great IMO.
    • stormiS

      XCP-ng 8.3 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      298
      1 Votes
      298 Posts
      116k Views
      stormiS
      New security and maintenance update candidate for you to test! A hardware issue was found in AMD Zen 5 CPU devices, related to how random numbers are generated. It's best fixed via a firmware update, but we also provide updated microcode to mitigate it, and Xen is updated to support loading the newer microcode. We also publish other non-urgent updates which we had in the pipe for the next update release. Security updates: amd-microcode: This release fixes vulnerability CVE-2025-62626 in AMD Zen 5 CPUs microcode that may generate excessive number of zeros in random outputs, potentially compromising cryptographic security. xen: Introduce support for the new Linux AMD microcode container format (multiple blobs per CPU), Address the XSA-476 vulnerability (CVE-2025-58149), low severity on XCP-ng (affects an unsupported feature of Xen) Enable passthrough of devices on non-zero PCI segments. Improve performance of resumed or migrated VMs by supporting superpage restoration Fix detection of the Self Snooping feature on capable Intel CPUs gpumon, xcp-featured: rebuilt for updated XAPI qemu: Synchronize with XenServer's fix for the Windows Server 2025 NVMe write cache issue that we fixed previously Fix device passthrough with devices in a PCI segment different from 0 sm: Upstream changes: Robustify CBT enable/disable calls to prevent errors. Various fixes regarding SCSI commands/functions. Add tolerance in the GC during leaf coalesce. Improves GC logging and corrects rare race conditions. Our changes Use serial instead of SCSI ID for SR on USB devices to prevent bad match. Explicit error message during LVM metadata generation when VDI type is missing. Correct and robustify LINSTOR deletion algorithm to manage in-use volumes. Avoid throwing LINSTOR exceptions in case of impossible temporary volume deletion in order to properly terminate higher-level API calls. Prevent XOSTOR operations if LINSTOR versions mismatches on a pool. varstored: Restore and update the default dbx for new VMs. That's the main change for users: we now embed the latest UEFI certificates with XCP-ng, making pools ready for secure boot out of the box. We'll update the documentation to explain how to handle the transition for existing pools (ranging from "nothing to do" to "do something to ensure that future certificate updates become automatically the pool's default). Fix the format of the default included KEK/db/dbx to ensure safe updates Fix an issue with UEFI variable length limit xapi: Support up to 16 VIFs (virtual network interfaces) per VM (previously: 7) Runnable metrics: runnable_any runnable_vcpus Various fixes, optimizations, small improvements, and foundational changes (such as getting prepared for a newer version of ocaml) gpumon xcp-featured: rebuild for updated XAPI. xcp-ng-pv-tools: Properly detect Red Hat 10 and its derivatives, when installing the Linux guest agent Update Windows Tools to 9.1.100 xcp-ng-release: fix benign "unary operator expected" error, displayed when connecting from some terminal software xha: Nothing of note, minor changes such as logging typos... xo-lite: version 0.17.0 [VM/New] Fix the default topology by setting the platform:cores-per-socket value correctly (PR #9136) [Host/HostSystemResourceManagement] Fix display when control domain memory is undefined (PR [#9197]) xsconsole: Prepare for a future feature. Optional packages updated: qlogic-netxtreme2-alt: alternate driver for NetXtreme2 updated to version 7.15.24. qlogic-qla2xxx-alt: alternate driver qla2xxx updated to version 10.02.14.01_k Test on XCP-ng 8.3 yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates reboot The usual update rules apply: pool coordinator first, etc. Versions: amd-microcode: 20251203-1.1.xcpng8.3 gpumon: 24.1.0-71.1.xcpng8.3 qemu: 4.2.1-5.2.15.1.xcpng8.3 sm: 3.2.12-16.1.xcpng8.3 varstored: 1.2.0-3.4.xcpng8.3 xapi: 25.33.1-2.1.xcpng8.3 xcp-featured: 1.1.8-3.xcpng8.3 xcp-ng-pv-tools: 8.3-15.xcpng8.3 xcp-ng-release: 8.3.0-35 xen: 4.17.5-23.1.xcpng8.3 xha: 25.2.0-1.1.xcpng8.3 xo-lite: 0.17.0-1.xcpng8.3 xsconsole: 11.0.9.1-1.1.xcpng8.3.3 Optional packages: qlogic-netxtreme2-alt: 7.15.24-1.xcpng8.3 qlogic-qla2xxx-alt: 10.02.14.01_k-1.xcpng8.3 What to test Normal use and anything else you want to test. Test window before official release of the updates 2 days.
    • L

      Coral TPU PCI Passthrough

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      44
      0 Votes
      44 Posts
      14k Views
      andSmvA
      @firereverie Sorry, these last few weeks was very-very busy. So I REALLY hope will do something on this before the december end and come back to you.
    • P

      CBT disabling itself / bug ?

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      5
      1 Votes
      5 Posts
      117 Views
      florentF
      @Pilow I will take a look in deep later, but the key/delta and disk usage is set during backup, even if they are merged during LTR retention