Hi Liam, It works now, thank you so much for your great help.
Thanks and Regards, -Leo > Hi Leo, > > Leo Liu wrote, On 16/06/2009 10:27: > >> Leo Liu wrote, On 16/06/2009 09:39: > >>> ENV: > >>> SPARC-Enterprise-T5220 boxes > >>> Sunt5220b is the source node with source domain > >> ldom2, ldom2 used a flat file as its vdisk(as a > full > >> disk) which locates on a share disk; > >>> Sunt5220a is the target node, the target domain > >> still used a flat file as its vdisk which also > >> locates on a share disk; > > > > Hi Liam, > > > > Thanks for your quick reply, I am not sure if I got > your idea, you mean I > should use /ldom2/bootdisk from > /dev/vx/dsk/ldoquitmdg2/ldomvol2 on both > source and target domains? Not only the same name but > also the same > storage(here it's the bootdisk file), in this > situation, after migration, I > need to bring the bootdisk file online on the target > node, then I can access > the target ldom? > > > > Correct, not just the same name but the same storage > and if you are doing > a migration while the domain is active (warm > migration), it needs to be > accessible on the target before the migration starts. > > Otherwise, if the disk image cannot be accessed on > both the source and > target systems at the same time, you would have to > unbind the domain before > you do the migration and bring the boot disk online > on the target system > before you bind the domain again. > > HTH > > - Liam > _______________________________________________ > ldoms-discuss mailing list > ldoms-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ldoms-dis > cuss -- This message posted from opensolaris.org
