Solaris Cluster Guest Domain (LDom) Node/System/Server was Rebooted with "Reservation Conflict" when Perform Live Migration Between two Control Domains
Last updated on MARCH 21, 2017
Applies to:Solaris Cluster - Version 3.2U2 2/09 to OSC 4.1 [Release 3.2 to 4.0]
Oracle Solaris on SPARC (64-bit)
When migrating a guest domain with Solaris Cluster installed on it caused the guest domain to panic with "Reservation Conflict".
The migration was between two Txxx hosts. The panic just occurred without any messages indicating that a Solaris Cluster reconfiguration was going on.
During the LDom live migration between the two control domains. The LDom was panicked.
The control domains is running Solaris 11, the guest LDom is running Solaris 10 and Solaris Cluster 3.2
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms