During my PowerCLI scripting for the provisioning of new ESX Hosts i have found another bug. The Set-VDSwitch CMDlet does not set the number of uplink ports correctly in every case.
Time for the next PowerCLI bug. The Set-VDUplinkTeamingPolicy CMDlet has problems with the “failback” option.
It is possible to switch “Failback” from true to false, but not from false to true.
One feature that is really missing at Citrix XenServer compared to VMware vSphere is OS Customization. My dear co-blogger Birk (the VMware guy) will never stop to underline this. At vSphere settings like Hostname, Network configuration, Domain membership, Licensing can be defined in specifications and applied to templates and VM images.
Recently I had to troubleshoot network performance issues for VMs running on Citrix XenServer 6.0.2. All VMs were running W2k8R2 and it seems that CIFS copy jobs where incredible slow. The network itself couldn’t be the problem as all VMs were connected to the same virtual network on only one XenServer.
Some days ago I ran into the problem that XenCenter was not connecting to my XenServer correctly. The initial connect seems to be fine, but it got stuck at “synchronizing with …”.