I'm running another test hot sv-motion now. (I gave it another 1GB of RAM). Swapping is firmly on 0. The VM itself seems fragile, if I sneeze load
seems to climb :smileyhappy:
Could the VM be starved of I/O bandwidth to the shared storage perhaps, causing the load to climb? That is the only other thing I can think of.
Currently I have it set up as follows, now that I think of it the svmotion and the SAN traffic may be potentially contended over the one link;
VMKernel. vmotion - enabled
=Active Adapters=
vmnic0
vmnic3
vmnic4
vmnic5
Should I have something like this instead?
VMKernel
vmotion - disabled
Active: vmnic 0, vmnic4
VMKernel2
vmotion - enabled
Active: vmnic 3, vmnic5
If so:
i) Can they be on the same vswitch, or should they be separated, or does it not matter?
ii) How do I ensure that only vmotion traffic goes over VMKernel2, and not iSCSI general traffic? I know I can check 'use this port group for Vmotion', but I would obviously like to isolate only iscsi traffic on VMKernel and only vmotion traffic on VMKernel2.
iii) I assume that svmotion and vmotion traffic are functionally the same thing when setting up the ports.
Thanks for all your assistance.