1. Oracle VM Server for SPARC 3.6 Administration Guide
  2. Migrating Domains
  3. Domain Migration Restrictions
  4. Migration Restrictions for Setting perf-counters
  5. Forced Cross-CPU Migration Can Fail if Global Performance Counters are Enabled

Forced Cross-CPU Migration Can Fail if Global Performance Counters are Enabled

In certain cross-CPU migration scenarios, a migration can fail with the following errors when you force the migration by using the -f option: 

API group 0x20b v1.0 is not supported in the version of the firmware
 running on the target machine.
API group 0x214 v1.0 is not supported in the version of the firmware
 running on the target machine.

All of the following conditions must be present to encounter this problem:

  • The domain has the cpu-arch property set to generic or migration-class1

  • The domain has a perf-counter property setting that includes the global value

  • The domain was booted on at least a SPARC M7 series server or a SPARC T7 series server

  • The target machine is a platform released prior to the SPARC M7 series server or SPARC T7 series server

This problem occurs because a domain booted on at least a SPARC M7 series server or a SPARC T7 series server with a perf-counter property setting that includes the global value will register platform-specific performance counter Hypervisor interfaces that do not exist on older platforms. As part of the migration, a check is performed to ensure that all the interfaces used by the domain are present on the target machine. When these SPARC M7 series server or SPARC T7 series server specific interfaces are detected, the migration is aborted.

Do not set perf-counter=global if cpu-arch is note native and at least SPARC M7 series servers and SPARC T7 series servers are part of the migration pool.