[MS-VDS]: Virtual Disk Service (VDS) Protocol Specification

•diskId is the VDS_OBJECT_ID of the disk object that was added.•ullOffset is the byte offset at which the partition starts on the disk.Finally, for each volume on the disk, for each callback object that is registered in the list of callbackobjects, the server MUST call the callback object's IVdsAdviseSink::OnNotify method with aVDS_NOTIFICATION structure that has the following attributes:•objectType member is VDS_NTT_VOLUME.•Volume member is a VDS_VOLUME_NOTIFICATION that has the following attributes:•ulEvent is VDS_NF_VOLUME_ARRIVE.•volumeId is the VDS_OBJECT_ID of the volume object.•plexId SHOULD be GUID_NULL, but it is not relevant when ulEvent isVDS_NF_VOLUME_ARRIVE.•ulPercentCompleted needs to be in the range from 0-100 and is implementation-specific;however, it is not relevant when ulEvent is VDS_NF_VOLUME_ARRIVE.Dynamic Disk: If the disk is a dynamic disk, the server MUST create a corresponding disk object andMUST assign it a unique VDS_OBJECT_ID. The server MUST set the disk object's pack pointer tothe pack object that corresponds to the pack that the disk belongs to.Note that for dynamic disks, pack object creation occurs separately from disk object creation. Thisbehavior is different from basic disks, where pack objects are created when the disk object iscreated, because on basic providers, packs can have only one disk. For information on pack objectcreation for dynamic disk packs, see section 3.4.5.1.1.The server MUST add the disk object to the list of storage management objects. Then, for eachcallback object that is registered in the list of callback objects, the server MUST call the callbackobject's IVdsAdviseSink::OnNotify method with a VDS_NOTIFICATION structure that has thefollowing attributes:•objectType member is VDS_NTT_DISK.•Disk member is a VDS_DISK_NOTIFICATION that has the following attributes:•ulEvent is VDS_NF_DISK_ARRIVE.•diskId is the VDS_OBJECT_ID of the disk object that was added.Unallocated Disk: If the disk is an unallocated disk, the server MUST create a corresponding diskobject and MUST assign it a unique VDS_OBJECT_ID. The server MUST add the disk object to thelist of storage management objects. Then, for each callback object that is registered in the list ofcallback objects, the server MUST call the callback object's IVdsAdviseSink::OnNotify methodwith a VDS_NOTIFICATION structure that has the following attributes:•objectType member is VDS_NTT_DISK.•Disk member is a VDS_DISK_NOTIFICATION that has the following attributes:•ulEvent is VDS_NF_DISK_ARRIVE.•diskId is the VDS_OBJECT_ID of the disk object that was added.[MS-VDS] — v20110610Virtual Disk Service (VDS) Protocol SpecificationCopyright © 2011 Microsoft Corporation.Release: Friday, June 10, 2011163 / 360