Update05/06/2026

Updates to collected telemetry.

XenServer
Citrix

Early Access channel updates

May 6, 2026
Checksum: fe242e7aeacc8f4a8c21bf511df2388084bf77271bf40439f6ecc15851f2bd86

These updates contain the following improvements:

Updates to collected telemetry. For more information, see Data governance.
When using a VM with disks on a GFS2 or XFS SR, a serial number is now supplied.
Update OpenSSL to 3.5.5.
Update the Secure Boot Forbidden Signature Database (DBX) provided to new VMs to the latest published version.
When a large number of VDIs are active on an individual host, improve the speed of control plane operations.
Improve the ability of a pool using GFS2 SRs to fence specific hosts which are having networking issues, rather than allowing them to negatively affect the whole cluster.

These updates include fixes for the following issues:

In some cases AD user login can fail due to a failure to retrieve subject details.
In some cases attempting to join a freshly installed host to an existing pool may fail with a POOL_JOINING_SM_FEATURES_INCOMPATIBLE error.
Certain records (e.g. PCI data) are left behind in the pool database after ejecting a host from a pool.
A toolstack restart after an update synchronization may block application of updates until another synchronization is performed.
Live patches that were not applicable may be incorrectly reported as applicable on hosts.
In rare circumstances VHD handling tools can crash when processing an invalid VHD.
If a scan on an LVM-based Storage Repository finds a virtual disk in the metadata that is not known to the toolstack it will (re)introduce it. In the event the VDI is not still present on the SR this (re)introduction will encounter an error.
A recent change caused GFS2 and XFS datapaths to use an increased amount of Control Domain memory.
After upgrading an HA-enabled GFS2 pool from an older XenServer or Citrix Hypervisor release, HA may not be able to be re-enabled.
BIOS boot VMs may fail to network boot if a vlan priority tag is set in the DHCP response.
When installing a UEFI VM from a local DVD, the VM may hang at the firmware screen before starting installation.
In rare circumstances, the device model can fail due to a problem managing the Xen map cache.