- Citrix Xenserver Pricing
- Citrix Xenserver For Mac High Sierra
- Citrix For Mac 10.12.6
- Citrix Xenserver Mac
- Citrix Workspace For Mac
A list containing the majority of Citrix Workspace app for Mac (formerly Receiver for Mac) support articles collated to make this page a one stop place for you to search for and find information regarding any issues you have with the product and its related dependencies.
The page is updated daily with new support articles and information. Articles will change from time and if information here is outdated or incorrect please let me know using the comments. Links may also expire or change so if you find broken links, please again let me know. For each issue, known product versions affected are recorded however that does not mean product versions that aren’t listed are not affected.
Citrix offers a unified, secure and intelligent digital workspace that enables users to access their apps, desktops and data from anywhere and transforms employee experience. XenApp, XenDesktop, XenMobile and XenServer are part of the Xen® family of products. For information about XenServer 7.6.0 release, see the XenServer Product Download page. For information about getting started with XenServer and for links to product documentation and other useful resources, see XenServer Product Documentation. To access XenServer Developer documentation, see Citrix Developer Documentation.
There is a search box that you can use if looking for a specific fault. For example if you have an error code or error message, use that to perform a search. You can also use your browsers search feature which will perform a search against the whole page based on the words you enter.
Receiver for Mac / Workspace app for Mac:
wdt_IDBrief Description of IssueBrief Description of FixApplicable Product Versions Affected (if known)Link to supplemental Support Article(s)1Bloomberg keyboard and finger print scanner not redirecting to Citrix session.Redirection of this device is not fully supported but there is a method to follow that can be tried to get it working, as explained in the CTX article.https://support.citrix.com/article/CTX2270752Windows Mac users connect to NetScale full VPN, they cannot reach external websites. Split DNS is not working.This is by design. The Mac VPN client does not support split DNS so all DNS requests are sent to NetScaler for resolution. If NetScaler cannot resolve the domain name then users will get an invalid response. This issue will be fixed under an existing enhancement request.https://support.citrix.com/article/CTX2252973When using HDX 3D Pro, a black box may appear around some custom cursors.This is a known issue and 32-bit cursors are being investigated as part of the product road maps for Citrix Receiver for Mac. Cursors that employ shadow effects for example are classed as 32-bit cursors and not currently supported by Receiver for Mac.https://support.citrix.com/article/CTX2236264If using a proxy connection, communication over EDT fails.This is a known issue.Receiver for Mac 12.5.5You receive an ‘Initialization failed’ error.This is caused by an upgrade to macOS Sierra. Upgrade to Receiver for Mac 12.3 which is compatible with this OS.6Delivering a proxy.pac file to clients via NetScaler Session Policies works for Windows devices but now Mac.At the moment, only Windows devices are supported. Proxy PAC support for MacOS is currently being worked on.https://support.citrix.com/article/CTX2272627When launching an application or desktop you may receive error ‘System Extension Blocked’.A new feature introduced to MacOS High Sierra requires user approval to load any newly-installed third-party kernel extensions. Navigate to ‘System Preferences -> Security & Privacy’ and click ‘Allow’ against ‘Citrix Systems Inc’.Citrix Receiver for Mac 12.7 and above, and MacOS High Sierra.https://support.citrix.com/article/CTX2282088French Canadian special accent characters do not display correctly when accessing a Windows 7 VDA.Upgrade to Receiver for Mac 12.7.Citrix Receiver for Mac 12.4.https://support.citrix.com/article/CTX2316239Alt+Tab does not switch properly all the time and Alt+Enter does not work in Excel.Upgrade to Receiver for Mac 12.7.Citrix Receiver for Mac 12.6.https://support.citrix.com/article/CTX23162410When using a DisplayLink docking station with v3.1 drivers and Receiver for Mac there is a high ICA RTT spike over 1000ms.Upgrading to DisplayLink v4.0 drivers and MacOS 10.13 High Sierra resolves the issue. The issue is still being investigated for earlier MacOS versions.Citrix Receiver for Mac 12.6 and 12.7.https://support.citrix.com/article/CTX231625
This article describes following items.
- How to configure SR-IOV Network
- How to create SR-IOV VLAN network
- How to assign SR-IOV Network to a VM
- How to destroy SR-IOV Network
- Additional steps for NICs that use a legacy driver
Single Root I/O Virtualization (SR-IOV) is a virtualization technology that allows a single PCI device to appear as multiple PCI devices on the physical system. The actual physical device is known as a Physical Function (PF) while the others are known as Virtual Functions (VF). With this feature, the hypervisor can assign one or more VFs to a Virtual Machine so that the guest can then use the device as if it were directly assigned.
SR-IOV feature now can be supported in XenServer 7.6.
How to use SR-IOV with XenServer
In this article, we provide steps to use SR-IOV with XenServer. Before proceeding, ensure the following requirements are met:
- NICs that are in XenServer Hardware Compatibility List website, http://hcl.xenserver.org
- XenServer Enterprise Edition (or access to XenServer through a XenDesktop/XenApp entitlement)
- NIC drivers are installed to XenServer and virtual machines.
- Virtual machines must be HVM guest.
- Ubuntu Xenial Xerus 16.04
- Ubuntu Trusty Tahr 14.04
- Debian Jessie 8.0
- CentOS 7
- Red Hat Enterprise Linux 7
- Scientific Linux 7
- Oracle Linux 7
- Windows server 2008R2, 2012 and 2016
SR-IOV feature can be enabled on both XenCenter and xe CLI, please refer to following sections for detailed steps.
Steps within XenCenter
- Enable SR-IOV on XenCenter
- Add new network.
Citrix Xenserver Pricing
- Select “SR-IOV Network”
Citrix Xenserver For Mac High Sierra
- Name the network.
- Select the proper NIC to enable SR-IOV.
- Click Finish button, read and click on “Create SR-IOV anyway” button on the warning popup.
- Confirm SR-IOV Network is added.
- Check if host reboot is required. If yes, reboot the host.
- Remaining available VFs can be checked from NICs tab.
- Assign an SR-IOV network for a VM.
- Select the VM and add a new interface.
- Select the SR-IOV network, and click Add.
- Start the VM.
- SR-IOV VFs do not support hot-plugging. If SR-IOV network is assigned to a VM while the VM is running, please shutdown then start the VM to make this take effect. A restart operation will not activate the feature for the VM.
- Performing live migration, suspend, and checkpoint is not supported on VMs using an SR-IOV VF.
- Disable SR-IOV Network.
- Select the SR-IOV Network, and click Remove.
- Select “Yes” on the popup.
- Create SR-IOV VLAN network
- Add External Network.
- Name the SR-IOV VLAN network.
- Check the check-box of “Create the VLAN on the SR-IOV network” and click finish.
Note, VLAN network on top of SR-IOV Network belongs to SR-IOV Network.
Steps for xe CLI
- Command to enable SR-IOV
Citrix For Mac 10.12.6
- Create the network with the network-create command, which returns the UUID of the newly created network:
xe network-create name-label=<network_name>
xe network-create name-label=SRIOV
- Determine the PIF uuid of the NIC on which SRIOV Network would be configured.
uuid ( RO) : 4762a246–1f11–7b93–44ca-06703affc149
device ( RO): eth1
currently-attached ( RO): true
VLAN ( RO): -1
network-uuid ( RO): b37076a1–2309–9a04-ae32–446819732713
Citrix Xenserver Mac
- Configure the network as a SR-IOV network, which returns the newly created SR-IOV Network UUID:
xe network-sriov-create network-uuid=<network_uuid> pif-uuid=<physical_pif_uuid>
xe network-sriov-create network-uuid=ee8ed573-edaa-21ca-5ce3–928a9a1e8eb3 pif-uuid=4762a246–1f11–7b93–44ca-06703affc149
ae70ddcb-fd2e-fdab-6612–91fe2e8eefcc →this is the uuid of SR-IOV Network you created.
- You may check if host reboot is required to make SR-IOV Network take effect, and the remaining capacity.
xe network-sriov-param-list uuid=<SR-IOV Network_uuid>
xe network-sriov-param-list uuid=ae70ddcb-fd2e-fdab-6612–91fe2e8eefcc
uuid ( RO) : ae70ddcb-fd2e-fdab-6612–91fe2e8eefcc
physical-PIF ( RO): 4762a246–1f11–7b93–44ca-06703affc149
logical-PIF ( RO): efb46271-fa28–11eb-92d9–7098f00704bf
requires-reboot ( RO): false
remaining-capacity ( RO): 63
- Command Line to assign the SR-IOV network to a VM:
- Determine the vif mac address of the VM:
xe vm-vif-list vm=”vm name label”
xe vm-vif-list vm=’Windows Server 2016'
uuid ( RO) : b22b444d-4d5b-a697–754f-5a7d42bbd990
vm-name-label ( RO): Windows Server 2016
device ( RO): 0
MAC ( RO): b2:61:fc:ae:00:1b
network-uuid ( RO): 5f0bb332-da64-f95d-633e-570edee7ee33
network-name-label ( RO): Pool-wide network associated with eth0
- Assign SR-IOV Network to the VM, vif uuid of SR-IOV Network assigned to the VM is returned.
xe vif-create device=<device index> mac=<vf_mac_address> network-uuid=<sriov_network> vm-uuid=<vm_uuid>
xe vif-create device=1 mac=b2:61:fc:ae:00:1b network-uuid=ee8ed573-edaa-21ca-5ce3–928a9a1e8eb3 vm-uuid=91b7ec7c-07d7–1454-a229–48c07b2ff2a7
Please note, if a VM that is exported from a previous XenServer version and then imported into XenServer 7.6, and the guest OS of the VM supports SR-IOV Network, you assign a SR-IOV Network or SR-IOV VLAN Network to that VM via xe CLI only. For more details, please refer to How To Assign SR-IOV Network to a VM exported from a previous XenServer Version
- Command to disable SR-IOV
xe network-sriov-destroy uuid=<network_sriov_uuid>
xe network-sriov-destroy uuid=ae70ddcb-fd2e-fdab-6612–91fe2e8eefcc
Additional steps for NICs that use a legacy driver
For some NICs that use legacy drivers (for example, Intel I350 family), the maximum number of VFs that the NIC can support is defined within the driver module configuration file and may need to be adjusted manually prior to enable SR-IOV.
To do this, open modprobe configuration in
/etc/modprobe.d/<driver_name>.conf using an editor and change the line starting:
For example, to set the maximum VFs to 4 for the igb driver edit /etc/modprobe.d/igb.conf to read:
# VFs-param: max_vfs
# VFs-maxvfs-by-default: 7
# VFs-maxvfs-by-user: 4
options igb max_vfs=0
- The value of VFs-maxvfs-by-user must be less than or equal to the value in the line VFs-maxvfs-by-default.
- Do not change any other line in the file.
- The host must be rebooted to enable or disable SR-IOV on these devices.
- If rebooting is again required even after host reboot, it indicates that the NIC is not able to enable SR-IOV.
Citrix Workspace For Mac
How To Assign SR-IOV Network to a VM exported from a previous XenServer Version
How to troubleshoot common SR-IOV related issues
SR-IOV support FAQ