Asset ID:	1-75-1019982.1
Update Date:	2009-10-12
Keywords:

---

Solution Type  Troubleshooting Sure

Solution  1019982.1 :   Troubleshooting failures to bind VCPUs/MAUs to LDOM guest.  


PreviouslyPublishedAs
250247

Description
This document provides the steps to diagnose issues encountered during the binding of VCPUs or MAUs to a LDOM guest domain.
Symptoms:

One of more of the following are observed or described when one have issue binding VCPU/MAU:

• Insufficient VCPUS resources to bind LDom
• Only <number> physical crypto unit resource(s) available to bind to LDom
• Unable to bind VCPU
• Unable to bind MAU/Cryptographic

Purpose/Scope:

This document describe in the context during guest domain creation. Adding of resources to an active domain can also fail due to lack of additional resources to be assigned to a domain. The corrective actions are the same as described here.

Related Documents:

For more information on creation of LDoms guest domains, please refer to following references:

- Beginners Guide to LDOMs (820-0832) availabe at http://www.sun.com/blueprints.
- Logical Domains (LDoms) X.X.X Administration Guides, which are available on http://docs.sun.com/ .

Additional information specific to the software release is available on http://docs.sun.com/ as:

- LDOMs Release Notes.
- Release Notes for the specific Solaris release.

Up to date information on LDoms is available at http://www.sun.com/ldoms/ .


Steps to Follow
Please validate that each troubleshooting step below is true for your environment. The steps will provide instructions or a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step
Before attempting the following steps, please ensure the user account used has the appropriate RBAC profiles for LDOMs Management. The user either has to have to "LDoms Management" profile or just login as root. For more information on user authorization, please refer to the Security chapter of the LDoms Administration Guide.

Step 1. Verify that the minimal system requirements for the optimal operation of LDoms have been satisfied.

See <Document: 1020007.1> Steps to verify pre-requisites have been followed in LDOM environment.

Step 2. Ensure that resources are assigned to the LDoms appropriately.

See <Document: 1019970.1> Procedure to ensure appropriate LDOM resources are assigned to domains.

Step 3. Verify that VCPU/MAU resources are available for binding to the domain.

See <Document: 1019983.1> Steps to ensure proper binding of resources to LDOM domains.

At this point, if you have validated that each troubleshooting step above is true for your environment, and the issue still exists, further troubleshooting is required. Provide an Explorer output and open a Service Request. See <Document: 1020212.1> Data Collection for troubleshooting LDom issues.

Product
Logical Domain Manager 1.0.1
Sun Fire T2000 Server
Sun Fire T1000 Server
Sun Netra T2000 Server
Sun Netra T5220 Server


Internal Comments
This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the "Document Feedback" alias(es) listed below:

Normalization Lead: [email protected]

Normalized, ldom, ldm, MAU, Cryptographic Unit, VCPU

Attachments

This solution has no attachment