On 16/01/2009 15:29, Tom Gendron wrote: > Hi, > > I am playing with the warm migration feature of ldm 1.1 and notice that > there is no provision made to move the root disk from source to target > machine. I must do this by some external means correct? >
Yes, the disk backend(s) must be visible to both machines. e.g. a SAN or have the disk image files exported via NFS. > My setup has two T5x20s with three to four ldoms each. Both machines are > setup identically and the ldoms boot off of local files that resides in > a zfs file system on one of the internal disks on each server. From the > control domain it looks like this. > > VDS > NAME VOLUME OPTIONS DEVICE > primary-vds0 ldm1-vol1 /export/ldoms/ldm1/rootdisk > ldm2-vol1 /export/ldoms/ldm2/rootdisk > > > Using shared storage, what are options in getting this rootdisk from > ldom1 from the source to the target machine? > > Note that I do have a Fiber channel JBOD array attached to both machines > but I am not sure how to use it to faciliate warm migration and moving > this file. With Vmotion the vmdk file (rookdisk) is not moved becuase of > vmfs being a clustered file system. Anyone care to offer an easy way to > approximate vmotion w.r.t to the ldom root disk file? > > I am Looking for ideas. > You don't really "move" the file. If the disk images are on shared storage and visible to both machines then you keep it at the same location and bother the source and target machines access it at that location. e.g. both source and target machines would have a disk added like this. ldm add-vdsdev /net/somemachine/disk.image disk1 at primary-vds0 or something similar for a SAN LUN HTH -- Liam
