You can a vds to any domain. Adding a vds to a domain just allows that domain to export virtual disks to other domains. It makes more sense to add a vds to an I/O domain because that domain does not depend on any other domain.
A domain can also export a virtual disk to itself. This allows a domain to see a backend as a virtual disk. However this feature is currently not documented because it hasn't been tested. This feature will make more sense with VIO DR, and you will, for example, be able to access a file or a volume as a virtual disk from the service domain exporting that file or volume. alex. Misha Chawla Shanker wrote: > Hi, > > I know that a VDS is meant to be a service from which devices can be > exported to guests, but what I found is that the LDM allows a VDS to be > associated with a guest ldom and allows a device from the same VDS to be > exported to the same guest. > > Let me explain with an example, consider ldom2 which is a guest ldom, I > have associated a VDS with it: > > # ldm list-services ldom2 > VDS > NAME VOLUME OPTIONS DEVICE > ldom2-vds0 testvol > /dev/vx/dsk/vxpooldg/testvol > > As can be seen above, ldom2 has a VDS called "ldom2-vds0" and it has a > volume exported as a vdisk from this service. > > # ldm list-bindings ldom2 > DISK > NAME VOLUME TOUT > DEVICE SERVER > testvol_from_ldom2-vds0 testvol at ldom2-vds0 disk at 0 > ldom2 > > > Then the same vdisk (backed by the volume) is bound to the the same > guest ldom2!! > > How does the LDC channel get established in this scenario ? > Is this a supported configuration? If not, why does LDM allow this ? > > Regards, > Misha. > > > ------------------------------------------------------------------------ > > _______________________________________________ > ldoms-discuss mailing list > ldoms-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
