Thin provisioning physical layer vs VHDX

so i'm creating new host server 2012 core , i'm going run server 2012 essentials on vm.  i'm trying decide disks.

i have created 2tb volume on physical layer thin provisioned using storage spaces , create 1.5tb vhd essentials main disk if create fixed volume use full 1.5tb of physical volume?  if so, what's point of thin provisioning @ physical layer virtualized workloads?

if used thin provisoning @ virtual layer pay performance penalty twice?  once vhdx file , again @ physical layer?

any recommendations on how set make efficient use of disk space here?

so i'm creating new host server 2012 core , i'm going run server 2012 essentials on vm.  i'm trying decide disks.

i have created 2tb volume on physical layer thin provisioned using storage spaces , create 1.5tb vhd essentials main disk if create fixed volume use full 1.5tb of physical volume?  if so, what's point of thin provisioning @ physical layer virtualized workloads?

if used thin provisoning @ virtual layer pay performance penalty twice?  once vhdx file , again @ physical layer?

any recommendations on how set make efficient use of disk space here?

if storage thin provisioning stick fixed size vhdx. it's faster , you're going make san/nas life easier less fragmentation. 

---

starwind iscsi san & nas

Windows Server  >  Hyper-V