Skip to main content

Contents

  1. Preface
  2. Chapter 1 Software Requirements
    1. Click XCP/Oracle Solaris and Required SRUs/Patches
    2.  How to Obtain XCP and Oracle Solaris SRUs/Patches/Oracle VM Server for SPARC
    3.  Web Browser
    4.  Software Supporting Remote Storage
    5.  Obtaining the SAS-2 Integrated RAID Configuration Utility
    6.  Existing XCP Firmware Versions and Support Information
  3. Chapter 2 XCP 2430-Related Information
    1.  Latest Information on XCP 2430
    2. Click Notes and Restrictions
    3.  XCP 2430 Problems and Workarounds
  4. Chapter 3 Information on Software
    1. Click Notes and Restrictions
    2. Click Problems With XCP and Workarounds
    3. Click Problems With Oracle Solaris and Workarounds
  5. Chapter 4 Information on SPARC M10-1 Hardware
    1. Click Notes and Restrictions
    2.  Problems With Hardware and Workarounds
  6. Chapter 5 Information on SPARC M10-4 Hardware
    1. Click Notes and Restrictions
    2.  Problems With Hardware and Workarounds
  7. Chapter 6 Information on SPARC M10-4S Hardware
    1. Click Notes and Restrictions
    2.  Problems With Hardware and Workarounds
  8. Chapter 7 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
  9. Chapter 8 Information on SPARC M10 Manuals

Notes on Live Migration of Oracle VM Server for SPARC


Notes on Live Migration of Oracle VM Server for SPARC
  1. If you execute the ldm migrate-domain command in Oracle VM Server for SPARC to perform a live migration, the following problems occur with the XSCF.
    - If you execute the showdomainstatus(8) command, "Unknown" is the status displayed for the migrated guest domain.
    If you execute the ldm add-spconfig command from the migrated control domain to save configuration information, the status will be displayed normally by the showdomainstatus(8) command.

    - After a live migration is performed, if showdomainstatus(8) is then executed at the migration source, "Host stopped" is the status displayed for the migrated and non-existent guest domain.

    - When a physical partition (PPAR) is powered off by the poweroff(8) command, not all of the guest domains may be shut down correctly.

    - When a guest domain is reset by the reset(8) command, a guest domain other than the specified one may be reset. To reset a guest domain, do so from the guest domain, not the XSCF.

    - If SNMP is set, the name of the guest domain under trap notification may be incorrect.
  1. The migration with the ldm migrate-domain command is not supported if the logical domain at the migration source is in the OpenBoot PROM state.
    Perform migration with the ldm migrate-domain command after changing the logical domain at the migration source to either of the following states (CR 15858731):
    - Stopped state (bound state)

    - State where Oracle Solaris is running
  1. Before performing a live migration, check the physical partition containing the logical domains targeted by the live migration. Check whether Oracle Solaris 11.3 or later is installed on any logical domains (except the control domain) and Oracle Solaris kernel zones in the physical partition.
    For every logical domain and Oracle Solaris kernel zone that has Oracle Solaris 11.3 or later installed, perform the following steps before performing a live migration.
    1. Add the following line to the /etc/system file.
set uhrt_enable = 0x0
  1. 2. Reboot the logical domain or Oracle Solaris kernel zone.
  1. The "sparc64-class1" value of the cpu-arch property is being supported from Oracle VM Server for SPARC 3.1.1 onwards. For details on the cpu-arch property and its values, see the Oracle VM Server for SPARC Reference Manual for the version used.
  1. The value of the cpu-arch property, which supports live migration, differs according to the type of CPU operation on the physical partition and the version of Oracle VM Server for SPARC. Refer to the following table. For details on types of CPU operation on physical partitions, see "7.2.1 CPU Mounted on a Physical Partition and CPU Operational Mode" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide.
Table 3-4  cpu-arch Property Values That Support Live Migration (on Oracle VM Server for SPARC 3.1.1 or Later)
Migrate To
 Run on SPARC64 X+
 Run on SPARC64 X Compatible
Run on SPARC64 X
Migrate From
Run on SPARC64 X+ generic, native, sparc64-class1 generic, sparc64-class1
Run on SPARC64 X Compatible
Run on SPARC64 X		 generic, sparc64-class1 generic, native, sparc64-class1
Table 3-5  cpu-arch Property Values That Support Live Migration (on Oracle VM Server for SPARC 3.1 or 3.1.0.1)
Migrate To
 Run on SPARC64 X+
 Run on SPARC64 X Compatible
Run on SPARC64 X
Migrate From
Run on SPARC64 X+ generic, native generic
Run on SPARC64 X Compatible
Run on SPARC64 X		 generic generic, native
Table 3-6  cpu-arch Property Values That Support Live Migration (on Oracle VM Server for SPARC 3.0)
Migrate To
 Run on SPARC64 X+
 Run on SPARC64 X Compatible
Run on SPARC64 X
Migrate From
Run on SPARC64 X+ native none
Run on SPARC64 X Compatible
Run on SPARC64 X		 none generic, native
  1. For the cpu-arch property values that enable live migration between SPARC M12 and SPARC M10 systems, see Table 3-7.
Table 3-7  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 Table 3-4, Table 3-5, and Table 3-6.
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.
  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.
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. If you perform a live migration of a domain with a kernel zone running, from a SPARC M10 system with XCP 2230 or later, the following output is displayed, 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.
  1. Live migration from a SPARC M10 system with XCP 2210 or newer, to another SPARC M10 system with XCP 2092 or older fails and produces the following error message:
primary# ldm migrate ldg1 root@target-name
Target Password:
Domain ldg1 is using features of the system firmware that are not supported in the version of the firmware running on the target machine.
Domain Migration of LDom ldg1 failed.
  1. When performing a live migration from a SPARC M10 system with XCP 2210 or later, to another SPARC M10 system, make sure to update the XCP firmware of the target system to XCP 2210 or later.
  1. Refer to the following table to determine the feasibility of performing a live migration, based on the version of the firmware.
Table 3-8  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
Migrate From   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
SPARC M12 Available Available(*2) Available(*2) Not available Available(*2) Not available
SPARC M10
(XCP 2230 or later)		 Available(*2) Available Available(*3) Not available Available(*3) Not available
SPARC M10
(XCP 2210 or later
and earlier than XCP 2230)		 Available(*2) Available Available Not available Available(*3) Available(*3)
SPARC M10
(XCP 2092 or earlier)		 Available(*2) Available Available Available Available(*3) Available(*3)
SPARC
T-series
M-series(*1)
(SysFW 8.4 or later)		 Available(*2) Available(*3) Available(*3) Not available Available Not available
SPARC
T-series
M-series(*1)
(SysFW 8.3 or earlier)		 Available(*2) Available(*3) Available(*3) Not available Available Available
*1 It is an Oracle system, such as SPARC M5/M6, which supports Oracle VM Server for SPARC.
*2 For details, see "Notes on Live Migration of Oracle VM Server for SPARC" in the Fujitsu SPARC M12 Product Notes.
*3 Live migration is possible only for cpu-arch=generic.
  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

Top of Page