| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||||||||||||||
Solution Type Sun Alert Sure Solution 1968958.1 : Sun System Firmware 8.6.0.b, 8.6.0.c, and 9.3.0.b through 9.3.0.f May Cause Guest Domains to be Unresponsive Following a Live Migration
In this Document
Applies to:SPARC T4-2SPARC T4-1B SPARC T4-1 SPARC T4-4 SPARC T5-2 SPARC SPARC T4-1B Server Module Netra SPARC T4-1 Server Netra SPARC T4-2 Server Netra SPARC T4-1B Server Module SPARC T5-2 Server SPARC T5-4/T5-8 Server SPARC T5-1B Server Module Netra SPARC T5-1B Server Module SPARC M5-32/M6-32 Server ________________________________________ Date of Workaround Release: 9-Feb-2015 Date of Resolved Release: 16-Jun-2015 ________________________________________ DescriptionSun System Firmware 8.6.0.b, 8.6.0.c, and 9.3.0.b through 9.3.0.f may cause guest domains to be unresponsive on the destination server following a live migration. OccurrenceThis issue can occur on the following platforms: SPARC Platform
To determine the current firmware version on one of these servers, the following command can be used: SymptomsAfter performing a live migration of a guest domain, the migrated domain may be unresponsive on the target system. In addition, the CPU utilization may be high (see below example), and it may not be possible to log in to the domain. # ldm list-domain ldom-1
NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME
ldom-1 active -n---- 5002 8 8G 100% 100% 2h 16m
WorkaroundThe cause of the described issue is that a certain register is not set during a migration. The workaround below forces that register to be set for all strands before a migration occurs. To prevent this issue from occurring, execute the following steps prior to performing a live domain migration: 1. Log in to the control domain on the target host. 2. Start each guest at least once (if not already done since poweron). # ldm start-domain existing-domain LDom existing-domain started 3. Determine the number of unused VCPU's: # ldm list-devices
:
:
VCPU
PID %FREE
128 100
129 100
130 100
131 100
132 100
133 100
134 100
135 100
136 100
137 100
138 100
139 100
140 100
:
:
:
4. Execute the following commands as 'root' to create a domain containing the unused VCPU's: # ldm add-domain max-vcpus
# ldm add-vcpu 128 max-vcpus
# ldm add-memory 128G max-vcpus
# ldm bind-domain max-vcpus
# ldm start-domain max-vcpus
LDom max-vcpus started
# ldm list-domain
NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME
primary active -n-cv- UART 128 128G 0.0% 0.0% 7m
max-vcpus active -t---- 5000 128 128G 0.8% 0.8% 2m
#
# telnet localhost 5000
:
:
{0} ok
telnet> quit
Connection to localhost closed.
#
# ldm stop-domain max-vcpus
Remote graceful shutdown or reboot capability is not available on max-vcpus
LDom max-vcpus stopped
# ldm list-domain
NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME
primary active -n-cv- UART 128 128G 0.0% 0.0% 9m
max-vcpus bound ------ 5000 128 128G
#
# ldm unbind max-vcpus
# ldm remove-domain max-vcpus
#
5. Perform the domain migration. This issue is addressed in the following releases:
Note: There is an issue with Firmware 9.4.2.c and 9.4.2.d for the SPARC T5 and SPARC M5-32/M6-32 Servers. Please see Service Alert <Document:2027245.1> for more details. Patches<SUNPATCH:151743-01> History09-Feb-2015: Document released, status Workaround Internal Section: Comments: This regression was caused by the putback for 18994335 Note: The bugID that was used to fix this issue was 19197738 and not 20142591 as originally intended. References<NOTE:2027245.1> - SPARC T5 Series and SPARC M5-32/M6-32 Servers System Firmware Version 9.4.2.c and 9.4.2.d May Erroneously Disable CPUs Attachments This solution has no attachment |
||||||||||||||||||||||||
|
||||||||||||||||||||||||