Fixed issues
The following issues have been fixed in XenServer 8.4. In addition to these fixed issues, additional fixes are released on the Normal and Early Access update channels.
General
-
[Fixed in Early Access and Normal on 2 June 2025. After applying this update, you can upgrade your firmware to a version compatible with bnxt_en driver version 1.10.3-232.0.155.5.] On hosts with Broadcom 5750x NICs that have their firmware level updated to a version that is incompatible with bnxt_en driver version 1.10.2-223.0.083, the host crashes on reboot with a kernel panic. To work around this issue, take the following steps:
-
Refer to your vendor documentation to understand which firmware versions are compatible with the bnxt_en driver version in XenServer 8.4.
For example:
- On a Dell server, the compatible firmware version is 23.11.16.22.
- On an HPE server, the compatible firmware version is 223.1.96.0.
- If you have not yet applied an incompatible firmware level, do not apply it until after the latest bnxt_en driver is available for XenServer 8.4.
- If you’ve already applied the firmware, roll it back to a version compatible with bnxt_en driver version 1.10.2-223.0.083.
-
-
Rebooting the VM does not have the same effect as powering off and then starting the VM. (CA-188042)
-
If an Active Directory user inherits the pool admin role from an AD group that has spaces in its name, the user cannot log in to XenServer 8.4 through SSH. (CA-363207)
-
In clustered pools, a network outage might cause the following issues: inability to reconnect to the GFS2 storage after a host reboot, inability to add or remove hosts in a pool, difficulties in managing the pool. (XSI-1386)
-
[Fixed in Early Access on 16 April 2025. Fixed in Normal on 22 April 2025] In some situations, such as if you have HA enabled in your pool, or are using GPUs, XenCenter® and Workload Balancing might not be able to correctly load performance data from the pool. This issue shows the following symptoms:
- In XenCenter, performance graphs do not load and show as blank, or contain gaps.
- In Workload Balancing, you might see consultation and recommendation failures.
(XSI-1845)
Graphics
- On hardware with NVIDIA A16/A2 graphics cards, VMs with vGPUs can sometimes fail to migrate with the internal error “Gpumon_interface.Gpumon_error([S(Internal_error);S((Failure “No vGPU available”))])”. (CA-374118)
Guests
Windows guests
-
When UEFI-boot Windows VMs start, they show a TianoCore logo. (CP-30146)
-
On a Windows VM, sometimes the IP address of an SR-IOV VIF is not visible in XenCenter. (CA-340227)
-
On a Windows VM with more than 8 vCPUs, Receive Side Scaling might not work because the xenvif driver fails to set up the indirection table. (CA-355277)
-
If a XenServer® host crashes, or shuts down abruptly, starting more Windows 11 VMs or migrating more Windows 11 VMs onto that host eventually fails. (CA-375992)
Linux guests
-
The XenServer VM Tools for Linux can provide an incorrect value for the free memory of the VM that is higher than the correct value. (CA-352996)
-
VMs running on Oracle Linux 8 with a single vCPU fail to resume from a paused state when the Dynamic Memory Control (DMC) feature is enabled and the allocated memory for the VM is set to its maximum limit. (CA-3907760)
Installation
-
[Fixed in the June 2025 ISO release] On hosts with Broadcom 5750x NICs that have their firmware level updated to a version that is not compatible with bnxt_en driver version 1.10.2-223.0.083, the host crashes during installation with a kernel panic or the installation can hang.
-
[Fixed in the May 2025 ISO release] The April 22, 2025 XenServer 8.4 installation ISO contains an issue that can cause upgrades to fail with the error
KeyError: 'target-platform'when performing a manual upgrade. -
[Fixed in the June 2024 ISO release] Due to an incompatibility with some system firmware, installing XenServer using software boot-from-iSCSI can fail with the error message: “An unrecoverable error has occurred.”
PVS Accelerator
- [Fixed in Early Access on 24 September 2025 and Normal on 1 October 2025.] PVS-Accelerator metrics may be blank or in an incorrect range. (CA-414341)
SDK
- In the Java SDK, some calls might fail with a JsonMappingException. (CA-393866)
Storage
-
When attaching an iSCSI LVM SR with multi-target and wildcard targetIQNs to a host, the attach operation can fail if not all targets respond. (CA-375968)
-
If a GFS2 SR has less than 500 MB of space on it, when you attempt to delete disks stored on this SR, the operation can fail. (CA-379589)
-
When attempting to repair a connection to a read-only NFS v3 SR, the operation can fail on the first attempt with the error “SM has thrown a generic python exception”. To work around this issue, attempt the repair operation again. This issue is caused by a write operation in the initial repair attempt. (XSI-1374)
Updates
-
While the install update is in progress on a pool member, you might see the error “The operation could not be performed because getting updates is in progress.”. To resolve this error, you can retry the operation. (CA-381215)
-
When using the originally released update bundles for May 6 or May 12, the offline bundle upload fails with the error “Syncing with bundle repository failed”. Replacement bundles have now been released that include the string
-v2in the file name. If you have already downloaded the original versions of these bundles, get the latest versions (v2) before attempting your update. (XSI-1909)
Workload Balancing
-
For a Workload Balancing virtual appliance version 8.2.2 and later that doesn’t use LVM, you cannot extend the available disk space. (CA-358817)
-
In XenCenter, the date range showed on the Workload Balancing Pool Audit Report is incorrect. (CA-357115)
-
During the Workload Balancing maintenance window, Workload Balancing is unable to provide placement recommendations. When this situation occurs, you see the error: “4010 Pool discovery has not been completed. Using original algorithm.” The Workload Balancing maintenance window is less than 20 minutes long and by default is scheduled at midnight. (CA-359926)
XenCenter
For information about known and fixed issues in XenCenter, see XenCenter What’s New.