No – the vault drives cannot be used in a pool due to different free capacity

I assume you meant block pool and not file pool (AVM)

Rainer_EMC, yes, I meant block storage pool or traditional RAID group. So these drives are completeley unusable in terms of block storage array and during solution sizing procedures we shouldn't take them into account? I will really appreceate if you provide links to documentation that contains information related to this question. Thank you!

You can use the remainder of these drive with traditional raidgroups

You just cannot use them to add to a block pool – a block pool needs complete disks

boot LUNs for ESX servers should be just fine, everything gets loaded into ESX memory so there is very little I/O.

Rainer_EMC, thank you for the information! In case if I want to use these drives I will create Traditional RAID Group RAID5 (4+1) with adding one additional drive.

dynamox, I just want to create LUNs for operating systems of virtualization servers (Boot from SAN).

do not put anything very i/o intensive on those LUNs, might impact array's overall performance.

Actually I'm planing to use Windows Server 2008 R2 with a Hyper-V role. But I don't think that there is any significant difference in I/O behaviour of these two systems.

so you were planning on putting the root partition on these LUNs and child partitions would reside in the pool ? I remember there used to be a white paper that helps with Hyper-V and VNX architecture, i can't find it now.