How to Manually Bypass Oracle VM Agent HA Pre-check (Doc ID 1089117.1)

Last updated on JUNE 02, 2017

Applies to:

Oracle VM - Version: 2.2.1 and later   [Release: OVM221 and later ]
Information in this document applies to any platform.

Goal

When you create Oracle VM server pool, it's required that all the servers in the pool have the same type and family of CPUs. Beginning in Oracle VM Server 2.2.1 (or Oracle VM Server 2.2.0 with upgraded agent ovs-agent-2.3-32 or later), Oracle VM agent will enforce the pre-check by default when you create a server pool or add a new server to an existing server pool (for example see <Document 1088245.1>). The pre-check includes the server version, agent version, CPU compatibility, storage repositories, NFS, OCFS2 configuration, and so on. It is to ensure successful setup of the server pool and OCFS2 cluster integrity.

Still there might be use cases where you want to set up the testing environment where different type of servers may be formed into the server pool. For example, the testing environment may be to verify network or storage configuration of multi-node server pool, but it's not required to perform live migration or HA.

Warning: Oracle VM 2.2 requires all processors in a given pool to be of the same type. The bypass procedure provided below is available for test and experimental environments,and is not recommended or supported by Oracle.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms