VHD (file format)
This article needs additional citations for verification. (March 2010) (Learn how and when to remove this template message)
|Developed by||Connectix / Microsoft|
|Type of format||Virtual machine disk image|
VHD (Virtual Hard Disk) is a file format which represents a virtual hard disk drive (HDD). It may contain what is found on a physical HDD, such as disk partitions and a file system, which in turn can contain files and folders. It is typically used as the hard disk of a virtual machine.
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)
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 raw disk image followed by a VHD footer (512 or formerly 511 bytes).
- 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.
- 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: a file which contains a link to a physical hard drive or partition of a physical hard drive.
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 which 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 which infects other users, or make changes to the OS which 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.
The VHD format has a built-in limitation of just under 2 TiB (2040 GiB) for the size of any dynamic or differencing VHDs. 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. About 127 GiB is also the limit for VHDs in Windows Virtual PC. 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. 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.
Virtual Hard Disk format was initially used only by Microsoft Virtual PC (and Microsoft Virtual Server). Later however, Microsoft used the VHD format in Hyper-V, the hypervisor-based virtualization technology of Windows Server 2008. Microsoft also used the format in Complete PC Backup, a backup software component included with Windows Vista and Windows 7. In addition, Windows 7 and Windows Server 2008 R2 include support for creating, mounting, and booting from VHD files.
The Vista (or later) drive manager GUI supports a subset of the functions in the diskpart command line tool. 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, . The virtual machine additions in older VPC versions and the virtual machine integration features in Windows Virtual PC contain precompact ISO images for the first step in supported guest systems.
Third-party products also use VHD file format. Oracle VirtualBox, part of Sun xVM line of Sun Microsystems supports VHD in versions 2 and later. The VHD file format is also adopted by XenSource for what is now the Citrix XenServer hypervisor.
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. 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. 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. Other virtual machine software such as VMWare Workstation and VMware Player can mount raw floppy images in the same way.
Virtual Hard Disk (VHDX)
VHDX (Virtual Hard Disk v2) is the successor format to VHD. Where VHD has a capacity limit of 2048 GB, VHDX has a capacity limit of 64 TB. VHDX protects against power failures and is used by Hyper-V. VHDX can be mounted like VHD.
- "Virtual Hard Disk Image Format Specification". Microsoft TechNet. Microsoft Corporation. 27 February 2009.
- "Hyper-V Virtual Hard Disk Format Overview". Microsoft TechNet. Microsoft. Retrieved 1 December 2016.
- "Frequently Asked Questions: Virtual Hard Disks in Windows 7 and Windows Server 2008 R2". Microsoft TechNet. Microsoft corporation. 15 October 2010. Retrieved 12 November 2010.
- "Walkthrough: Deploy a Virtual Hard Disk for Native Boot". Microsoft TechNet. Microsoft corporation. 8 July 2010. Retrieved 12 November 2010.
- "Requirements and Limits for Virtual Machines and Hyper-V in Windows Server 2008 R2". Microsoft TechNet. Microsoft Corporation. 2009. Retrieved 12 April 2010.
- "About VHD". MSDN. Microsoft Corporation. 2009. Retrieved 12 April 2010.
- Jain, Ranjana (23 March 2010). "Virtual Hard Disk (VHD) Architecture Explained". Microsoft TechNet Blogs. Microsoft Corporation. Retrieved 13 April 2010.
- "Disk2vhd v1.63". Microsoft SysInternals. 2010. Retrieved 2011-07-14.
- Vanover, Rick. "The anatomy of a Hyper-V 2012 R2 VM: A breakdown of the key files". hyperv.veeam.com. Veeam Software. Retrieved March 5, 2015.
- Koenig, Chris (28 October 2008). "PDC Day 2 – Windows 7, Windows Live, Mesh and Office Online". MSDN Blogs. Microsoft Corporation. Retrieved 17 December 2010.
- "How to make a Virtual Hard Drive in Windows 7" (PDF). 3dhomejoe. Retrieved 22 January 2011.
- "DiskPart". Windows Server 2008 and Windows Server 2008 R2. Microsoft Technet. 2010-10-25. Retrieved 2011-07-15.
- "Modify a virtual hard disk". Windows 7 Technical Library. Microsoft Technet. 2009-06-25. Retrieved 2011-07-15.
- "Windows Server 2008 Reviewers Guide". Microsoft. 4 February 2008.
- "How to create a floppy disk image in Virtual PC for Windows versions 4.0 to 5.2". Microsoft Support. Microsoft Corporation. Retrieved 26 June 2011.
- "Virtual floppy disk overview". ADS Administrator's Guide. Microsoft Corporation. Retrieved 26 June 2011.
- "Creating virtual floppy disks in Virtual Server". TechNet Library. Microsoft Corporation. Retrieved 26 June 2011.
- Armstrong, Ben (2007-01-05). "Floppy disk image formats supported by Virtual PC and Virtual Server". Virtual PC Guy's Blog. Microsoft Corporation. Retrieved 2011-07-03.
- "Virtual Floppy Disks with VMware". Petri.co.il. 2009-01-08. Retrieved 2011-12-10.
- Armstrong, Ben (1 October 2009). "Using Floppy Disks with Windows Virtual PC". Virtual PC Guy's Blog. Microsoft Corporation. Retrieved 26 June 2011.