Hyper-V pass-through disk support limitations

SnapDrive supports Hyper-V pass-through disks; however, there are some limitations related to this feature.

SnapDrive does not support direct attached storage to a Hyper-V parent host.
Only Data ONTAP iSCSI and FC LUNs are supported.
SnapDrive does not support LUNs already mapped to a Hyper-V parent host.
A pass-through disk must be freshly provisioned from a storage system to be added dynamically.
Windows 2008 R2 does not support pass-through disks using IDE.
Windows 2008 R2 supports only SCSI disks.
Micorosoft cluster shared volume (CSV) disks are not supported.
Hyper-V does not support the SnapDrive space reclaimer feature.
Pass-through LUN creation fails when Data ONTAP DSM is installed on Hyper-V virtual machines.
Note: Removing MPIO will not remove MPIO iSCSI sessions that SnapDrive might have been using. After removing MPIO, you must remove existing iSCSI sessions and, if needed, create new iSCSI sessions.
Due to a Microsoft limitation, if a pass-through disk is down, the virtual machine to which the disk is assigned cannot be rebooted.
To reboot the virtual machine, you must bring the pass-through disk back up, or remove it from the virtual machine using Microsoft Hyper-V Manager or another Microsoft remote server management tool.
If DataFabric Manager role-based access control is enabled on a SnapDrive for Windows Hyper-V parent host, you cannot dynamically add or remove pass-through disks with SnapDrive in a Hyper-V virtual machine.
Windows Server 2008 Server Core does not support the ability to dynamically add and remove Hyper-V pass-through disks because Server Core does not support Windows Communication Foundation (WCF) Web services that are required to dynamically add and remove pass-through disks.