Exporting VxVM volumes to a non-global zone

A volume device node can be exported for use in non-global zone using the zonecfg command. The following procedure makes a volume vol1 available in the non-global zone myzone.


Exporting raw volumes to non-global zones has implicit security risks. It is possible for the zone administrator to create malformed file systems that could later panic the system when a mount is attempted. Directly writing to raw volumes, exported to non-global zones, and using utilities such as dd can lead to data corruption in certain scenarios.

To export VxVM volumes to a non-global zone

  1. Create a volume vol1 in the global zone:

      global# ls -l /dev/vx/rdsk/rootdg/vol1
      crw-------   1 root     root     301, 102000 Jun  3
      12:54 /dev/vx/rdsk/rootdg/vol1crw-------   1 root     sys      301, 10200
      0 Jun  3 12:54 /devices/pseudo/vxio@0:rootdg,vol1,102000,raw
  2. Add the volume device vol1 to the non-global zone myzone:

      global# zonecfg -z myzone
      zonecfg:myzone> add device
      zonecfg:myzone:device> set match=/dev/vx/rdsk/rootdg/vol1
      zonecfg:myzone:device> end
      zonecfg:myzone> commit
  3. Ensure that the devices will be seen in the non-global zone:

      global# zoneadm -z myzone halt
      global# zoneadm -z myzone boot
  4. Verify that /myzone/dev/vx contains the raw volume node and that the non-global zone can perform I/O to the raw volume node.

    The exported device can now be using for performing I/O or for creating file systems. Symantec recommends using VxFS file systems, due to the increased fault tolerance provided by VxFS.