Misha Chawla Shanker wrote: >Yes it is a single file. >And I believe you meant "assign that to the guest" instead of "assign >that to the alternate" below? > > No, here is what i would do from the primary
# cp /fsmnt1/ldom1_boot.img /fsmnt1/ldom2_boot.img Then add the dev to alternate such that the list below now shows (pl. see the DEVICE col) # /opt/SUNWldm/bin/ldm list-services alternate VDS NAME VOLUME OPTIONS DEVICE alternate-vds0 vdisk1 /fsmnt1/ldom2_boot.img The file /fsmnt1/ldom1_boot.img physcially present on the domain named "alternate" is not used at all - -regards -pallab >Regards, >Misha. > >On Jan 11, 2008 5:31 PM, Pallab Bhattacharya ><Pallab.Bhattacharya at sun.com> wrote: > > >>So >> >>/fsmnt1/ldom1_boot.img >> >>is a single file as seen from the primary ? >> >>Can you pl. copy the file to a different name and assign >>that to the alternate? >> >>-regards >>-pallab >> >> >> >>Misha Chawla Shanker wrote: >> >> >> >>>To all Alternate I/O domain Gurus, >>> >>>I have an alternate i/o domain setup on one of my T2000 box. >>>I am stuck at the point where only one boot disk of the guest >>>shows up inside the guest and not the other. >>> >>>>From the control domain: >>># ldm list >>>NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME >>>primary active -n-cv SP 4 4G 0.8% 1d 3h 24m >>>alternate active -n--v 5000 4 4G 0.6% 22h 31m >>>ldom1 active -n--- 5001 4 4G 0.5% 23m >>> >>>guest domain bindings: >>># ldm list-bindings ldom1 | grep vds0 >>> vdisk1 vdisk1 at primary-vds0 disk at 0 primary >>> vdisk2 vdisk1 at alternate-vds0 disk at 1 alternate >>> >>># /opt/SUNWldm/bin/ldm list-services primary >>>VDS >>>NAME VOLUME OPTIONS DEVICE >>> primary-vds0 vdisk1 /fsmnt1/ldom1_boot.img >>> >>># /opt/SUNWldm/bin/ldm list-services alternate >>>VDS >>> NAME VOLUME OPTIONS DEVICE >>> alternate-vds0 vdisk1 /fsmnt1/ldom1_boot.img >>> >>>Inside the guest I see only: one disk: c0d1: >>># format >>>Searching for disks...done >>>AVAILABLE DISK SELECTIONS: >>> 0. c0d1 <SUNVDSK cyl 22717 alt 2 hd 1 sec 600> >>> /virtual-devices at 100/channel-devices at 200/disk at 1 >>>Specify disk (enter its number) >>> >>>Both the files are accessible from both the i/o domains: >>>primary # ls -l /fsmnt1/ldom1_boot.img >>>-rw------T 1 root root 6979321856 Jan 10 17:06 >>>/fsmnt1/ldom1_boot.img >>> >>>alternate # ls -l /fsmnt1/ldom1_boot.img >>>-rw------T 1 root root 6979321856 Jan 10 17:11 >>>/fsmnt1/ldom1_boot.img >>> >>>Also, from the ok prompt of the guest, I can see 2 disks attached to it: >>>a) /virtual-devices at 100/channel-devices at 200/disk at 1 <-- this one is >>>visible inside the guest as c0d1 >>>b) /virtual-devices at 100/channel-devices at 200/disk at 0 <-- this one is >>>not >>>visible, should have showed up as "c0d0" >>> >>>"c0d1" visible inside the guest is the backed by the file exported >>> >>> >>>from the alternate i/o domain. >> >> >>>but the other disk backed by the file exported from the primary i/o >>>domain is not visible. >>> >>>Any idea what may be going wrong here? >>> >>>Thanks, >>>Misha. >>>_______________________________________________ >>>ldoms-discuss mailing list >>>ldoms-discuss at opensolaris.org >>>http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss >>> >>> >>> >>> >>-- >>Pallab Bhattacharya >>Performance & Architecture Engineering >> >> >> >> -- Pallab Bhattacharya Performance & Architecture Engineering
