1 Reply Latest reply: Dec 21, 2011 5:29 AM by 855105 RSS

    Cold migration of old LDoms with slice-based system disks - not possible?

    874401
      We have a couple of older T5120s that we would like to upgrade both the firmware and LDoms software on.

      Currently they both run LDoms 1.2; we'd like to go to 2.0 or hopefully 2.1.

      --
      cas2:1:1006 [root] # ldm -V

      Logical Domain Manager (v 1.2_patch)
      Hypervisor control protocol v 1.4
      Using Hypervisor MD v 1.1

      System PROM:
      Hypervisor v. 1.7.4. @(#)Hypervisor 1.7.4.a 2009/09/21 08:25\015

      OpenBoot v. 4.30.4 @(#)OBP 4.30.4 2009/08/19 07:23
      --

      We thought we would clear out our other "sandbox" T5120 (with LDoms 2.0) and migrate the client LDoms in the machines to be updated over to the sandbox, so if anything went wrong we could clear out the old 1.2 machine and then re-migrate the LDoms back over to it.

      Well, it turns out the client LDoms on the 1.2 system were made with paired slices as the system disks instead of files :-(

      --
      vdisk0@casdev c1t0d0s3
      vdisk1@casdev c1t1d0s3
      vdisk0@casray c1t0d0s1
      vdisk1@casray c1t1d0s1
      --

      In one of the client LDoms it has (as you would expect, given this setup)

      --
      NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
      casdev active -n---- 5000 12 4G 0.1% 414d 18h

      [...]

      DISK
      NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
      vdisk0 c1t0d0s3@primary-vds0 0 disk@0 primary
      vdisk1 c1t1d0s3@primary-vds0 1 disk@1 primary

      [...]

      --

      The control LDom for these client LDoms has 2 disks and slice 0 of each disk (~ 20 GB) is used for the control LDom, and there are these other slices (slice 1, 3, ... also each ~ 20 GB) for the client LDoms.

      The target "sandbox" system we wanted to migrate to also has 2 disks, but slice 0 of each is a single, disk-spanning partition - since we're using files as virtual disks for the client LDoms that were previously on that system (since wiped out), there was no need for multiple slices.

      I'm guessing that with this setup there is no way to even do a cold migration of the old LDoms 1.2 client LDoms to the newer LDoms 2.0 sandbox system, short of a complete reinstall of the sandbox to create a similar slice-based setup. :-(

      (Unless it involved somehow re-slicing the control LDom's disks and making identically-sized partitions to match the old system's and then - somehow - "dd"'ing the source system's client LDom disk slices over into the target system's)

      Am I right?

      Edited by: Riot Nrrrd™ on Oct 28, 2011 3:30 PM
        • 1. Re: Cold migration of old LDoms with slice-based system disks - not possible?
          855105
          I'm guessing that with this setup there is no way to even do a cold migration of the old LDoms 1.2 client LDoms to the newer LDoms 2.0 sandbox system, short of a complete reinstall of the sandbox to create a similar slice-based setup. :-(

          (Unless it involved somehow re-slicing the control LDom's disks and making identically-sized partitions to match the old system's and then - somehow - "dd"'ing the source system's client LDom disk slices over into the target system's)
          If you are not using SAN-disks, then it is a bit difficult to do the migration. If you are using ZFS on LDoms 2.0 sandbox, you could try to create ZFS volumes for guest domains and send data on those volumes from LDoms 1.2 system, after creating guest domains from exported XML configurationg files.

          Does this sound tryable solution?