To use migration, your disks need to be shared between the system
you are migrating to/from. It does not matter if you are using slices
or full disks, but this needs to be shared disks. Similarly, if you
use files then your files need to be shared (e.g. using NFS).

alex.

On 10/28/11 14:23, Greg Earle wrote:
All,

After getting advice from my earlier question about downgrading the firmware in 
an LDom to match a proposed firmware/LDoms version upgrade, we revised our 
strategy.

We thought we would clear out our "sandbox" T5120 and migrate the client LDoms in 
the machine to be updated (firmware and LDoms software from 1.2 ->  2.0 or 2.1) so if 
anything went wrong we could clear out the machine and 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 clients it has (as you would expect, given this)

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 clients has 2 disks and slice 0 of each is used for 
the control LDom and there are these other slices (1, 3, ... ) for the client 
LDoms.

The target system we wanted to migrate to also has 2 disks, and slice 0 of each 
is a single disk-spanning partition - since we're using files as virtual disks 
for the client LDoms that were on that system previously.

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 system, short of a 
complete reinstall.

(Unless it involved somehow re-slicing the control LDom 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?

        - Greg


_______________________________________________
ldoms-discuss mailing list
ldoms-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
_______________________________________________
ldoms-discuss mailing list
ldoms-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss

Reply via email to