Fixed issues

This article lists issues present in previous releases that are fixed in this release.

  • For XenServer pools that use certain storage targets, a race condition in the iSCSI module can cause hosts in the pool to fail. (CA-287658)
  • A Windows 10 VM with the I/O drivers installed can fail with bugcheck code 139. This is caused by a Windows issue which causes an inconsistent state during nonpaged memory allocation. (CA-290852)
  • On reboot, VMs can fail to start with the error code SR_BACKEND_FAILURE_453. (CA-292268)
  • Live migration of VMs newly created on XenServer 7.5 is incompatible with adding or removing a network device from a Windows VM configured with has-vendor-device to be true (to enable Windows Update for PV drivers). VMs live migrated from a previous version of XenServer are not affected by this issue. (CA-286948)
  • After rebooting, a XenServer host can fail to connect to iSCSI targets on Compellent arrays. (CA-288738)
  • When shutting down, the XenServer host can hang at ‘reached target shutdown’. This happens if XAPI is unable to cleanly unplug PBDs to iSCSI SRs before shutdown. (CA-288738)
  • When updating the PVS Accelerator Supplemental Pack, the update can fail with the following error in XenCenter: UPDATE_APPLY_ERROR. (CA-292633)
  • XenCenter can fail after automatically reconnecting to a pool that it had previously lost connection to. (CA-289150)
  • When a user with the Pool Operator role tries to create a new SR of the type Hardware HBA or Software FCoE by using XenCenter, the scan for LUNs can fail. (CA-290064)
  • Importing a VHD type of VDI file larger than 1TiB was unsupported and led to an VDI_IO_ERROR. (CA-292288)
  • When you attempt to migrate a VM between resource pools, the migration can fail with the following error: Storage_interface.Internal_error("Jsonrpc.Parse_error(_)"). This migration failure can cause some versions of XenCenter to fail. (CA-291048)
  • An out-of-memory condition in the PV-IOMMU module of the Xen hypervisor can cause the XenServer host to fail. (CA-290664)

Fixed issues

In this article