Hopefully this is the right area for this question, the boards have been broken up so much compared to the last time I was here. I'm running into an issue now with vMotion not necessarily completing successfully but with causing a disruption in the network where clients are having their XenDesktop sessions pop up a message that they have been disconnected from the XenDesktop servers. This is happening not only when I'm moving the actual XenDesktop virtual machines but also servers on the hosts involved. The servers have no issues with the vMotion what so ever. I'm all but sure that Citrix will point to VMware as the issue and vise versa.
Our current setup is we have ESXi 5.0 U1 hosts, each has 3 vSwitches configured as follows- 3 pNICs go to MGMT / VM Traffic, 2 pNICs to vMotion (VMKernal), 2 pNICs to DMZ. The pNICs for MGMT/VM Traffic and vMotion plug into the same switch stack of Cisco 3750x switches with no vLan's or tagging, and the DMZ is its own physical switch isolated. I would think that dedicated pNICs for VM traffic and vMotion traffic on gigabit connections would suffice, and I would assume that the Cisco 3750X switch stack should be able to handle that kind of bandwidth without any issue.
I've been thinking about isolating the vMotion traffic onto it's own vLan but I'm not sure if that would do anything as it would still be plugged into the same switch stack. Has anyone heard of issues with XenDesktop and vMotion before or where I should start to look for bottleneck issues?