Troubleshooting LDom Live Migration
(Doc ID 2303433.1)
Last updated on JANUARY 06, 2023
Applies to:
Solaris Operating System - Version 10 and laterOracle Solaris on SPARC (64-bit)
Purpose
This document provides hints on how to troubleshoot LDom live migration issues
Troubleshooting Steps
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
| Purpose |
| Troubleshooting Steps |
| Overview of a Migration Operation |
| Software Compatibility |
| Domain Migration Restrictions |
| Migrating a Domain |
| New option " -s spconfig-name" from version LDom 3.5 on |
| Migration Requirements for Memory |
| Monitoring a live migration operation |
| Data to collect |
| Use Debug Option 'logctl' in LDom 3.5 |
| Check network ports 6482 and 8101 on LDom migration partners |
| Ensure that the guest LDom does not contain a running KZ inside |
| Error message: Failed to establish connection with ldmd(1m) on target: |
| Error Message: Native CPU Family Migration does not work between T5 and M5 |
| Error message: The LDoms manager on the source system {source} does not support ADI tag migration. |
| Error Message: Unable to bind memory. Limit of 1023 segments reached |
| LDom migration related MOS documents |
| Migration DTrace Example for Oracle VM Server SPARC |
| Max pagesize might be important when doing LDom live migration (Live Migration mblock splitting) |
| References |