Product Documentation

Known issues

Mar 08, 2017
  • In some cases, the configuration wizard may take a long time after entering the database name and clicking Next
  • SUSE and CentOS distributions do not stay joined to a Windows Domain after PVS imaging.
  • When using the streaming wizard to create a VM on a XenServer host and specifying a single VCPU, the VM is created with an associated topology of "2 cores per socket." This prevents the VM from booting; an error message, similar to the following, appears in the XenCenter console:

"The value 'VCPU_max must be a multiple of this field' is invalid for field 'platforms:cores-per-socket'." 

  • The console may crash when attempting to display vDisk usage information in environments containing a large number of clients; this issue occurs when an administrator continually navigates around the console while retrieving client information.
  • A template has no hard disk, and as a result, does not have a SCSI controller associated with it. ESX automatically adds a default SCSI controller, which is not the same as the SCSI controller used by the master VM. Therefore, all provisioned VM templates violate the rule dictated by the template and the master vm indicating that they should use the same SCSI controller. 
  • When creating a vDisk using the Linux Streaming imaging tool (i.e., pvs-imager), the device type fails to update properly leading to imaging failure. To resolve this issue, use the Provisioning Services console to change the vDisk device type to Production.