X

Logical Domains Physical-to-Virtual (P2V) Migration

Guest Author

The Logical domains P2V migration tool automatically converts an existing physical system
to a virtual system that runs in a logical domain on a chip multithreading (CMT) system.
The source system can be any of the following:


    \*  Any sun4u SPARC system that runs at least the Solaris 8 Operating System
    \*  Any sun4v system that runs the Solaris 10 OS, but does not run in a logical domain

In this entry I will demonstrate how to use Logical domains P2V migration tool to migrate Solaris running on V440 server (physical)
Into guest domain running on the T5220 server (virtual)
Architecture layout :


Before you can run the LogicalDomains P2VMigration Tool, ensure that the following are true:

  •     Target system runs at least LogicalDomains 1.1 on the following:
  •      Solaris 10 10/08 OS
  •     Solaris 10 5/08 OS with the appropriate LogicalDomains 1.1 patches
  •     Guest domains run at least the Solaris 10 5/08 OS
  •     Source system runs at least the Solaris 8 OS

prerequisites

In addition to these prerequisites, configure an NFS file system to be shared by both the source
and target systems. This file system should be writable by root.However, if a shared file system
is not available, use a local file system that is large enough to hold a file system dump of the
source system on both the source and target systems Limitations
Version 1.0 of the LogicalDomains P2VMigration Tool has the following limitations:

  •      Only UFS file systems are supported.
  •      Each guest domain can have only a single virtual switch and virtual disk
  •      The flash archiving method silently ignores excluded file systems.
The conversion from a physical system to a virtual system is performed in the following phases:
  • Collection phase   Runs on the physical source system. collect creates a file system image of the source system based on the configuration information that it collects about the source system.
  • Preparation phase. Runs on the control domain of the target system. prepare creates the logical domain on the target system based on the configuration information collected in the collect phase.
  • Conversion phase. Runs on the control domain of the target system. In the convert phase,the created logical domain is converted into a logical domain that runs the Solaris 10 OS by using the standard Solaris upgrade process.

    Collection phase
    On the target machine T5220

    Prepare the NFS server in order to hold the a file system dump of the source system on both the source and target systems.
    In this use case I will use the target machine (T5220) as the NFS server
    # mkdir /p2v
    # share -F nfs -o root=v440 /p2v

    Verify the NFS share
    # share
    -  /p2v  root=v440  ""
    Install the Logical Domains P2V MigrationTool
    Go to the Logical Domains download page at http://www.sun.com/servers/coolthreads/
    ldoms/get.jsp.
    Download the P2V software package, SUNWldmp2v
    Use the pkgadd command to install the SUNWldmp2v package
    # pkgadd -d . SUNWldmp2v

    Create the /etc/ldmp2v.conf file we will use it later
    # cat /etc/ldmp2v.conf

    VSW="primary-vsw0"
    VDS="primary-vds0"
    VCC="primary-vcc0"
    BACKEND_PREFIX="/ldoms/disks/"
    BACKEND_TYPE="file"
    BACKEND_SPARSE="no"
    BOOT_TIMEOUT=10
    On the source machine V440
    Install the Logical Domains P2V MigrationTool
    # pkgadd -d . SUNWldmp2v
    Mount the NFS share
    # mkdir /p2v
    # mount t5220:/p2v /p2v
    Run the collection command
    # /usr/sbin/ldmp2v collect -d /p2v/v440
    Collecting system configuration ...
    Archiving file systems ...
    DUMP: Date of this level 0 dump: August 2, 2009 4:11:56 PM IDT
    DUMP: Date of last level 0 dump: the epoch
    DUMP: Dumping /dev/rdsk/c1t0d0s0 (mdev440-2:/) to /p2v/v440/ufsdump.0.
    The collection phase took 5 minutes for 4.6 GB dump file
    Preparation phase
    On the target machine T5220
    Run the preparation command
    We will keep the source machine (V440) mac address
    # /usr/sbin/ldmp2v prepare -d /p2v/v440 -o keep-mac v440
     Creating vdisks ...
    Creating file systems ...
    Populating file systems ...
    The preparation phase took 26 minutes

    We can see that for each physical cpu on the V440 server the LDom P2V Tool create 4 vcpu on the guest domain and assigns the same amount memory that the physical system has
    # ldm list -l v440

    NAME             STATE      FLAGS   CONS    VCPU  MEMORY   UTIL  UPTIME
    v440                   inactive   ------                                   4     8G

    CONTROL
        failure-policy=ignore

    DEPENDENCY
        master=

    NETWORK
        NAME             SERVICE                     DEVICE     MAC               MODE   PVID VID                  MTU
        vnet0            primary-vsw0                           00:03:ba:c4:d2:9d        1

    DISK
        NAME             VOLUME                      TOUT DEVICE  SERVER         MPGROUP
        disk0            v440-vol0@primary-vds0

    Conversion Phase
    Before starting the conversion phase shout down the source server (V440) in order to avoid ip address conflict
    On the V440 server
    # poweroff
    On the jumpstart server

    You can use the Custom JumpStart feature to perform a completely hands-off conversion.
    This feature requires that you create and configure the appropriate sysidcfg and profile files for the client on the JumpStart server.
    The profile should consist of the following lines: install_type upgrade root_device  c0d0s0

    The sysidcfg file :

    name_service=NONE
    root_password=uQkoXlMLCsZhI
    system_locale=C
    timeserver=localhost timezone=Europe/Amsterdam
    terminal=vt100 security_policy=NONE nfs4_domain=dynamic network_interface=PRIMARY {netmask=255.255.255.192 default_route=none protocol_ipv6=no}
    On the target server T5220
    # ldmp2v convert -j -n vnet0 -d /p2v/v440 v440Testing original system status ...
    LDom v440 started
    Waiting for Solaris to come up ...
    Using Custom JumpStart
    Trying 0.0.0.0...
    Connected to 0.
    Escape character is '\^]'.

    Connecting to console "v440" in group "v440" ....
    Press ~? for control options ..
    SunOS Release 5.10 Version Generic_139555-08 64-bit
    Copyright 1983-2009 Sun Microsystems, Inc.  All rights reserved.
    Use is subject to license terms.


    For information about the P2V migration tool, see the ldmp2v(1M) man page.

Join the discussion

Comments ( 12 )
  • guest Saturday, January 25, 2014

    Hi,

    I have to move Solaris 10 Global zones with local zones from M9000 to M6-32.

    Please suggest me How can we do this.

    We need Solaris 10 on M6-32 as there was some application dependency to Solaris 10.

    Thanks in advance

    PR


  • guest Saturday, January 25, 2014

    Hi PR,

    You can setup guest domains with Solaris 10 in the M6-32.

    You can migrate the Solaris 10 Global Zones from the M9000 using the ldmp2v tool as described here: http://docs.oracle.com/cd/E38405_01/html/E38406/ldomsp2v.html

    Note: Oracle Solaris 10 systems that have zones can be converted if the zones are detached by using the zoneadm detach command prior to running the ldmp2v collect operation.

    After the P2V conversion completes, use the zoneadm attach command to reattach the zones that have been created on the guest domain.

    HTH,

    Orgad


  • guest Monday, January 27, 2014

    Thanks, Orgad

    would we need to perform same procedure for Whole root zone and Sparse root zone?

    Regards

    PR


  • Orgad Monday, January 27, 2014

    Hi PR,

    Yes, you we need to perform same procedure for Whole root zone and Sparse root zone.

    Thanks,

    Orgad


  • Manivarma Friday, April 4, 2014

    Hi ,

    We are planning to do a p2v but we are already having an latest Version of Sol 10(1/13) so i dont want to upgrade 1 more time in convert phase ..is this possible ? or in convert phase we must upgrade the OS ? Please clarify the same.

    Thanks & Regards,

    Manivarma


  • Orgad Kimchi Friday, April 4, 2014

    Hi Manivarma,

    During the convert phase you must upgrade the OS even if you have the latest Solaris 10 version.

    Thanks,

    Orgad


  • Showkat Ahmad Friday, January 9, 2015

    Hi Team,

    I am planing P2V migration from T5210 to T5-2 server and LDOM to LDOM migration from T5210 to T5-2 server, can any one please suggest me the procedure with possible challanges while performing this activity.

    Thanks


  • guest Friday, January 9, 2015

    Hi,

    Please refer to Chapter 14 "Oracle VM Server for SPARC Physical-to-Virtual Conversion Tool" in the admin guide http://docs.oracle.com/cd/E38405_01/html/E38406/ldomsp2v.html for the P2V procedure.

    Thanks,

    Orgad


  • Showkat Ahmad Wednesday, January 28, 2015

    Hi Orgad,

    My entire existing setup which i am planning to P2V is running on Solaris 11 only (both control domain & LDOMs) and what i understood from the document you shared is that P2V is not possible for hosts which are running Solaris 11.

    what would be workaround in this scenario?

    --------------------------------------------------------------------

    Note - The ldmp2v command does not support any SPARC based system that runs the Oracle Solaris 10 OS with a ZFS root or the Oracle Solaris 11 OS.

    --------------------------------------------------------------------


  • Orgad Wednesday, January 28, 2015

    Hi Ahmad,

    If you are looking for a cross platform migration tool take a look at the Unified Archives technology that was introduced in Solaris 11.2.

    Any archived system from within a Unified Archive can be deployed to any supported same-ISA platform. This support includes crossing virtualization boundaries, so a Unified Archive created on a SPARC T5 LDOM can be supported as a Zone, and a Zone archive can be installed to a bare-metal system. With this ability you can create an image that includes all the software components inside a single image including the Global Zone and all the VMs (non-global zones).

    This can be used to move Solaris 11 systems between physical and virtual deployments (P2V) and vice versa, virtual to physical (V2P).

    For more information see:

    https://blogs.oracle.com/maineoffice/entry/introducing_unified_archives_in_solaris

    Thanks,

    Orgad


  • Sivakumar Wednesday, March 25, 2015

    Hello. I am trying to migrate LDOMs from a T2 server running LDOM 1.3 to a T4 blade running LDOM 3.1. 'ldm migrate' failed because of the version difference.

    Can I use p2v method to do the migration?

    Or is the only way to do is to upgrade/downgrade the LDOM versions to be same? Thanks


  • Orgad Kimchi Wednesday, March 25, 2015

    Hi Sivakumar,

    You need to have the same LDom version on the source and target systems.

    Refer to Supported Platforms in Oracle VM Server for SPARC 3.1.1.1, 3.1.1,

    and 3.1 Release Notes for a list of supported platforms.

    http://docs.oracle.com/cd/E38405_01/html/E38409/migrationissues.html#LDSRNversionrestrictionsformigration

    If you can't upgrade the T2 server you can migrate the guest domain using P2V.

    For more information about P2V see http://docs.oracle.com/cd/E38405_01/html/E38406/ldomsp2v.html

    HTH,

    Orgad


Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha
Oracle

Integrated Cloud Applications & Platform Services