The vendor has published 4 unique mention(s) for this bug: 1. When using the CVAD Setup Wizard with a XenServer host, the provisioned VMs will not be bootable if the number of vCPUs chosen is not a multiple of the "Cores per socket" setting in the chosen VM template. You must pick a template that reflects the desired cores per socket and then choose a number of vCPUs that is a multiple of this. 2. When using the Streamed VM Setup Wizard to create VMs on a XenServer host while specifying 1 vCPU, the VM is created with 1 vCPU and a topology of 2 cores per socket. Creating VMs in this fashion prevents the VM from booting, while displaying the following error message in XenCenter®: “The value ‘VCPU_max must be a multiple of this field’ is invalid for field platforms: cores-per-socket. As a result, XenCenter fails to boot the VM because the topology and vCPU configuration are incompatible. 3. When using the Streamed VM Setup Wizard to create VMs on a XenServer host while specifying 1 vCPU, the VM is created with 1 vCPU and a topology of 2 cores per socket. Creating VMs in this fashion prevents the VM from booting, while displaying the following error message in XenCenter®: “The value ‘VCPU_max must be a multiple of this field’ is invalid for field platforms:cores-per-socket. As a result, XenCenter fails to boot the VM because the topology and vCPU configuration are incompatible. 4. When using the Streamed VM Setup Wizard to create VMs on a Citrix Hypervisor™ host while specifying 1 vCPU, the VM is created with 1 vCPU and a topology of 2 cores per socket. Creating VMs in this fashion prevents the VM from booting, while displaying the following error message in XenCenter: “The value ‘VCPU_max must be a multiple of this field’ is invalid for field platforms: cores-per-socket. As a result, XenCenter fails to boot the VM because the topology and vCPU configuration are incompatible. Latest urls for this bug: 1. https://docs.citrix.com/us/en/provisioning/2106/known-issues.html 2. https://docs.citrix.com/us/en/provisioning/2109/known-issues.html 3. https://docs.citrix.com/us/en/provisioning/2112/known-issues.html 4. https://docs.citrix.com/us/en/provisioning/2203-ltsr/known-issues.html 5. https://docs.citrix.com/us/en/provisioning/2206/whats-new/known-issues.html 6. https://docs.citrix.com/us/en/provisioning/2209/whats-new/known-issues.html 7. https://docs.citrix.com/us/en/provisioning/2212/whats-new/known-issues.html 8. https://docs.citrix.com/us/en/provisioning/2303/whats-new/known-issues.html 9. https://docs.citrix.com/us/en/provisioning/2305/whats-new/known-issues.html 10. https://docs.citrix.com/us/en/provisioning/2308/whats-new/known-issues.html