Skip to main content

Contents

  1. Preface
  2. Chapter 1 Latest Information
    1.  Latest Information
    2.  Revision Information
  3. Chapter 2 Software Requirements
    1. Click Supported Firmware and Oracle Solaris Versions
    2.  Web Browser
    3.  Software Supporting Remote Storage
    4.  XCP and Oracle Solaris Version Supporting Power Aware Dispatcher Function
    5.  How to Obtain XCP and Oracle Solaris SRU/Patch/Oracle VM Server for SPARC
    6. Click Notes on Memory
    7. Click Notes on Mixing Different Hardware
    8.  Obtaining the SAS-2 Integrated RAID Configuration Utility
  4. Chapter 3 Information on XCP
    1. Click Latest Information on XCP
    2.  XCP Firmware Versions and Support Information
    3. Click Notes and Restrictions
    4. Click Problems With XCP and Workarounds
  5. Chapter 4 Information on Oracle Solaris
    1. Click Notes and Restrictions
    2. Click Problems With Oracle Solaris and Workarounds
  6. Chapter 5 Information on SPARC M12 System Hardware
    1. Click Notes and Restrictions
    2.  Problems With Hardware and Workarounds
  7. Chapter 6 Information on the PCI Expansion Unit
    1.  PCI Expansion Unit Firmware Versions and Support Information
    2. Click Direct I/O Function for the PCI Expansion Unit
    3. Click Problems With the PCI Expansion Unit and Workarounds
  8. Chapter 7 Information on SPARC M12 Manuals

Notes on Live Migration of Oracle VM Server for SPARC


Notes on Live Migration of Oracle VM Server for SPARC
  1. With an Oracle Solaris 11 control domain running Oracle VM Server for SPARC 3.5 or later, cpu-arch=sparc64-class1 and cpu-arch=generic can be set for SPARC M12 systems. Likewise, with an Oracle Solaris 10 control domain running Oracle VM Server for SPARC 3.2 with patch 151934-04 or later, cpu-arch=generic can be set for SPARC M12 systems. With other versions of Oracle VM Server for SPARC, only cpu-arch=native can be set for SPARC M12 systems, which limits live migrations for those configurations to another SPARC M12 system.
  1. For the cpu-arch property values that enable live migration between SPARC M12 and SPARC M10 systems, see Table 4-4.
Table 4-4  cpu-arch Property Values That Enable Live Migration Between SPARC M12 and SPARC M10 Systems
Migrate To SPARC M12 SPARC M10
Migrate From    
SPARC M12 generic
sparc64-class1
native		 generic
sparc64-class1
SPARC M10 generic
sparc64-class1		 generic
sparc64-class1
native(*1)
*1 For details, see "Notes on Live Migration of Oracle VM Server for SPARC" in the Fujitsu M10/SPARC M10 Systems Product Notes.
To perform a live migration of a logical domain with cpu-arch=sparc64-class1 between a SPARC M12 system and a SPARC M10 system, perform the following procedure.
Note - If both of the following conditions are met, you do not need to perform the procedure.
- Oracle VM Server for SPARC 3.5 or later is installed on the control domain of the SPARC M10.

- SRU 11.3.23.5.0 or later is installed on the logical domain.
  1. Add the following lines to the /etc/system file on the logical domain.
set enable_1ghz_stick = 1
set uhrt_enable=0x0
  1. Reboot the logical domain with the above settings.
  1. Refer to the following table to determine the feasibility of performing a live migration based on the version of the firmware.
Table 4-5  Versions of the Firmware That Support Live Migration
Migrate To SPARC M12 SPARC M10 SPARC M10 SPARC M10 SPARC
T-series
M-series		 SPARC
T-series
M-series
    (XCP 2230 or later) (XCP 2210 or later
and earlier than XCP 2230)		 (XCP 2092 or earlier) (SysFW 8.4
or later)		 (SysFW 8.3
or earlier)
Migrate From            
SPARC M12 Available Available(*2) Available(*3) Not available Available(*3) Not available
SPARC M10
(XCP 2230 or later)
 Available(*2) Available Available(*4) Not available Available(*4) Not available
SPARC M10
(XCP 2210 or later
and earlier than XCP 2230)		 Available(*2) Available Available Not available Available(*4) Available(*4)
SPARC M10
(XCP 2092 or earlier)		 Available(*2) Available Available Available Available(*4) Available(*4)
SPARC
T-series
M-series(*1)
(SysFW 8.4 or later)		 Available(*3) Available(*4) Available(*4) Not available Available Not available
SPARC
T-series
M-series(*1)
(SysFW 8.3 or earlier)		 Available(*3) Available(*4) Available(*4) Not available Available Available
*1 It is an Oracle system, such as SPARC M5/M6, which supports Oracle VM Server for SPARC.
*2 On the SPARC M12 with an Oracle Solaris 11 control domain, only Oracle VM Server for SPARC 3.5 or later enables you to perform a live migration. For the SPARC M12 with an Oracle Solaris 10 control domain, see also Table 4-6.
*3 On the SPARC M12 with an Oracle Solaris 11 control domain, only Oracle VM Server for SPARC 3.5 or later enables you to set cpu-arch=generic and perform a live migration. For the SPARC M12 with an Oracle Solaris 10 control domain, see also Table 4-6.
*4 Live migration is possible only for cpu-arch=generic.
  1. The following table shows cross-CPU (cpu-arch=generic) live migration requirements for the SPARC M12 with an Oracle Solaris 10 control domain.
Table 4-6  Software Requirements for the SPARC M12 With an Oracle Solaris 10 Control Domain
Platform Control Domain Requirement
SPARC M12 Oracle Solaris 10 Oracle VM Server for SPARC 3.2
151934-04 or later
SPARC M10/SPARC T-Series Oracle Solaris 10 Oracle VM Server for SPARC 3.2
151934-03 or later
  1. When a live migration is performed between a SPARC M12 system and a SPARC M10 system, the uptime of a logical domain may not be displayed correctly.

    [Example]
    UPTIME of a logical domain displays 6m for a SPARC M12 system.
M12# ldm list-domain
NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME
primary active -n-cv- UART 24 8G 0.8% 0.2% 21d 5h 22m
guest active -n---- 5000 8 8G 0.6% 0.6% 6m
  1. After a live migration is performed, UPTIME of the logical domain displays 1h11m for the SPARC M10 system.
M10# ldm list-domain
NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME
primary active -n-cv- UART 8 8G 0.1% 0.1% 4h 18m
guest active -n---- 5000 8 8G 0.0% 0.0% 1h 11m
  1. If you perform a live migration of the domain with the kernel zone running from a SPARC M12 system, the following message is output, and the live migration fails.
# ldm migrate-domain ldg1 root@target-name
Target Password:
Failure occurred while preparing domain ldg1 for suspend operation
Live migration failed because Kernel Zones are active.
Stop Kernel Zones and retry.
Timeout waiting for domain ldg1 to suspend
Domain Migration of domain ldg1 failed, domain suspend failure.
Domain Migration of LDom ldg1 failed
  1. To perform a live migration of a domain with a kernel zone running, stop the kernel zone beforehand.

Top of Page