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

Section 3.4.5.2.38.3: Windows does not implement the IVdsVDisk::GetHostVolumemethod. Section 3.4.5.2.39.1: Windows uses a string in the Security Descriptor Definition Language(SDDL) format. Section 3.4.5.2.39.1: For the Microsoft virtual disk provider, this parameter must be 0 or 1.If the parameter is 1, the pStringSecurityDescriptor parameter MUST be NULL. Section 3.4.5.2.39.1: In Windows, TimeoutInMs is not used. Section 3.4.5.2.39.2: For the Microsoft provider, this must be 0. Section 3.4.5.2.39.3: For the Microsoft provider, this must be 0. Section 3.4.5.2.39.5: In Windows, once the merge operation completes, the given virtualdisk is still usable but, once the blocks in the differencing disk have been merged into its parent, thelist of changed blocks stored in the differencing disk are duplicates of the same blocks in the parent.It is for this reason that: (1) It is recommended that the given virtual disk be deleted because it isno longer necessary and continuing to use the given disk will waste space; by definition, adifferencing virtual disk should consist of only the set of blocks that differ from blocks in the parentvirtual disk. (2) If a merge operation fails to complete, then the given differencing disk and itschildren are still valid. (3) Because it is recommended that the given virtual disk be deleted, anydifferencing virtual disks using the given virtual disk as a parent will become invalid as a result ofdeleting the given virtual disk.Also note that once the merge operation has commenced, any other virtual disks using the givendisk's parent as a parent become invalid. These disks will fail all operations. The reason for this isthat any other virtual disks using the given virtual disk's parent as a parent may have change blocksthat conflict with blocks merged into the parent.To illustrate the above: Given diskA, its parent is diskB, diskB's parent is diskC, and diskX, whichalso uses diskC as its parent, then once a merge of diskB into diskC is started (some number ofblocks have been copied from diskB to diskC), diskX becomes invalid. Section 3.4.5.2.39.5: For the Microsoft virtual disk provider, the disk MUST have beenopened with a ReadWriteDepth at least equal to this value. Section 3.4.5.2.39.6: In Windows, the expand operation invalidates a virtual diskdifferencing chain. Section 3.4.7: Windows Virtual Disk Service Remote Protocol servers use the Plug and Playsubsystem to register with the operating system to receive notifications of changes to the storagedevice. Section 3.4.7: When the sequence in the behavior log entry shown here is executedrepeatedly in a program (say, 200 times) on Windows Server 2008, the client will occasionallyencounter the error "0x800706BE". This error mainly comes at AddDisk and sometimes on Wait.However, on the server, the following entry is recorded in the event log: "====Faulting applicationvds.exe, version 6.0.6001.18000, time stamp 0x479198cb, faulting module ntdll.dll, version6.0.6001.18000, time stamp 0x4791adec, exception code 0xc0000005, fault offset0x000000000001f7fa, process id 0xda4, application start time 0x01c967e37ddea470.====-QueryUnallocatedDisks- CreatePack- AddDisk- Clean- Wait (for clean to complete)"[MS-VDS] — v20110610Virtual Disk Service (VDS) Protocol SpecificationCopyright © 2011 Microsoft Corporation.Release: Friday, June 10, 2011350 / 360