Edit

Share via

Msvm_BasedOn class

  • Article

An association that describes how storage extents can be assembled from lower level extents. For example, ProtectedSpaceExtents are parts of PhysicalExtents, while VolumeSets are assembled from one or more Physical or ProtectedSpaceExtents. As another example, CacheMemory can be defined independently and realized in a PhysicalElement or can be based on Volatile or NonVolatileStorageExtents.

The following syntax is simplified Managed Object Format (MOF) code, and it includes all of the inherited properties.

Syntax

[Association, Dynamic, Provider("VmmsWmiInstanceAndMethodProvider"), AMENDMENT]
class Msvm_BasedOn : CIM_BasedOn
{
  CIM_StorageExtent REF Antecedent;
  CIM_StorageExtent REF Dependent;
  uint64                StartingAddress;
  uint64                EndingAddress;
  uint16                OrderIndex;
};

Members

The Msvm_BasedOn class has these types of members:

Properties

The Msvm_BasedOn class has these properties.

Antecedent

Data type: CIM_StorageExtent

Access type: Read-only

The lower level storage extent. This property is inherited from CIM_BasedOn.

Dependent

Data type: CIM_StorageExtent

Access type: Read-only

The higher level storage extent. This property is inherited from CIM_BasedOn.

EndingAddress

Data type: uint64

Access type: Read-only

The ending address where, in lower level storage, the higher level extent ends. This property is useful when mapping non-contiguous extents into a higher level grouping. This property is inherited from CIM_BasedOn.

OrderIndex

Data type: uint16

Access type: Read-only

If there is an order to the based on associations that describe how a higher level storage extent is assembled, the OrderIndex property indicates this. When an order exists, the instances with the same Dependent value (the same higher level extent) should place unique values in the OrderIndex property. The lowest value implies the first member of the collection of lower level extents, and increasing values imply successive members of the collection. If there is no ordered relationship, a value of zero should be specified. An example of the use of this property is to define a RAID-0 striped array of three disks. The resultant RAID array is a storage extent that is dependent on the storage extents that describe each of the three disks. The OrderIndex of each association from the disk extents to the RAID array could be specified as 1, 2, and 3 to indicate the order in which the disk extents are used to access the RAID data. This property is inherited from CIM_BasedOn.

StartingAddress

Data type: uint64

Access type: Read-only

The starting address where, in lower level storage, the higher level extent begins. This property is inherited from CIM_BasedOn.

Requirements

Requirement Value
Minimum supported client
 Windows 8 [desktop apps only]
Minimum supported server
 Windows Server 2012 [desktop apps only]
Namespace
 Root\Virtualization\V2
MOF
WindowsVirtualization.V2.mof
DLL
Vmms.exe