Deploying a configuration in fenced mode hosts all the virtual machines on a single Managed Server system. You must have a Managed Server system connected to the storage server where the templates that serve as the basis of this configuration reside on. The Managed Server system must have sufficient resources, such as memory, slots, and fences.
If you deploy a configuration, perform an operation which saves the state of the configuration (for example, suspend or capture to library), and redeploy the configuration with fencing (which requires hosting all virtual machines on the same physical machine), a situation could come up where the only Managed Server systems available are ones with incompatible processor types. The captured memory expects a particular processor type.
To address this situation, deploy the configuration without fencing, undeploy it without saving the memory state (use the
Turn Off deployment setting in the User Preferences page or the
Undeploy - Discard State mouseover menu), and redeploy the configuration.
