For Solaris Zones
Description
Creation of a virtual L-Server for a Solaris Zone may not finish even after a long time has passed.
When a VM Host is Solaris 10
In such cases, there is a chance that creation has stopped at the window for parameter entry during the installation of the virtual L-Server's OS.
Log in to the VM host being used to create the virtual L-Server and check the following.
Execute the following command and check that the status of the non-global zone being created is "running".
# zoneadm list -vc <RETURN> |
Execute the following command and log in to the non-global zone that was checked in step 1.
After logging in, if the window for parameter entry during OS installation is being displayed, this problem has occurred.
# zlogin -C zonename <RETURN> |
When a VM Host is Solaris 11
There is a possibility that the initial boot service of a non-global zone has not been completed, or that a setting in the completion waiting definition file is incorrect. It is also possible that there is a problem in the operation status of a VM guest or VM host, or the network connection status.
Log in to the VM host being used to create the virtual L-Server and check the following.
Execute the following command and check that the status of the non-global zone being created is "running".
# zoneadm list -vc <RETURN> |
Execute the following command and confirm the status of the initial boot status of the non-global zone checked in step 1.
# zlogin zonename svcs Initial boot service name <RETURN> |
Initial boot service name: The value given in the completion waiting definition file of the initial boot service
Property name of the script completion flag: The value given in the completion waiting definition file of the initial boot service
If a command fails, or the output result of the second command is something other than "true" or "false", a setting in the completion waiting definition file is incorrect.
For details of the definition file, refer to "8.7.1 Creating Definition Files" in the "Setup Guide CE".
In any other cases, execution of the initial boot service has not been completed.
Corrective Action
The following causes are possible:
When a VM Host is Solaris 10
Check that a network interface that does not exist on the VM host has not been specified.
For details, refer to "8.7.4 Manual Network Configuration" in the "Setup Guide CE".
Check that a network interface used by another zone has not been specified on the VM host.
For details, refer to "8.7.4 Manual Network Configuration" in the "Setup Guide CE".
When the L-Server network interface was configured using the DHCP settings, check that the settings to allocate IP addresses from the DHCP server have been configured.
Check that the IP address allocated to the L-Server has not been allocated in duplicate.
For details on network interfaces, refer to "8.7.4 Manual Network Configuration" in the "Setup Guide CE".
First, perform the "Procedure for Deleting Non-global Zones".
After that, check and correct the parameters specified at the time of virtual L-Server creation, and in the environment, and then perform the operation again.
When a VM Host is Solaris 11
When a setting in the completion waiting definition file is incorrect
Check and correct the settings of the definition file. For details of the definition file, refer to "8.7.1 Creating Definition Files" in the "Setup Guide CE".
After that, perform the "Procedure for Deleting Non-global Zones", and then perform the operation again.
If there is a problem in the operation status of a VM guest or VM host, or the network connection status
Check the settings of VM guests and VM hosts and the status of the network connection and resolve the problem.
After that, perform the "Procedure for Deleting Non-global Zones", and then perform the operation again.
When execution of the initial boot service has not been completed
Check the reason in the log of the initial boot service of the non-global zone, and resolve the cause of the problem.
As a result, if the initial boot service does not finish successfully, perform the "Procedure for Deleting Non-global Zones, and then perform the operation again.
Log out from the non-global zone that was logged in to.
Stop the non-global zone.
When a VM host is Solaris 11 and a data disk is specified for a VM guest, delete the created data disk.
Execute the following command, and confirm the zfs path (the "special" value of fs resources with "zfs" specified for "type"). However, fs resources that have been created through image (zone.conf) specification are excluded.
# zonecfg -z zonename info <RETURN> |
When executing the following command, specify the zfs path confirmed in step a and delete the data disk.
# zfs destroy obtained zfs path <RETURN> |
Execute the following command to delete the non-global zone.
# zoneadm -z zonename uninstall -F <RETURN> |
Check from the ROR console that the executed process has been completed.
For OVM for SPARC
Description
Creation of a virtual L-Server for OVM for SPARC may not finish even after a long time has passed. In such cases, there is a chance that installation of the virtual L-Server's OS has failed.
Log in to the VM host being used to create the virtual L-Server and check the following.
Execute the following command and check that the status of the guest domain being created is "active".
# ldm list-domain <RETURN> |
Check the following log file stored in the service domain that provides the virtual console concentrator service.
The log file to check
/var/log/vntsd/guest domain's name/console-log
The contents output to the virtual console of the guest domain are recorded in this log file. This enables checking of the progress of installation.
Refer to the Solaris manuals and check whether installation of OS has completed normally.
Corrective Action
If OS installation fails, the following causes are possible.
The IP address specified at the time of L-Server creation may be being used by another server.
Check that the specified IP address is not conflicting with other servers.
The configuration of CPU, memory size, disks, etc. specified during L-Server creation may not satisfy the requirements for installation of Solaris.
Refer to the Solaris manuals and check whether the specified composition satisfies the requirements for installation of Solaris.
The installation server may have been inaccessible during installation of the OS.
Check whether this product can access the installation server.
Multiple default gateways may have been specified during creation of an L-Server with a Solaris 10 image specified.
Check the default gateway specified during creation of the L-Server.
Moreover, refer to "IP address specified during L-Server creation" in "8.8.8 Advisory Notes for OVM for SPARC Usage" in the "Setup Guide CE", and check whether the default gateway of the admin LAN has been set up.
Perform the following corrective action.
Refer to the "Procedure for checking the run state of a job in BladeLogic Server Automation" of "Message Number 67390", and cancel the job being executed.
Use the ROR console to check that the operation that was being performed has been completed.
Perform the operation again, after improving the parameter specified at the time of virtual L-Server creation, and environment.
