The format was created by Connectix for their Virtual PC product, known as Microsoft Virtual PC since Microsoft acquired Connectix in 2003. VHDX was introduced in Windows 8/Windows Server 2012 to add features and flexibility missing in VHD that had become apparent over time.
Since June 2005, Microsoft has made the VHD and VHDX Image Format Specifications available to third parties under the Microsoft Open Specification Promise.[2]
Features
A Virtual Hard Disk allows multiple operating systems to reside on a single host machine. This method enables developers to test software on different operating systems without the cost or hassle of installing a second hard disk or partitioning a single hard disk into multiple volumes. The ability to directly modify a virtual machine's hard disk from a host server supports many applications, including:
Moving files between a VHD and the host file system
Backup and recovery
Antivirus and security
Image management and patching
Disk conversion (physical to virtual, and vice versa)
Life-cycle management and provisioning (re)
VHDX was added in Hyper-V in Windows Server 2012 to add larger storage capacity, data corruption protection, and optimizations to prevent performance degradation on large-sector physical disks.[3]
Supported formats
VHDs are implemented as files that reside on the native host file system. The following types of VHD formats are supported by Microsoft Virtual PC and Virtual Server:
Fixed hard disk image: a file that is allocated to the size of the virtual disk. Fixed VHDs consist of a rawdisk image followed by a VHD footer (512 or formerly 511 bytes).[2]
Dynamic hard disk image: a file that at any given time is as large as the actual data written to it, plus the size of the header and footer. Dynamic and differencing VHDs begin with a copy of the VHD footer (padded to 512 bytes), and for dynamic or differencing VHDs created by Microsoft products this results in a VHD-cookie string conectix at the beginning of the VHD file.[2]
Differencing hard disk image: a set of modified blocks (maintained in a separate file referred to as the "child image") in comparison to a parent image. The Differencing hard disk image format allows the concept of Undo Changes: when enabled, all changes to a hard drive contained within a VHD (the parent image) are stored in a separate file (the child image). Options are available to undo the changes to the VHD, or to merge them permanently into the VHD. Different child images based on the same parent image also allow "cloning" of VHDs; at least the globally unique identifier (GUID) must be different.
Linked to a hard disk (aka pass-through): a file that contains a link to a physical hard drive or partition of a physical hard drive.
Advantages
Significant benefits result from the ability to boot a physical computer from a virtual hard drive:
Ease of deployment: IT organizations can deploy standardized, 'pre-built' configurations on a single VHD. As an example, software engineering organizations that need a specific set of tools for a particular project could simply 'pull' the appropriately-configured VHD from a network location.
Backup-and-Restore: Changes to the contents of a VHD (such as infection by a virus, or accidental deletion of critical files) are easily undone.
Multi-User Isolation: Many current operating systems support having multiple users, but offer varying degrees of protection between them (e.g., one user of the OS could become infected by a virus that infects other users, or make changes to the OS that affect other users). By giving each user their own version of the operating system—say, by creating for each of them a differencing VHD based on a base installation of the OS—changes to any particular child image would have no effect on any of the other child images.
Native VHD Boot
Native VHD Boot refers to the ability of a physical computer to mount and boot from an operating system contained within a VHD. Windows 7 Enterprise and Ultimate editions support this ability, both with and without a host operating system present. Windows Server 2008 R2 is also compatible with this feature.[4][5]
The VHD format has a built-in limitation of just under 2 TiB (2048 GiB) for the size of any dynamic or differencing VHDs.[6][7][8] This is due to a sector offset table that only allows for the maximum of a 32-bit quantity. It is calculated by multiplying 232 by 512 bytes for each sector.
The C×H×S formula in the VHD specification allows a maximum of 65535×16×255 sectors.[2] About 127 GiB is also the limit for VHDs in Windows Virtual PC.[9] For fewer than 65535×16×63 sectors (about 31 GiB) the CHS-value in the VHD footer uses a minimum of H = 4 and a maximum of H = 16 heads with S = 17, 31, or 63 sectors per track. The CHS algorithm then determines C = (T/S)/H.[2] The specification does not discuss cases where the CHS value in the VHD footer does not match the (virtual) CHS geometry in the Master Boot Record of the disk image in the VHD. Microsoft Virtual Server (also Connectix derived) has this limitation using virtual IDE drivers but 2 TiB if virtual RAID or virtual SCSI drivers are used.
The Vista (or later) drive manager GUI supports a subset of the functions in the diskpart command line tool.[12] VHDs known as vdisk in diskpart can be created, formatted, attached (mounted), detached (unmounted), merged (for differencing VHDs), and compacted (for VHDs on an NTFS host file system). Compacting is typically a two step procedure, first unused sectors in the VHD are filled with zeros, and then diskpart can use the NTFS feature of sparse files to eliminate runs of zeros in the VHD[citation needed]. The virtual machine additions in older VPC versions and the virtual machine integration features in Windows Virtual PC contain precompactISO images for the first step in supported guest systems.[13]
It is sometimes useful to modify a VHD file without booting an operating system. Hyper-V features offline VHD manipulation, providing administrators with the ability to securely access files within a VHD without having to instantiate a virtual machine. This provides administrators with granular access to VHDs and the ability to perform some management tasks offline.[16] The Windows Disk Management MMC plugin can directly mount a VHD file as a drive letter in Windows 7/Server 2008 and newer.
For situations where mounting a VHD within the operating system is undesirable, several programs enable software developers to inspect and modify VHD files, including .NET DiscUtils, WinImage, and R1soft Hyper-V VHD Explorer. 7-Zip supports extraction and inspection of VHD files.
Virtual Floppy Disk (VFD)
Virtual Floppy Disk (VFD) is a related file format used by Microsoft Virtual PC, Microsoft Automated Deployment Services and Microsoft Virtual Server 2005.[17][18][19] A VFD that contains an image of a 720 KB low-density, 1.44 MB high-density or 1.68 MB DMF 3.5-inch floppy disk can be mounted by Virtual PC.[17][19][20] Other virtual machine software such as VMWare Workstation and VMware Player can mount raw floppy images in the same way.[21]
Windows Virtual PC for Windows 7 (version 6.1) does not offer a user interface for manipulating virtual floppy disks; however, it still supports physical and virtual floppy disks via scripting.[22] Under Hyper-V, VFD files are usable through the VM settings for Generation 1 virtual machines. Generation 2 virtual machines do not emulate a floppy controller and do not support floppy disk images.
Virtual Hard Disk (VHDX)
VHDX (Virtual Hard Disk v2) is the successor format to VHD. Where VHD has a capacity limit of 2040 GB, VHDX has a capacity limit of 64 TB. For disk images with this newer format the filename extension vhdx is used instead of vhd. VHDX protects against power failures and is used by Hyper-V.[23] VHDX format is optimized for both HDD and SSD.
Convention: Any item in this table that has the form of "A+B" or "A+B+C" indicates a disk format that spans multiple files, where A contains the bulk of the data, and B and C are sidecar files.
