My Oracle Support Banner

[ PCA ] Live Migration of Oracle Solaris Guest Results in Reboot in Mixed-release Compute Nodes Environments (Doc ID 2345013.1)

Last updated on FEBRUARY 02, 2019

Applies to:

Private Cloud Appliance - Version 2.3.1 and later
Linux x86-64

Symptoms

In a mixed-release* Oracle VM environment, when an attempt to live-migrate a virtual machine with Oracle Solaris as its guest operating system is made, there could be
problems due to the Compute Node (Oracle VM Server; "OVS") version.

"mixed-release" means that the compute nodes run different levels of OVS. This typically occurs if, when a PCA was upgraded, not all of the compute nodes were upgraded at the same time. This is a supported configuration to allow a staged upgrade of compute nodes, but it is expected that all compute nodes will be upgraded to the same release level in due course.

Thus if a Private Cloud Appliance vm is live-migrated from a compute node running PCA release 2.3.1 or lower to a compute node running PCA release 2.3.2 or higher, the Oracle Solaris virtual machine will reboot.

The issue is the same with OVM in a non-PCA system: if a vm running Oracle Solaris is live-migrated to an OVS at 3.4.4 or newer, from a version prior to 3.4.4, Oracle Solaris will reboot. 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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

In this Document
Symptoms
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.