I am a beginner. I just start to test LDOM. I installed and setup LDOM for the first time on a SunFire T2000. I setup a logic domain and my first guest domain by following LDOM 1.1 Admin guide. Then I decide to reinstall OS since I want difference slice size and no mirror, so I can use extra disk for other testing. I reinstalled my OS on one of the disk. weird things happened, after I finished installation of OS, applied patches, installed ldom 1.1 package and login in for the first time. Weird things happened, there are two domains control domain and guest domain I setup before my second OS install are still there up and running. Is this because those ldom configurations are actually save in ALOM, not on disk?
Thanks, Yang -----Original Message----- From: [email protected] [mailto:ldoms-discuss-bounces at opensolaris.org] On Behalf Of ldoms-discuss-request at opensolaris.org Sent: Thursday, January 22, 2009 3:00 PM To: ldoms-discuss at opensolaris.org Subject: ldoms-discuss Digest, Vol 18, Issue 18 Send ldoms-discuss mailing list submissions to ldoms-discuss at opensolaris.org To subscribe or unsubscribe via the World Wide Web, visit http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss or, via email, send a message with subject or body 'help' to ldoms-discuss-request at opensolaris.org You can reach the person managing the list at ldoms-discuss-owner at opensolaris.org When replying, please edit your Subject line so it is more specific than "Re: Contents of ldoms-discuss digest..." Today's Topics: 1. Re: ldm 1.1 warm migration and shared storage (Alexandre Chartre) ---------------------------------------------------------------------- Message: 1 Date: Thu, 22 Jan 2009 05:22:37 -0800 From: Alexandre Chartre <[email protected]> Subject: Re: [ldoms-discuss] ldm 1.1 warm migration and shared storage To: Tom Gendron <Tom.Gendron at Sun.COM> Cc: ldoms-discuss at opensolaris.org Message-ID: <4978731D.90009 at sun.com> Content-Type: text/plain; format=flowed; charset=ISO-8859-1 On 01/16/09 10:21, Tom Gendron wrote: > > > Liam Merwick wrote: >> 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. >> >> > I see how NFS could do this but I am confused on how to do it with my > SAN. I have direct attached fiber channel disks that are visible to > both hosts but I am not sure how to share the file system. ZFS is going > to label the pool and be tied to one of the hosts. I would have to > explicitly export it and then import it to the target machine. Is there > a filesystem solution to this with native Solaris tools? I think QFS > would solve this but that is not native. Anything else? With a SAN, you directly export a LUN as a virtual disk, and the guest domain will use that disk. Then you can use ZFS or whatever filesystem from the guest domain. > How are we planning to solve this when we complete the migration > capability as in live migration? We plan to support more types of storage, like ZFS in some future version of migration. Basically a zpool will be initially imported on the source system, then when the target domain is suspended the zpool will be exported from the target system and imported on the source system. Finally the domain will be resumed on the target system. So the zpool will be automatically migrated during the migration by using a zpool export/import. alex. >>> 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 >> _______________________________________________ >> ldoms-discuss mailing list >> ldoms-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss >> > > -- > Tom Gendron > SPARC Systems Technologist > U.S Systems Practice > Sun Microsystems > 781 442-2622 > > > ------------------------------------------------------------------------ > > _______________________________________________ > ldoms-discuss mailing list > ldoms-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss ------------------------------ _______________________________________________ ldoms-discuss mailing list ldoms-discuss at opensolaris.org http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss End of ldoms-discuss Digest, Vol 18, Issue 18 *********************************************
