Information about settings in the Solaris Zones VGP XML file

This topic contains the following sections:

Decription of sections and settings
To get the Global Zone ID - Solaris
To get the Solaris resource pool name
To get the Solaris physical value

Decription of sections and settings

Section	Settings
<GeneralInfo>>	<Name> and <Description> — Name and description of the VGP. <DepotGroupId> — You store VGPs in the Depot. You can get the ID of a depot group by using the command DepotGroup : groupNameToId. <VirtualGuestPackageType> — Specify the following integer: 7 - SolarisNonGlobalZone <VirtualGuestName> — The zone name for the package. The zone name should be alphanumeric and can contain special characters like _ , - , . Example: my-zone
<ZoneInfo>	<ZonePath> — Path to the zone root directory, starting with a forward slash ( / ). For example, enter /home/export/my-zone <ResourcePool> — Resource pool name. For information on how to get the resource pool name, see To get the Solaris resource pool name. <BootArgs> — The boot arguments you want to apply to the zone. For example, enter -m debug to set the boot behavior of SMF to write messages at the debug level. Boot arguments should be: -i altinit -m smf_options -s Example syntax: -m debug,-s <LimitPrivileges> — Specify Limit Privileges without double quotes. Example: default,dtrace_proc,dtrace_user <SchedulingClass> — The scheduling class you want to apply to the zone. The scheduling class controls the allocation of available CPU resources among zones, based on their importance. Valid scheduling classes codes are: FSS — Fair Share sheduler FX — Fixed Priority IA — Inter Active RT — Real Time SYS — System TS — Time Shared
<ZoneInfo> cont	<ProcessorType> — Specify one of the following: Capped Dedicated Capped sets a limit on the amount of CPU resources that can be used by the zone. Dedicated allocates a subset of the system processors for exclusive use by zone. <NumCPUsORRange> — This value is related to the value you set for ProcessorType: ProcessorType=Capped: Enter a positive decimal to represent the CPU cap. ProcessorType=Dedicated: Enter a positive decimal (or range) to represent the number of dedicated CPUs. Number of CPU's should be numeric values or in a range with special character '-'. Examples: 1 1-2 <Importance> — If you specified a CPU range, enter a positive decimal in the Importance field. The Importance field defines the relative importance of the dynamic resource pool. Note: Importance must be numeric values. Example: 10 <PhysicalMemory>, <MaximumSwap>, and <LockedMemory> — Use these settings to provide limits for the physical, swap, and locked memory usage of the zone. For example, you could specify a maximum swap memory of 256 MB for the zone.You must specify at least one of the memory settings when capping memory for the zone. <IPType> — Set this to one of the following values: shared exclusive If you set this to shared, you can use all three <ZoneNetworkAddress> elements to specify the IP address, the physical device, and (optionally) the default router. For example: <ZoneNetworkAddress> <Physical>eth1</Physical> <Address>192.168.1.1</Address> <DefaultRouter>192.168.1.2</DefaultRouter> </ZoneNetworkAddress> If you set this to exclusive, only the physical device value applies: <ZoneNetworkAddress> <Physical>eth1</Physical> </ZoneNetworkAddress>
<ZoneNetworkAddress>>	<Physical> — If you set IPType to shared, specify both the IP address and the physical device. Optionally, you can also set the default router. For example, Physical = hme0, Address=192.168.0.1, Default Router=10.0.0.1. For information on how to get the Physical value, see To get the Solaris physical value. <Address> — Address should be in the form 0-255.0-255.0-255.0-255 or 0-255.0-255.0-255.0-255 . Example: 10.20.81.146 or 10.20.81.146/10 <DefaultRouter> — If you set IPType to shared, specify both the IP address and the physical device. Optionally, you can also set the default router. For example, Physical = hme0, Address=192.168.0.1, Default Router=10.0.0.1
<ZoneFileSystem>	Adding a file system is optional. <FileSystemDir> — The mount point for the file system. For example, /mnt. <FileSystemSpecial> — Enter the block special device name or directory to mount from the global zone. For example, /dev/dsk/c0t0d0s2. <FileSystemRaw> — Enter the raw device on which to run the file system consistency check command (fsck) before mounting the file system. For example, /dev/rdsk/c0t0d0s2. <FileSystemType> — Set this to one of the following values: ufs zfs <FileSystemOptions> — Enter additional mount options similar to those used with the mount command. For example, nodevices.logging.
<ZoneDataSet>	<DataSetName> — Adding data sets is optional. Adding a ZFS data set resource enables storage administration to be delegated to a non-Global zone. The DataSetName should not start with / and should not contain any spaces. Example: testpool/testzfs.
<ZoneDevice>	<DeviceMatch> — Specify the path to a device to make the device available and dedicated to the zone.For example, /dev/pts. DeviceMatch value should start with '/' and accepts [ , - . ] characters. Example: /dev/prt10-2
<ZoneInheritedPkgDir>	Use this tag to specify a Sparse Root zone type. Omit this tag if you want to use a Whole Root zone type. <PackagePath> — Path to to the inherited package. This is the portion of the global zone's file system for which you want to create a read/write copy.
<ZoneResourceControl>	<ResourceControlName> — Should start with zone. Example: zoneMyResourceControl <ResourceControlValue> — Specify this in the form of: (priv=some privilege,limit=some limit,action=some action Note that these components are comma-separated. Example: (priv=privileged,limit=52428800,action=deny)
<ZoneAttribute>	Adding an attribute is optional. These are generic comments used for user comments or other subsystems. <AttributeName> — Name of the attribute. <AttributeType> — Set this to one of the following types: boolean int uint string <AttributeValue> — Value of the attribute. Example: <ZoneAttribute> <AttributeName>comment</AttributeName> <AttributeType>string</AttributeType> <AttributeValue>Production zone</AttributeValue> </ZoneAttribute>

To get the Global Zone ID - Solaris

Some of the commands you use to get VGP values require you to pass in the ID of the Global Zone.
To do this, use the listVirtualEntityManagers command, and pass in an EntityType argument that specifies the Global Zone - SolarisGlobalZone:

Command	Virtualization listVirtualEntityManagers SolarisGlobalZone
Output format	GlobalZoneID::GlobalZoneName
Output example	1::MyGlobalZone

In this example, the Global Zone ID is 1.

To get the Solaris resource pool name

Get the Global Zone ID, as described in To get the Global Zone ID - Solaris. For the purpose of this example, assume the ID is 1.
Now you can use the listVirtualEntitiesByEntityManagerServerIdAndEntityType command to get the resource pool name. This command takes 2 arguments – ServerId and EntityType. You already have the ServerId (1). Because you want a pool name, you specify SolarisGlobalZoneResourcePool as EntityType:
Command
Virtualization listVirtualEntitiesByEntityManagerServerIdAndEntityType 1 SolarisGlobalZoneResourcePool
Output format
Name
Output example
Pool1 \\
Pool2 \\
Pool3
For example, in the VGP file, you might specify the following:
<ResourcePool>Pool3</ResourcePool>

To get the Solaris physical value

Get the Global Zone ID, as described in To get the global zone ID - Solaris. For the purpose of this example, assume the ID is 1.
Now you can use the listVirtualEntitiesByEntityManagerServerIdAndEntityType command to get the physical value. This command takes 2 arguments – ServerId and EntityType. You already have the ServerId (1). Because you want a physical value, you specify SolarisGlobalZoneNetworkCard as EntityType:
Command
Virtualization listVirtualEntitiesByEntityManagerServerIdAndEntityType 1 SolarisGlobalZoneNetworkCard
Output format
PhysicalValue
Output example
hme0
For example, in the VGP file you might specify the following:
<Physical>hme0</Physical>