Today I had our Ignition server “crash” when a function of VMware, called V-Motion, transferred our virtual machine to another physical machine.
Apparently, from what our IT department tells me, VMware saw that one physical machine was too heavily loaded and shuffled the Ignition server over to another physical machine. During this move the Ignition service pegged the CPU at 100% and basically locked up the server. To fix the issue we had to “power off” the Ignition virtual server and bring it back up. They told me that some software does not like to be transferred between physical PC’s as they have had this issue before with other software.
My question is, has anyone had any problems with this virtual functionality before? This is the first time I’ve had a problem with a virtual environment, but from what I can tell, this is the first time this V-motion piece has ever kicked in.