Fixed issues

The following issues have been fixed in XenServer 8. In addition to these fixed issues, additional fixes are released on the Normal and Early Access update channels.


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


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


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)


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


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

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)


For information about known and fixed issues in XenCenter, see XenCenter What’s New.

Fixed issues