![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||||
Solution Type Sun Alert Sure Solution 2402477.1 : For SPARC M8 and SPARC T8 Series Servers: Oracle VM Server for SPARC Might Experience a Kernel Panic or a Fatal Error When `cpu-arch=migration-class1' is Set on a Guest Domain
In this Document
Applies to:SPARC T8-2SPARC T8-4 Sun Software - Generic Oracle VM SPARC M8-8 Information in this document applies to any platform. SPARC ________________________________________ Date of Workaround Release: 23-May-2018 ________________________________________ DescriptionSPARC M8 or SPARC T8 series servers running Oracle VM Server for SPARC 3.5, 3.5.0.1, or 3.5.0.2 software might experience a kernel panic or another fatal error condition if a guest domain has the 'cpu-arch' property value set to 'migration-class1'. This applies to any domain migrated to a SPARC M8 or SPARC T8 series server with the 'cpu-arch' property having been set to 'migration-class1' on the source system, and to any domain created on a SPARC-M8 or SPARC-T8 platform with the 'cpu-arch' property set to 'migration-class1'. The problem occurs when the Oracle Solaris kernel or any user application attempts to reference a 2 GB page on a SPARC M8 or SPARC T8 series server. The 'cpu-arch=migration-class1' setting incorrectly permits 2 GB page sizes on the underlying hardware platform, even though the SPARC M8 and SPARC T8 series servers do not support 2 GB page sizes. OccurrenceThis issue can occur in the following releases: SPARC Platform (for SPARC M8 or SPARC T8 series servers):
Notes: 1. No other SPARC servers are affected directly by this issue. However, a domain on another server that supports the 'migration-class1' value of the 'cpu-arch' property (at least the SPARC T4, SPARC M5, or SPARC S7 series server) becomes vulnerable if that domain is migrated to a SPARC M8 or a SPARC T8 series server. 2. To determine whether a guest domain is vulnerable to this issue, run the following command on the primary domain for each guest domain: # ldm list -l <guest-domain> | grep cpu-arch A guest domain is vulnerable to this issue if the output shows 'cpu-arch=migration-class1'. SymptomsWhile the symptoms can vary, the Oracle Solaris kernel typically panics in the guest domain that has the 'cpu-arch=migration-class1' setting. The associated panic string is "bad unexpected error from hypervisor call at TL 1." WorkaroundUntil an update is available, change the value of the 'cpu-arch' property on all SPARC M8 and SPARC T8 series servers as follows:
Note: After setting the 'cpu-arch' property, you must reboot the guest domain to make the change take effect. Resolution A pending update to Oracle VM Server for SPARC software will remove 2 GB page size support from the 'migration-class1' CPU architecture type. This resolution will ensure that page size support is fully compatible for all supported SPARC platforms starting with the SPARC T4, SPARC M5, and SPARC S7 series servers. For more information about the 'cpu-arch' property, see: https://docs.oracle.com/cd/E80106_01/html/E80109/migratingactivedomain.html Note: Although the Administration Guide (as referenced by the link above) does not list the SPARC M8 and SPARC T8 series servers as options under 'migration-class1', those servers are in fact included, and the references in this Alert are applicable. History23-May-2018: Document released, status is Workaround Questions regarding any portion of this document should be Internal Contributor/Submitter: john.falkenthal@oracle.com
References<BUG:27952673> - GUEST LDOM BAD UNEXPECTED ERROR FROM HYPERVISOR CALL AT TL 1Attachments This solution has no attachment |
||||||||||||||||||||||
|