LDOM guests do not recognize VxVM volumes when they are assigned to the domain as a "slice".

To utilize a filesystem created from the control domain inside a guest domain the VxVM volume should be exported to the guest using the "options=slice" option.

 

There is a known Sun issue (Bug id 6558966) which prevents a volume exported as a "slice" from being accessible inside the guest. Sun patch 138042-01 (or later) contains the fix for this issue.

 

From the LDOM support guide:

 

Caution: With Solaris 10, Update 5 and LDoms 1.1, a volume by default shows  up as a full disk in the guest. The Virtual Disk Client driver writes a VTOC on  block 0 of the virtual disk, which will end up as a WRITE on block 0 of the
VxVM volume. This can potentially cause data corruption, because block 0  of the VxVM volume contains user data. Using options=slice exports a  volume as a slice to the guest and does not cause any writes to block 0,  therefore preserving user data.

After the patch is applied the previously created file system should be accessible.

For example, to add a VxVM volume to a LDOM guest from the control domain the following commands may be issued (where  "ldom1" is the domain and "testvol" is the VxVM volume which will be added to the guest domain)

Syntax:
ldm [function][options] [device] [volume@service_name]
Refer to the Solaris man page for the "ldm" command for additional information relating to the available parameters which modify the command.

a) Add a Virtual Disk Server device with the "slice" option:
# ldm add-vdsdevoptions=slice /dev/vx/dsk/testdg/testvolslicevol@primary-vds0

b) Add the Virtual Disk Slice to the domain configuration
# ldm add-vdisk vsliceslicevol@primary-vds0 ldom1

c) Mount the slice inside the guest (execute the command from a prompt running inside the guest).
# mount -F vxfs /dev/dsk/c0d2s0/mnt