I was gobsmacked when I learned this week that the new Windows 8/Windows Server 2012 (WS2012) format for virtual disks, VHDX, would have a maximum size of 64 TB. 64 TB! Damn, I was impressed with the Build announcement that it would go out to 16 TB. Even then, it was dwarfing the paltry 2040 GB that vSphere 5.0 VMDK can do. Wow, Hyper-V has vSphere smacked down on storage scalability; isn’t that a shocker!?!?!
Back to the serious side of things … what does this mean? One of the big reasons that people have implemented virtualisation (28.19% – Great Big Hyper-V Survey of 2011) was flexibility. What makes that possible is that virtual machines are normally just files, unbound to their hardware they reside on unlike legacy hardware OS installations and data storage. A limiting factor on that has been the scalability of virtual disks. Both VHD (pre-Windows 8 Hyper-V) and VMDK (all current versions of vSphere) are limited to 2040 GB. The alternative is Raw Device Mapping (vSphere) or Passthrough disk (Hyper-V).
I hate this type of storage. It’s bound to disk because it’s just a raw LUN presented to a VM and therefore it’s a hardware boundary that limits mobility, flexibility, and precludes other things that we can do such as Hyper-V Replica, snapshots, VSS backups of running VMs, etc. Way too often I see people using Passthrough for “performance” reasons (usually with no assessment done and based on pure guesswork) without realising that even VHD has great performance (and I cannot wait for VHDX performance results to be published publicly). The only real reason to use Passthrough disk in my opinion has been to scale a VM’s LUN beyond 2040 GB.
That changes with Windows Server 2012 Hyper-V. I am thinking that Passthrough disk will become one of those things that is theoretical to 99.999999% of us. It’ll be that exam question that no one can answer because they never do it. Think about it: a 64 TB virtual disk that performs near as good as the physical disk it sits on. Wow!
Question: So which virtualisation platform isn’t scalable or enterprise ready? *sniggers* I cannot wait to see the excuses that the competition come up with next.
There are other benefits to the VHDX format:
- “Larger block sizes for dynamic and differencing disks, which allows these disks to attune to the needs of the workload.
- A 4-KB logical sector virtual disk that allows for increased performance when used by applications and workloads that are designed for 4-KB sectors.
- The ability to store custom metadata about the file that the user might want to record, such as operating system version or patches applied.
- Efficiency in representing data (also known as “trim”), which results in smaller file size and allows the underlying physical storage device to reclaim unused space. (Trim requires physical disks directly attached to a virtual machine or SCSI disks, and trim-compatible hardware.)”
There are other things I’d love to share about VHDX, but I’m not sure of their NDA status at the moment so I’ll be sitting on those facts until later. Being an MVP aint easy
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.