After Hotfix 1 and Hotfix 2 Citrix has released the third hotfix for XenServer 6.1.0.
This hotfix resolves the following issues:
Note: There is no specific threshold for the performance issues described below. Customers experiencing any of the symptoms should install the hotfix.
- Connecting XenCenter to a large pool can increase the load on the pool master, resulting in excessive inter-host communication and cause delays when performing VM lifecycle operations.
- Delays can occur when restarting XAPI in a pool consisting of large number of Virtual Disk Images (VDIs), for example more than 1000, as this can cause excessive load on the pool master.
- A pool consisting of a large number of Windows VMs with XenServer Tools installed, can cause a high (up to 100%) CPU load on the pool master, resulting in communication overhead. For example, customers may not be able to connect XenCenter to the pool.
- When using High Availability (HA) in an environment where the protected Virtual Machines (VMs) use VLANs, HA may be unable to detect that a VM is agile: it cannot therefore plan a suitable recovery procedure. In this case, customers may find that their XenServer pools unexpectedly become “overcommitted”, or that they may be unable to use HA.
- QoS settings do not work when set through XenCenter or the xe CLI.
- For active-active bonds on the vSwitch network stack, the bond rebalancing interval has changed from 10 seconds to 30 minutes.
- Performance data collection from pool members can cause XAPI session leaks, which eventually may exceed the maximum allowed number of open sessions. If this occurs, the pool master’s xensource.log file will display the following message: Number of disposable sessions in database (416/416) exceeds limit (400): will delete the oldest.
You can download the hotfix here.