no need to apologize... you are learning. It's rather a steep learning curve you have to change your thought process on how you think about interfacing with hardware.
Think of it this way, the LDOM doesn't know about any hardware that the primary OS and LDM don't tell it about. This includes harddrives, storage media (like CDROMs or ISO files) and even network interface cards.
in order for you to install from an .iso file you have to make the .iso available to the LDOM as a virtual disk.
to do this there are two steps.
#1. you have to add the .iso as virtual disk device (vdsdev) like this:
root@server:~# ldm add-vdsdev
Usage:
ldm add-vdsdev [-f] [-q] [options={ro,slice,excl}] [mpgroup=<mpgroup>]
<backend> <volume_name>@<service_name>
root@server:~# ldm add-vdsdev /var/tmp/sol-11_1_14_5_0-text-sparc.iso install@vds0
root@server:~# ldm list -o disk primary
NAME
primary
VDS
NAME VOLUME OPTIONS MPGROUP DEVICE
install /var/tmp/sol-11_1_14_5_0-text-sparc.iso
This is assuming you have already created your virtual disk server (vds0) and the LDOM itself.
#2.Next you will have to export that vds device as a disk to the LDOM, like this:
root@server:~# ldm add-vdisk
Usage:
ldm add-vdisk [timeout=<seconds>] [id=<diskid>]
<disk_name> <volume_name>@<service_name> <ldom>
root@server:~# ldm add-vdisk install install@vds0 ldom
root@server:~# ldm list -0 disk ldom
Usage:
ldm list [-e] [-l] [-S] [-o <format>] [-p] [<ldom>...]
'format' is one or more of:
cmi,console,core,cpu,crypto|mau,disk,domain,memory|mem,
network|net,physio,resmgmt,serial,status
root@server:~# ldm list -o disk ldom
NAME
ldom
DISK
NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
swap ldom_swap@vds0 4 disk@4 primary
disk0 ldom_disk0@vds0 0 disk@0 primary
disk1 ldom_disk1@vds0 1 disk@1 primary
install install@vds0 2 disk@2 primary
now you have an install disk to boot from...