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
      803
      1 Votes
      803 Posts
      1m Views
      vxgmichelV
      New maintenance update candidates for XCP-ng 8.3 LTS This batch of updates contains security fixes, new Windows guest tools, and other improvements. It also changes some defaults of the SSH server: read the OpenSSH section before you update. What changed Virtualization guest-templates-json: Sync with XenServer guest-templates-json-2.0.17-1. New guest template: Ubuntu Resolute Raccoon 26.04. The Rocky Linux 10 template does not change (15 GB default disk). swtpm: This release contains a fix for CVE-2026-75900, an out-of-bounds read in the swtpm daemon that could cause a crash of the daemon. xcp-ng-pv-tools: Update to XCP-ng Windows Guest Tools 9.2.445. Remove the XenTools-fix-9.2.351.msp hotfix tool for users of 9.2.350. xen: This release is a synchronization with XenServer release 4.17.7-6. It contains the patches for XSA-524 and XSA-525, and a fix for lost timer interrupts. It also fixes a bug in the original XSA-524 fix where the IOMMU device table size on AMD systems was always set to 2 MiB. System gnutls: Update to gnutls 3.8.12. This update fixes multiple vulnerabilities, including CVE-2026-3833. libssh2: Update libssh2 to fix five security vulnerabilities. They affect the SFTP/SCP connections that curl and Midnight Commander (mc) make: CVE-2026-58051: potential arbitrary free when listing public keys CVE-2026-66032: use-after-free in SFTP CVE-2026-66033: out-of-bounds read/write with the AES-GCM cipher CVE-2026-66034: out-of-bounds read when listing public keys CVE-2026-66035: heap buffer overflow during ETM (Encrypt-then-MAC) decryption nettle: Update to nettle 3.10. Sync with XenServer nettle-3.10-3, which includes a fix that XCP-ng released previously. openssh: Update to OpenSSH 9.9p1. This update fixes 21 CVEs: CVE-2026-3497, CVE-2026-35386, CVE-2026-35387, CVE-2026-55653, CVE-2026-55654, CVE-2026-55655, CVE-2026-59995, CVE-2026-59996, CVE-2026-59997, CVE-2026-59999, CVE-2026-60000, CVE-2026-60001, CVE-2026-60002, CVE-2026-73281, CVE-2026-73282, CVE-2026-73283, CVE-2026-106552, CVE-2026-106553, CVE-2026-106582, CVE-2026-106583, CVE-2026-106585. Post-Quantum Key Exchange is now available. It is the preferred key exchange by default. FIDO2 keys are now available, but they are disabled by default. See Enabling FIDO2 keys. The SSH client now reads drop-in files in /etc/ssh/ssh_config.d/. Fix a temporary lockout with ssh-copy-id. We hardened the SSH server configuration with our security team. Some changes modify how existing configurations work: sshd refuses SSH user certificates by default. If you log in with certificates, follow SSH user certificates before the update, or you will lose SSH access. Forwarding is limited to the host itself (VNC console and XO Lite/XAPI tunnels continue to work). See Forwarding. MaxAuthTries is now 3, LoginGraceTime is now 60 seconds, and PerSourcePenalties (brute-force protection) is enabled. See What you can safely customize. sshd no longer accepts hmac-sha1 and ssh-rsa (SHA-1). Very old SSH clients can fail to connect. The update restarts sshd and replaces /etc/ssh/sshd_config. Put your changes in drop-in files: see Do not edit our configuration files. openssl: Update to openssl 3.5.7. This is a security update that fixes multiple CVEs, including one rated High (CVE-2026-45447, heap use-after-free in PKCS7_verify()). It also contains a fix for CVE-2026-72897. See the openssl vulnerabilities page for more information. samba: Sync with XenServer: update samba to 4.23.3, to support LDAPS and the Windows security hardening. xcp-ng-deps: Remove ldns and unbound-libs as they are not used (this avoids the frequent security updates of these packages). New and updated dependencies of gnutls 3.8, samba 4.23 and OpenSSH FIDO2 support: libcbor, libfido2, libidn2, libtalloc, libtdb, libtevent. Rebuilds with the updated gnutls: wget, and the optional neon, nut and nbdkit. Control Plane xapi: Fix an RPU that could stop in some cases, because xapi lost track of an event. Improve performance for storage migrations with snapshots, with a fix of the migration order. Support adding SSL certificates signed with SHA384. Fix SM plugins that xapi registered twice. This broke SR functions. Fix migration of VDIs with tags to SRs that are not plugged on the source host. Fix incomplete VDI cleanup when HA is disabled while a host is fenced. Fix a host that could stop when it joins the pool, because of a dangling reference. sdn-controller: Add reliability fixes, make sure that xapi applies the rules. This update contains many storage-related changes. We tested each change alone, but not all together. Please test your storage operations. xcp-python-libs: Sync with XenServer xcp-python-libs-3.0.11-1. xha: Fix a potential memory access crash during the activation step. Storage blktap: This release contains 2 performance improvements and 2 important fixes: The NBD server of tapdisk does fewer memory allocations. This improves VDI migrations. The polling algorithm of tapdisk sends fewer notifications. This improves the performance in polling mode. Fix a possible VDI inconsistency with Windows VMs, when the Windows driver reconnects a stalled ring. Fix a possible local data corruption during a storage migration with CBT enabled. nbd: Update to nbd 3.25 (sync with XenServer). sm: Fix LINSTOR VDI locking failing during a transient state, which could prevent a user from executing a VDI command. LINSTOR SR scans are now ~35% faster (e.g. ~1m08s down to 44s on a host with 950 VDIs in our tests). Fix diskless LINSTOR resources being cleaned up even though they are still in use. Fix an issue on LVM SRs that could block VDI activation of QCOW2 VDIs on a non-coordinator host. Fix incremental backup failures (SR_BACKEND_FAILURE_460) with CBT on file-based SRs. Clean up gc_running_file on GC exception so that operations on the SR can continue after the GC error. Network Optional packages libreswan: Remove DNSSEC support. This allows us to remove ldns and avoid the frequent security updates of this package. UI xo-lite: [New network] Choose between no NBD, secure NBD and insecure NBD (not encrypted) when creating a network (PR #10540) [VM/System] Fix video RAM displayed in bytes instead of MiB (PR #10486) [Treeview] Add a search bar and virtualize the tree (PR #10414) [New/VM] Hide guest tools ISO SR in new VM ISO selector (PR #10430) [Host] Add possibility to enable/disable a host (PR #10337) [Host] Add possibility to restart a host toolstack (PR #10480) [Host] Add possibility to detach a host (PR #10520) [Side panels] Harmonize card titles across side panels (PR #10289) [VM/New] Fix UEFI VMs booting in BIOS mode when created with a network install or without disk (PR #10521) [Treeview] Press Ctrl+K (Cmd+K on macOS) to focus the treeview search (PR #10492) [Pool] Fix connection, stats and consoles when overriding the pool master with ?master=: use HTTPS by default instead of the protocol and port of the page (PR #9955) [Pool/Host/VM] Add copy button for multiple information on Host/VM Dashboard and Pool/Host/VM System tabs (PR #9976) [New/VM] Fix MAP_DUPLICATE_KEY error that could randomly prevent the VM creation (PR #10552) [Host/Network] Add the possibility to forget a PIF (PR #10239) [Lite] Display dates and times as YYYY-MM-DD HH:mm:ss (PR #10547) [Pool/Hosts] Add a side panel displaying the selected host's details, and a search bar to filter the hosts table (PR #10580) [VM/Host] Add console clipboard management (PR #10625) [VM/Network] Add the possibility to edit a VIF (PR #10505) Drivers and Firmware amd-microcode: Update to the 2026-10-01 AMD microcode drop as redistributed by XenServer. Updated CPUs: GN-B1 00a00f11: 2025-04-18, rev 0a0011de -> 2026-06-19, rev 0a0011e1 GN-B2 00a00f12: 2025-03-27, rev 0a001247 -> 2026-06-19, rev 0a00124e RS-B1 00a10f11: 2025-06-09, rev 0a101158 -> 2026-07-06, rev 0a10115b RS-B2 00a10f12: 2025-06-12, rev 0a101253 -> 2026-07-01, rev 0a10125b RSDN-A2 00aa0f02: 2025-06-12, rev 0aa0021c -> 2026-07-06, rev 0aa0021f cisco-enic: Update to 4.7.0.6 (sync with XenServer). Add SR-IOV v2 support with PF/VF mailbox communication and lifecycle management. Add administrative queue support and improve queue/IRQ handling. Improve PF/VF link-state, MTU, shutdown, and SR-IOV teardown handling. This is a large update of the driver. If you have Cisco hardware that uses enic, please test it. intel-microcode: This update installs the Intel IPU 2026.4 microcode from the XenServer 20260929-1 release. mellanox-mlnxen: Fix ConnectX-4 Ethernet and RDMA devices that the driver did not register correctly. Optional packages r8125-module-alt: New alternative driver (Realtek 9.018.00). Various bug fixes for 2.5G Realtek NICs. It does not support the 5G devices: use the main driver for them. Versions amd-microcode: 20260923-1.1.xcpng8.3 -> 20261001-2.1.xcpng8.3 blktap: 3.55.5-12.3.xcpng8.3 -> 3.55.5-12.4.xcpng8.3 cisco-enic: 4.5.0.7-1.xcpng8.3 -> 4.7.0.6-1.1.xcpng8.3 gnutls: 3.3.29-10.2.xcpng8.3 -> 3.8.12-1.1.xcpng8.3 gpumon: 24.1.0-99.1.xcpng8.3 -> 24.1.0-100.1.xcpng8.3 guest-templates-json: 2.0.16-1.1.xcpng8.3 -> 2.0.17-1.1.xcpng8.3 intel-microcode: 20260925-1.xcpng8.3 -> 20260929-1.xcpng8.3 libcbor: 0.11.0-3.1.xcpng8.3 libfido2: 1.14.0-7.1.xcpng8.3 libidn2: 2.3.4-4.xcpng8.3 libssh2: 1.11.0-1.xcpng8.3 -> 1.11.0-1.2.xcpng8.3 libtalloc: 2.1.16-1.el7 -> 2.4.3-1.1.xcpng8.3 libtdb: 1.3.18-1.el7 -> 1.4.14-1.1.xcpng8.3 libtevent: 0.9.39-1.el7 -> 0.17.1-1.xcpng8.3 mellanox-mlnxen: 5.9_0.5.5.0-3.1.xcpng8.3 -> 5.9_0.5.5.0-3.2.xcpng8.3 nbd: 3.24-1.xcpng8.3 -> 3.25-2.1.xcpng8.3 nettle: 2.7.1-9.el7_9 -> 3.10-3.1.1.xcpng8.3 openssh: 9.8p1-1.2.6.xcpng8.3 -> 9.9p1-33.2.xcpng8.3 openssl: 3.5.5-1.3.xcpng8.3 -> 3.5.7-1.1.xcpng8.3 rpm: 4.11.3-32.el7 -> 4.11.3-32.1.xcpng8.3 samba: 4.10.16-25.3.xcpng8.3 -> 4.23.3-1.1.xcpng8.3 sm: 3.2.12-25.2.xcpng8.3 -> 3.2.12-25.3.xcpng8.3 swtpm: 0.7.3-12.1.xcpng8.3 -> 0.7.5-1.xcpng8.3 wget: 1.21.4-1.1.xcpng8.3 -> 1.21.4-1.2.xcpng8.3 xapi: 26.1.21-1.4.xcpng8.3 -> 26.1.23-2.1.xcpng8.3 xcp-featured: 1.2.1-6.xcpng8.3 -> 1.2.1-7.xcpng8.3 xcp-ng-deps: 8.3-14 -> 8.3-16 xcp-ng-pv-tools: 8.3-19.xcpng8.3 -> 8.3-21.xcpng8.3 xcp-python-libs: 3.0.10-1.1.xcpng8.3 -> 3.0.11-1.1.xcpng8.3 xen: 4.17.7-4.2.xcpng8.3 -> 4.17.7-6.2.xcpng8.3 xha: 25.2.0-1.1.xcpng8.3 -> 25.2.0-1.2.xcpng8.3 xo-lite: 0.26.0-1.xcpng8.3 -> 0.27.0-1.xcpng8.3 Optional packages fakechroot: 2.20.1-2.el7 http-nbd-transfer: 1.7.0-1.xcpng8.3 -> 1.8.0-1.xcpng8.3 libreswan: 4.12-2.3.3.xcpng8.3 -> 4.12-2.3.4.xcpng8.3 nbdkit: 1.8.0-4.el7 -> 1.8.0-4.1.xcpng8.3 neon: 0.30.0-3.el7 -> 0.30.2-6.1.xcpng8.3 nut: 2.8.0-2.1.xcpng8.3 -> 2.8.0-2.2.xcpng8.3 python3-py: 1.4.32-2.el7 python3-pytest: 2.9.2-5.el7 r8125-module-alt: 9.018.00-1.xcpng8.3 Test on XCP-ng 8.3 Warning: if you log in to your hosts with SSH user certificates, or if you edited /etc/ssh/sshd_config, read the OpenSSH section before the update. yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates reboot # required: new Xen hypervisor, microcode, and drivers The usual update rules apply: pool coordinator first, etc. What to test As usual, normal use and anything else you want to test. These checks help us most: SSH: deploy a public key with ssh-copy-id, then connect with the key. It must work. If you use SSH tunnels (VNC console, XO Lite) or FIDO2 keys, test them too. Storage: enable CBT on the disks of a running VM, migrate the VM with its storage, then run an incremental backup. Also do your usual backups, restores and snapshots. They must complete, and the data must be correct. If you have Cisco hardware that uses the enic driver, make sure that the NICs have link and pass traffic. If you use SR-IOV on them, test it too. If you use XOSTOR, do SR scans and VDI operations. They must complete without errors. If a check fails, tell us the hardware, the VM type, and provide the logs (/var/log/xensource.log, /var/log/SMlog, /var/log/secure). Test window before official release of the updates ~6 days We would like to thank users who shared feedback since our last call for testing: @acebmxer, @Andrew, @XCP-ng-JustGreat, @JeffBerntsen, @hoh, @flakpyro, @robertblissitt, @Greg_E
    • olivierlambertO

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

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      334
      7 Votes
      334 Posts
      228k Views
      coolsport00C
      @julienXOvates Superb Julien. I figured it was in your really long list that you all are working on. Appreciate the response!
    • B

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

      Watching Ignoring Scheduled Pinned Locked Moved News
      66
      1
      9 Votes
      66 Posts
      18k Views
      B
      @clip I don't think this has anything to do with the app though - it's very dense on my systems, I think it's more related to OS theme that he is using, that's why it's so spacy.
    • F

      Xen Orchestra web UI becomes unresponsive when an NFS backup remote goes offline

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Xen Orchestra
      19
      0 Votes
      19 Posts
      898 Views
      poddingueP
      Thanks, both of you, for putting the tests on the GitHub issue (https://github.com/vatesfr/xen-orchestra/issues/10741). Florent and the devs have everything in one place now. @frb94, sorry the NFS side pushed you back to Veeam for the VM backups. I can't promise anything on timing, but I'll keep an eye on the issue and post here if it moves.
    • B

      Missing vdi which is a base for a delta

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      17
      0 Votes
      17 Posts
      901 Views
      B
      And the health check passes. How can that be possible? { "id": "0mwnnmk6y-jd7jumsiui", "start": 1795099050682, "status": "success", "updatedAt": 1795103578854, "tasks": [ { "id": "0mwnnmmmn-jvm3zflms38", "start": 1795099053839, "status": "success", "end": 1795103578854, "result": { "size": 302621130752, "id": "b656b0d4-b575-c805-5738-6fd50d150951", "liveMounts": [] }, "message": "transfer" } ], "end": 1795103578854, "result": { "size": 302621130752, "id": "b656b0d4-b575-c805-5738-6fd50d150951", "liveMounts": [] }, "message": "restore", "data": { "backupId": "dc0a417c-e1cb-4b4b-8fd9-d59e2564999f//xo-vm-backups/fb7fca7d-7355-4a48-f35c-d32c8dfa71ee/20261119T051216Z.json", "jobId": "73d695c7-901b-45bd-94ba-f38682705d35", "srId": "caba922c-ac32-67e8-f83b-a5907d880179", "time": 1795065136373 } }
    • florentF

      V2V in XO 6: a brand new migration wizard, with Auto-pilot docking šŸ›¬

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      15
      5
      0 Votes
      15 Posts
      288 Views
      O
      @jr-m4 hello, thanks for your feedback, I've gathered your feedback and will work with our designer to improve the UX/UI. Thanks again for testing
    • P

      Full backup failure when upgrading XOce

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      13
      0 Votes
      13 Posts
      311 Views
      P
      @acebmxer said: So when you used my script it worked aside from the backup hiccup? Yes, so far what I have tested. Seems like You put some effort int this one, keeping my fingers crossed It' using node v24.22.3
    • O

      Rolling pool update

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      13
      0 Votes
      13 Posts
      681 Views
      J
      @tjkreidl said: @john.c Note that a two-host pool running HA can run into the split-brain issue if one of the hosts fails; it's highly recommended to have at least three hosts in an HA pool (or look into HA-Lizard if running a pool with two hosts and HA). Right but also considering the in development Twinstor for when it goes stable and in production!
    • G

      random backups failing

      Watching Ignoring Scheduled Pinned Locked Moved Solved Backup
      13
      0 Votes
      13 Posts
      718 Views
      G
      OK, marking this solved... It was the phantom reboots causing issues because the tools were not fully installed, only thing I can't understand is why only 2 out of 3 Windows servers would quit. Any way, got the Xen Tools updated and a couple reboots later, everything is working again. Also I can now report that a bug that was fixed maybe a year ago is confirmed to work in my system. The bug was backing up a Windows VM that had a lot of empty space in the drive (over 250GB free) and turning on compression. It would time out counting zeros because it thought the process wasn't doing work. Both of these VMs are now compressing with zstd, one of them is substantially smaller now, the other only shrunk about 20GB. Because of the way Windows uses the drive, these are all full backups. The differential never seemed to be small because Windows does a lot of changes on the drive (there is a post about this somewhere in here from Olivier).
    • B

      Native Ceph RBD SM driver for XCP-ng

      Watching Ignoring Scheduled Pinned Locked Moved Development
      43
      3 Votes
      43 Posts
      12k Views
      A
      @dicode-nl Thank you for the code. I'm in testing now with ceph 20.2.5 and so far I haven't had any issues.
    • coolsport00C

      XO RBAC Granularity?

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

      Slow SR Creation

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Management
      15
      1
      0 Votes
      15 Posts
      1k Views
      I
      @tjkreidl everything looks normal. I also shared SOS report with @goulven I hope I'll get a feedback on slowness.
    • S

      Backup failures after VHD to QCOW2 conversion

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      8
      0 Votes
      8 Posts
      488 Views
      poddingueP
      Thanks for sharing those. I can't read SMlogs well enough to add anything useful myself, so this is really one for @Team-Storage. One thing though: if I read the link right, it expires on 23 November, so it would be good if someone grabbed the files before then.
    • Z

      Veeam and XO backup CBT. How to avoid conflict?

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      7
      0 Votes
      7 Posts
      496 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.
    • A

      Broadcom removed public access to VDDK download links

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Migrate to XCP-ng
      10
      1 Votes
      10 Posts
      2k Views
      olivierlambertO
      FYI, our approach with vectura is only temporary, we have other plans in few months to get rid of this potential cat & mouse game Broadcom could do by slightly change their protocol (without even talking about the potential legal risk with it).
    • 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 ā”Š ╰───────────────────────────────────────────────────────────────────╯
    • F

      Unable to update Windows PV driver

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Management
      6
      4
      0 Votes
      6 Posts
      408 Views
      D
      @fred974 Hello, Could you please provide the logs produced by XenClean after its execution? If your VM couldn't boot after XenClean, XenBootFix executed from a recovery environment should get your VM working again. Instructions are available here: https://docs.xcp-ng.org/troubleshooting/windows-pv-tools/#windows-fails-to-boot-hangs-inaccessible_boot_device
    • D

      Node.js October 21, 2026 Security Releases

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      6
      0 Votes
      6 Posts
      1k Views
      poddingueP
      @acebmxer I haven't run your script, so I can't vouch for the log lines, but the systemctl status check looks like the safer of the two to me. It shows the binary the service is really running. Whichever node comes first in your shell can be a different one if more than one Node is installed. For XOA I'd go with what @Danp said above.
    • acebmxerA

      Backups in OX v6

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      5
      3
      0 Votes
      5 Posts
      126 Views
      F
      If i can also add some feedback to how backups look in XO6. In its current from is very hard to see what VM is currently being backed up in a job. In XO5 clicking on tasks showed you a quick at a glance view of what VMs were being backedup and their current progress. In XO6, unless im missing something this is missing: [image: image.jpeg] I think it would be useful to be able to monitor backup progress as we currently can in XO5.
    • C

      XOSTOR getting an SR_BACKEND_FAILURE because it is trying to connect to a random IP

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved XOSTOR
      5
      0 Votes
      5 Posts
      72 Views
      C
      @ronan-a said: @ccooke As said by @poddingue , your network is not isolated. You must change that to protect your pool. We are aware of this issue and we will change this behavior in a future release to block LINSTOR controller and satellite access from the outside (probably in December). Also we will use TLS to add another security layer. Right. I missed that warning - I was going from https://xcp-ng.org/forum/topic/5361/xostor-hyperconvergence-preview which doesn't look to link to the XOSTOR documentation with the warning. Does this need a full reinstall effectively, or can I recover it? I see the warning is you can't have hypervisors with any public IPs - that will need a little re-engineering for my small test cluster. I know you can change the IP addresses for linstor after installing xostor - does that resolve the issue, or is there no way to secure it when the hypervisor is on a public IP? Could I not just add some firewall rules for now? Thanks for the reply.